Skip to content

Gate A — Technical

Owner: Engineering. Sign-off: written, by the engineering lead.

#CheckCondition
A.1robots.txt reachable, valid, AI-bot allowlist matches template, Content Signals comment block presentalways
A.2sitemap.xml reachable, parses, <lastmod> recent, no thin/archive URLsalways
A.3/llms.txt serves text/plain, under 50 KB, structured per specalways
A.4llms-full.txt per major section serves markdown, each under 200 KBalways
A.5Markdown returns Content-Type: text/markdown + Vary: accept + x-markdown-tokens on Accept: text/markdownalways
A.6/{slug}/index.md URL fallback returns the same markdown as A.5 for all indexable pagesalways — most agents do not send the Accept header
A.7Link: rel="alternate"; type="text/markdown" header on HTML responsesalways
A.8content-signal header on public pages only (not wp-admin, REST, cron, authenticated)always
A.9/.well-known/agent-statement.json returns 200, valid JSON, schema-validatedalways
A.10/.well-known/api-catalog returns 200, RFC 9727 shapeif APIs
A.11OAuth metadata endpoints valid (RFC 8414, RFC 9728)if APIs
A.12MCP Server Card + Agent Skills index serve and validateif MCP
A.13Web Bot Auth directory at /.well-known/http-message-signatures-directory; signatures verify with Cloudflare verifierif site originates bot traffic
A.14Schema.org JSON-LD validates (Google Rich Results Test + Schema.org Validator)always
A.15All indexable content renders without JavaScriptalways
A.16IsItAgentReady passes all in-scope checks; out-of-scope items documented in engagement briefalways

Items A.10–A.13 apply conditionally on property type. Out-of-scope items must be documented in the engagement brief and explicitly excluded — not silently failing.