---
title: "Agent Ready's Own Agent-Readability Scorecard"
description: "The live result of scanning agent-ready.dev with its own scanner: the current agent-readability score, every check the site does not pass, and the full per-check results."
last_updated: 2026-10-04
canonical_url: https://agent-ready.dev/agent-ready-scorecard
---

# Agent Ready's Own Agent-Readability Scorecard

> The live result of scanning agent-ready.dev with its own scanner: the current agent-readability score, every check the site does not pass, and the full per-check results.

## What does agent-ready.dev score on its own scanner?

On 2026-10-04, agent-ready.dev scored 96/100 for agent readability against the [Vercel Agent Readability Spec](https://vercel.com/kb/guide/agent-readability-spec) and 100/100 on the llms.txt standard, across 25 pages. The scan is the one any visitor can run, scored by the rules in the [methodology](https://agent-ready.dev/methodology).

- Agent-readability score (vs the Vercel Agent Readability Spec): **96/100** (excellent)
- llms.txt score: **100/100**
- Accessibility sub-score: 100/100
- Better than 98% of 2,092 sites scanned
- Pages checked: 25
- Scanned: 2026-10-04

| Check group | Passed | Warned | Failed | Not scored |
|---|---|---|---|---|
| Site-wide checks | 15 | 0 | 0 | 0 |
| Page checks | 24 | 0 | 1 | 0 |
| llms.txt checks | 10 | 0 | 0 | 0 |
| Protocol discovery checks | 18 | 0 | 0 | 0 |
| Accessibility checks | 18 | 0 | 0 | 5 |

## Which checks does agent-ready.dev not pass?

- **FAIL** `P13` Text-to-HTML ratio (Page checks) - 1.7% text content (minimum 10%, recommended >15%)

## What did the scan check?

Every result from the scan. Page checks are collapsed across the scanned pages, so each shows its worst result on any page. The full interactive report is at <https://agent-ready.dev/scan/SUTec4npPS>.

### Site-wide checks

- **PASS** `S1` llms.txt exists — Found at https://agent-ready.dev/llms.txt
- **PASS** `S2` llms.txt Content-Type — Served as text/plain
- **PASS** `S3` llms.txt not empty — File has 27694 characters of content
- **PASS** `S4` llms.txt URL format — 115 URLs found, none use .html extensions
- **PASS** `S5` robots.txt — AI bots allowed — No citation crawlers are blocked; training-only crawlers blocked (CCBot, Bytespider) — no visibility cost
- **PASS** `S6` robots.txt — /llms.txt not blocked — /llms.txt is not blocked
- **PASS** `S7` robots.txt exists — robots.txt found
- **PASS** `S8` sitemap.xml valid — Valid sitemap with 66 URLs
- **PASS** `S9` sitemap.xml has lastmod — All 66 entries have lastmod dates
- **PASS** `S10` sitemap.md exists — Found at https://agent-ready.dev/sitemap.md
- **PASS** `S11` sitemap.md has headings + links — Contains structured headings and links
- **PASS** `S12` AGENTS.md exists — Found at https://agent-ready.dev/AGENTS.md
- **PASS** `S13` AGENTS.md has required sections — Contains 2 sections: configuration, usage
- **PASS** `S14` HTTPS — Site is served over HTTPS
- **PASS** `S15` Root OpenAPI spec — OpenAPI spec found at https://agent-ready.dev/openapi.json

### Page checks

Collapsed across 25 scanned pages — each check shows its worst result on any page.

- **PASS** `P1` HTTP 200 — Returns HTTP 200
- **PASS** `P2` Redirect chain — No redirects
- **PASS** `P3` Content-Type header — Content-Type includes text/html
- **PASS** `P4` x-robots-tag — No restrictive x-robots-tag header
- **PASS** `P5` Canonical link — Canonical URL: https://agent-ready.dev
- **PASS** `P6` Meta description — Description present (143 chars)
- **PASS** `P7` og:title — og:title: "Agent Ready — AI Agent Readability Checker"
- **PASS** `P8` og:description — og:description present
- **PASS** `P9` HTML lang attribute — lang="en"
- **PASS** `P10` JSON-LD present — 5 JSON-LD blocks found
- **PASS** `P11` JSON-LD has required fields — All required fields present
- **PASS** `P12` Section headings — 10 headings (h1-h3) found
- **FAIL** `P13` Text-to-HTML ratio — 1.7% text content (minimum 10%, recommended >15%)
  - How to fix: Your page is mostly HTML/CSS/JS with very little readable text. AI agents struggle to extract useful content from pages dominated by framework boilerplate. Add more text content or reduce unnecessary markup.
- **PASS** `P14` Glossary link — Links to glossary: /docs/api/reference
- **PASS** `P15` Markdown mirror exists — Markdown version of this page exists
- **PASS** `P16` Markdown frontmatter — Frontmatter includes title, description, and last_updated
- **PASS** `P17` Alternate link (markdown) — Alternate markdown link: https://agent-ready.dev/index.md
- **PASS** `P18` Link header in markdown — Markdown endpoint returns Link header with rel="canonical"
- **PASS** `P19` Content negotiation — Accept: text/markdown returns markdown content
- **PASS** `P20` Sitemap section in markdown — Markdown includes ## Sitemap section linking to /sitemap.md
- **PASS** `P21` Code block language tags — No code blocks found (not applicable)
- **PASS** `P22` API schema link — Not an API page (check not applicable)
- **PASS** `P23` JS rendering dependency — Static HTML contains 6554 characters of rendered text
- **PASS** `P24` llms.txt discovery link — describedby link to llms.txt (HTTP Link header): /llms.txt
- **PASS** `P25` AI snippet directives — max-snippet:-1 and max-image-preview:large are set — full text and large images are eligible for AI Overviews

### llms.txt checks

- **PASS** `L1` File accessible — llms.txt returns HTTP 200
- **PASS** `L2` H1 present — H1: "Agent Ready"
- **PASS** `L3` Valid markdown — llms.txt is valid, parseable markdown
- **PASS** `L4` Blockquote summary — Blockquote summary present below H1
- **PASS** `L5` H2 file-list sections — 8 H2 sections with links
- **PASS** `L6` Link format correct — All 113 links use correct format
- **PASS** `L7` Links are accessible — All 5 sampled links are accessible
- **PASS** `L8` Optional section used correctly — ## Optional section has 8 links for secondary content
- **PASS** `L9` Content-Type: text/plain — Served as text/plain
- **PASS** `L10` llms-full.txt available — Found at https://agent-ready.dev/llms-full.txt

### Protocol discovery checks

Run because this site publishes agentic-protocol discovery endpoints. Informational — these don't contribute to the score above.

- **PASS** `C1` MCP Server Card exists — Server Card published at /.well-known/mcp.json
- **PASS** `C2` MCP Server Card fields — Server Card has all required fields (name, description, version)
- **PASS** `C4` A2A Agent Card exists — Agent Card published at /.well-known/agent-card.json
- **PASS** `C5` A2A Agent Card fields — Agent Card matches a2a.proto v1.0.0 with all required fields
- **PASS** `C6` Wildcard agents.json — agents.json at https://agent-ready.dev/.well-known/agents.json validates against the agents.json v0.1.0 schema
- **PASS** `C7` agent-permissions.json — agent-permissions.json at https://agent-ready.dev/agent-permissions.json validates against the v1.0.0 schema (5 resource rules, 4 action guidelines)
- **PASS** `C8` UCP profile (/.well-known/ucp) — UCP profile published at https://agent-ready.dev/.well-known/ucp
- **PASS** `C9` UCP OAuth Authorization Server metadata — OAuth Authorization Server metadata present and valid
- **PASS** `C10` x402 Payment Required response — Valid x402 402 response from https://agent-ready.dev/api/x402/scan (advertised by https://agent-ready.dev/.well-known/x402)
- **PASS** `C11` x402 accepts entries — All 2 accepts entries are well-formed
- **PASS** `C13` API Catalog (RFC 9727) — API catalog published at https://agent-ready.dev/.well-known/api-catalog advertising 5 API resource(s)
- **PASS** `C14` Web Bot Auth directory — Web Bot Auth directory published at https://agent-ready.dev/.well-known/http-message-signatures-directory with 1 signing key(s) (1 Ed25519)
- **PASS** `C15` Agent Skills Discovery — Agent Skills discovery index published at https://agent-ready.dev/.well-known/agent-skills/index.json with 4 valid skill(s)
- **PASS** `C16` Content parity (no cloaking) — No cloaking — AI crawlers and the scanner receive equivalent content (4981 vs 4981 chars).
- **PASS** `C17` Agent-driven UI (A2UI) — Server Card advertises an agent-driven UI surface (mcp-apps) at https://agent-ready.dev/api/apps/mcp with 1 ui:// widget resource
- **PASS** `C18` MPP Payment challenge — MPP Payment scheme is present at https://agent-ready.dev/api/x402/scan
- **PASS** `C19` MPP challenge params — MPP Payment challenge required parameters are valid
- **PASS** `C22` Declared endpoints crawlable — All 11 declared agent endpoints are crawlable — robots.txt does not block anything this site advertises to agents.

### Accessibility checks

WCAG signals over the homepage DOM, scored into the separate accessibility sub-score.

- **PASS** `A1` Images have text alternatives — All 1 image carry a text alternative.
- **PASS** `A2` Form controls have labels — All 1 form control have an accessible label.
- **PASS** `A3` Controls have accessible names — All 98 links/buttons expose an accessible name.
- **PASS** `A4` Media declares explicit dimensions — All 1 media element declare explicit dimensions.
- **PASS** `A5` ARIA name references resolve — All label/aria-labelledby references resolve and ids are unique.
- **NOT SCORED** `A6` Iframes have an accessible name — No visible iframes on the page.
- **PASS** `A7` Heading hierarchy is well-formed — Exactly one h1 and no skipped heading levels.
- **PASS** `A8` No positive tabindex — No positive tabindex values — focus order follows the DOM.
- **PASS** `A9` Pinch-zoom is not disabled — The viewport meta does not disable zoom.
- **PASS** `A10` Page has a title — Page title: "Agent Ready — AI Agent Readability Checker"
- **PASS** `A11` Accessible name contains the visible label — All 10 labelled controls include their visible text in the accessible name.
- **PASS** `A12` Content is reachable past the chrome — One main landmark marks where the content begins.
- **PASS** `A13` Language tag is valid — <html lang="en"> is a well-formed language tag.
- **PASS** `A14` Hidden elements are not focusable — No focusable elements are hidden from assistive technology.
- **PASS** `A15` Interactive controls are not nested — No interactive control contains another.
- **PASS** `A16` Headings are not empty — All 10 headings carry text.
- **PASS** `A17` No timed meta refresh — No meta refresh on the page.
- **NOT SCORED** `A18` Autocomplete tokens are valid — No autocomplete attributes to validate.
- **NOT SCORED** `A19` Tables declare their headers — No data tables on the page.
- **NOT SCORED** `A20` SVG images have a text alternative — No SVGs are exposed as images.
- **NOT SCORED** `A21` Media declares a captions track — No audio or video elements on the page.
- **PASS** `A22` List structure is well-formed — Lists contain only list items, and every item sits in a list.
- **PASS** `A23` ARIA roles and attributes are valid — All ARIA roles and attributes are valid.

## Why does Agent Ready publish its own scorecard?

A scanner asks you to trust its verdict on your site. The simplest test of that verdict is what it says about the site that makes it. So the result is public, it is refreshed from a daily scan, and it is never edited by hand - when a deploy breaks a check, this page shows it.

It is also a worked example: each passing check is something agent-ready.dev actually publishes, such as its [llms.txt](https://agent-ready.dev/llms.txt), the markdown mirror of every page, and the discovery manifests listed on the [specs page](https://agent-ready.dev/specs).

## Does Agent Ready publish other sites' scorecards?

No. A scan report is reachable only through its share link, and report pages are not indexed by search engines - your scan is private unless you choose to share it. Across all scanned sites we publish aggregate figures only, in the [State of Agent Readability](https://agent-ready.dev/state-of-agent-readability) report, where no site is named and our own domains are left out.

## Frequently asked questions

### What does Agent Ready score on its own scanner?

The current score is at the top of this page, read from the most recent completed scan of agent-ready.dev. It is the same scan anyone can run from the home page, scored by the same rules as every other site, and the page shows it as it is - including every check the site does not pass.

### Why isn't the score a perfect 100?

Because the scan is real. Whatever agent-ready.dev does not pass is listed on this page with the scanner's own explanation, exactly as it would be for any other site, rather than hidden or scored around. A scanner that gave its own site a free pass would be telling you nothing about yours.

### How often is this scorecard updated?

agent-ready.dev is re-scanned every day, and this page shows the latest completed scan, so it is normally no more than a day old. The scan date is shown under the heading. Nothing here is edited by hand - when a deploy breaks a check, the scorecard shows the failure on the next scan.

### Is the scan of agent-ready.dev treated differently from other sites?

No. It runs through the same scanner, the same checks and the same scoring formula as any other scan. The one difference is in the research pages: our own domains are left out of the corpus behind the State of Agent Readability report, so a site we tune every week doesn't flatter the averages.

### Can I see another site's scorecard on Agent Ready?

Not as a public page. A scan report is reachable only through its share link, which goes to the person who ran the scan, and report pages are not indexed by search engines. Your scan stays private unless you choose to share it. This page exists because the site is ours to publish.

### How do I get a scorecard like this for my own site?

Run a scan from the home page - it takes about a minute and needs no account. You get the same score, the same per-check results and a fix for each issue, plus a share link and a badge you can publish if you want to show the result.

---

Read this scorecard on the web: <https://agent-ready.dev/agent-ready-scorecard>

Scan your own site: <https://agent-ready.dev>

## Sitemap

See the full [sitemap](https://agent-ready.dev/sitemap.md) for all pages on agent-ready.dev.
