adidas.com
success
Claude Code
intent

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

11steps
73.2sduration
$0.7107cost
95,789tokens
19 steps8 reasoning steps6 searches
home
search
/us
/us/men
search
/us/originals
search
/us/help
search
search
search
20%
on-site discovery
60%
reliability
0%
link following
path origin
  • web search80%
  • prior knowledge20%
insight

The agent assembled a comprehensive overview of adidas.com by combining web search results with two successful page fetches (US homepage and category pages), working around security blocks that prevented direct site exploration. The site's core e-commerce purpose, product categories, pricing tiers, and competitive positioning are clearly documented and discoverable via search, but the agent had to rely heavily on external sources (80% web search) rather than the site publishing structured, machine-readable answers to 'who it's for' or 'how it's different' questions. The site is moderately agent-ready for basic discovery but lacks transparent product-level detail and policy information in accessible form.

  • ›Direct fetches of /us and category pages (/us/men, /us/originals) returned HTML with meta descriptions but limited structured product data or business positioning—the agent extracted brand intent from page titles and meta tags, which is fragile.
  • ›80% of the answer came from web search results pointing to third-party sources (competitive analyses, pricing guides, brand strategy articles) rather than adidas.com itself publishing this information in a machine-readable or easily discoverable format on its own domain.
  • ›The site actively blocks bot access with 403 security responses on help pages and some routes, making it difficult for agents to explore beyond the homepage and category landing pages—pricing, membership tier details, shipping policies, and return windows were all inaccessible directly.
  • ›The agent successfully found the adiClub loyalty program URL via search and correctly identified it as a loyalty mechanism, but the full tier structure and requirements had to be inferred from incomplete search snippets rather than fetched from a canonical source.
  • ›Product-level information (actual inventory, detailed specs, exact price ranges per category) was not accessible, forcing the agent to cite external shoe pricing guides rather than data from adidas.com itself.
  • ›The site's multi-country structure (50+ localized versions) is discoverable but pricing and regional policy variations are not transparently documented in search results or fetched pages.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →