github.com

• Homepage open to agent access — HTTP 200 text/html; charset=utf-8 with 572789 bytes and 1091 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 · 572789 bytes · 110 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 "GitHub", blockquote summary, 12 H2 sections with 117 markdown links, 28658 bytes. The scan requested 1 link it names, and it answered 2xx. Not requested: 116 links on another origin. 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 · 28658 bytes · 191 ms · headings: GitHub | How to use | Building with GitHub, for coding agents and automation | GitHub Copilot | Authentication | Get st…

  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 →

• Canonical and hreflang discipline — 1 canonical, absolute and self-referential on https, 26 hreflang alternates including x-default. Recommended Medium Adopted ⌄

  An agent needs one consistent URL per important page.

  Observation

  <link rel="canonical" href="https://github.com"> · hreflang: en-us, pt-br, es-ar, es-bo, es-cl, es-co, es-cr, es-cu, es-do, es-ec, es-gt, es-hn, es-mx, es-ni, es-pa, es-pe, es-pr, es-py, es-sv, es-uy, es-ve, ja, ko-kr, fr-fr, de-de, x-default

  id

  canonical

  weight

  2

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• Semantic heading structure — 1 H1 with 9 H2s and 16 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: H2 H1 H2 H2 H2 H3 H3 H3 H3 H3 H2 H3 H2 H3 H3 H3 H3 H3 H2 H2 H2 H3 H3 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 →

• Prominent summary block — Block with class="lp-IntroHero" holds 256 characters before the first H2. Recommended Medium Draft ⌄

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

  Observation

  <section class="Primer_Brand__Hero-module__Hero___It6gj Primer_Brand__Hero-module__Hero--variant-default___lNgHw Primer_Brand__Hero-module__Hero--align-center___6FMoH lp-IntroHero-hero" aria-labelledby="hero-section-brand-heading" data-testid="Hero" data-h

  id

  summary

  weight

  1

  points

  1.00

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• Language declaration and multilingual access — html lang="en" with 26 hreflang alternates, all with absolute hrefs plus a self-reference and x-default. Recommended Medium Adopted ⌄

  A wrong language tag makes an agent misread the content.

  Observation

  html lang="en"; alternates: en-us -> https://github.com, pt-br -> https://github.com?locale=pt-br, es-ar -> https://github.com?locale=es-419, es-bo -> https://github.com?locale=es-419, es-cl -> https://github.com?locale=es-419, es-co -> https://github.com?locale=es-419, es-cr -> https://github.com?locale=es-419, es-cu -> https://github.com?locale=es-419, es-do -> https://githu…

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

  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 ("GitHub · Change is constant. GitHub kee…" vs "About GitHub · GitHub") and different main text (12% 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 "GitHub · Change is constant. GitHub keeps you ahe…" / "About GitHub · GitHub"; skeleton 55%; main-text word overlap 12%; main text 2137 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" sets width=device-width and leaves zoom unrestricted. Emerging Low Adopted ⌄

  Agent browsers mostly run at mobile scale.

  Observation

  viewport meta: width=device-width; 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 →

• Named AI bot rules in robots.txt — 6 of 18 named AI bots addressed with their own Allow or Disallow rules (GPTBot, OAI-SearchBot, ClaudeBot, anthropic-ai, PerplexityBot); Bytespider is blocked outright. Essential High Draft ⌄

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

  Observation

  User-agent: gptbot, oai-searchbot, claudebot, anthropic-ai, perplexitybot | rules 195 ;; User-agent: bytespider | rules 1

  id

  ai-rules

  weight

  2

  points

  1.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  RFC 9309

  Reproduction command and full detail →

• security.txt (RFC 9116) — security.txt at /.well-known/security.txt declares 1 Contact and an Expires 2026-11-11T22:55:00z in the future. Not scored: its Policy URL is on bounty.github.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/github Acknowledgments: https://hackerone.com/github/hacktivity Preferred-Languages: en Canonical: https://github.com/.well-known/security.txt Policy: https://bounty.github.com Hiring: https://github.careers Expires: 2026-11-11T…

  id

  security-txt

  weight

  1

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 9116

  Reproduction command and full detail →

• Crawl rate declaration — Crawl-delay: 1s for User-agent: GPTBot, OAI-SearchBot, ClaudeBot, anthropic-ai, PerplexityBot (1 of 2 declared Crawl-delay lines applies to an AI crawler or *). Emerging Low Adopted ⌄

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

  Observation

  # If you would like to crawl GitHub contact us via https://support.github.com?tags=dotcom-robots # We also provide an extensive API: https://docs.github.com User-agent: GPTBot User-agent: OAI-SearchBot User-agent: ClaudeBot User-agent: ant…

  id

  crawl-delay

  weight

  1

  points

  1.00

  standard

  Adopted — A ratified standard with real deployment.

  Reproduction command and full detail →

• Documentation reachable — Documentation is reachable at /docs (standard path) and returns HTTP 200 text/html with 620 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 — 8 groups, 496 rules and 12 named agent groups, but no Sitemap directive. Essential High Adopted ⌄

  The front door for agent traffic (RFC 9309).

  Observation

  HTTP 200 · text/plain · 16739 bytes · 178 ms · # If you would like to crawl GitHub contact us via https://support.github.com?tags=dotcom-robots # We also provide an extensive API: https:…

  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 →

• /llms-full.txt expanded context — 2778 words of text and 117 link lines in 28658 bytes, which is a list of links rather than expanded page content. 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/plain · 28658 bytes · 179 ms · # GitHub > GitHub is a developer platform for building, shipping, and maintaining software. It provides cloud-based Git…

  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 70 characters (band 50-60) and description 186 characters (band 120-160). Essential High Adopted ⌄

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

  Observation

  title(70): GitHub · Change is constant. GitHub keeps you ahead. · GitHub · GitHub | description(186): Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.

  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 →

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

  States the rules agents must follow and reduces licensing ambiguity.

  Observation

  ai (andrey sitnik) · github skip to content navigation menu sign in appearance settings platform ai code creation github copilot write better code with ai github copilot app direct agents from issue to merge mcp registry integrate external tools developer wor…

  id

  ai-policy

  weight

  2

  points

  0.50

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

  Explains which agents are permitted and how they are verified.

  Observation

  bot · github skip to content navigation menu sign in appearance settings platform ai code creation github copilot write better code with ai github copilot app direct agents from issue to merge mcp registry integrate external tools developer workflows actions …

  id

  bot-page

  weight

  1

  points

  0.50

  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 →

• ARD resource discovery manifest — ARD manifest at /.well-known/ai-catalog.json lists 1 entry of which 0 are complete and 0 carry both url and data, which the specification forbids. Emerging Low Experimental ⌄

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

  id

  ard-manifest

  weight

  1

  points

  0.50

  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 →

• Structured pricing information — No structured offer is present in the homepage JSON-LD and the only price signal is an image labelled "Copilot Autofix identifies vulnerable code and provides an …". 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.50

  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 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 6 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: 6/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 — /shipping 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: /shipping 184571 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 572789 bytes; vendors: none; markers: none

  id

  agent-analytics

  weight

  1

  points

  0.50

  standard

  Draft — A published specification that is not yet ratified.

  Reproduction command and full detail →

• sitemap.xml valid and current — sitemap.xml answered HTTP 406 with 0 bytes. Essential High Adopted ⌄

  The primary URL discovery source for agent crawlers.

  Observation

  HTTP 406 · application/xml · 246 ms

  id

  sitemap-xml

  weight

  2

  points

  0.00

  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 →

• Discovery via Link response headers — No Link header on the homepage response (HTTP 200, 572789 bytes). Emerging Medium Adopted ⌄

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

  Observation

  HTTP 200 · text/html; charset=utf-8 · 572789 bytes · 110 ms

  id

  link-headers

  weight

  2

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 8288

  Fix

  # nginx: advertise discovery resources on the homepage response.
  add_header Link '</llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="alternate"; type="application/xml"' always;
  
  # Raw header, one comma-separated field:
  Link: </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="alternate"; type="application/xml"

  Reproduction command and full detail →

• DNS-AID discovery record — 0 SVCB records and 0 TXT records resolve at _index._agents.github.com and _agent.github.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.github.com and _agent.github.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 406, 0 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 406 · text/html · 224 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 — HTML was returned for /sitemap.md with HTTP 200 by a catch-all route, 191911 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 · 191911 bytes · 240 ms · <!DOCTYPE html> <html lang="en" data-color-mode="light" data-light-theme="light…

  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 →

• Markdown content negotiation — The homepage answered Accept: text/markdown with Content-Type text/html; charset=utf-8 (HTTP 200), so the HTML document is served to every client. Recommended Critical Adopted ⌄

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

  Observation

  status: 200; content-type: text/html; charset=utf-8; vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, X-GitHub-Client-Version, Accept-Language, Sec-Fetch-Site,Accept-Encoding, Accept, X-Requested-With; markdown body: no

  id

  markdown-negotiation

  weight

  3

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  RFC 9110

  Fix

  // server.js - one URL, two representations (RFC 9110).
  import express from 'express';
  import { readFile } from 'node:fs/promises';
  
  const app = express();
  app.use(async (req, res, next) => {
    if (req.method !== 'GET') return next();
    res.vary('Accept'); // the HTML response must carry this too
    if (req.accepts(['text/html', 'text/markdown']) !== 'text/markdown') return next();
    try {
      const file = `public${req.path.replace(/\/$/, '/index')}.md`;
      res.type('text/markdown').send(await readFile(file, 'utf8'));
    } catch {
      next(); // no markdown twin for this path: fall back to HTML
    }
  });
  app.use(express.static('public'));
  app.listen(3000);

  Reproduction command and full detail →

• JSON-LD structured data — No JSON-LD script block on the homepage (0 blocks found). Essential Critical Adopted ⌄

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

  Observation

  blocks: 0 total, 0 non-empty, 0 parsed; schema.org @context: no; @types: none

  id

  jsonld

  weight

  3

  points

  0.00

  standard

  Adopted — A ratified standard with real deployment.

  standards

  schema.org

  Fix

  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "WebSite",
    "name": "Acme Agent Readiness",
    "url": "https://www.example.com/",
    "description": "Audits how well a website serves autonomous AI agents.",
    "publisher": {
      "@type": "Organization",
      "name": "Acme",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/logo.svg"
    }
  }
  </script>

  Reproduction command and full detail →

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

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

  Observation

  @types: none

  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 0 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: none

  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 1.2% (7396 visible of 572689 markup characters, ~1473 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: 7396; markup characters: 572689; words: 1091; estimated tokens: 1473

  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

  <!DOCTYPE html> <html lang="en" data-color-mode="auto" data-light-theme="light" data-dark-theme="dark" data-a11y-animated-images="system" data-a11y-link-underlines="true" > <head> <meta charset="utf-8"> <link rel="dns-p…

  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 410). 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 →

• Content-Signal usage signals — No Content-Signal line in robots.txt (16739 bytes) and none in the homepage response headers. Recommended High Draft ⌄

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

  Observation

  HTTP 200 · text/plain · 16739 bytes · 178 ms

  id

  content-signal

  weight

  2

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  standards

  contentsignals.org

  Fix

  # https://example.com/robots.txt - Content Signals Policy (contentsignals.org)
  # search   = index the content and return links and short excerpts
  # ai-input = use the content in a model at answer time (grounding)
  # ai-train = use the content to train or fine-tune a model
  
  User-agent: *
  Content-Signal: search=yes, ai-input=yes, ai-train=no
  Allow: /
  
  User-agent: GPTBot
  Content-Signal: search=yes, ai-input=yes, ai-train=no
  Allow: /

  Reproduction command and full detail →

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

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

  id

  ai-txt

  weight

  1

  points

  0.00

  standard

  Draft — A published specification that is not yet ratified.

  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 application/json; /.well-known/mcp.json 404 application/json; /mcp.json 200 application/json). 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 410 | /openapi.yaml 406 | /.well-known/openapi.json 404 | /api/openapi.json 404 | /swagger.json 410

  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 →

• OAuth discovery documents — None of the 3 OAuth discovery paths returned a JSON document (/.well-known/oauth-authorization-server 404 text/html; /.well-known/openid-configuration 404 text/html; /.well-known/oauth-protected-resource 404 text/html). 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 →

• API catalog — No API catalog linkset was served at the 3 declared paths (/.well-known/api-catalog 404 text/html; /api-catalog.json 410 application/json; /.well-known/ai-plugin.json 404 application/json). Recommended Medium Experimental ⌄

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

  id

  api-catalog

  weight

  2

  points

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

• Agent Skills declaration — No agent skills index with a non-empty skills array was served as JSON at the 3 declared paths (/.well-known/agent-skills/index.json 404 application/json; /.well-known/agent-skills.json 404 application/json; /.well-known/skills.json 404 application/json). 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.

  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 →

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

• 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 →

• Service/product scope machine-readable — The homepage JSON-LD carries 0 model types with 0 Service or Product nodes, so the offer scope cannot be read. 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.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 →

• Structured contact information — The homepage JSON-LD carries 0 model types with 0 Organization nodes and the page states 0 contact channels. 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.00

  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 →

• Product/catalog schema — No Product, Offer or AggregateOffer type appears in the homepage JSON-LD (0 types) or in the JSON-LD of the 2 readable product or collection pages. 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: none; product paths: /products HTTP 200, /shop HTTP 200, /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 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 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: /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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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: api, ecommerce). 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 →