Is e-recht24.de agent ready?
e-recht24.de is partly agent ready: it scores 52/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Protocols (20).
Changed since last check
−1 points since the previous check (2026-09-16)
Regressed: Reachable as Perplexity-User
Changed: Response time (partial → fail)
Category scores
Technical
86
Agent Auth
0
Agent Discovery
50
Agent Protocols
20
Content Quality
87
Structured Data
81
Bot Accessibility
61
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 existsfail
- ✓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 tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ✓Heading hierarchypass
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✓Freshness signalspass
- ✓Author attributionpass
- ✓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 formspass
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ?Reachable as Google-Agenterror
- ✓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 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Other
- ✓wp-page-builder-souppass
- ✗wp-rest-api-accessiblefail
- ~wp-security-blocking-botspartial
- ✓wp-robots-default-blockingpass
- ✓local-business-hours-jsonldpass
- ✓local-business-nap-structuredpass
- —local-business-booking-accessibleskip
Score history
- 52/100 · rubric v3.0
- 53/100 · rubric v3.0
- 51/100 · rubric v3.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 50/100 · rubric v2.0
- 51/100 · rubric v2.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0