Emerging Standards - AI-readiness signals
All 10 signals in the Emerging Standards category, with what each tests and why it matters for visibility in AI.
-
MCP server endpoint - the protocol AI agents use to call your tools
Tests whether your site exposes a Model Context Protocol endpoint that AI agents can find and call.
-
Agent Card - the A2A protocol's identity file that lets agents find your agent
Tests for a /.well-known/agent-card.json document describing your agent to other agents.
-
llms.txt - a curated map of your site written for AI crawlers
Tests whether you publish an /llms.txt file giving AI agents a context-window-sized overview of your site.
-
llms-full.txt - the entire documentation bundled into one file for AI
Tests whether you publish /llms-full.txt, a concatenated Markdown dump of your primary documentation.
-
Markdown mirror - every page available as plain Markdown by adding .md
Tests whether your HTML pages also resolve at the same URL with a .md suffix, returning clean Markdown.
-
AI usage preferences - the IETF draft that replaces a tangle of vendor rules
Tests for the Content-Usage header or robots.txt rule from the IETF aipref working group draft.
-
TDM Reservation Protocol - the W3C signal that satisfies EU AI Act opt-out
Tests for the W3C TDMRep declaration that satisfies EU machine-readable opt-out requirements.
-
noai / noimageai directives - the community-convention AI opt-out tokens
Tests for noai, noimageai, or noml tokens in meta robots tags or X-Robots-Tag headers.
-
ai-plugin.json - the legacy OpenAI plugin manifest, now largely deprecated
Tests for the legacy /.well-known/ai-plugin.json manifest from the original OpenAI plugins era.
-
did:web - a cryptographic identity document that agents can verify
Tests for a W3C did:web identity document at /.well-known/did.json verifying ownership of your domain.