developers.cloudflare.com

• Homepage open to agent access — HTTP 200 text/html with 219652 bytes and 1341 words of visible text. Essential Critical Adopted ⌄

  If an agent cannot read your site, every other check is moot. Cloudflare began blocking AI crawlers by default in 2025, with signed agents routed separately.

  Observation

  HTTP 200 · text/html · 219652 bytes · 23 ms

  id

  reachable

  weight

  3

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• /llms.txt published and well-structured — H1 "Cloudflare Developer Documentation", blockquote summary, 9 H2 sections with 113 markdown links, 16925 bytes. The scan requested 6 links it names, and each answered 2xx. Not requested: 107 same-origin links (the scan samples up to 6). Essential Critical Draft ⌄

  The most widely adopted contract for making a site legible to agents. In the curated corpus we measured, 46% of sites published one and the average quality score was 37 out of 100 — adoption is not the same as usefulness.

  Observation

  HTTP 200 · text/plain; charset=utf-8 · 16925 bytes · 22 ms · headings: Cloudflare Developer Documentation | Application performance | Application security | Cloudflare One | Consumer service…

  id

  llms-txt

  weight

  3

  points

  1.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  llmstxt.org

  Reproduction command and full detail →

• Discovery via Link response headers — 4 Link entrys, 3 carrying a discovery relation (rel=service-doc → /api/). Emerging Medium Adopted ⌄

  RFC 8288 Link headers let an agent find your discovery resources without parsing HTML.

  Observation

  link: </api/>; rel="service-doc", <https://developers.cloudflare.com/.well-known/ard.json>; rel="ard", <https://developers.cloudflare.com/llms.txt>; rel="describedby"; type="text/plain", <https://developers.cloudflare.com/index.md>; rel="alternate"; type="text/markdown"

  id

  link-headers

  weight

  2

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 8288

  Reproduction command and full detail →

• Canonical and hreflang discipline — 1 canonical, absolute and self-referential on https, no hreflang alternates declared. Recommended Medium Adopted ⌄

  An agent needs one consistent URL per important page.

  Observation

  <link rel="canonical" href="https://developers.cloudflare.com/">

  id

  canonical

  weight

  2

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• Markdown content negotiation — Content-Type text/markdown with Vary: accept-encoding, accept on the negotiated response (HTTP 200). Recommended Critical Adopted ⌄

  Agents can request a markup-free version with "Accept: text/markdown", which cuts token cost.

  Observation

  status: 200; content-type: text/markdown; charset=utf-8; vary: accept-encoding, accept; markdown body: yes

  id

  markdown-negotiation

  weight

  3

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 9110

  Reproduction command and full detail →

• Semantic heading structure — 1 H1 with 7 H2s and 24 H3s, and no level in the outline is skipped. Essential High Adopted ⌄

  A single H1 and a consistent H2 structure let the content be split correctly.

  Observation

  outline: H1 H2 H2 H3 H3 H3 H3 H2 H3 H2 H3 H3 H3 H3 H3 H3 H3 H3 H2 H3 H4 H4 H4 H3 H4 H4 H4 H2 H3 H3 H3 H3 H3 H3 H2 H3 H3 H3

  id

  headings

  weight

  2

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  WCAG 2.2

  Reproduction command and full detail →

• JSON-LD structured data — 1 JSON-LD block parsed with a schema.org @context declaring WebPage (6 @types in total). Essential Critical Adopted ⌄

  The entity type becomes unambiguous to a machine. Without authoritative data, an agent answers from whatever it can scrape.

  Observation

  blocks: 1 total, 1 non-empty, 1 parsed; schema.org @context: yes; @types: WebPage, Organization, ImageObject, PostalAddress, ContactPoint, WebSite

  id

  jsonld

  weight

  3

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org

  Reproduction command and full detail →

• Language declaration and multilingual access — html lang="en" with 0 hreflang alternates to check. Recommended Medium Adopted ⌄

  A wrong language tag makes an agent misread the content.

  Observation

  html lang="en"; alternates: none; content-language: (none)

  id

  lang

  weight

  1

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• Content that needs no JavaScript — 9703 characters of static text and 1 H1 is in the HTML before any JavaScript runs. Essential High Adopted ⌄

  If content is only produced client-side, the page is empty for agents that do not run JavaScript.

  Observation

  static characters: 9703; H1 in static HTML: 1; characters inside noscript: 0; markup characters: 219627

  id

  no-js-fallback

  weight

  2

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• Per-page content separation (no SPA fallback) — Homepage and /docs ship different titles ("Cloudflare Developer Docs | Cloudflare …" vs "Docs directory | Cloudflare Docs") and different main text (20% word overlap). Emerging Medium Experimental ⌄

  A catch-all route returning the same skeleton for every URL makes pages indistinguishable to an agent.

  Observation

  compared / vs /docs; titles "Cloudflare Developer Docs | Cloudflare Docs" / "Docs directory | Cloudflare Docs"; skeleton 25%; main-text word overlap 20%; main text 12155 characters

  id

  spa-fallback

  weight

  2

  points

  1.00

  standard

  Experimental — An early convention that may still change shape.

  Reproduction command and full detail →

• Responsive markup — viewport content "width=device-width, initial-scale=1" sets width=device-width and leaves zoom unrestricted. Emerging Low Adopted ⌄

  Agent browsers mostly run at mobile scale.

  Observation

  viewport meta: width=device-width, initial-scale=1; media queries on the page: 0

  id

  viewport

  weight

  1

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• Content-Signal usage signals — 1 Content-Signal line in a robots.txt user-agent group, setting all three signals (search=yes, ai-input=yes, ai-train=yes). Recommended High Draft ⌄

  Declares how your content may be used, inside robots.txt. Cloudflare included this in its readiness checks.

  Observation

  robots.txt: ai-train=yes, search=yes, ai-input=yes

  id

  content-signal

  weight

  2

  points

  1.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  contentsignals.org

  Reproduction command and full detail →

• API catalog — Linkset at /.well-known/api-catalog carries 1 entry, and 1 of them pairs an anchor with a service-desc link, the first pointing at https://developers.cloudflare.com/openapi.json. The scan requested the same-origin service-desc target /openapi.json, which answered HTTP 200. Not scored: the service-doc target /api/ answered HTTP 200. Not scored: the status target is on www.cloudflarestatus.com, which this scan does not request. Recommended Medium Experimental ⌄

  Lets an agent see which capabilities are callable in a single document (RFC 9727).

  Observation

  relations: service-desc, service-doc, status; observed target: /openapi.json

  id

  api-catalog

  weight

  2

  points

  1.00

  standard

  Experimental — An early convention that may still change shape.

  standards

  RFC 9727

  Fix

  {
    "linkset": [
      {
        "anchor": "https://your-domain.example/apis/public_api",
        "service-desc": [
          { "href": "https://your-domain.example/openapi.json", "type": "application/json" }
        ],
        "service-doc": [
          { "href": "https://your-domain.example/docs/", "type": "text/html" }
        ],
        "status": [
          { "href": "https://your-domain.example/status.json", "type": "application/json" }
        ]
      }
    ]
  }

  Reproduction command and full detail →

• WebMCP browser tool declaration — WebMCP tools are declared at the homepage: 2 tools, each with a name, a description and a JSON Schema inputSchema. Emerging Medium Experimental ⌄

  WebMCP lets sites expose tools to in-browser agents. It is the only normative deliverable of the W3C Agentic Web WG.

  id

  webmcp

  weight

  2

  points

  1.00

  standard

  Experimental — An early convention that may still change shape.

  standards

  W3C WebMCP

  Fix

  {
    "tools": [
      {
        "name": "search_products",
        "title": "Search products",
        "description": "Search the public catalogue by free-text query and return matching products with prices.",
        "inputSchema": {
          "type": "object",
          "properties": {
            "query": { "type": "string", "description": "Free-text search query" },
            "limit": { "type": "integer", "minimum": 1, "maximum": 50, "default": 10 }
          },
          "required": ["query"],
          "additionalProperties": false
        }
      }
    ]
  }

  Reproduction command and full detail →

• ARD resource discovery manifest — ARD manifest at /.well-known/ard.json lists 3 entries, each with identifier, displayName and type plus exactly one of url or data. Emerging Low Experimental ⌄

  Cisco/Outshift's Agentic Resource Discovery specification; Lighthouse audits it too.

  id

  ard-manifest

  weight

  1

  points

  1.00

  standard

  Experimental — An early convention that may still change shape.

  standards

  ard-spec

  Fix

  {
    "entries": [
      {
        "identifier": "urn:air:your-domain.example:server:support",
        "displayName": "Example Support MCP Server",
        "type": "application/mcp-server-card+json",
        "url": "https://your-domain.example/.well-known/mcp/server-card.json",
        "description": "Tools for order status and returns."
      }
    ]
  }

  Reproduction command and full detail →

• Documentation reachable — Documentation is reachable at /api/ (Link header rel=service-doc) and returns HTTP 200 text/html with 22979 readable words. Recommended Medium Adopted ⌄

  An agent needs documentation to complete an integration on its own.

  id

  docs

  weight

  1

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <!-- Homepage <head>: tell agents where the public docs are -->
  <link rel="service-doc" href="/docs/" type="text/html">
  
  <!-- Homepage body: a real link, so crawlers and users both find it -->
  <a href="/docs/">Documentation and API reference</a>

  Reproduction command and full detail →

• robots.txt with agent directives — Only a blanket User-agent: * group is present (5 rules), with a Sitemap declared. Essential High Adopted ⌄

  The front door for agent traffic (RFC 9309).

  Observation

  HTTP 200 · text/plain · 1442 bytes · 21 ms · # As a condition of accessing this website, you agree to # abide by the following content signals: # (a) If a content-signal = yes, you may…

  id

  robots-txt

  weight

  2

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 9309

  Fix

  # https://example.com/robots.txt  (RFC 9309)
  User-agent: *
  Allow: /
  Disallow: /admin/
  
  User-agent: GPTBot
  Allow: /
  
  User-agent: ClaudeBot
  Allow: /
  
  Sitemap: https://example.com/sitemap.xml

  Reproduction command and full detail →

• sitemap.xml valid and current — sitemapindex with 1 child sitemap but none carrying <lastmod>. Essential High Adopted ⌄

  The primary URL discovery source for agent crawlers.

  Observation

  HTTP 200 · application/xml · 196 bytes · 25 ms · final https://developers.cloudflare.com/sitemap-index.xml

  id

  sitemap-xml

  weight

  2

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <?xml version="1.0" encoding="UTF-8"?>
  <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <url>
      <loc>https://example.com/</loc>
      <lastmod>2026-01-15</lastmod>
    </url>
    <url>
      <loc>https://example.com/docs/quickstart</loc>
      <lastmod>2026-01-15</lastmod>
    </url>
  </urlset>

  Reproduction command and full detail →

• /llms-full.txt expanded context — 259190 words of expanded page text in 3149824 bytes, but /llms.txt does not link to /llms-full.txt. Recommended Low Draft ⌄

  Lets an agent take in the full context in a single request instead of walking the site step by step.

  Observation

  HTTP 200 · text/markdown; charset=utf-8 · 3149824 bytes · 51 ms · --- description: Route traffic across the fastest network paths to reduce latency and packet loss. title: Argo Smart Ro…

  id

  llms-full

  weight

  1

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  # In /llms.txt, under Docs:
  - [Full context](https://example.com/llms-full.txt): Every key page as one document
  
  # /llms-full.txt
  # Example Inc - full context
  
  > Complete text of the pages an agent needs, in a single request. Regenerated on deploy.
  
  ## https://example.com/ (Home)
  
  Example Inc runs a payments API for marketplaces. Production traffic is served from three regions.
  
  ## https://example.com/pricing (Pricing)
  
  Starter is $0 for 1,000 calls per month. Growth is $99 for 100,000 calls.

  Reproduction command and full detail →

• Title and summary metadata — Both carriers are present but outside the band: title 43 characters (band 50-60) and description 39 characters (band 120-160). Essential High Adopted ⌄

  This is how an agent learns what a page is about without opening it.

  Observation

  title(43): Cloudflare Developer Docs | Cloudflare Docs | description(39): Connect, protect, and build everywhere.

  id

  meta

  weight

  2

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <head>
    <meta charset="utf-8" />
    <title>Agent readiness audit for e-commerce teams | Acme Inc</title>
    <meta
      name="description"
      content="Acme audits how well your store serves AI agents: 52 checks across discovery, content, bot access and commerce, each paired with a paste-ready fix."
    />
  </head>

  Reproduction command and full detail →

• Named AI bot rules in robots.txt — 0 of 18 named AI bots addressed: the only 5 robots.txt rules sit in the User-agent: * group. Essential High Draft ⌄

  Naming agent crawlers explicitly is the first step to being visible in agent traffic.

  Observation

  # As a condition of accessing this website, you agree to # abide by the following content signals: # (a) If a content-signal = yes, you may collect content # for the corresponding use. # (b) If a content-signal = no, you may not collect co…

  id

  ai-rules

  weight

  2

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  standards

  RFC 9309

  Fix

  # robots.txt - named AI agents, each with a rule of its own.
  User-agent: OAI-SearchBot
  Allow: /
  User-agent: ChatGPT-User
  Allow: /
  User-agent: Claude-User
  Allow: /
  User-agent: PerplexityBot
  Allow: /
  User-agent: GPTBot
  Disallow: /
  User-agent: CCBot
  Disallow: /
  User-agent: *
  Allow: /
  Sitemap: https://example.com/sitemap.xml

  Reproduction command and full detail →

• AI usage policy page — AI policy at /ai covers 1 of 3 expected topics (a contact route stated; permitted uses and prohibited uses missing) and is not linked from the home page. Essential High Adopted ⌄

  States the rules agents must follow and reduces licensing ambiguity.

  Observation

  overview · cloudflare ai docs skip to content documentation index fetch the complete documentation index at: https://developers.cloudflare.com/ai/llms.txt use this file to discover all available pages before exploring further. docs directory api sdks changelo…

  id

  ai-policy

  weight

  2

  points

  0.35

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <!doctype html>
  <html lang="en">
  <head><meta charset="utf-8"><title>AI usage policy</title></head>
  <body>
    <h1>AI usage policy</h1>
    <h2>Permitted</h2>
    <p>Indexing, retrieval and citation by identified search and answer engines.</p>
    <h2>Not permitted</h2>
    <p>Do not train, fine-tune or distil a model on this content; no bulk scraping or resale.</p>
    <h2>Contact</h2>
    <p><a href="mailto:agents@example.com">agents@example.com</a></p>
  </body>
  </html>

  Reproduction command and full detail →

• Crawler and agent policy page — Bot policy at /agents covers 2 of 4 expected topics (welcomed agents and a contact route stated; refused agents and identity verification missing) and is linked from the home page. Recommended Medium Adopted ⌄

  Explains which agents are permitted and how they are verified.

  Observation

  agents · cloudflare agents docs skip to content documentation index fetch the complete documentation index at: https://developers.cloudflare.com/agents/llms.txt use this file to discover all available pages before exploring further. docs directory api sdks ch…

  id

  bot-page

  weight

  1

  points

  0.40

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <!doctype html>
  <html lang="en">
  <head><meta charset="utf-8"><title>Bot policy</title></head>
  <body>
  <h1>Bot and agent policy</h1>
  <h2>Welcome</h2>
  <p>Identified search and answer engines that cite the source.</p>
  <h2>Refused</h2>
  <p>Training crawlers, spoofed User-Agents, clients that ignore robots.txt.</p>
  <h2>How we verify identity</h2>
  <p>Signed requests are checked against our key directory at /.well-known/http-message-signatures-directory; unsigned clients by published IP ranges.</p>
  <h2>Contact</h2>
  <p><a href="mailto:agents@example.com">agents@example.com</a></p>
  </body>
  </html>

  Reproduction command and full detail →

• MCP server card — MCP server card at /.well-known/mcp/server-card.json carries name, version and description for com.cloudflare/mcp but its 7 remotes entries yield 0 usable transports, so an agent learns the server exists but not where to connect. Essential High Draft ⌄

  Since MCP 2026-07-28, agents discover tool servers through a published declaration.

  id

  mcp-card

  weight

  2

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  standards

  MCP 2026-07-28

  Fix

  {
    "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
    "name": "com.example/weather",
    "version": "1.0.0",
    "description": "Live weather and forecast data for partner agents.",
    "title": "Example Weather",
    "websiteUrl": "https://your-domain.example/developers",
    "remotes": [
      {
        "type": "streamable-http",
        "url": "https://your-domain.example/mcp",
        "supportedProtocolVersions": ["2026-07-28"]
      }
    ]
  }

  Reproduction command and full detail →

• OpenAPI definition — The API description advertised by api-catalog service-desc (/.well-known/api-catalog) points at /openapi.json, which answered not an OpenAPI 3.x document, and the other 5 candidate paths yielded no OpenAPI 3.x document. Essential High Adopted ⌄

  A machine-readable contract so an agent can discover your API and generate correct calls.

  Observation

  tried: /openapi.json 200 | /api/ 200 html | /openapi.yaml 404 | /.well-known/openapi.json 404 | /api/openapi.json 404 | /swagger.json 404

  id

  openapi

  weight

  2

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  standards

  OpenAPI 3.x

  Fix

  {
    "openapi": "3.1.0",
    "info": { "title": "Example Public API", "version": "1.4.0" },
    "servers": [{ "url": "https://api.your-domain.example/v1" }],
    "paths": {
      "/orders/{orderId}": {
        "get": {
          "operationId": "getOrder",
          "summary": "Get the status of one order",
          "parameters": [{ "name": "orderId", "in": "path", "required": true, "schema": { "type": "string" } }],
          "responses": { "200": { "description": "The order" } }
        }
      }
    }
  }

  Reproduction command and full detail →

• Service/product scope machine-readable — Homepage JSON-LD carries only 2 generic Organization or WebSite nodes across 1 model types, so what is offered and to whom is not readable. Recommended High Draft ⌄

  An agent must be able to answer "what does this site offer, and to whom".

  id

  service-schema

  weight

  2

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  {
    "@context": "https://schema.org",
    "@type": "Service",
    "name": "Agent readiness audit",
    "serviceType": "Website agent-readiness audit and remediation",
    "provider": { "@type": "Organization", "name": "Example Inc.", "url": "https://your-domain.example" },
    "areaServed": [{ "@type": "Country", "name": "United States" }],
    "audience": { "@type": "BusinessAudience", "name": "E-commerce and SaaS teams" }
  }

  Reproduction command and full detail →

• Structured contact information — Homepage JSON-LD declares 1 organization node with 0 contact details while the page itself carries 0 plain-text contact signals. Emerging Medium Adopted ⌄

  An agent must know where to reach you before starting a transaction, or when something fails.

  id

  contact

  weight

  1

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/Organization

  Fix

  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Example Inc.",
    "url": "https://your-domain.example",
    "contactPoint": [
      {
        "@type": "ContactPoint",
        "contactType": "technical support",
        "email": "agents@your-domain.example",
        "telephone": "+1-555-0100",
        "availableLanguage": ["en"]
      }
    ]
  }

  Reproduction command and full detail →

• Service status and changelog feed — The homepage advertises 1 status or feed reference, but the status document at https://www.cloudflarestatus.com/ was not fetched by this scan, so its response was not observed. Emerging Low Adopted ⌄

  An agent should be able to learn about outages and API changes in a machine-readable way.

  id

  status-page

  weight

  1

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <!-- Homepage <head>: advertise machine-readable status and history -->
  <link rel="alternate" type="application/atom+xml" title="Service status"
        href="/status/feed.atom">
  <link rel="alternate" type="application/atom+xml" title="Changelog"
        href="/changelog/feed.atom">
  
  <!-- Homepage body: links a user (or a crawler) can follow -->
  <a href="/status/">Service status</a>
  <a href="/changelog/">Changelog</a>

  Reproduction command and full detail →

• Agent traffic measurement — No analytics vendor signature among the 8 checked appears in the homepage source, so nothing about the agent channel can be attributed. conditional Emerging Low Draft ⌄

  If agent traffic is not measured separately, the channel's return is invisible and never funded.

  Observation

  homepage 219652 bytes; vendors: none; markers: tracking-widest uppercase">agen…

  id

  agent-analytics

  weight

  1

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• Sandbox or test environment documented — A sandbox is referenced at /sandbox but it mentions a sandbox in 2 documents but names no non-production base URL, so an agent cannot integrate safely. Recommended Medium Experimental ⌄

  An agent cannot safely integrate against a production endpoint; a documented sandbox is the difference between a working trial and a support ticket.

  id

  sandbox-environment

  weight

  2

  points

  0.50

  standard

  Experimental — An early convention that may still change shape.

  Fix

  {
    "openapi": "3.1.0",
    "info": {
      "title": "Example API",
      "version": "1.4.0",
      "description": "Sandbox base URL https://api.sandbox.example.com/v1; test keys at https://example.com/docs/sandbox; no live payments, resets nightly."
    },
    "servers": [
      { "url": "https://api.example.com/v1", "description": "Production" },
      { "url": "https://api.sandbox.example.com/v1", "description": "Sandbox - test keys only" }
    ],
    "paths": {
      "/ping": {
        "get": { "operationId": "ping", "responses": { "200": { "description": "reachable" } } }
      }
    }
  }

  Reproduction command and full detail →

• Rate limits and quotas documented — Rate limiting is acknowledged through 0 numeric limits, 0 windows and 11 scope declarations in /docs with 0 quota headers observed, but no single statement carries a limit with its unit, window, scope and the behaviour on exceed. Recommended Medium Experimental ⌄

  An agent that does not know the quota discovers it by being throttled, halfway through a task it cannot resume.

  Observation

  observed headers: none

  id

  rate-limits-declared

  weight

  1

  points

  0.50

  standard

  Experimental — An early convention that may still change shape.

  standards

  RFC 9110

  Fix

  ## Rate limits
  
  Every endpoint is limited per API key; anonymous requests are limited per IP.
  
  | Scope | Limit | Window | On exceed |
  | --- | --- | --- | --- |
  | API key | 1000 requests | 1 hour | 429 + Retry-After (seconds) |
  | API key, burst | 20 requests | 1 second | 429 + Retry-After (seconds) |
  | Anonymous, per IP | 60 requests | 1 minute | 429 + Retry-After (seconds) |
  
  Responses carry RateLimit-Policy and RateLimit; a throttled request returns 429 with
  Retry-After. Machine-readable copy: https://your-domain.example/rate-limits.json

  Reproduction command and full detail →

• DNS-AID discovery record — 0 SVCB records and 0 TXT records resolve at _index._agents.developers.cloudflare.com and _agent.developers.cloudflare.com. Emerging Medium Experimental ⌄

  Lets agents read discovery information over DNS without an HTTP round trip. Cloudflare added it to its readiness checklist.

  Observation

  DNS-AID names queried for SVCB and TXT records: _index._agents.developers.cloudflare.com and _agent.developers.cloudflare.com

  id

  dns-aid

  weight

  2

  points

  0.00

  standard

  Experimental — An early convention that may still change shape.

  Fix

  ; DNS-AID (draft-mozleywilliams-dnsop-dnsaid)
  _index._agents.example.com. 3600 IN SVCB 1 agent-index.example.com (
      alpn="h2"
      port=443
      well-known=agent-card.json
  )
  
  assistant.example.com. 3600 IN SVCB 1 . (
      alpn="mcp,h2"
      port=443
      well-known=agent-card.json
      cap=https://example.com/.well-known/agent-card.json
  )

  Reproduction command and full detail →

• AGENTS.md with the required sections — Not found (HTTP 404, 307 bytes). Recommended High Draft ⌄

  The instruction file for coding and operations agents. It fails more often than any other check in the curated corpus we measured, and the usual reason is not a missing file but a file without the sections an agent needs.

  Observation

  HTTP 404 · text/markdown; charset=utf-8 · 307 bytes · 4 ms

  id

  agents-md

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  # AGENTS.md
  
  ## Project overview
  Example Inc is a payments API for marketplaces. Docs: https://example.com/docs
  
  ## Setup and build
  - `pnpm install`
  - `pnpm dev` -> http://localhost:3000
  - `pnpm build`
  
  ## Testing
  - `pnpm test`; lint and types: `pnpm lint && pnpm typecheck`
  
  ## Conventions
  - TypeScript strict mode; no `any` in exported signatures.
  - Public API routes live in `src/routes/api/`.
  
  ## Security and contact
  - Never commit secrets; use `.env.local`.
  - Report vulnerabilities to security@example.com.

  Reproduction command and full detail →

• /sitemap.md markdown site map — Not found (HTTP 404, 307 bytes). Emerging Low Draft ⌄

  Lets an agent read your site structure as markdown in a single file. Adoption is still very low, so this is an early-mover advantage.

  Observation

  HTTP 404 · text/markdown; charset=utf-8 · 307 bytes · 3 ms

  id

  sitemap-md

  weight

  1

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  # Sitemap
  
  - [Home](https://example.com/): What Example Inc does and who it is for
  - [Quickstart](https://example.com/docs/quickstart): First API call in five minutes
  - [API reference](https://example.com/docs/api): Every endpoint and response field
  - [Pricing](https://example.com/pricing): Plans, limits and overage rates
  - [Status](https://example.com/status): Live service status and incident history
  - [Contact](https://example.com/contact): Sales and support routes

  Reproduction command and full detail →

• FAQ / question-answer schema — No FAQPage entity among 1 parsed JSON-LD block on the homepage. Recommended High Draft ⌄

  Question-and-answer content is the type agents quote most.

  Observation

  @types: WebPage, Organization, ImageObject, PostalAddress, ContactPoint, WebSite

  id

  faq-schema

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  schema.org/FAQPage

  Fix

  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What does an agent readiness audit measure?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Fifty-two checks across discovery, content, bot access, protocol and commerce, each scored and paired with a fix."
        }
      }
    ]
  }
  </script>

  Reproduction command and full detail →

• Breadcrumb / navigation schema — No BreadcrumbList entity among 1 parsed JSON-LD block on the homepage. Emerging Low Draft ⌄

  Helps an agent make sense of where a page sits in your site.

  Observation

  @types: WebPage, Organization, ImageObject, PostalAddress, ContactPoint, WebSite

  id

  breadcrumb

  weight

  1

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  schema.org/BreadcrumbList

  Fix

  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com/" },
      { "@type": "ListItem", "position": 2, "name": "Checks", "item": "https://www.example.com/checks" },
      { "@type": "ListItem", "position": 3, "name": "Structured data", "item": "https://www.example.com/checks/jsonld" }
    ]
  }
  </script>

  Reproduction command and full detail →

• Prominent summary block — The first 1000 characters of main content hold no paragraph or summary block (6183 characters of main text). Recommended Medium Draft ⌄

  The llms.txt contract recommends a short summary at the top of every page; agents quote it directly.

  Observation

  Cloudflare Developer Docs Explore guides and tutorials to start building on Cloudflare's platform Get started Copy prompt Prompt copied! Meet the Agentic Internet Builders IRL Connect brings the Cloud

  id

  summary

  weight

  1

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  <main>
    <h1>Token efficiency for agent-readable pages</h1>
    <p class="summary">
      Content-to-markup ratio is the share of a page's bytes an agent can read: below 15% most of the
      HTML is scaffolding, and every wrapper div is billed to someone's context window.
    </p>
    <h2>How the ratio is measured</h2>
    <p>Script, style and template blocks are removed, the remaining tags are stripped, and the visible
    characters are divided by the raw HTML size.</p>
  </main>

  Reproduction command and full detail →

• Token efficiency (content-to-markup ratio) — Content-to-markup ratio 4.4% (9703 visible of 219627 markup characters, ~1810 tokens), below the 8% floor where markup outweighs the content. Recommended Medium Draft ⌄

  A bloated DOM wastes an agent's context window.

  Observation

  visible characters: 9703; markup characters: 219627; words: 1341; estimated tokens: 1810

  id

  token-efficiency

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  // scripts/tighten-html.mjs - run after the build over every emitted page.
  import { readdirSync, readFileSync, writeFileSync } from 'node:fs';
  import { minify } from 'html-minifier-terser';
  
  const pages = readdirSync('dist', { recursive: true, encoding: 'utf8' }).filter((p) => p.endsWith('.html'));
  
  for (const page of pages) {
    const file = `dist/${page}`;
    const before = readFileSync(file, 'utf8');
    const after = await minify(before, {
      collapseWhitespace: true,
      removeComments: true,
      removeRedundantAttributes: true,
      minifyCSS: true,
      minifyJS: true,
    });
    writeFileSync(file, after);
  }

  Reproduction command and full detail →

• Web Bot Auth key directory — /.well-known/http-message-signatures-directory answered HTTP 404, not a JWK Set. Essential Critical Draft ⌄

  RFC 9421 with Ed25519: the mechanism that lets a site verify which agent is calling rather than guessing from a user-agent string. Adoption in the curated corpus we measured is around one site in a hundred.

  Observation

  # 404 Page not found The page you requested does not exist or has moved. Browse the documentation via [llms.txt](/llms.txt). Search the documentation via the [AI Search API](https://ai-search.developers.cloudflare.com/a…

  id

  webbotauth

  weight

  3

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  RFC 9421

  Reproduction command and full detail →

• Agent permission model (agent-permissions.json) — Neither path served a permission document (/.well-known/agent-permissions.json HTTP 404, /agent-permissions.json HTTP 404). Essential Critical Experimental ⌄

  Declares which actions an agent may take, which are refused, and which need a person. It is the difference between a policy and a wish: in the curated corpus we measured, roughly one site in a hundred publishes one.

  id

  agent-permissions

  weight

  3

  points

  0.00

  standard

  Experimental — An early convention that may still change shape.

  Reproduction command and full detail →

• security.txt (RFC 9116) — No security.txt was served (/.well-known/security.txt HTTP 404, /security.txt HTTP 404). Recommended Low Adopted ⌄

  Provides a responsible disclosure channel for agent-related security incidents.

  id

  security-txt

  weight

  1

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 9116

  Fix

  # security.txt - RFC 9116
  Contact: mailto:security@example.com
  Expires: 2027-09-30T18:37:07Z
  Canonical: https://example.com/.well-known/security.txt
  Preferred-Languages: en
  Policy: https://example.com/security-policy

  Reproduction command and full detail →

• Crawl rate declaration — No Crawl-delay line in 1 robots.txt group, so no crawl rate is declared. Emerging Low Adopted ⌄

  Cloudflare's Verified Bots policy drops AI crawlers that ignore crawl-delay.

  Observation

  # As a condition of accessing this website, you agree to # abide by the following content signals: # (a) If a content-signal = yes, you may collect content # for the corresponding use. # (b) If a content-signal = no, you may not collect co…

  id

  crawl-delay

  weight

  1

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  # robots.txt - a crawl rate inside the group it applies to.
  User-agent: *
  Crawl-delay: 1
  
  User-agent: OAI-SearchBot
  Crawl-delay: 1
  
  User-agent: GPTBot
  Crawl-delay: 10

  Reproduction command and full detail →

• /ai.txt access declaration — /ai.txt answered HTTP 404, not an access declaration. Emerging Low Draft ⌄

  Some agent ecosystems read an /ai.txt contract alongside robots.txt.

  Observation

  # 404 Page not found The page you requested does not exist or has moved. Browse the documentation via [llms.txt](/llms.txt). Search the documentation via the [AI Search API](https://ai-search.developers.cloudflare.com/a…

  id

  ai-txt

  weight

  1

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• OAuth discovery documents — None of the 3 OAuth discovery paths returned a JSON document (/.well-known/oauth-authorization-server 404 text/markdown; /.well-known/openid-configuration 404 text/markdown; /.well-known/oauth-protected-resource 404 text/markdown). Essential High Adopted ⌄

  Required for agents to connect to your authenticated API on their own (RFC 8414 / RFC 9728).

  id

  oauth-discovery

  weight

  2

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 8414, RFC 9728

  Fix

  {
    "resource": "https://api.your-domain.example/",
    "resource_name": "Example API",
    "resource_logo_uri": "https://your-domain.example/logo.png",
    "authorization_servers": ["https://auth.your-domain.example/"],
    "scopes_supported": ["api.read", "api.write"],
    "bearer_methods_supported": ["header"]
  }

  Reproduction command and full detail →

• Agent Skills declaration — The skills index declares a sha256 digest that does not match the bytes of the artifact it names. The artifact was fetched and hashed; a digest is a claim about content, and this one is false. Recommended Medium Draft ⌄

  Offers ready-made capability packages to agent runtimes.

  id

  agent-skills

  weight

  1

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• A2A agent card — No A2A agent card was served as JSON at the 2 declared paths (/.well-known/agent-card.json 404 text/markdown; /.well-known/agent.json 404 text/markdown). Recommended Medium Draft ⌄

  A2A v1.0 (Linux Foundation) is the emerging standard for agent-to-agent discovery. Almost no site publishes a card yet, which makes this one of the cheapest places to be early.

  id

  a2a-card

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  A2A v1.0

  Fix

  {
    "name": "Example Support Agent",
    "description": "Answers product and billing questions for partner agents.",
    "version": "1.0.0",
    "supportedInterfaces": [
      { "url": "https://your-domain.example/a2a/v1", "protocolBinding": "JSONRPC", "protocolVersion": "1.0" }
    ],
    "capabilities": { "streaming": true },
    "defaultInputModes": ["text/plain"],
    "defaultOutputModes": ["text/plain"],
    "skills": [
      {
        "id": "billing-question",
        "name": "Billing question",
        "description": "Answers invoice questions for one account.",
        "tags": ["billing"]
      }
    ]
  }

  Reproduction command and full detail →

• /auth.md agent authentication guide — No markdown authentication guide was served at the 2 declared paths (/auth.md 404 text/markdown; /.well-known/auth.md 404 text/markdown). Emerging Medium Draft ⌄

  A guide telling an agent which authentication flow to use.

  id

  auth-md

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  # auth.md
  
  Agents authenticate here: discover, register, claim if needed, call.
  
  ## Methods
  - `identity_assertion`: you hold an ID-JAG bound to this `resource`.
  - `service_auth`: you have the user's verified email; a claim follows.
  - `anonymous`: no user identity yet.
  
  ## Endpoints
  GET https://api.your-domain.example/.well-known/oauth-protected-resource
  POST `agent_auth.identity_endpoint`, then `agent_auth.claim_endpoint` when claim is
  required; exchange at `token_endpoint` for an access_token.

  Reproduction command and full detail →

• Structured pricing information — The homepage JSON-LD carries 1 model types with 0 Offer nodes and 0 price statements. Recommended High Adopted ⌄

  An offer without a price cannot be compared by an agent — you drop out of consideration.

  id

  pricing-structured

  weight

  2

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/Offer

  Fix

  {
    "@context": "https://schema.org",
    "@type": "Service",
    "name": "Agent Readiness Audit",
    "offers": {
      "@type": "Offer",
      "price": "490.00",
      "priceCurrency": "USD",
      "availability": "https://schema.org/InStock",
      "priceSpecification": {
        "@type": "UnitPriceSpecification",
        "price": "490.00",
        "priceCurrency": "USD"
      }
    }
  }

  Reproduction command and full detail →

• Product/catalog schema — No Product, Offer or AggregateOffer type appears in the homepage JSON-LD (6 types) or in the JSON-LD of the 1 readable product or collection page. conditional Essential Critical Adopted ⌄

  Product data is the most valuable and the least machine-readable: price, availability and returns are usually rendered for a person to read and never declared for a machine to parse.

  Observation

  homepage @type: WebPage, Organization, ImageObject, PostalAddress, ContactPoint, WebSite; product paths: /products HTTP 200, /shop HTTP 404, /store HTTP 404

  id

  product-schema

  weight

  3

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/Product

  Fix

  {
    "@context": "https://schema.org",
    "@type": "Product",
    "name": "Aurora Desk Lamp",
    "sku": "ADL-100-BLK",
    "offers": {
      "@type": "Offer",
      "price": "1299.00",
      "priceCurrency": "USD",
      "availability": "https://schema.org/InStock"
    }
  }

  Reproduction command and full detail →

• Agent payment standard support (AP2/ACP/x402/UCP) — None of AP2, ACP, x402 or UCP is named on the 1 readable payment and policy pages, and no UCP manifest or agent-purchase wording was found. conditional Recommended High Draft ⌄

  The least-implemented surface in the rubric. Accepting an agent payment means choosing a standard and changing a checkout, which is a business decision most sites have not made yet.

  Observation

  /.well-known/ucp HTTP 404, /ai-policy HTTP 404, /agent-policy HTTP 404, /pricing HTTP 404, /agentic-commerce HTTP 404, /developers HTTP 404, /docs HTTP 200, /faq HTTP 404

  id

  payment-protocols

  weight

  3

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  AP2, ACP, x402, UCP

  Reproduction command and full detail →

• Agent purchase policy — No page among the 5 agent policy paths carries both an agent word and a purchase word (/ai-policy HTTP 404, /agent-policy HTTP 404, /terms HTTP 404, /agentic-commerce HTTP 404, /ai HTTP 200). conditional Recommended High Draft ⌄

  Liability is the open question in agent commerce, and it is a policy decision rather than a technical one: a site that accepts an agent purchase has to decide who carries the cost when the agent is wrong, and publish that decision where an agent can read it.

  Observation

  readable pages: /ai

  id

  agent-purchase

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• UCP manifest (/.well-known/ucp) — Neither /.well-known/ucp nor /.well-known/ucp.json returned HTTP 200 (/.well-known/ucp HTTP 404, /.well-known/ucp.json HTTP 404), so no manifest was served. conditional Emerging Medium Draft ⌄

  Google and Shopify's Universal Commerce Protocol; lets a merchant declare checkout capabilities at transaction time.

  id

  ucp-manifest

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  {
    "protocol_version": "1.0",
    "merchant": { "id": "shop.example.com", "name": "Example Shop", "url": "https://shop.example.com" },
    "capabilities": { "catalog_search": true, "product_detail": true, "cart": true, "checkout": true },
    "checkout": {
      "endpoint": "https://shop.example.com/api/ucp/checkout",
      "payment_handlers": ["ap2", "acp", "x402"]
    }
  }

  Reproduction command and full detail →

• Return and shipping terms machine-readable — No return or shipping page responded (/returns HTTP 404, /shipping HTTP 404, /refund-policy HTTP 404) and the homepage JSON-LD declares neither MerchantReturnPolicy nor OfferShippingDetails. conditional Recommended Medium Adopted ⌄

  An agent must verify return terms before making a purchase decision.

  Observation

  homepage @type: WebPage

  id

  returns

  weight

  1

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/MerchantReturnPolicy

  Fix

  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "merchantReturnDays": 14,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    },
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": { "@type": "MonetaryAmount", "value": "49.00", "currency": "USD" }
    }
  }

  Reproduction command and full detail →

The scanner could not observe these checks. Under rubric v0.7, each one stays in the denominator at 0 points, the same as a missing check.

• Cryptographically signed agent card — No A2A agent card is published, so there are no signatures to inspect and the check is not scored. Emerging Medium Draft ⌄

  A2A v1.0 makes identity verifiable through JWS (RFC 7515).

  id

  a2a-signed

  weight

  1

  points

  not counted

  standard

  Draft — A published specification that is not yet ratified.

  standards

  RFC 7515

  Reproduction command and full detail →

The scan did not ask this site for these checks. Each applies to a site profile the scan did not confirm here, or needs a commercial signal it did not detect. They left the denominator. They are not failures, and they are not requests. If this report asks you to fix something that does not apply to your site, the error is ours, not yours.

• Inventory and price freshness — Not scored: this check applies to ecommerce or marketplace sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Recommended High Adopted ⌄

  An agent that cannot tell whether an item is in stock — or when a price was last valid — will quote a stale offer to a buyer, or refuse to quote at all.

  id

  inventory-freshness

  weight

  2

  points

  not counted

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/Offer

  Reproduction command and full detail →

• Seller identity declared — Not scored: this check applies to ecommerce or marketplace sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Recommended Medium Adopted ⌄

  On a marketplace an offer is meaningless without knowing who is selling and who is the merchant of record, because that is who the agent has a contract with.

  id

  seller-identity

  weight

  2

  points

  not counted

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/Organization

  Reproduction command and full detail →

• Shipping cost and delivery declared — Not scored: this check applies to ecommerce or marketplace sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Recommended High Adopted ⌄

  A purchase agent that cannot compute the delivered total cannot complete a checkout, and returns to the merchant without it.

  id

  shipping-costs

  weight

  2

  points

  not counted

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/OfferShippingDetails

  Reproduction command and full detail →

• Reuse and licensing terms declared — Not scored: this check applies to publisher or institution sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Recommended High Draft ⌄

  Declaring ai-train=no without stating a licensing path leaves both the publisher and the agent without an answer they can act on.

  id

  licensing-terms

  weight

  2

  points

  not counted

  standard

  Draft — A published specification that is not yet ratified.

  standards

  TDM Reservation Protocol

  Reproduction command and full detail →

• Content provenance declared — Not scored: this check applies to publisher or institution sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Emerging Medium Draft ⌄

  Author, publication date and update date are what let an agent judge whether a source is current and attributable before it quotes it.

  id

  provenance-declared

  weight

  1

  points

  not counted

  standard

  Draft — A published specification that is not yet ratified.

  standards

  schema.org/author, C2PA

  Reproduction command and full detail →

• Machine-readable booking action — Not scored: this check applies to services sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Recommended Medium Draft ⌄

  For a service business the agent's task is to book, not to browse — a declared action is what turns a contact page into a completed job.

  id

  booking-action

  weight

  2

  points

  not counted

  standard

  Draft — A published specification that is not yet ratified.

  standards

  schema.org/ReserveAction

  Reproduction command and full detail →

• Documents in machine-readable formats — Not scored: this check applies to institution sites; this site was measured as api. It is excluded from the denominator rather than counted as a failure. Recommended Medium Draft ⌄

  A PDF that carries no document structure is unreadable to an agent and to a screen reader alike — the same defect, found twice.

  id

  document-formats

  weight

  2

  points

  not counted

  standard

  Draft — A published specification that is not yet ratified.

  standards

  PDF/UA

  Reproduction command and full detail →