# Agent readiness

Category: [Agents & Protocols](https://seo-geo-glossary.com/en/glossary/category/agents-protocols/) › [Agent readiness & browser agents](https://seo-geo-glossary.com/en/glossary/category/agents-protocols/agent-readiness-browser-agents/)

**Agent readiness** describes how well AI agents can discover, read and use a website. The term also appears for how prepared a company is to run AI agents in production. This entry covers the website meaning.

## How is agent readiness measured?

Cloudflare published an Agent Readiness Score on April 17, 2026, and compares the idea to what Lighthouse does for performance. Its checks fall into four categories:

- **Discoverability:** robots.txt (RFC 9309), sitemap.xml and Link headers (RFC 8288).
- **Content:** serving Markdown to agents through content negotiation (`Accept: text/markdown`).
- **Bot access control:** Content Signals, AI bot rules in robots.txt and Web Bot Auth.
- **Capabilities:** Agent Skills discovery, an API catalog (RFC 9727), OAuth server discovery (RFC 8414, RFC 9728), an MCP Server Card and WebMCP.

Cloudflare's post lists commerce standards such as UCP, ACP and x402 separately from the score, and the isitagentready.com tool now shows them as a fifth category, Commerce. The score is a model from one vendor and has no standard status (as of October 2026; the post was last modified on July 15, 2026). Cloudflare's own conclusion was that most sites are not very agent ready yet. The checks can be run with isitagentready.com.

Starting with Chrome 150, Lighthouse includes an experimental "Agentic Browsing" category. It checks WebMCP tool registration, a subset of accessibility audits, layout stability (CLS) and whether an llms.txt file exists, and it reports the result as a fraction of passed checks, such as 2/3.

## Example

An online shop publishes a robots.txt with explicit rules for AI bots and an XML sitemap. It serves product pages as Markdown on request. At `/.well-known/api-catalog` it lists its APIs as RFC 9727 describes. That covers parts of discoverability, content and capabilities.

## Checklist

- robots.txt, sitemap.xml and Link headers (RFC 8288) are in place (the discoverability category of Cloudflare's score).
- Key pages can be retrieved as Markdown (`Accept: text/markdown`), optionally complemented by an llms.txt file.
- Rules for AI bots are in robots.txt, and Content Signals are set if wanted.
- Existing APIs are listed at `/.well-known/api-catalog` as RFC 9727 describes.
- Buttons and links are real `<button>` and `<a>` elements, and labels are tied to their fields with `for` (web.dev, as of 2026-04-01).
- The layout does not shift while loading, because agents that use screenshots would otherwise miss their targets (web.dev).
- No transparent overlays cover clickable elements (web.dev).
- Optionally, WebMCP tools are registered (a W3C Community Group draft).

## Common mistakes

According to web.dev (as of 2026-04-01), these patterns make a site harder for agents to use:

- **Transparent overlays over clickable elements.** Agents may discard covered nodes.
- **Divs and spans instead of `<button>` and `<a>`.** Without a fitting role, agents recognize the elements less reliably.
- **Labels without a `for` attribute.** The purpose of the field stays unclear.
- **A layout that keeps shifting.** Agents that analyze screenshots lose track of elements.

## FAQ

**Is agent readiness a ranking factor?**
No evidence supports that. The score measures how usable a site is for agents.

**How does it differ from the business meaning?**
In companies the term covers internal requirements such as infrastructure, logging and security when deploying agents. The website meaning covers what a site offers to agents from the outside.

## At a glance

- **Type:** how suitable a website is for AI agents
- **Used in:** Cloudflare Agent Readiness Score; Lighthouse "Agentic Browsing" (from Chrome 150, experimental)
- **Status:** scoring model from individual vendors, not a standard
- **Docs:** [Cloudflare: Agent Readiness Score](https://blog.cloudflare.com/agent-readiness/)

Last checked: October 8, 2026

*Diagram: Which protocol covers what?.* Map of agent protocols as of 2026-10-08: which connection each protocol covers, who publishes it and what its status is. In commerce, ACP, UCP and AP2 overlap, and several protocols build on MCP or A2A. Versions change quickly.

## Related terms

- [llms.txt](https://seo-geo-glossary.com/en/glossary/llms-txt/index.md)
- [robots.txt](https://seo-geo-glossary.com/en/glossary/robots-txt/index.md)
- [WebMCP](https://seo-geo-glossary.com/en/glossary/webmcp/index.md)
- [MCP (Model Context Protocol)](https://seo-geo-glossary.com/en/glossary/mcp/index.md)
- [OpenAPI](https://seo-geo-glossary.com/en/glossary/openapi/index.md)
- [AI agent](https://seo-geo-glossary.com/en/glossary/ai-agent/index.md)
- [Agent analytics](https://seo-geo-glossary.com/en/glossary/agent-analytics/index.md)

## More on the searchVIU blog

- [Optimizing for AI Agents — Common Pitfalls and How to Fix Them](https://www.searchviu.com/en/optimize-for-ai-browsers/)
- [Agentic Engine Optimization (AEO): Making Websites Usable for AI Agents](https://www.searchviu.com/en/agentic-engine-optimization/)

## Sources

- [Introducing the Agent Readiness Score – Cloudflare Blog (Apr 17, 2026)](https://blog.cloudflare.com/agent-readiness/)
- [RFC 9727: api-catalog – IETF](https://www.rfc-editor.org/rfc/rfc9727)
- [Is it agent ready? – Cloudflare](https://isitagentready.com/)
- [Optimizing for AI Agents — Common Pitfalls and How to Fix Them – searchVIU blog (2026)](https://www.searchviu.com/en/optimize-for-ai-browsers/)
- [Lighthouse agentic browsing scoring – Chrome for Developers](https://developer.chrome.com/docs/lighthouse/agentic-browsing)
- [Build agent-friendly websites – web.dev (updated 2026-04-01)](https://web.dev/articles/ai-agent-site-ux)

---

Last updated: October 8, 2026
URL: https://seo-geo-glossary.com/en/glossary/agent-readiness/