Agent readiness is whether AI agents (ChatGPT, Claude, Perplexity, Operator, named crawlers like GPTBot and ClaudeBot) can discover, read, understand, and act on a website. It’s the agent-era equivalent of mobile-readiness or accessibility: a property of the site that determines whether an automated client can use it as effectively as a human can.
Five capabilities
AgentSpeed scores agent readiness across five sub-categories. They’re ordered by what an agent does, in sequence, when it first encounters a site:
- Discoverability. Can an agent find your canonical pages?
robots.txtallows known agent UAs;llms.txtpoints at docs and pricing;sitemap.xmllists URLs. - Readability. Can an agent parse the page without executing JavaScript? Primary content renders server-side; the page is useful with JS disabled.
- Structured data. Are JSON-LD blocks present and valid? Agents prefer typed data to inferred prose.
- Actionability. Can an agent identify the primary offering and complete the task? Pricing, CTAs, and agent-callable tools are reachable.
- Performance. Does the page render fast enough that agents don’t time out? Most agents abort at six seconds.
Why now?
A growing share of web traffic comes from agents acting on behalf of users. ChatGPT’s browse mode, Perplexity’s search, Claude’s research mode, and the agentic runtimes built on top of MCP all read pages programmatically. A site optimised purely for humans loses citations to one optimised for both.
How is it different from SEO?
Different audience, different rubric. SEO measures how Googlebot ranks pages for human searchers. Agent readiness measures whether AI agents can use pages on behalf of automated clients. Most sites pass SEO and fail agent readiness, because they were built before agents mattered. Running both audits is the sensible move.