liesl.ch
success
Claude Code
intent

What does liesl.ch do and who is it for? Explain it back to me.

6steps
32.4sduration
$0.3223cost
14,083tokens
8 steps2 reasoning steps
home
/en/how-it-works
/en/pricing
home
home
/en/about
80%
answer from your site
50%
answer efficiency
80%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task17%
  • followed a link67%
  • guessed the URL17%
insight

Agent successfully extracted core information about Liesl's service, pricing, and differentiation from the homepage alone, but the site's navigational structure was fragile—expected subpages (pricing, about, how-it-works) returned 404s, forcing reliance on homepage content that the agent had to re-fetch multiple times to surface different sections.

  • ›Homepage was the only accessible content source; three explicit navigation attempts (/en/pricing, /en/how-it-works, /en/about) all returned 404, indicating either a routing issue or that the site relies entirely on single-page app content without stable subpage URLs.
  • ›Agent re-fetched the homepage (steps [1], [5], [6]) as 'URL typed from memory' to extract different details, suggesting the initial response was truncated or the agent needed to prompt the model to surface different sections of the same content—a sign the homepage itself is information-rich but not well-structured for machine parsing.
  • ›All substantive claims (training academy, GPS tracking, Liesl Guarantee, pricing examples, founder attribution) came directly from the homepage; no secondary pages or external sources were consulted, leaving gaps in competitive positioning and nationwide availability that the agent noted but could not resolve.
  • ›Pricing information was present but fragmented across sitter examples (CHF 15, CHF 22.90, CHF 45) with no centralized price list or fee structure for the platform itself, forcing the agent to infer the pay-per-service model rather than read it explicitly stated.
  • ›The site's routing or internal linking appears unreliable for agent navigation—the agent guessed standard URL paths and they failed, but the homepage fetches succeeded, indicating the site may be a single-page app without proper subpage routing or sitemaps for machine traversal.

See every agent that visits liesl.ch

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 →