physioaktiv-chemnitz.de
success
Claude Code
intent

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

23steps
65.5sduration
$0.2333cost
294,203tokens
36 steps13 reasoning steps6 searches
home
home
/wp-json/wp/v2/pages/2
/kontakt
/uber-uns
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages/780
/wp-json/wp/v2/pages/778
search
search
search
/wp-json/wp/v2/posts
search
/leistungen/klassische…
/preise
search
/impressum
/wp-json/wp/v2/pages/920
/leistungen/manuelle-t…
/leistungen/lymphdrain…
search
76%
on-site discovery
71%
reliability
71%
link following
path origin
  • previous resource71%
  • web search24%
  • prior knowledge6%
insight

The agent successfully identified PhysioAktiv's core services (massage, manual therapy, lymphatic drainage, and wellness courses) and contact information, but could not find pricing or detailed differentiation because the website does not publish this information publicly. The site is minimally agent-ready: it required web search fallbacks and WordPress API probing to assemble a basic picture, and critical business information (pricing, hours, insurance) is simply absent.

  • ›Steps [5], [13], [24], [25] returned service descriptions, but only via partial HTML responses that had to be reassembled; the WordPress JSON API (step [5]) was more reliable than HTML fetches, indicating the site was built with a headless/API-first structure but service pages are not optimized for machine parsing.
  • ›Step [27] (impressum/imprint) was the only content-bearing fetch that yielded structured, complete information—owner name, address, phone, email. All other content arrived as truncated HTML fragments. The site does not expose pricing, operating hours, insurance acceptance, or service differentiation anywhere; the agent correctly noted this as absent rather than guessing.
  • ›The agent had to use web search (steps [11], [20], [31], [32], [34]) to discover that service pages existed at all (e.g., /leistungen/klassische-massage), since the homepage fetch was truncated and the WordPress pages API did not return a usable page list. This indicates poor navigation structure visibility and reliance on prior knowledge or external indexing rather than self-documenting site structure.
  • ›Attempts to access common URLs (/uber-uns, /kontakt, /preise) returned 404s, suggesting the site's navigation is either custom or poorly labeled. The agent could not identify how to contact them or book appointments from the site itself—only extracted phone/email from the imprint.
  • ›The site's most agent-hostile pattern: pricing is completely absent, and a notice about fully booked appointments (step [8]) indicates a waiting-list-only model, but no instructions for joining the list are visible. The agent had to resort to general inference and web search context rather than finding this on the site.

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