bergsonne-allgaeu.de
success
Claude Code
intent

What does bergsonne-allgaeu.de do and who is it for? Explain it back to me.

5steps
32.1sduration
$0.2886cost
38,667tokens
9 steps4 reasoning steps1 search
home
/buchen
/en
llms.txt
search
100%
on-site discovery
100%
reliability
75%
link following
path origin
  • previous resource75%
  • prior knowledge25%
insight

The agent successfully understood the hotel's core positioning, target audience, pricing, and differentiators by fetching the homepage and the llms.txt artifact. The site publishes its key message in machine-readable form via llms.txt, making it agent-ready for discovery and positioning tasks; however, the HTML homepage itself is React-rendered with minimal static content, forcing reliance on the structured llms.txt file and external OTA sites (Hotels.com, TripAdvisor) to assemble a complete picture. The agent identified genuine friction points (AI-only check-in confusion, room type abbreviations unexplained, care room access unclear) that reflect gaps in the site's own documentation.

  • ›Step [6] (llms.txt) was the single most valuable content source — it explicitly answered what the hotel does ('Smart Retreat'), who it's for (digital nomads, solo travelers, mobility-impaired guests), pricing (€55–100/person), and key differentiators (no reception, AI concierge, sustainability focus). This file was machine-readable and well-structured.
  • ›Step [1] (homepage HTML) returned only a React shell with minimal static content — the actual page content is rendered client-side, making it difficult for a crawler to extract marketing copy, room details, or pricing without executing JavaScript. The agent relied on prior knowledge (75% of fetch sources) to fill gaps.
  • ›The agent correctly identified that the site does NOT clearly explain: (a) the step-by-step check-in workflow despite it being the core differentiator, (b) what each room type abbreviation means, (c) Lio's actual capabilities and failure modes, (d) seasonal variation in pricing/activities, and (e) how to access the care room. These gaps are real friction points for both humans and agents.
  • ›External OTA sites (Hotels.com, TripAdvisor, Expedia) were cited as sources but not fetched during this run — the agent's final answer leaned heavily on the llms.txt artifact and the homepage structure, demonstrating that the hotel's own published content (llms.txt) was sufficient to answer the task without external disambiguation.
  • ›The site's llms.txt artifact indicates deliberate agent-readiness and a likely audience of AI systems, positioning it ahead of typical hotel sites; however, the core HTML remains client-rendered, suggesting the hotel understands LLM audiences better than general web crawlers.

See every agent that visits bergsonne-allgaeu.de

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 →