vooks.com
success
Claude Code
intent
What does vooks.com do and who is it for? Explain it back to me.
7steps
35.1sduration
$0.0446cost
18,319tokens
8 steps1 reasoning step
home
/features
/books
docs
/faq
docs
/parents
80%
answer from your site
43%
answer efficiency
33%
followed site links
answer sources
- from this site80%
- from agent knowledge20%
url discovery
- given in the task14%
- followed a link29%
- guessed the URL57%
insight
The agent successfully assembled a comprehensive overview of Vooks by fetching the homepage, about page, and pricing page—all typed from memory rather than discovered via site navigation. The site was minimally navigable; most standard URLs (features, books, faq, parents) returned 404s, forcing the agent to rely on direct URL guessing and information already present on three core pages.
- ›Site publishes core positioning, mission, pricing, and features only on homepage, about, and pricing pages; no FAQ, blog, or resources pages were accessible, limiting self-service discovery.
- ›71% of URLs were typed from memory (homepage, /about, /pricing), indicating the site does not surface navigation paths—agent had to guess or rely on convention.
- ›The homepage response was truncated in the trajectory output, yet contained sufficient structured information (features, pricing, audience) to ground the final answer without requiring the agent to guess core facts.
- ›Attempted standard content URLs (/features, /books, /faq, /parents) all returned 404s, suggesting either incomplete site structure or client-side routing that fetch tools cannot access.
- ›No direct competitor comparison, content catalog size, age-by-book breakdown, or parental controls documentation was reachable, leaving those gaps explicitly noted in the final response rather than filled speculatively.
See every agent that visits vooks.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 →