What is agent readiness? A complete guide

Agent readiness is how well AI agents can get into your website, understand it, find their way around it, and complete the tasks people send them to do. This guide explains each part, what good looks like, and where to start.

Why it matters now

AI assistants increasingly visit websites on a person's behalf: to answer a question, compare products, check a policy, or buy something. Each of those visits stands in for a customer. If the agent can't use your site, it doesn't complain or call support. It moves on to a site it can use, and recommends that one instead.

Agent readiness is not the same as SEO, though they overlap. SEO is about being found and ranked. Agent readiness is about what happens next: whether an agent that has found you can actually do something useful with your site.

Not every agent wants the same thing. A crawler collecting pages for AI training is very different from an assistant checking your returns policy for a customer, or a browser agent trying to check out. See the AI agents that visit your website, and keep the agent readiness glossary handy for the terms in this guide.

The four parts of agent readiness

AgentScore measures agent readiness out of 100, across four categories. The weights reflect what stops agents most often in practice.

Category	The question	Points
Access	Can agents get in?	25
Readability	Can agents understand your pages?	25
Navigability	Can agents find their way around?	20
Task completion	Can an agent actually get the job done?	30

1. Access: can agents get in?

Before anything else, the agent has to be allowed through the door. Most access failures are accidental: a robots.txt rule copied from a template, or bot protection that challenges every visitor that isn't a person.

• robots.txt allows AI assistants and AI search agents. You can still block training crawlers separately. See robots.txt for AI agents.
• Bot protection doesn't block AI agents that a person would get through, and can tell real agents from impostors. See bot protection and CAPTCHAs and how to tell if an AI crawler is real.
• No CAPTCHA or challenge page on arrival for ordinary pages.
• An llms.txt file points agents to your most important pages. See how to write an llms.txt file.

2. Readability: can agents understand your pages?

Many agents read the HTML your server sends and never run JavaScript. If your prices, product details or policies only appear after scripts load, those agents see an empty page.

• Key content is in the HTML, through server-side rendering or static generation, not only added by JavaScript. See why AI agents can't see JavaScript-only content.
• Structured data (schema.org) describes products, prices, availability and your business. See product data AI shopping agents can read.
• Clear titles, headings and image descriptions on every important page.
• A valid sitemap that lists the pages you want found.

3. Navigability: can agents find their way around?

Browser agents find their way around a page much as a screen reader does: by the names and roles of buttons, links and form fields. Much of agent readiness here is simply good accessibility. See buttons, links and forms agents can use.

• Every button, link and form field has a name an agent can read. An icon with no label is invisible.
• Cookie banners and pop-ups can be dismissed and don't cover the content.
• Menus open on click or focus, not only on hover.
• Page landmarks such as header, navigation, main and footer let agents find what they need quickly.

4. Task completion: can an agent get the job done?

This is the part that matters most, and the only way to measure it is to try. A site can pass every technical check and still lose agents at the size selector or the checkout button.

• Online stores: an agent can search, find a product, choose options and add it to the cart. See how to make checkout work for AI shopping agents.
• Software companies: an agent can find pricing and reach the sign-up form.
• Service businesses: an agent can find prices, availability and a way to book.

The free AgentScore scan doesn't test this yet: it marks Task completion “not tested” and works out your score from the other three categories. Ghost Agents test it today, running the journeys you choose on a schedule, with a step-by-step replay of each run, and alerting you when one breaks.

How to measure your agent readiness

1. Run AgentScore. It's free, takes under a minute, and checks Access, Readability and Navigability. Task completion isn't part of the free scan yet.
2. Look at your agent traffic. Your analytics probably can't see agents, because most never run the JavaScript tag. Server or CDN logs can, and Ghost Agent Labs reads them for you. See how to measure agent traffic.
3. Test your money journeys. Checkout, sign-up and booking are the journeys where an agent failure costs you a customer.

A 30-minute starter checklist

Common questions

Won't letting agents in mean letting scrapers in?

No. Agent readiness is about letting in the agents you want, and the main ones can be verified. Keep blocking unknown and abusive bots; just make sure your rules don't catch AI assistants that are bringing you customers.

Do I have to let AI companies train on my content?

No. Training crawlers and the agents that fetch pages for people use different names, so you can block one and allow the other. Our robots.txt guide shows how.

Is this just accessibility?

There's a big overlap, especially in navigation, and work on one helps the other. But agent readiness also covers access rules, machine-readable data, and whether an agent can finish a real task.