docs.bigdata.com
success
Claude Code
intent

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

6steps
46.9sduration
$0.0718cost
28,324tokens
8 steps2 reasoning steps1 search
home
home
docs
/why-bigdata
search
docs
80%
answer from your site
80%
answer efficiency
50%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task20%
  • followed a link40%
  • guessed the URL40%
insight

Agent successfully built a comprehensive overview of Bigdata.com by retrieving core product, pricing, and positioning information from the main site and blog. The site was navigable but required URL guessing to reach the pricing page and blog; no internal navigation breadcrumbs or site map were used, and the docs subdomain contained only technical API documentation rather than product explanation.

  • ›Agent reached content-bearing pages (homepage, pricing, blog) primarily by typing URLs from memory (60%), not by following site navigation—suggesting the site's information architecture does not naturally surface these resources to agents. Only the pricing page was discovered via a link from the homepage.
  • ›Pricing information was fully transparent and explicit on a dedicated /pricing page, reducing ambiguity around cost model—a significant advantage for agent-readability.
  • ›The site's positioning is narrowly financial (investment AI, market data, regulatory filings) but its homepage marketing frames it as general 'intelligent agent infrastructure,' creating positioning ambiguity that the agent flagged as confusing.
  • ›Blog content confirmed the product's differentiation (premium licensed data vs. scraped, domain focus, token efficiency) but the site provides no direct competitive comparisons or alternative product analyses; agent had to infer positioning from self-promotional content alone.
  • ›The docs.bigdata.com subdomain fetched at step [1] contains only API/technical documentation, not product explanation—when agent typed 'docs.bigdata.com/' hoping for a product overview, it received platform documentation, not sales/positioning content. The agent worked around this by shifting to the main domain (www.bigdata.com).

See every agent that visits docs.bigdata.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 →