smartcrowd.ae
success
Claude Code
intent

What does smartcrowd.ae do and who is it for? Explain it back to me.

8steps
39.4sduration
$0.0641cost
53,844tokens
13 steps5 reasoning steps1 search
home
/how-it-works
docs
/faq
search
/smartcrowd-investment…
/en/articles/7990467-w…
docs
71%
on-site discovery
57%
reliability
43%
link following
path origin
  • previous resource43%
  • web search29%
  • prior knowledge29%
insight

The agent successfully assembled a comprehensive explanation of SmartCrowd by combining homepage content (step 1), a 'How It Works' page (step 3), and fee/pricing details from a dedicated fees page (step 10) and help center article (step 11). The site's navigation was moderately poor—key pages like /pricing and /faq returned 404 errors, forcing the agent to discover pricing information via web search rather than site structure. The agent delivered a complete, well-sourced answer despite fragmented information architecture.

  • ›Step 1 (homepage) provided foundational positioning: regulated MENA platform, fractional real estate investing from AED 500. Step 3 (how-it-works) corroborated the core concept but did not add unique details beyond what the homepage conveyed.
  • ›Pricing information was completely absent from intuitive URLs (/pricing returned 404 in step 4). The agent discovered pricing via web search (step 8), which surfaced a dedicated fees page (step 10) and help center article (step 11). Both returned 200s and contained explicit fee tiers (1.5% entry, 0.5% annual, 2.5% exit). The site does NOT surface pricing on its main navigation; it requires external search or direct knowledge of the /smartcrowd-investment-fees-and-costs URL.
  • ›Site's agent-readiness is mixed: homepage and some content pages load cleanly, but key pages (FAQ, pricing, about) are either missing or fragmented across a separate help center domain. The agent had to resort to web search to answer the core 'how it's priced' question, indicating poor internal content architecture. No structured data (JSON-LD pricing, FAQ schema) was extracted from the HTML responses to reduce friction.
  • ›The agent explicitly called out missing information: no detailed return percentages, unclear holding periods, vague process flow. These gaps were due to content not being present on accessible pages, not agent failure—the site simply does not publish this detail on public-facing pages the agent could reach.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →