brunarossa.com
success
Claude Code
intent
What does brunarossa.com do and who is it for? Explain it back to me.
13steps
104.2sduration
$0.3538cost
88,866tokens
17 steps4 reasoning steps1 search
home
docs
/menu
/menus
docs
/how-it-works
home
/services
/faq
/contact
search
docs
/our-services
83%
on-site discovery
42%
reliability
50%
link following
path origin
- previous resource50%
- web search17%
- prior knowledge33%
insight
The agent successfully assembled a comprehensive overview of Bruna Rossa's business model, target audience, and differentiation by combining homepage metadata, menu/services pages, and the about page—but had to work around a deliberately opaque pricing model and several broken/timeout-prone pages. The site is moderately navigable for discovery but deliberately obscures critical information like pricing and booking details, requiring direct contact.
- ›Step [1] (homepage) provided foundational metadata via title tags and meta descriptions identifying the service as 'gourmet pizza catering' and geographic coverage. This was the initial north star.
- ›Steps [14] (about) and [15] (our-services) became accessible only after a web search surfaced them; direct navigation attempts (step [4]) timed out. These pages contained the core narrative: founders' names, the experiential pitch, and event types served.
- ›Step [3] (menu) and [6] (menus) returned 200 responses but the agent could not extract specific menu items, prices, or detailed descriptions from the truncated HTML—the content existed but was not machine-readable in the fragments captured.
- ›The agent had to explicitly call out that /pricing (step [2]), /contact (step [11]), /faq (step [10]), and /how-it-works (step [7]) all return 404 errors, forcing reliance on inferring the quote-based pricing model from the about page language and contact information.
- ›The site does not publish pricing, booking process, or package details in a discoverable, structured form—this is intentional design (high-touch, custom-quote model) but creates friction for agent-driven evaluation.
- ›50% of fetches came from prior knowledge / direct URL guessing, and 17% required web search to find working URLs, indicating the site's navigation is incomplete or non-obvious even with common conventions.
See every agent that visits brunarossa.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 →