bigbus.com
success
Claude Code
intent
What does bigbus.com do and who is it for? Explain it back to me.
6steps
50.7sduration
$0.4587cost
28,206tokens
8 steps2 reasoning steps2 searches
home
home
home
/en/london
search
search
50%
answer from your site
50%
answer efficiency
100%
followed site links
answer sources
- from this site50%
- from search results33%
- from agent knowledge17%
url discovery
- followed a link75%
- guessed the URL25%
insight
The agent successfully gathered enough information to explain Big Bus Tours' core offering, pricing model, and market positioning, though the site itself offered limited comparative differentiation details and pricing was scattered across city-specific pages rather than centralized. The agent synthesized site content with search results to produce a coherent business overview.
- ›Step [2] was the primary source for what Big Bus Tours *is* and *does* — the homepage delivered clear positioning as a hop-on hop-off operator with 30+ years, 25+ cities, and expanded offerings. This information was directly fetchable and clearly laid out.
- ›Step [4] (London city page) was the only source for concrete pricing; the homepage contained no pricing data at all, forcing the agent to navigate to a specific city page to fulfill that part of the task. Pricing appears city-specific but not indexed centrally.
- ›Steps [5] and [6] (search results) provided almost all competitive differentiation and market-positioning claims ('largest operator', 444 buses, 18 countries, pioneered hop-on hop-off model). This information was not available on the bigbustours.com site itself and had to be sourced from Wikipedia, Viator listings, and other third parties.
- ›The domain redirect (bigbus.com → bigbustours.com) was a routing-only step [1] but reflects poor discoverability for users trying to guess the domain.
- ›The agent correctly identified that the site does not compare itself to competitors or articulate why users should choose Big Bus over alternatives—a critical gap for evaluation tasks. This is agent-inferred absence, not model memory, based on fetches that succeeded but contained no comparative content.
See every agent that visits bigbus.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 →