classic.com
partial
Claude Code
intent
What does classic.com do and who is it for? Explain it back to me.
6steps
45.0sduration
$0.4450cost
28,546tokens
9 steps3 reasoning steps3 searches
home
search
docs
search
search
/whats-changing-july2026
20%
answer from your site
33%
answer efficiency
0%
followed site links
answer sources
- from this site20%
- from search results60%
- from agent knowledge20%
url discovery
- given in the task33%
- found via web search67%
insight
The agent assembled a usable explanation of classic.com despite the site blocking direct access (403 errors on all main domain URLs). It relied entirely on web search results and a single accessible blog post to answer the task, filling gaps with reasonable inferences about missing details.
- ›All four primary URLs on classic.com's main domain returned 403 Forbidden, forcing the agent to pivot to search-based discovery rather than direct site exploration. The only fetchable resource was a blog post on the Insights subdomain (step [7]), which was discoverable only through search results.
- ›Step [3] (initial search) and step [5] (pricing search) returned only links and snippets, not full pages—the agent extracted its core facts about what classic.com does and costs from search result titles and the agent's synthesis, not from fetched content. These are treated as content-bearing because search results contained substantive claims (e.g., 'search engine for classic, exotic, and specialty cars'), but the site itself did not surface them.
- ›Step [7] was the only site-fetched content and carried the clearest positioning: the membership-vs.-advertising differentiator, pricing tiers, and feature roadmap. This single page anchored the competitive positioning claim.
- ›Step [6] (competitor search) returned link titles and external profiles but no substantive detail from classic.com itself—all competitor and differentiation claims rest on search snippets or inferred logic (e.g., 'BaT focuses on live auctions'), not site documentation.
- ›The agent correctly flagged five gaps (AI feature details, competitive feature parity, seller incentives, geographic scope, dealer payment model) that could not be resolved without accessing the main site or support documentation—indicating the 403 blocks genuinely prevented a complete answer.
Help the next agent finish on classic.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 →