gyn-probst.de
success
Claude Code
intent

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

21steps
86.7sduration
$0.2770cost
282,477tokens
33 steps12 reasoning steps8 searches
home
home
/home-en
/share/sitemap.xml
/leistungen
/services
/praxis
/faq
search
/curriculum-vitae-en
search
search
/frauenarzt/leipzig/ta…
search
/frauenarzpraxis.probst
search
search
/arzt/frauenheilkunde-…
search
search
/home-en
69%
on-site discovery
92%
reliability
62%
link following
path origin
  • previous resource62%
  • web search31%
  • prior knowledge8%
insight

The agent satisfied the core discovery-evaluation task by assembling a coherent explanation of Dr. Probst's practice from web search results and directory listings, since the primary website (gyn-probst.de / probst-leipzig.de) returned truncated HTML that blocked direct content extraction. The agent successfully identified what the practice does (holistic gynecology with nutritional medicine focus), who it serves (women seeking preventive care), and its key differentiators (IBCLC credential, anti-aging/prevention focus, integrated services), but could not locate publicly available pricing information despite extensive searching.

  • ›The site's own pages (fetches [1], [3], [4], [8], [9], [10], [14], [15], [16]) all returned truncated HTML responses that cut off at stylesheet/script sections, making the site's own content completely inaccessible to the agent. This forced reliance on external sources.
  • ›All content-bearing information came from web search results ([12], [18], [22], [25], [28]) and third-party directory listings ([27]), never from the primary domain. The agent explicitly cited arzt-auskunft.de, Yelp, and the Facebook page—none of which are gyn-probst.de itself.
  • ›Pricing information was not publicly available anywhere—not on the practice website, not in German medical directories, not on review platforms. The agent correctly identified this as a gap and noted that it likely requires direct contact.
  • ›The site's HTML truncation suggests either a rendering/crawl issue, a CMS (Contao) configuration problem, or content delivery that doesn't expose meaningful body text to fetchers. This is a critical accessibility problem for agents.
  • ›The agent had to bridge the gap by inferring the practice's positioning from search snippets, directory keywords, and transitive information (e.g., inferring IBCLC credential from search queries rather than reading it directly from the site).

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