vercel.com

• Homepage open to agent access — HTTP 200 text/html; charset=utf-8 with 603262 bytes and 534 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; charset=utf-8 · 603262 bytes · 248 ms

  id

  reachable

  weight

  3

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• sitemap.xml valid and current — 8618 absolute URLs, 8618 with <lastmod>. Essential High Adopted ⌄

  The primary URL discovery source for agent crawlers.

  Observation

  HTTP 200 · application/xml; charset=utf-8 · 1201699 bytes · 2027 ms · final https://vercel.com/crawled-sitemap.xml · root <urlset>

  id

  sitemap-xml

  weight

  2

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• /llms.txt published and well-structured — H1 "Vercel", blockquote summary, 7 H2 sections with 25 markdown links, 4935 bytes. The scan requested 8 links it names, and each answered 2xx. Not requested: 17 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 · 4935 bytes · 334 ms · headings: Vercel | When to use Vercel | How agents should use Vercel | Agent setup | Documentation | REST API and developer resou…

  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 — 3 Link entrys, 1 carrying a discovery relation (rel=api-catalog → /.well-known/api-catalog). Emerging Medium Adopted ⌄

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

  Observation

  link: </.well-known/api-catalog>; rel="api-catalog", </.well-known/ai-catalog.json>; rel="ai-catalog"; type="application/ai-catalog+json", </.well-known/agent-skills/index.json>; rel="agent-skills"; type="application/json"

  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://vercel.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, accept-encoding 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, accept-encoding; 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 17 H2s and 0 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 H2 H2 H2 H2 H2 H2 H2 H2 H2 H2 H2 H2 H2 H2 H2

  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 — 3 JSON-LD blocks parsed with a schema.org @context declaring Organization (8 @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: 3 total, 3 non-empty, 3 parsed; schema.org @context: yes; @types: Organization, ImageObject, Person, ContactPoint, PostalAddress, Service, SoftwareApplication, Offer

  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 — 3680 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: 3680; H1 in static HTML: 1; characters inside noscript: 0; markup characters: 603176

  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 /about ship different titles ("Agentic Infrastructure - Vercel" vs "About Us") and different main text (9% 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 /about; titles "Agentic Infrastructure - Vercel" / "About Us"; skeleton 87%; main-text word overlap 9%; main text 1346 characters

  id

  spa-fallback

  weight

  2

  points

  1.00

  standard

  Experimental — An early convention that may still change shape.

  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=no). Recommended High Draft ⌄

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

  Observation

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

  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 →

• security.txt (RFC 9116) — security.txt at /.well-known/security.txt declares 2 Contacts and an Expires 2027-09-28T12:00:00.000Z in the future. Not scored: its Policy URL is on security.vercel.com, which this scan does not request. Recommended Low Adopted ⌄

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

  Observation

  Contact: https://hackerone.com/vercel Contact: mailto:responsible.disclosure@vercel.com Expires: 2027-09-28T12:00:00.000Z Preferred-Languages: en Policy: https://security.vercel.com/ Canonical: https://vercel.com/.well-known/security.txt Hiring: https://verce…

  id

  security-txt

  weight

  1

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 9116

  Reproduction command and full detail →

• OAuth discovery documents — RFC 8414 metadata at /.well-known/openid-configuration declares issuer https://vercel.com, authorization_endpoint, token_endpoint and 1 response type. 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

  1.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 →

• ARD resource discovery manifest — ARD manifest at /.well-known/ai-catalog.json lists 4 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 /docs (homepage anchor) and returns HTTP 200 text/html with 1371 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 →

• Structured pricing information — Homepage JSON-LD carries 1 complete offer node, the first stating price 0 with priceCurrency USD and availability https://schema.org/OnlineOnly. Recommended High Adopted ⌄

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

  Observation

  {"price":0,"priceCurrency":"USD","availability":"https://schema.org/OnlineOnly"}

  id

  pricing-structured

  weight

  2

  points

  1.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 →

• Service/product scope machine-readable — Homepage JSON-LD declares a service-like node offering "Agentic infrastructure platform" from Vercel Inc. to Worldwide, among 10 total model nodes. Recommended High Draft ⌄

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

  id

  service-schema

  weight

  2

  points

  1.00

  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 →

• Product/catalog schema — Homepage JSON-LD declares Offer among its 8 schema types. 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: Organization, Service, SoftwareApplication, Offer, ImageObject, Person, ContactPoint, PostalAddress

  id

  product-schema

  weight

  3

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org/Product

  Reproduction command and full detail →

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

  The front door for agent traffic (RFC 9309).

  Observation

  HTTP 200 · text/plain; charset=utf-8 · 629 bytes · 206 ms · User-Agent: * Content-Signal: search=yes, ai-input=yes, ai-train=no # Allow robots to be able to crawl the OG Image API route and all the s…

  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 →

• AGENTS.md with the required sections — Served as text/html; charset=utf-8 rather than text/markdown, with 5 of 5 required sections. 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 200 · text/html; charset=utf-8 · 2517867 bytes · 1469 ms · headings:

  id

  agents-md

  weight

  2

  points

  0.50

  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 →

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

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

  Observation

  title(31): Agentic Infrastructure - Vercel | description(45): The autonomous stack for every app and agent.

  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 →

• Prominent summary block — Opening paragraph holds 23 characters, under the 40-character floor for a summary. Recommended Medium Draft ⌄

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

  Observation

  Ship 26 is coming to SF

  id

  summary

  weight

  1

  points

  0.50

  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 →

• Responsive markup — viewport content "width=device-width, initial-scale=1, maximum-scale=1" pins maximum-scale, so a mobile-scale agent browser cannot zoom. Emerging Low Adopted ⌄

  Agent browsers mostly run at mobile scale.

  Observation

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

  id

  viewport

  weight

  1

  points

  0.50

  standard

  Adopted — A ratified standard with real deployment.

  Fix

  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style>
      img, video { max-width: 100%; height: auto; }
      .grid { display: grid; gap: 1rem; grid-template-columns: repeat(auto-fit, minmax(260px, 1fr)); }
      @media (max-width: 640px) {
        .sidebar { display: none; }
        h1 { font-size: 1.75rem; }
      }
    </style>
  </head>

  Reproduction command and full detail →

• Named AI bot rules in robots.txt — 0 of 18 named AI bots addressed: the only 17 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

  User-Agent: * Content-Signal: search=yes, ai-input=yes, ai-train=no # Allow robots to be able to crawl the OG Image API route and all the subpaths Allow: /api/og/* Allow: /api/docs-og* Allow: /api/product-og* Allow: /api/dynamic-og* Allow:…

  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-policy covers 0 of 3 expected topics (permitted uses, prohibited uses and a contact route all missing) and is not linked from the home page. Essential High Adopted ⌄

  States the rules agents must follow and reduces licensing ambiguity.

  Observation

  skip to content login – vercel sign up log in to vercel terms privacy policy log in to vercel continue with email continue with google continue with github continue with chatgpt continue with saml sso continue with passkey show other options don't have an acc…

  id

  ai-policy

  weight

  2

  points

  0.20

  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 /agent covers 2 of 4 expected topics (welcomed agents and identity verification stated; refused agents and a contact route missing) and is linked from the home page. Recommended Medium Adopted ⌄

  Explains which agents are permitted and how they are verified.

  Observation

  vercel agent skip to content copy wordmark copy logo download brand assets brand guidelines products agent stack ai sdk ai gateway sandbox passport connect eve core platform security content delivery fluid compute observability workflows ci/cd tools next.js v…

  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 →

• /ai.txt access declaration — /ai.txt answered HTTP 200 with HTML rather than a text declaration, so 0 of 3 expected topics are covered. Emerging Low Draft ⌄

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

  Observation

  <!DOCTYPE html><html data-dpl-id="dpl_EvJRL9hSJtDHL8xWaMrkxoYbQhqo" class="VEU71W_className M8bjnG_className VEU71W_variable M8bjnG_variable dash" lang="en-US"><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width, initial-scale=1, ma…

  id

  ai-txt

  weight

  1

  points

  0.20

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  # ai.txt - access declaration for example.com
  Site: https://example.com
  Contact: agents@example.com
  Policy: https://example.com/ai-policy
  
  Allow:
  - Indexing, retrieval and citation by identified search and answer engines.
  - Summarising public pages with attribution and a link to the source.
  
  Disallow:
  - Training, fine-tuning or distilling a model on this content.
  - Bulk scraping, resale or redistribution of content or data.

  Reproduction command and full detail →

• API catalog — A linkset is served at /.well-known/api-catalog with 2 entries, but 1 of them pairs an anchor with a service-desc link, so no callable API is identified. 1 same-origin target was declared but never fetched by this scan, and 1 target on another host was not followed, so no callable API was observed. Not scored: the status target is on www.vercel-status.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: item, service-desc, service-doc, status

  id

  api-catalog

  weight

  2

  points

  0.50

  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 →

• Agent Skills declaration — Agent skills index at /.well-known/agent-skills/index.json lists 9 skills with name, description, url and a digest, but 9 of 9 declared artifact urls (https://github.com/vercel-labs/agent-skills/releases/download/agent-skills-063bee94c3f4df8453406c830b0a7df0f2860278/deploy-to-vercel.tar.gz) are on another host, which this scan does not follow. Recommended Medium Draft ⌄

  Offers ready-made capability packages to agent runtimes.

  id

  agent-skills

  weight

  1

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  Fix

  {
    "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
    "skills": [
      {
        "name": "invoice-reconciliation",
        "type": "skill-md",
        "description": "Reconcile invoices against payments and flag unmatched line items.",
        "url": "/.well-known/agent-skills/invoice-reconciliation/SKILL.md",
        "digest": "sha256:9f2c1a4b7d8e0f3a5c6b1d2e4f7089a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6"
      }
    ]
  }

  Reproduction command and full detail →

• /auth.md agent authentication guide — An authentication guide is served at /auth.md but it serves an HTML sign-in page instead of a markdown guide, so an agent cannot register itself. Emerging Medium Draft ⌄

  A guide telling an agent which authentication flow to use.

  id

  auth-md

  weight

  2

  points

  0.50

  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 contact information — Homepage JSON-LD declares 3 organization nodes 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 — A status document is advertised at /status (HTTP 200) but the homepage advertises 0 Atom or RSS changelog feeds. 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 payment standard support (AP2/ACP/x402/UCP) — Exactly one agent-payment signal (agent-purchase grant stated on /docs); the 7 readable payment and policy pages name no second standard, manifest or agent-purchase wording. 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

  paths read: 7/8; standards: none

  id

  payment-protocols

  weight

  3

  points

  0.70

  standard

  Draft — A published specification that is not yet ratified.

  standards

  AP2, ACP, x402, UCP

  Reproduction command and full detail →

• Return and shipping terms machine-readable — /returns, /shipping, /refund-policy responded but none of the 4 documents read declares MerchantReturnPolicy or OfferShippingDetails. conditional Recommended Medium Adopted ⌄

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

  Observation

  readable return pages: /returns 333724 bytes, /shipping 333728 bytes, /refund-policy 333748 bytes

  id

  returns

  weight

  1

  points

  0.65

  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 →

• 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 603262 bytes; vendors: none; markers: events-none"/><img alt="build a…, agent</span></span></a></li><li…

  id

  agent-analytics

  weight

  1

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• DNS-AID discovery record — 0 SVCB records and 0 TXT records resolve at _index._agents.vercel.com and _agent.vercel.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.vercel.com and _agent.vercel.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 →

• /llms-full.txt expanded context — HTML was returned for /llms-full.txt with HTTP 200 by a catch-all route, so no expanded text is offered (2563329 bytes). 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/html; charset=utf-8 · 2563329 bytes · 1617 ms · <!DOCTYPE html><html data-dpl-id="dpl_EvJRL9hSJtDHL8xWaMrkxoYbQhqo" class="VEU7…

  id

  llms-full

  weight

  1

  points

  0.00

  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 →

• /sitemap.md markdown site map — HTML was returned for /sitemap.md with HTTP 200 by a catch-all route, 2608461 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 200 · text/html; charset=utf-8 · 2608461 bytes · 1172 ms · <!DOCTYPE html><html data-dpl-id="dpl_EvJRL9hSJtDHL8xWaMrkxoYbQhqo" class="VEU7…

  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 3 parsed JSON-LD blocks on the homepage. Recommended High Draft ⌄

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

  Observation

  @types: Organization, ImageObject, Person, ContactPoint, PostalAddress, Service, SoftwareApplication, Offer

  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 3 parsed JSON-LD blocks on the homepage. Emerging Low Draft ⌄

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

  Observation

  @types: Organization, ImageObject, Person, ContactPoint, PostalAddress, Service, SoftwareApplication, Offer

  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 →

• Token efficiency (content-to-markup ratio) — Content-to-markup ratio 0.6% (3680 visible of 603176 markup characters, ~721 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: 3680; markup characters: 603176; words: 534; estimated tokens: 721

  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

  Not Found

  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) — Both paths answered without JSON (/.well-known/agent-permissions.json HTTP 404, /agent-permissions.json HTTP 200). 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.

  Observation

  <!DOCTYPE html><html data-dpl-id="dpl_EvJRL9hSJtDHL8xWaMrkxoYbQhqo" class="VEU71W_className M8bjnG_className VEU71W_variable M8bjnG_variable dash" lang="en-US"><head><meta charSet="utf-8"/><meta name="viewport" content=…

  id

  agent-permissions

  weight

  3

  points

  0.00

  standard

  Experimental — An early convention that may still change shape.

  Fix

  {
    "version": "1.0",
    "site": "https://example.com",
    "default": "deny",
    "actions": {
      "read:public-content": { "permission": "allow" },
      "purchase:create-cart": { "permission": "allow" },
      "purchase:pay": { "permission": "human-approval" },
      "train:model": { "permission": "deny" }
    },
    "contact": "agents@example.com",
    "policy": "https://example.com/ai-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

  User-Agent: * Content-Signal: search=yes, ai-input=yes, ai-train=no # Allow robots to be able to crawl the OG Image API route and all the subpaths Allow: /api/og/* Allow: /api/docs-og* Allow: /api/product-og* Allow: /api/dynamic-og* Allow:…

  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 →

• MCP server card — No MCP server card was served as JSON at the 3 declared paths (/.well-known/mcp/server-card.json 404 text/plain; /.well-known/mcp.json 404 text/plain; /mcp.json 200 text/html). Essential High Draft ⌄

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

  id

  mcp-card

  weight

  2

  points

  0.00

  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 — No OpenAPI document was found: 5 candidate paths (0 advertised, 5 standard) returned no JSON 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 | /openapi.yaml 200 html | /.well-known/openapi.json 404 | /api/openapi.json 404 | /swagger.json 200 html

  id

  openapi

  weight

  2

  points

  0.00

  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 →

• A2A agent card — No A2A agent card was served as JSON at the 2 declared paths (/.well-known/agent-card.json 404 text/plain; /.well-known/agent.json 404 text/plain). 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 →

• WebMCP browser tool declaration — No WebMCP declaration was found: the 3 manifest paths served no tools array and the homepage contains 0 registerTool calls. 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

  0.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 →

• Agent purchase policy — No page among the 5 agent policy paths carries both an agent word and a purchase word (/ai-policy HTTP 200, /agent-policy HTTP 200, /terms HTTP 200, /agentic-commerce HTTP 200, /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-policy, /agent-policy, /terms, /agentic-commerce, /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 →

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, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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 →

• Sandbox or test environment documented — Not scored: this check applies to saas or api sites, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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

  not counted

  standard

  Experimental — An early convention that may still change shape.

  Reproduction command and full detail →

• Rate limits and quotas documented — Not scored: this check applies to api sites, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. Recommended Medium Experimental ⌄

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

  id

  rate-limits-declared

  weight

  1

  points

  not counted

  standard

  Experimental — An early convention that may still change shape.

  standards

  RFC 9110

  Reproduction command and full detail →

• Reuse and licensing terms declared — Not scored: this check applies to publisher or institution sites, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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, and the site type could not be confirmed (best candidates: saas, api). Declare the type to have it measured. 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 →