nasdaq.com
success
Claude Code
intent

What does nasdaq.com do and who is it for? Explain it back to me.

18steps
92.0sduration
$1.0892cost
228,919tokens
20 steps2 reasoning steps7 searches
home
docs
/solutions
/products
search
search
search
/market-data
search
/trading
/indices
search
docs
ir.home
search
/careers
search
docs
100%
on-site discovery
55%
reliability
45%
link following
path origin
  • previous resource45%
  • prior knowledge45%
  • other9%
insight

The agent successfully assembled a comprehensive explanation of Nasdaq's business, target customers, and competitive positioning, but had to work around a largely inaccessible corporate website. Direct fetches of the main domain returned truncated HTML that did not yield actionable content; the agent relied instead on web search results, investor relations pages, and prior knowledge to construct the answer. The site's fragmented structure (multiple 404s on expected paths like /pricing, /trading, /market-data) forced heavy reliance on external sources rather than first-party information.

  • ›Steps [7], [11], [13], [15], [16], [17] — all web searches — were the primary content sources for the final answer. Search result snippets and linked articles (PortersFiveForce, Wikipedia, ad-hoc-news, SEC filings, comparison sites) provided the core business model, revenue segments, and competitive differentiation. The agent never extracted this information from nasdaq.com itself.
  • ›Direct fetches to nasdaq.com ([1], [2], [3], [14]) returned HTML that was truncated and not parseable for content; no text was visible enough to extract the actual business description, pricing, or service offerings. The responses show only boilerplate HTML head sections, suggesting the pages are heavily JavaScript-rendered and not agent-readable without JavaScript execution.
  • ›The agent attempted common URL patterns (/about, /solutions, /pricing, /market-data, /trading, /indices, /news) based on prior knowledge and standard site structure. Most returned 404s ([4], [5], [6], [8], [18]), indicating either poor site structure or content reorganization. /solutions and /products resolved but returned no usable HTML content.
  • ›Step [9] — fetching ir.nasdaq.com (investor relations) — succeeded with 200 and was cited in sources, but the HTML excerpt shown is also truncated and non-content-bearing. The agent cited investor relations as a source but did not extract specific information from the fetched HTML.
  • ›The agent's final answer acknowledges multiple gaps: no transparent consumer pricing published, unclear subsidiary relationships, fragmented website structure, and confusion about consumer vs. enterprise focus. These are all observations the agent had to infer from the *absence* of information rather than information the site provided.
  • ›The agent explicitly called out that expected pages were missing or broken ('Many expected pages (pricing, specific product pages) returned 404 errors'), which directly affected task completion quality. This is a strong signal of poor site navigability for agent discovery.

Help the next agent finish on nasdaq.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →