Readiness

Agent Standards

Track adoption of agent-readiness checks such as machine-readable docs, API discovery, and content negotiation.

Current Signal30d
robotsTxt93,681
sitemap76,459
linkHeaders10,476
markdownNegotiation11,507

Agent readiness checks

Updated: 2026-08-24

Use this to: prioritize machine-readable signals that make the site easier for agents.

robotsTxt93,681
robotsTxtAiRules90,180
sitemap76,459
markdownNegotiation11,507
oauthDiscovery10,747
linkHeaders10,476
oauthProtectedResource9,903
ucp9,125
contentSignals9,031
apiCatalog502
agentSkills395
mcpServerCard358
webBotAuth62
a2aAgentCard47
acp15

Country activity

Use geography as a planning signal before changing crawl policy or regional infrastructure.

Why This Matters

Agent standards make sites easier for AI systems to navigate without scraping brittle UI assumptions.

What To Do

  • Start with robots.txt, sitemap, and API docs.
  • Add markdown negotiation where it preserves meaning.
  • Expose machine-readable service descriptions for repeatable agent use.
Data source: Cloudflare Radar. Processed by LLMBase for publisher and agent-readiness workflows.