Is azbyka.ru agent ready?
azbyka.ru is partly agent ready: it scores 59/100 (grade C) on the w2agent rubric. Weakest areas: Agent Protocols (24), Agent Auth (46).
Changed since last check
+26 points since the previous check (2026-09-16)
Fixed: Answer-first content, OpenGraph meta tags, No error status codes, Semantic HTML elements, Canonical URLs, Content length, Content accessible without JS, Citation readiness, Lists and tables for structured info, llms.txt links resolve
Regressed: Response time, Heading hierarchy, Reachable as Google-Agent, Reachable as Perplexity-User
Changed: Appropriate Schema.org type (fail → partial), Structured forms (fail → partial), JSON-LD valid (fail → partial), Schema.org completeness (fail → partial)
Category scores
Technical
86
Agent Auth
46
Agent Discovery
50
Agent Protocols
24
Content Quality
75
Structured Data
55
Bot Accessibility
83
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- 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 tagspass
- ✓Semantic HTML elementspass
- ~Appropriate Schema.org typepartial
- ~JSON-LD validpartial
- ~Heading hierarchypartial
- ~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 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 formspartial
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✗Reachable as Google-Agentfail
- ✓Reachable as ChatGPT-Userpass
- ✗Reachable as Perplexity-Userfail
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✓PKCE S256 supportpass
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- ~OAuth discovery chain (RFC 9728 → RFC 8414)partial
- —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-accessiblepass
- ✓wp-security-blocking-botspass
- ✓wp-robots-default-blockingpass
Score history
- 59/100 · rubric v3.0
- 33/100 · rubric v3.0
- 13/100 · rubric v3.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0
- 52/100 · rubric v2.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0