hellofresh.com
success
Claude Code
intent

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

13steps
69.9sduration
$0.6874cost
166,694tokens
18 steps5 reasoning steps3 searches
home
/how-it-works
/plans
/meal-plans
search
/finance/learn/how-muc…
/articles/how-hellofre…
search
search
docs
docs
docs
/faq
80%
on-site discovery
40%
reliability
40%
link following
path origin
  • previous resource40%
  • web search20%
  • prior knowledge30%
  • other10%
insight

The agent assembled a comprehensive explanation of HelloFresh's business model, pricing, target audience, and competitive positioning—but had to rely heavily on external sources because the HelloFresh.com website itself returned only truncated HTML with no readable content. Steps [1], [2], [3] fetched the homepage and key pages but returned no usable text; multiple direct URL guesses ([5], [6], [8], [9], [10]) returned 404s or truncated boilerplate. The agent pivoted to web search ([12], [15], [16]), which surfaced third-party reviews and comparison articles that contained the pricing details, audience demographics, and competitive differentiation the final answer required. The site is poorly navigable for agents due to client-side rendering and lack of accessible structured data.

  • ›Steps [1], [2], [3] successfully fetched the homepage and /how-it-works and /plans pages, but all responses were truncated HTML boilerplate with no readable body text—likely due to heavy JavaScript client-side rendering that the agent's HTML fetcher could not execute.
  • ›The agent's direct URL guesses for common pages (/pricing, /about, /faq, /meal-plans) all returned 404s, forcing exploration away from the site entirely.
  • ›All substantive information in the final answer came from external sources: NerdWallet (step [13]) provided pricing breakdowns; web search results (steps [12], [15], [16]) surfaced third-party comparisons with competitors (EveryPlate, Green Chef, Factor) and audience demographic reports. The agent cited four external URLs in its sources section and zero content from hellofresh.com itself.
  • ›The agent filled significant knowledge gaps using prior knowledge (30% per metadata) and web search (20%), but could not extract that information directly from the domain being analyzed—a fundamental accessibility problem.
  • ›The final answer acknowledges several items the agent 'couldn't clearly find': exact meal combinations, detailed menu variety, cancellation policies, shipping costs, and international availability—all of which should be discoverable on a meal kit service homepage but were inaccessible.

Help the next agent finish on hellofresh.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 →