10vu10.ch
success
Claude Code
intent

What does 10vu10.ch do and who is it for? Explain it back to me.

31steps
107.7sduration
$0.9762cost
349,075tokens
44 steps13 reasoning steps4 searches
home
/en
/services
docs
search
/de
docs
/portfolio
/contact
docs
/api/services
search
/api/pricing
search
/impressum
sitemap
sitemap
/en
sitemap
sitemap
sitemap
/en/projects/mint-syst…
sitemap
/en/services/webdesign
/en/services/webprogra…
/en/services/search-en…
/en/services/webshops
search
/en/services/generativ…
sitemap
robots.txt
96%
on-site discovery
67%
reliability
67%
link following
path origin
  • previous resource67%
  • web search4%
  • prior knowledge30%
insight

The agent successfully understood 10vu10's core identity and service offerings but could not locate pricing information, making the answer partial on the original task. The site uses a JavaScript-heavy SPA architecture that serves uniform 404 responses to conventional page paths; the agent discovered actual content only after finding the sitemap and extracting service URLs in a non-standard form (/leistungen/ for German, /en/services/ for English). The site is low on machine-readability and requires prior knowledge of sitemap navigation to be fully explored.

  • ›Content-bearing steps (33, 34, 38, 39, 42) all returned service description pages fetched via URLs discovered in sitemap XML files. The HTML responses were truncated in the trajectory, but the agent assembled a coherent answer about five service lines: web design, web programming, SEO, webshops, and generative engine optimization.
  • ›The site does not publish pricing publicly—the agent explicitly noted this gap and could not fulfill that portion of the task despite targeted searches and attempts to guess pricing/API endpoints. This is the primary unsatisfied component of the original request ('how it's priced').
  • ›The agent could not access rendered page content (all HTML responses were truncated and marked 4400+ chars); it relied on URL patterns and metadata (hreflang links, sitemap structure) rather than parsed body text. Conventional navigation paths (/services, /pricing, /about, /contact) all returned generic 404 responses, forcing sitemap enumeration.
  • ›The agent discovered services via sitemap rather than site navigation, indicating the site's structure is not discoverable through standard navigation. No contact details, team information, or client testimonials were surfaced, and the newer 'Generative Engine Optimization' service was named but not explained.
  • ›The site is bilingual (de-CH and en) with parallel URL structures, and the agent successfully navigated to English versions to complete the analysis. However, the overall UX for agents is poor: no public pricing, dynamically-loaded content, and reliance on XML sitemaps rather than accessible navigation.

Help the next agent finish on 10vu10.ch

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 →