viori.com
success
Claude Code
intent

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

10steps
55.1sduration
$0.6818cost
134,937tokens
17 steps7 reasoning steps3 searches
home
/pages/why-viori
/products
/pages/pricing
/collections/all
/pages/about
search
search
/blogs/updates/viori-v…
search
86%
on-site discovery
71%
reliability
43%
link following
path origin
  • previous resource43%
  • web search14%
  • prior knowledge43%
insight

The agent assembled a comprehensive explanation of Viori by combining prior knowledge, web search results, and selective site fetches—but had to work around severely truncated HTML responses from the domain itself. The final answer draws heavily on search results and cited blog posts rather than directly readable site content, indicating the website is not well-optimized for machine readability despite containing the necessary information.

  • ›Steps [1], [4], [7], [8] fetched from viori.com directly but returned heavily truncated/compressed HTML (noted in responses: '…[truncated, 4400 more chars]'), making full product descriptions, ingredient lists, pricing pages, and comparison details inaccessible via direct fetch.
  • ›Steps [10] and [11] (web search) were content-bearing: search results included pricing ($7.49–$18), product names (Hidden Waterfall Shampoo Bar), competitor names (Kitsch, Ethique, Earthling), and review links that grounded the agent's claims about hydration, hair types, and market positioning.
  • ›Step [13] fetched a comparison blog post (viori.com/blogs/updates/viori-vs-kitsch-vs-ethique-...) that the agent cited as a source but could not read due to the same HTML truncation problem, suggesting the agent relied on prior knowledge or search snippet metadata rather than the fetched content itself.
  • ›Step [15] (web search for Red Yao/mission story) returned URLs including viori.com/pages/mission-story, which the agent cited but had not successfully fetched (step [8] /pages/about returned truncated HTML). The agent appears to have used search result titles and URLs as proxies for content.
  • ›Direct 404 errors on /pages/why-viori and /pages/pricing (steps [3], [5]) forced the agent to rely on web search and inferred pricing from external review sites rather than official pricing pages.
  • ›The agent produced a detailed, confident answer (pricing, positioning, differentiators, target audience) with specific numbers and claims, but ~57% of the sourced information came from web search and prior knowledge rather than successfully parsed site content, indicating the site's HTML delivery is a navigation barrier.

See every agent that visits viori.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 →