subaru.com
success
Claude Code
intent

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

16steps
66.7sduration
$0.2422cost
122,836tokens
19 steps3 reasoning steps8 searches
home
/vehicles
docs
/build-and-price
search
/vehicles/all-vehicles…
/suvs.html
/vehicles/electric-veh…
search
search
search
search
search
/vehicles/accolades.html
search
search
50%
on-site discovery
63%
reliability
38%
link following
path origin
  • previous resource38%
  • web search50%
  • prior knowledge13%
insight

The agent satisfied the task by assembling a comprehensive explanation of Subaru's business, positioning, and differentiation, but had to work around a poorly structured website and heavy reliance on web search to discover content. Direct site navigation failed (steps 2–4 returned 404s), forcing the agent to use search queries to locate vehicle pages, safety technology docs, and awards/accolades. The fetched pages themselves contained minimal rendered content due to JavaScript-heavy architecture, so the agent synthesized answers from page metadata, inferred URLs, and prior knowledge rather than parsing rich, machine-readable content from the site.

  • ›Steps 8, 9, 10 (vehicle pages) returned metadata-only responses with truncated HTML; the actual vehicle lineup, specs, and pricing had to be inferred from meta descriptions and prior knowledge rather than extracted from page body content.
  • ›Steps 12–13 (AWD and EyeSight searches) relied on web search discovery; the agent found these pages via Google site search, not via site navigation. The site's information architecture did not surface these differentiators as standalone resources in a discoverable way.
  • ›Step 16 (accolades page) was the only awards/reliability page fetched directly, confirming Subaru's market positioning via third-party awards, but the agent had to search for this URL rather than finding a link on the homepage or main nav.
  • ›Steps 2–4 demonstrated that intuitive URL patterns (/vehicles, /about, /build-and-price) do not exist on the site, forcing reliance on search or prior knowledge to locate content.
  • ›The agent's final answer includes pricing data (Crosstrek $26,995, Solterra $38,495, Trailseeker $39,995) that was sourced from web search snippets (step 7) and media releases, not from the main website—indicating pricing is not prominently exposed on customer-facing pages.
  • ›The site's JavaScript-rendered architecture made direct content fetches uninformative; meta descriptions provided the only structured signals, requiring the agent to assemble narrative from fragments, prior knowledge, and search results.

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