swhl.de
success
Claude Code
intent
What does swhl.de do and who is it for? Explain it back to me.
11steps
50.7sduration
$0.7874cost
75,577tokens
17 steps6 reasoning steps5 searches
home
search
/de/ueber-uns
/de/produkte-services
/de/energie
/de/internet
/de/mobil
search
search
search
search
100%
on-site discovery
100%
reliability
50%
link following
path origin
- previous resource50%
- prior knowledge50%
insight
The agent successfully assembled a comprehensive explanation of Stadtwerke Lübeck by working around the site's client-side rendering limitation. Unable to directly access swhl.de's HTML content, the agent relied entirely on web search results and prior knowledge to build an answer covering what the company does, its target audience, pricing, and competitive positioning. The site itself was not machine-readable to the agent, forcing a heavy dependence on third-party sources and search snippets.
- ›Steps [1], [4], [5], [7], [8], [9] all returned identical truncated HTML skeletons due to Nuxt client-side rendering—none contained actual page content, making direct site navigation ineffective.
- ›All factual content in the final answer came from web search results (steps [11], [12], [14], [15]), which surfaced news articles, pricing aggregator sites, competitor databases, and Wikipedia. The site did not expose this information in a machine-readable form.
- ›Pricing details (€31.94/kWh electricity, €11.41/kWh gas, €29.95/month fiber) came from search snippet [11] citing a news article and energiemarie.de aggregator, not from swhl.de directly.
- ›The agent explicitly cited all four search result steps as sources, indicating these were the only sources that contained actionable content; the direct site fetches contributed nothing to the answer despite being attempted.
- ›The site's lack of structured data (schema markup), server-side rendering, or plain-text content summaries meant an agent could not independently learn about the company without external search—poor agent-readiness for discovery and identity evaluation.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →