--- title: "What is an agent-ready website? Definition and evidence" description: "An agent-ready website is one that AI agents can reliably read, act on, and trust: machine-readable structure, explicit action pathways, and verifiable, current information. The term converged in 2026 across Chrome's agent-ready toolkit, Cloudflare's Agent Readiness score, and the first controlled study (Elnaffar & Rashidi, arXiv:2607.12056), which measured 89.3% vs 49.3% task success and 18–40% lower token cost for an agent-ready redesign." last_updated: 2026-08-22 canonical_url: https://agent-ready.dev/what-is-an-agent-ready-website --- # What is an agent-ready website? > The definition, the research behind the term, and the checklist that gets you there. ## What is an agent-ready website? **An agent-ready website is one that AI agents can reliably read, act on, and trust.** When an autonomous agent lands on an agent-ready site, it can parse what the site says (machine-readable structure), do what it came to do (explicit, stable action pathways), and verify that what it found is current and genuine (evidence and temporal signals). Agent-ready design sits alongside human UX and SEO rather than replacing them: the same site keeps serving people, and additionally exposes its content and capabilities as semantic HTML, Schema.org JSON-LD, llms.txt, markdown mirrors, and declared agent-protocol capabilities. ## Where does the term come from? "Agent-ready" converged from three directions in 2026. Chrome for Developers shipped an agent-ready toolkit (), Cloudflare introduced an Agent Readiness score (), and the first controlled study — "Designing Agent-Ready Websites for AI Web Agents" (Elnaffar & Rashidi, July 2026, ) — formalised the agent-ready website as a design framework. Agent Ready approaches the same property from the measurement side: agent readability () is the degree to which a site can be discovered, parsed, understood, and acted on by agents, expressed as a 0–100 score. An agent-ready website is the state; agent readability is how you measure your distance from it. ## What does the research show? The Elnaffar & Rashidi study built two versions of the same prototype shop — a human-oriented baseline and an agent-ready variant with JSON-LD, exposed structured data, explicit action labels, and temporal-validity fields — and ran three browser agents (GPT-4.1, Gemini 2.5 Flash, Grok-4 Fast) through five tasks, 300 runs in total: - **Strict task success rose from 49.3% to 89.3%** (134/150 vs 74/150 runs), with partial completions collapsing from 43 to 3. - **Agents needed 30.4% fewer steps** on average (9.31 down to 6.49). - **Token consumption fell 18–40%** depending on the model — agent-ready pages are literally cheaper for agents to use. - The biggest gains came on comparison and multi-constraint selection tasks (roughly +77 percentage points each). Honest caveats: it is a preprint, the site was a prototype built by the authors, two of the five tasks showed no statistically significant improvement, and no ablation isolates which intervention did the work. A controlled proof of concept, not a final word. ## What are the three dimensions of agent readiness? | Dimension | The question it answers | What you publish | |---|---|---| | **Agent interpretability** | Can an agent parse and understand the page? | Semantic HTML, Schema.org JSON-LD, llms.txt, markdown mirrors | | **Agent executability** | Can an agent find and perform the right action? | Stable, labelled controls in-page; declared capabilities via MCP server cards, A2A agent cards, or agents.json | | **Agent decision reliability** | Can an agent trust what it just read? | Visible last-updated dates, canonical URLs, consistent metadata, an agent-permissions policy | Scope note: the study's experiment covered the first two dimensions inside the page itself. Site-wide artifacts such as llms.txt and agent-protocol manifests extend the same principles but were not part of the experiment, so the measured numbers do not speak to them directly. ## How is agent-ready different from SEO and AEO? - **SEO** optimises for being *found*: crawlers index pages, a ranking decides visibility, a human clicks. - **AEO** optimises for being *cited*: an AI assistant synthesises an answer and names its sources. - **Agent readiness** optimises for being *used*: an autonomous agent completes a task — extracts the fact, compares the options, fills the form, calls the API. The layers overlap: structured data does triple duty across rankings, citations, and task success. ## How do I make my website agent-ready? 1. **Expose real content in crawlable HTML with JSON-LD.** If the answer only exists after JavaScript runs, many agents never see it. This carried most of the measured improvement in the study. 2. **Publish the discovery files** — an llms.txt () plus markdown mirrors of key pages. 3. **Check your robots policy admits the agents you want** () — many sites block citation crawlers while trying to block trainers. 4. **Declare your capabilities** — an MCP server card, an A2A agent card (), or an agents.json () projected from your OpenAPI spec. 5. **Scan, fix, and re-scan** () — every layer graded, each failing check with a plain-English fix. ## How agent-ready is the web today? Across the 1,183 distinct sites scanned on agent-ready.dev as of August 2026, the mean agent-readability score is **56/100**, only 8% of sites reach the excellent band (90–100), and agent-protocol manifests remain in low single-digit adoption — in a sample that skews optimistic, because it is sites whose owners cared enough to check. Full aggregate: . ## Frequently asked questions ### What is an agent-ready website? An agent-ready website is one that AI agents can reliably read, act on, and trust. In practice that means three things: machine-readable structure (semantic HTML, Schema.org JSON-LD, markdown mirrors) so an agent can parse what the site says; explicit, stable action pathways (labelled controls, declared capabilities such as MCP server cards or an agents.json manifest) so an agent can do things rather than just read; and verifiable, current information (visible dates, canonical URLs, consistent metadata) so an agent can trust what it found. Agent-ready design sits alongside human UX and SEO — it does not replace either. ### Is an agent-ready website the same as agent readability? They are two views of the same property. Agent readability is the measurable degree to which a site can be discovered, parsed, understood, and acted on by AI agents — Agent Ready expresses it as a 0–100 score. An agent-ready website is the state you are aiming for: a site whose agent readability is high enough that agents complete tasks on it reliably. Scan a site and you measure its agent readability; fix what the scan finds and you get an agent-ready website. ### What evidence is there that agent-ready design works? The first controlled experiment was published in July 2026 (Elnaffar & Rashidi, arXiv:2607.12056). The authors built two versions of the same prototype shop — a conventional human-oriented baseline and an agent-ready variant with JSON-LD, exposed structured data, explicit action labels, and temporal-validity fields — and ran three browser agents (GPT-4.1, Gemini 2.5 Flash, Grok-4 Fast) through five tasks, 300 runs in total. Strict task success rose from 49.3% to 89.3%, average steps fell 30.4%, and token consumption fell 18–40% depending on the model. It is a preprint based on one prototype site, so treat it as a proof of concept rather than a final word — but it is the first quantified evidence for what practitioners had argued from experience. ### How is an agent-ready website different from an SEO-optimised website? SEO optimises for being found: crawlers rank your pages and a human clicks a link. Answer-engine optimisation (AEO) optimises for being cited: an AI assistant synthesises an answer and names its sources. Agent readiness optimises for being used: an autonomous agent completes a task on your site — extracts the right fact, compares options, fills the form, calls the API. Each layer builds on the previous one, and some artifacts do double duty: structured data helps rankings, citations, and agent task success at once. ### How do I make my website agent-ready? Five steps, in order of leverage. First, expose your real content in crawlable HTML with Schema.org JSON-LD, rather than only behind JavaScript. Second, publish the agent discovery files: llms.txt plus markdown mirrors of key pages. Third, make sure your robots policy actually admits the agents you want — many sites block AI crawlers by accident. Fourth, declare your capabilities in machine-readable form: an MCP server card, an A2A agent card, or an agents.json manifest, depending on what your site offers. Fifth, verify with a scan and fix what fails: each Agent Ready check maps to one concrete artifact or property, with a plain-English fix. ### How many websites are agent-ready today? Very few. Across 1,183 distinct sites scanned by Agent Ready as of August 2026, the mean agent-readability score is 56/100 — and that sample skews optimistic, because it is sites whose owners cared enough to check. Only 8% of scanned sites score in the excellent band (90–100), and agent-protocol adoption (MCP, A2A, agents.json and similar manifests) remains in the low single-digit percentages in the wild. The gap between the agentic-web conversation and what is actually published is still wide — which is also the opportunity for sites that move early. --- Read the full guide on the web: Scan your site for agent readiness: ## Sitemap See the full [sitemap](https://agent-ready.dev/sitemap.md) for all pages on agent-ready.dev.