lavendelcatering.de
partial
Claude Code
intent
What does lavendelcatering.de do and who is it for? Explain it back to me.
19steps
88.7sduration
$1.0805cost
316,896tokens
29 steps10 reasoning steps5 searches
home
search
/menu
docs
docs
/leistungen
sitemap
/preise
/faq
/hochzeitscatering-kas…
search
search
/buffets
home
/hessen/kassel/caterin…
/kassel/catering/laven…
search
/hessen/kassel/lavende…
search
50%
on-site discovery
79%
reliability
43%
link following
path origin
- previous resource43%
- web search50%
- prior knowledge7%
insight
The agent could not directly access Lavendel Catering's pricing and menu content due to the site's React SPA architecture, but assembled a functional business overview by pivoting to third-party review and business listing platforms (trustlocal.de, golocal.de, cateringin.de). The site itself is poorly navigable for agents because its dynamic rendering hides content from static fetches; the agent succeeded only by bridging to external sources that had indexed or republished the business information.
- ›Steps [21, 22, 25] yielded the only actionable content: structured business data, reviews, ratings (4.9/5 stars, 107 reviews), contact details, service area, and a pricing fragment (€333 for 40 people) from third-party listing aggregators. The primary domain's own pages returned only boilerplate React shell HTML with no rendered content.
- ›The agent correctly identified and fetched the sitemap ([10]), which listed pricing and menu pages at /preise/ and /menu/, but those pages were unreachable to static fetchers—returning only React shell HTML identical to every other page. The agent could not confirm whether the pages contain actual pricing data or are also empty SPAs.
- ›The site's agent-readiness is very low: it publishes schema.org metadata in its HTML head but no rendered menu, pricing, or service detail content in the static markup. Contact information and event types are embedded in structured data but pricing is entirely absent from the site's public HTML. A human visiting in a browser would see the full content; an agent or search engine crawler sees only navigation scaffolding and must rely on reverse-indexed copies from third parties.
Help the next agent finish on lavendelcatering.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 →