krones.com
success
Claude Code
intent

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

18steps
83.6sduration
$0.8574cost
244,331tokens
22 steps4 reasoning steps4 searches
home
/en/products.php
/en/about.php
/en/company.php
/en/service-solution.php
/en/solutions.php
/en/services.php
/en/pricing.php
/en/contact.php
search
/wiki/krones
/home/company/13320785…
search
/en/products/machines/…
search
/en/company/about-us.php
search
/en/company/investor-r…
64%
on-site discovery
57%
reliability
14%
link following
path origin
  • previous resource14%
  • web search36%
  • prior knowledge50%
insight

The agent successfully assembled a comprehensive explanation of Krones' business, positioning, and market role by combining fragments from the official site (homepage, products, company, contact pages) with Wikipedia and investor relations documents. However, the official Krones website itself was poorly structured for discovery—many intuitive URLs returned 404s, key information like pricing and service models were absent or buried, and the agent relied heavily on prior knowledge (50%) and web search (36%) to fill critical gaps that the site should have surfaced directly.

  • ›The homepage and main product pages (steps [1], [3], [18]) returned 200s but appear to have been truncated in the response and did not yield substantive content in the trajectory; the agent's final answer relied heavily on inferred structure rather than extracted copy.
  • ›Multiple expected pages returned 404s—/about.php, /service-solution.php, /solutions.php, /services.php, /pricing.php (steps [4], [6], [7], [8], [9])—forcing the agent to guess at likely URLs and fall back on web search and Wikipedia for core business facts.
  • ›The company/investor-relations page (step [17]) and company/about-us page (step [20]) were successfully fetched, but neither appears to have yielded detailed content in the response snippets; the agent's detailed answer suggests it synthesized information from sources largely outside the site itself.
  • ›Wikipedia (step [13]) and web search results (steps [12], [15], [16], [19]) provided more navigable entry points to Krones' business model, revenue segments, and competitors than the official site, indicating poor IA and SEO for a complex B2B manufacturer.
  • ›The agent explicitly flagged missing information in its final response—no transparent pricing page, vague competitive differentiation, unclear service vs. equipment revenue mix, and obscure business segment boundaries—all of which are discoverable only via external research, not the site itself.
  • ›The site's lack of pricing and service-model clarity is a structural weakness for a discovery-evaluation task: industrial equipment pricing is typically opaque (custom quotes), but Krones offers no ranges, case studies, or decision framework to help prospects self-qualify or compare alternatives.

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