gutlings.be
success
Claude Code
intent

What does gutlings.be do and who is it for? Explain it back to me.

6steps
27.1sduration
$0.2478cost
52,747tokens
9 steps3 reasoning steps1 search
home
/pages/about
home
search
/products/ginger-peach
/collections/all
60%
on-site discovery
100%
reliability
40%
link following
path origin
  • previous resource40%
  • web search40%
  • prior knowledge20%
insight

The agent assembled a coherent overview of Gutlings' business model, positioning, and product range despite severe truncation of fetched HTML pages. The site's Shopify structure was navigable enough to identify product URLs and pricing, but the actual page content—critical for explaining brand mission, full product range, and differentiators—was never successfully delivered to the agent. The agent compensated by inferring positioning from product names (prebiotic sodas, flavor combinations) and relying on prior knowledge and search result titles rather than page body content.

  • ›Every HTML fetch returned truncated responses (4400+ chars cut off), meaning the agent never received complete About page text, product descriptions, or marketing copy—only head metadata and truncated body snippets. Despite this, the agent correctly identified Gutlings as a Belgian prebiotic soda maker and inferred the gut-health positioning from product naming conventions (e.g., 'Peach & Ginger').
  • ›The agent located pricing ($23.88 per 12-pack) from product URLs it discovered via web search results, not from successfully parsing product pages. Search result titles (e.g., 'Peach & Ginger (12x33CL)') became the primary source for product names and pack size; the agent did not extract this from rendered product pages.
  • ›The site's agent-readiness was poor: Shopify boilerplate loaded but page content did not. No structured data (JSON-LD, microdata) was visible in the truncated responses. The agent had to guess that 'Gutlings' = gut health + beverage and that 'prebiotic' was the differentiator based on the brand name itself, not explicit positioning from the site. The About page story (founder 'Julie') and full mission were explicitly cited in the final response but never actually retrieved—this came from prior knowledge or search snippet context, not the fetched page.
  • ›The agent correctly flagged what it could not confirm: full product catalog, B2B/subscription models, geographic reach, and complete brand narrative. These gaps reflect genuine truncation and incomplete site exploration, not agent error. The site structure (collections, products, pages folders) was guessable and the agent's navigation strategy was sound; the content delivery failure was technical, not architectural.

Help the next agent finish on gutlings.be

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 →