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.

30/ 100
Grade: D

Last checked · Platform: Next.js

Scored Nov 16, 2026 · Rubric v3.1

What to fix first

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

Technical
79
Agent Auth
11
Agent Discovery
0
Agent Protocols
17
Content Quality
37
Structured Data
17
Bot Accessibility
67

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot measured
  • MCP discoveryNot found
  • llms.txt validityNot measured

Check results

Bot Accessibility

Passes: No error status codes, Response time, AI agent access, robots.txt exists

Not measured: Declared AI usage preferences (tracked, not scored)

Structured Data

Not measured: JSON-LD valid

Content Quality

Passes: Content length, Citation readiness, Lists and tables for structured info

Agent Discovery

Not measured: llms.txt follows spec, MCP server card (tracked, not scored), Agent Skills index (tracked, not scored), llms.txt links resolve

Agent Protocols

Passes: Structured forms

Not measured: /.well-known/ucp, WebMCP imperative API (tracked, not scored), WebMCP declarative API (tracked, not scored)

Agent Auth

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

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
w2agent AI Readiness score for wayfair.com

Markdown

[![w2agent AI Readiness score for wayfair.com](https://w2agent.dev/api/score/wayfair.com/badge.svg)](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

Is your own site agent ready?

Check your own site →

Re-audit wayfair.com