Is reuters.com agent ready?

reuters.com is not yet agent ready: it scores 11/100 (grade F) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Agent Protocols (0), Structured Data (0), Content Quality (13), Bot Accessibility (29).

11/ 100
Grade: F

Last checked

Scored Oct 14, 2026 · 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
50
Agent Auth
0
Agent Discovery
0
Agent Protocols
0
Content Quality
13
Structured Data
0
Bot Accessibility
29

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 timepass
  • ✗XML sitemap existsfail
  • ✗AI agent accessfail
  • ?Edge treatment of agent user-agentstracked, not scorederror
  • ✓robots.txt existspass
  • ✗Content negotiation (Markdown)fail
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ✗OpenGraph meta tagsfail
  • ✗Semantic HTML elementsfail
  • ✗Appropriate Schema.org typefail
  • —JSON-LD validskip
  • ✗Heading hierarchyfail
  • ✗Schema.org JSON-LD presentfail
  • ✗Schema.org completenessfail

Content Quality

  • ✗FAQ contentfail
  • ✗Answer-first contentfail
  • ✗Content lengthfail
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ✗Freshness signalsfail
  • ✗Author attributionfail
  • ✗Citation readinessfail
  • ✗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/ucpskip
  • —Structured formsskip
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ✗Reachable as Google-Agentfail
  • ✗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 URLsfail
  • ✗Mobile viewportfail
  • ✗Content accessible without JSfail
  • ~Security headerspartial

Score history

  • 11/100 · rubric v3.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 12/100 · rubric v2.0
  • 18/100 · rubric v2.0
  • 10/100 · rubric v2.0

Related websites

Is your own site agent ready?

Check your own site →

Re-audit reuters.com