surprise2go.com
success
Claude Code
intent
What does surprise2go.com do and who is it for? Explain it back to me.
9steps
45.9sduration
$0.3521cost
85,261tokens
13 steps4 reasoning steps2 searches
home
docs
docs
/services
search
/product/tray-for-2
/product/sweetheart-box
search
/menu
57%
on-site discovery
57%
reliability
43%
link following
path origin
- previous resource43%
- web search43%
- prior knowledge14%
insight
The agent successfully assembled a coherent overview of Surprise2Go by combining fragments from product pages and the menu page, but worked around a largely non-functional website — multiple standard navigation pages returned 404s, forcing reliance on web search and direct product URLs to piece together what the business does. The site's information architecture is broken, but individual product and category pages do contain enough content (pricing, imagery, product descriptions) to answer the core questions.
- ›Step [1] (homepage) returned HTML but was truncated and incomplete in the response; the agent could not extract actionable detail from it. Steps [7], [8], and [11] (individual product pages) were the actual content sources, each returning full product pages with pricing, descriptions, and images that informed the final answer.
- ›The site does not publish an /about, /pricing, or /services page (all returned 404 in steps [2], [3], [4]), forcing the agent to infer business model, pricing range, and differentiators from scattered product listings rather than from dedicated explanatory content. The agent relied on web search (steps [6], [10]) to discover which URLs were accessible — discovery was not organic navigation.
- ›Individual product pages (steps [7], [8]) do include pricing and thematic information (e.g., 'Sweetheart Bloom Box'), allowing the agent to infer the gift-experience positioning. However, no page explicitly states service area, ordering lead time, customization policy, or competitive differentiation. The agent had to synthesize positioning from product names and category structure, relying partially on prior knowledge and Yelp data referenced in the search results.
- ›The /menu page (step [11]) exists but is described as a product listing rather than a traditional menu, adding confusion rather than clarity. The site lacks basic information architecture (no FAQ, no About, no explicit Pricing page) that would have made the task trivial for both humans and agents.
Help the next agent finish on surprise2go.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 →