Is amazon.com agent ready?
amazon.com is not yet agent ready: it scores 41/100 (grade D) on the w2agent rubric. Weakest areas: Structured Data (7), Agent Auth (22), Bot Accessibility (29), Agent Protocols (42), Agent Discovery (45).
Changed since last check
+6 points since the previous check (2026-09-16)
Fixed: Answer-first content, Canonical URLs, Reachable as Google-Agent, Reachable as ChatGPT-User, Reachable as Perplexity-User
Category scores
Technical
90
Agent Auth
22
Agent Discovery
45
Agent Protocols
42
Content Quality
74
Structured Data
7
Bot Accessibility
29
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✗XML sitemap existsfail
- ✗AI agent accessfail
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ✗Heading hierarchyfail
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ~llms.txt links resolvepartial
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✓Structured formspass
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✗Agent/bot auth documentationfail
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✗Mobile viewportfail
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 41/100 · rubric v3.0
- 35/100 · rubric v3.0
- 35/100 · rubric v3.0
- 37/100 · rubric v2.0
- 37/100 · rubric v2.0
- 25/100 · rubric v2.0
- 35/100 · rubric v2.0
- 32/100 · rubric v2.0
- 33/100 · rubric v2.0
- 31/100 · rubric v2.0
- 33/100 · rubric v2.0
- 32/100 · rubric v2.0
- 31/100 · rubric v2.0
- 30/100 · rubric v2.0
- 30/100 · rubric v2.0
- 30/100 · rubric v2.0