Is kino-teatr.ru agent ready?
kino-teatr.ru is not yet agent ready: it scores 30/100 (grade D) on the w2agent rubric.
Changed since last check
+12 points since the previous check (2026-09-15)
Fixed: No error status codes, Content length, Content accessible without JS, Lists and tables for structured info, Reachable as ChatGPT-User, Reachable as Perplexity-User
Regressed: UTF-8 charset, Heading hierarchy
Changed: Canonical URLs (fail → partial), Structured forms (fail → partial)
Category scores
Category breakdown not recorded for this audit.
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 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 tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ✗Heading hierarchyfail
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ~Freshness signalspartial
- ✗Author attributionfail
- ~Citation readinesspartial
- ✓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 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-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 portalpartial
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✗UTF-8 charsetfail
- ~Canonical URLspartial
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Other
- —local-business-hours-jsonldskip
- ~local-business-nap-structuredpartial
- —local-business-booking-accessibleskip
Score history
- 30/100 · rubric v3.0
- 18/100 · rubric v3.0
- 30/100 · rubric v2.0
- 30/100 · rubric v2.0
- 30/100 · rubric v2.0
- 29/100 · rubric v2.0