How to explain agent readiness to your board
Your board doesn't need to know what robots.txt is. It needs to know what's changing, what that risks for the business, what you're doing about it, and how it will know the work is paying off. Here's a way to say all of that on one page, without hype and without numbers you can't stand behind.
The one-page version
Start with this structure. Each heading is one or two sentences. Fill in the bracketed parts with your own findings.
What's changing. People are starting to ask AI assistants to research, compare and buy on their behalf. Those assistants visit our website the way a customer would, but they read it differently.
Why it matters to us. If an assistant can't get in, can't read our prices or can't complete a purchase, it recommends someone else, and we never see the lost customer in our reports.
Where we stand. [Our AgentScore, the main issues it found, and whether AI agents can complete our most important journey today.]
What we're doing. [Three to five fixes, who owns each, and when they'll be done.]
What we need. [Time, tools or decisions, each with a review date.]
That's it. Everything below is about filling it in well.
Explaining the shift without hype
Boards have heard a lot about AI. The quickest way to lose the room is a slide of large market forecasts. You don't need them. The argument for agent readiness is modest and easy to defend:
- AI agents already visit websites for people. You can show this from your own server or CDN logs.
- Nobody knows how fast this will grow. That's a reason to be ready cheaply now, not to wait for certainty.
- Much of the work also improves accessibility, search and site quality, so it isn't a bet on one trend. See accessibility work is agent readiness work and SEO got you found. Agent readiness gets you chosen.
- The failure is silent. A blocked agent doesn't complain. It goes elsewhere. That makes it the kind of risk a board should want someone to own.
If you quote any outside figure, cite the source on the slide. If you can't, describe the trend in words instead.
The risks, in board language
| Risk | What it looks like | Usually owned by |
|---|---|---|
| Lost revenue | AI assistants are blocked by bot protection, can't see prices, or fail at checkout, so they recommend or buy from a competitor. | E-commerce or digital lead |
| Being misquoted | Assistants give customers the wrong price, stock or return policy because our pages are hard to read or out of date. | Marketing and content |
| Impostors | Scrapers pretend to be well-known AI agents to get past our defenses. Opening the door carelessly makes this worse. | Security |
| Content and legal | Decisions about AI training on our content, our terms of service, and responsibility for purchases an agent makes for a customer. | Legal, with marketing |
| Blind spots | Our analytics can't see most AI agents, so decisions are made on incomplete data. | Analytics or digital lead |
The point of the table is that this is a cross-team issue with no natural home. Ask the board to agree one accountable owner. See who owns agent readiness?
What to measure
Pick a few measures you can report every quarter, and show the trend rather than a single figure.
- AgentScore, by category. Access, Readability and Navigability tell you whether agents can get in, understand your pages and find their way around. The free scan doesn't test Task completion, so don't present its score as proof that agents can buy.
- Journey pass rate. Whether AI agents can complete your most important journeys, such as checkout or sign-up, from scheduled Ghost Agent tests.
- Agent traffic. How many requests come from AI assistants and search agents, how many are verified, and how many are impostors, from your logs. See how to measure agent traffic.
- Visits and orders from AI assistants. People who click through from an assistant's answer. See tracking visits and sales from AI assistants.
- Time to fix. How long a critical finding, such as AI agents being blocked, stays open.
Be careful with attribution. You can show that more agents get through and more journeys pass. You usually can't prove exactly how much revenue that produced, and the board will trust you more if you say so. For a fuller set, see agent readiness KPIs.
What to ask for
Keep the ask small and staged, with a review point after each stage. A typical shape:
- A baseline. A scan, a look at agent traffic in your logs, and one tested journey. This needs a few days of people's time, not a project.
- Fixes. Developer and content time to work through the findings. Much of it overlaps with work already on the accessibility and SEO backlog, so say where it does.
- Ongoing testing and monitoring. Tools that keep watching after the fixes, because a theme update or a new bot rule can undo them.
- Decisions. Time from legal and security to settle policy questions such as AI training crawlers and verified agents.
- Optional experiments. Newer interfaces such as MCP and WebMCP or agentic commerce protocols, framed as small trials with a date to decide whether to continue.
Our 90-day agent readiness plan maps well onto the first three stages.
Questions you'll probably get
Are we letting AI companies take our content?
No. AI training crawlers and the assistants that fetch pages for a customer use different names, so you can block one and allow the other. That's a policy choice to make once, with legal. See should you block AI crawlers?
Does this open us up to bots?
Not if it's done properly. The goal is to let in the agents you want, checked by verified identity, and keep blocking the rest. See how to tell if an AI crawler is real.
What happens if we do nothing?
Probably nothing you'll notice, which is the problem. Some customers' assistants will fail on the site and choose a competitor, and it won't show up in any report you currently read.
To fill in "Where we stand", run a free AgentScore scan. It takes under a minute and gives you a score out of 100 and a list of what to fix.