Is wayfair.com agent ready?
wayfair.com is not yet agent ready: it scores 30/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (11), Agent Protocols (17), Structured Data (17), Content Quality (37). Fixing /.well-known/agent-card.json would add about 4 points.
What to fix first
- /.well-known/agent-card.jsonNo /.well-known/agent-card.json found+4 points if fixed
- Agent/bot auth documentationNo agent/bot auth documentation signals found+4 points if fixed
- nextjs-well-known-served.well-known/ agent discovery files not found — Next.js needs route handlers or public/ files for these+4 points if fixed
- Public API surfaceNo public API surface detected+4 points if fixed
- Schema.org JSON-LD present0/5 pages have JSON-LD structured data+3 points if fixed
How wayfair.com compares
Better than 12% of measured sites
vs other Next.js sites: better than 1% of 333 Next.js sites
Next.js median: 56/100
Among 1223 websites measured under rubric v3.1
Changed since last check
No change in score since the previous check (2026-11-15)
Category scores
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✗XML sitemap existsNo valid XML sitemap foundfail
- ✗Edge treatment of agent user-agentsBlocked at the edge (agent-blocked): ChatGPT-User got HTTP 429 on https://wayfair.com, where our declared crawler got HTTP 200. Not probed: Claude-User.tracked, not scoredfail
- ✗Content negotiation (Markdown)No markdown served via Accept: text/markdown or .md URLs (checked homepage)fail
Passes: No error status codes, Response time, AI agent access, robots.txt exists
Not measured: Declared AI usage preferences (tracked, not scored)
Structured Data
- ~OpenGraph meta tagsMissing OpenGraph tags on some pagespartial
- ~Semantic HTML elementsLimited use of semantic HTML (<article>, <section>, <nav>, <main>)partial
- ✗Appropriate Schema.org type0/5 pages use recognized Schema.org typesfail
- ~Heading hierarchy2/5 pages have proper heading hierarchypartial
- ✗Schema.org JSON-LD present0/5 pages have JSON-LD structured datafail
- ✗Schema.org completenessNo Schema.org data to evaluatefail
Not measured: JSON-LD valid
Content Quality
- ✗FAQ contentNo FAQ or Q&A content detectedfail
- ~Answer-first contentSome pages lack early substantive content or meta descriptionspartial
- ✗Token efficiency (HTML-to-text ratio)Average text-to-HTML ratio: 1.5%fail
- ✗Freshness signals0/5 pages have date/freshness signalsfail
- ✗Author attribution0/5 pages have author attributionfail
Passes: Content length, Citation readiness, Lists and tables for structured info
Agent Discovery
- ✗llms.txt existsNo llms.txt found — coding agents and AI tools that read llms.txt have no curated index of your docsfail
- ✗Markdown alternate linksNo markdown alternate links foundfail
- ✗/.well-known/agent-card.jsonNo /.well-known/agent-card.json foundfail
Not measured: llms.txt follows spec, MCP server card (tracked, not scored), Agent Skills index (tracked, not scored), llms.txt links resolve
Agent Protocols
- ✗Discoverable API endpointsNo discoverable API endpoints (OpenAPI, GraphQL, etc.)fail
- ✗MCP endpointNo MCP endpoint found (tried homepage links, /mcp and mcp.<domain>)fail
- ✗Action schemasNo action schemas found (SearchAction, OrderAction, etc.)fail
- ✗Reachable as Google-AgentHomepage returned HTTP 429 to Google-Agentfail
- ✗Reachable as ChatGPT-UserHomepage returned HTTP 429 to ChatGPT-Userfail
- ✗Reachable as Perplexity-UserHomepage returned HTTP 429 to Perplexity-Userfail
Passes: Structured forms
Not measured: /.well-known/ucp, WebMCP imperative API (tracked, not scored), WebMCP declarative API (tracked, not scored)
Agent Auth
- ✗PKCE S256 supportNo PKCE S256 support detectedfail
- ✗Public API surfaceNo public API surface detectedfail
- ✗Agent/bot auth documentationNo agent/bot auth documentation signals foundfail
- ~Developer portalDeveloper portal at https://developer.wayfair.com/ has thin content (40 chars)partial
- ✗Scoped API permissionsNo scoped permission patterns found in developer portalfail
Not measured: MCP authorization (401 challenge → protected resource metadata), Client ID Metadata Documents (bonus), OpenAPI specification, OAuth discovery chain (RFC 9728 → RFC 8414), API catalog (RFC 9727), Agent operator signing directory (tracked, not scored)
Technical
- ~Canonical URLs1/5 pages have canonical URLspartial
Passes: HTTPS, UTF-8 charset, Mobile viewport, Content accessible without JS, Security headers
Other
- ✗nextjs-metadata-apiOnly 1/5 pages have complete metadata. Use Next.js Metadata API for consistent SEO.fail
- ~nextjs-static-generationMost pages appear to be rendered per request (0/5 sampled pages with rendering evidence are statically served). Static generation improves AI crawler reliability.partial
- ✗nextjs-well-known-served.well-known/ agent discovery files not found — Next.js needs route handlers or public/ files for thesefail
- ~local-business-nap-structured1/3 NAP fields present in structured markup (name, address, phone)partial
Not measured: local-business-hours-jsonld, local-business-booking-accessible
Score history
- 30/100 · rubric v3.1
- 30/100 · rubric v3.1
- 29/100 · rubric v3.1
- 30/100 · rubric v3.1
- 48/100 · rubric v2.0
- 48/100 · rubric v2.0
Related websites
Share this score
Link
https://w2agent.dev/score/wayfair.com
Markdown
[](https://w2agent.dev/score/wayfair.com)
HTML
<a href="https://w2agent.dev/score/wayfair.com"><img src="https://w2agent.dev/api/score/wayfair.com/badge.svg" alt="w2agent AI Readiness score for wayfair.com" /></a>
IMG
https://w2agent.dev/api/score/wayfair.com/badge.svg