Is arstechnica.com agent ready?
arstechnica.com is partly agent ready: it scores 48/100 (grade C) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (22), Agent Protocols (37).
Changed since last check
+1 points since the previous check (2026-09-16)
Changed: Response time (fail → partial)
Category scores
Technical
100
Agent Auth
22
Agent Discovery
0
Agent Protocols
37
Content Quality
78
Structured Data
58
Bot Accessibility
54
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✓XML sitemap existspass
- ✗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 tagspass
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ~JSON-LD validpartial
- ~Heading hierarchypartial
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ✓Content lengthpass
- ~Token efficiency (HTML-to-text ratio)partial
- ✓Freshness signalspass
- ~Author attributionpartial
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
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 schemaspass
- —/.well-known/ucpskip
- ~Structured formspartial
- —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 viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✓wp-page-builder-souppass
- ✗wp-rest-api-accessiblefail
- ✓wp-security-blocking-botspass
- ✗wp-robots-default-blockingfail
Score history
- 48/100 · rubric v3.0
- 47/100 · rubric v3.0
- 47/100 · rubric v3.0
- 46/100 · rubric v2.0
- 46/100 · rubric v2.0
- 45/100 · rubric v2.0
- 44/100 · rubric v2.0
- 40/100 · rubric v2.0
- 45/100 · rubric v2.0
- 46/100 · rubric v2.0
- 46/100 · rubric v2.0
- 46/100 · rubric v2.0
- 45/100 · rubric v2.0
- 54/100 · rubric v2.0
- 53/100 · rubric v2.0