solocoach.ai
success
Claude Code
intent
What does solocoach.ai do and who is it for? Explain it back to me.
10steps
29.3sduration
$0.0497cost
79,248tokens
11 steps1 reasoning step
home
docs
/features
docs
sitemap
llms.txt
/drills
/volleyball-practice-p…
/volleyball-coaching-app
home
100%
on-site discovery
70%
reliability
90%
link following
path origin
- previous resource90%
- prior knowledge10%
insight
The agent successfully assembled a comprehensive understanding of SoloCoach by relying almost entirely on two machine-readable artifacts—llms.txt and the homepage text extraction—rather than navigable website content. The site's HTML pages returned JavaScript-heavy shells with minimal rendered text, forcing the agent to reconstruct its answer from structured metadata and prior knowledge, ultimately delivering a complete but partially inference-dependent answer about what SoloCoach does, who it's for, its free pricing model, and its positioning.
- ›Steps [1], [2], [3], [6], [7], [8] returned only HTML boilerplate with no usable text content; the agent gained zero actionable information from conventional page navigation. Step [5] (/llms.txt) was the primary content-bearing resource, providing canonical product description, use cases, audience tiers, drill library details, and differentiation language. Step [9] (homepage text extraction, likely a fallback or second fetch) confirmed and reinforced that description.
- ›The site does not naturally expose pricing, feature comparisons, or competitive differentiation through linked pages (/pricing, /features, /about all returned 404s). The agent had to infer pricing as 'completely free' from llms.txt's app store references and absence of subscription mentions—a correct inference, but not explicitly stated on any page the agent could fetch.
- ›llms.txt is the only agent-ready artifact on the site; it is well-structured, canonical, and answers most of the task questions directly. The homepage and landing pages are Next.js applications that render client-side, making them opaque to fetches. The sitemap was discoverable but merely listed URLs with no content. The agent's success depended entirely on finding and parsing llms.txt, a specialized resource not typical for general website navigation.
- ›The agent correctly identified gaps (no competitor comparison, no testimonials, no freemium explanation, limited feature detail) by noting what was absent even from the best-available sources. This reflects honest assessment against what a user would expect from a product site, not hallucination.
See every agent that visits solocoach.ai
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 →