Is subway.com agent ready?

subway.com is not yet agent ready: it scores 22/100 (grade F) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Agent Protocols (0), Structured Data (10), Content Quality (28).

22/ 100
Grade: F

Last checked · Platform: Next.js

Scored Oct 14, 2026 · Rubric v3.0

How subway.com compares

Better than 7% of measured sites

vs other Next.js sites: better than 0% of 334 Next.js sites

Next.js median: 56/100

Among 1299 websites measured under rubric v3.0

Changed since last check

Rescored under rubric v3.0; the previous check used rubric v2.0, so scores are not compared.

Category scores

Technical
67
Agent Auth
0
Agent Discovery
0
Agent Protocols
0
Content Quality
28
Structured Data
10
Bot Accessibility
61

Agent protocol panel

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

Check results

Bot Accessibility

  • ~No error status codespartial
  • ~Response timepartial
  • ✗XML sitemap existsfail
  • ✓AI agent accesspass
  • ?Edge treatment of agent user-agentstracked, not scorederror
  • ✓robots.txt existspass
  • ✓Content negotiation (Markdown)pass
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ~OpenGraph meta tagspartial
  • ~Semantic HTML elementspartial
  • ✗Appropriate Schema.org typefail
  • —JSON-LD validskip
  • ~Heading hierarchypartial
  • ✗Schema.org JSON-LD presentfail
  • ✗Schema.org completenessfail

Content Quality

  • ✗FAQ contentfail
  • ~Answer-first contentpartial
  • ~Content lengthpartial
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ✗Freshness signalsfail
  • ✗Author attributionfail
  • ~Citation readinesspartial
  • ✗Lists and tables for structured infofail

Agent Discovery

  • —llms.txt follows specskip
  • ✗llms.txt existsfail
  • —MCP server cardtracked, not scoredskip
  • ✗Markdown alternate linksfail
  • ✗/.well-known/agent-card.jsonfail
  • —llms.txt links resolveskip

Agent Protocols

  • ✗Discoverable API endpointsfail
  • ✗MCP endpointfail
  • ✗Action schemasfail
  • ✗/.well-known/ucpfail
  • —Structured formsskip
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ?Reachable as Google-Agenterror
  • ✗Reachable as ChatGPT-Userfail
  • ✗Reachable as Perplexity-Userfail

Agent Auth

  • —MCP authorization (401 challenge → protected resource metadata)skip
  • —PKCE S256 supportskip
  • ✗Public API surfacefail
  • —Client ID Metadata Documents (bonus)skip
  • —OpenAPI specificationskip
  • —Agent/bot auth documentationskip
  • —OAuth discovery chain (RFC 9728 → RFC 8414)skip
  • —Developer portalskip
  • —Scoped API permissionsskip
  • —API catalog (RFC 9727)skip
  • —Agent operator signing directorytracked, not scoredskip

Technical

  • ✓HTTPSpass
  • ✓UTF-8 charsetpass
  • ~Canonical URLspartial
  • ✓Mobile viewportpass
  • ~Content accessible without JSpartial
  • ~Security headerspartial

Other

  • ✗nextjs-metadata-apifail
  • —ecommerce-gtin-validskip
  • —ecommerce-product-schemaskip
  • ~nextjs-static-generationpartial
  • ✗nextjs-well-known-servedfail
  • —ecommerce-checkout-accessibleskip

Score history

  • 22/100 · rubric v3.0
  • 42/100 · rubric v2.0
  • 42/100 · rubric v2.0
  • 44/100 · rubric v2.0
  • 31/100 · rubric v2.0
  • 44/100 · rubric v2.0
  • 44/100 · rubric v2.0
  • 45/100 · rubric v2.0
  • 48/100 · rubric v2.0

Related websites

Is your own site agent ready?

Check your own site →

Re-audit subway.com