Is clevelandclinic.org agent ready?
clevelandclinic.org is not yet agent ready: it scores 41/100 (grade D) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Protocols (20), Agent Discovery (35), Content Quality (44).
Changed since last check
+4 points since the previous check (2026-09-16)
Fixed: No error status codes, Content length, Appropriate Schema.org type
Regressed: Reachable as Perplexity-User
Changed: Heading hierarchy (partial → fail), nextjs-metadata-api (fail → partial)
Category scores
Technical
75
Agent Auth
0
Agent Discovery
35
Agent Protocols
20
Content Quality
44
Structured Data
52
Bot Accessibility
79
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ?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 tagspartial
- ~Semantic HTML elementspartial
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ✗Heading hierarchyfail
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
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-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✗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 charsetfail
- ~Canonical URLspartial
- ✗Mobile viewportfail
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ~nextjs-metadata-apipartial
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 41/100 · rubric v3.0
- 37/100 · rubric v3.0
- 37/100 · rubric v3.0
- 45/100 · rubric v2.0
- 45/100 · rubric v2.0
- 44/100 · rubric v2.0
- 45/100 · rubric v2.0
- 45/100 · rubric v2.0
- 44/100 · rubric v2.0