medipraxis.de
partial
Claude Code
intent

What does medipraxis.de do and who is it for? Explain it back to me.

14steps
84.8sduration
$0.2725cost
163,599tokens
18 steps4 reasoning steps9 searches
home
home
search
search
search
search
/impressum
/datenschutz
search
search
search
search
search
/arzt/sachsen/5813-lei…
40%
on-site discovery
80%
reliability
0%
link following
path origin
  • web search60%
  • prior knowledge40%
insight

The agent could not retrieve pricing or detailed service information from medipraxis.de due to its JavaScript-heavy construction, but assembled a partial profile by searching for external references and prior knowledge about the practice. The site proved difficult to navigate programmatically; the agent had to rely on third-party medical directories (arzt-auskunft.de, ärzte.de, Gesundheitsnetz Leipzig) to confirm what the practice does, while failing entirely to surface pricing, team details, or office hours that the site claims to host.

  • ›Steps [11] and [12] (searches for 'Dr. med. Wolfram Mertz' + 'medipraxis' + keywords) returned snippets from external medical directories and review aggregators that confirmed the practice name, location, credentials, and general positioning (Hausarztpraxis with psychosomatic focus), but these were third-party sources, not the site itself.
  • ›Step [13] searched for contextual comparison (psychosomatic + preventive care + alternatives in Leipzig) and returned results for competitor practices but not for medipraxis.de content—the agent used this to infer competitive positioning rather than to extract direct claims.
  • ›Direct fetches of medipraxis.de (steps [1], [2], [9], [10]) all returned identical truncated JavaScript boilerplate with no rendered HTML content; the site's content is rendered client-side and inaccessible to non-browser agents. Cited sources in the final response point to external directories (arzt-auskunft.de, ärzte.de, gesundheitsnetz-leipzig.de), not to medipraxis.de itself.
  • ›Pricing, office hours, team details, and service specifics are documented as existing ('Sprechzeiten' page, 'Praxisteam' page) but were never retrieved—the agent explicitly called this 'a significant gap' and acknowledged it could only be obtained by phone/email contact.
  • ›The agent's answer on 'what they do' and 'who it's for' relies heavily on prior knowledge of German general practice structure (Hausarztpraxis, Check-up 35+, EKG, psychosomatic care) combined with directory listings, not site-native discovery; this represents assembly rather than retrieval.

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