asklepios.com
success
Claude Code
intent

What does asklepios.com do and who is it for? Explain it back to me.

12steps
62.8sduration
$0.7277cost
144,913tokens
17 steps5 reasoning steps4 searches
home
/en/group
/en
/en/about
/en/clinics
search
/en/patient-services
/en/why-choose-asklepios
search
search
/clinic/asklepios-medi…
search
62%
on-site discovery
75%
reliability
38%
link following
path origin
  • previous resource38%
  • web search38%
  • prior knowledge25%
insight

The agent satisfied the task by assembling a coherent explanation of Asklepios from fragmented sources. The official website itself was largely opaque—pages fetched as HTML returned minimal content beyond metadata—forcing the agent to rely heavily on web search results and external third-party resources (MediGlobus, Wikipedia, specialty clinic pages) to answer what Asklepios does, who it serves, how it's priced, and how it differs from competitors. The site is poorly navigable for automated discovery: JavaScript-heavy rendering obscured content, internal links returned 404s, and pricing/service details are deliberately unpublished.

  • ›Steps [3] and [5] (the main English-language site pages) returned only HTML metadata and Next.js boilerplate—the actual page content did not load in the fetch responses, making the official site non-content-bearing for most claims in the final answer.
  • ›Step [10] (Patient Services page) and [11] (Why Choose Asklepios page) were cited in the sources but similarly returned truncated responses with no visible service or differentiator details—the agent reconstructed answers from external sources instead.
  • ›Step [14] (MediGlobus third-party clinic profile) was the only external fetch attempted and returned content; web search steps [9], [12], [13], [15] provided the bulk of actionable information (competitors, specialties, pricing model, international patient programs) but were routing-only and not directly cited.
  • ›The agent correctly identified a fundamental mismatch: asklepios.com is a B2B/corporate website, not a consumer-facing product site, so it deliberately obscures pricing and service details. This is typical for large hospital systems but makes machine-readable discovery impossible.
  • ›No public price list, service directory, or structured data (schema.org, JSON-LD) was published on the site; the agent had to infer the pricing model (prepayment, DRG-based, non-binding estimates) from external medical tourism and clinic profile pages.
  • ›The site's internal navigation is broken for English language paths (/en/about, /en/clinics returned 404s), limiting the agent's ability to discover information through normal crawl patterns.

See every agent that visits asklepios.com

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 →