Learning Center

Templates

Agent readiness usually needs someone else's yes: a board, a vendor, an agency. These are ready to edit: copy the text or download the file, and replace everything in [square brackets].

Board slide: agent readiness on one page

Heads of e-commerce or digital presenting agent readiness to a board or exec team, once a quarter or when asking for budget.

Download as a text file

# Agent readiness: [quarter, year]

- **What's changing.** Customers are starting to ask AI assistants to research, compare and buy for them. Those assistants visit [your site] the way a customer would, but read it differently. If one can't get in, can't read our prices or can't complete a purchase, it recommends someone else, and the lost customer never shows in our reports.
- **Where we stand.** AgentScore [score] out of 100 ([band]), from [last quarter's score] last quarter. Main issues: [two or three findings, in plain words]. AI agents [can / can't yet] complete [our most important journey, such as checkout] today.
- **What we're doing.** [Fix 1]: [owner], done by [date]. [Fix 2]: [owner], done by [date]. [Fix 3]: [owner], done by [date].
- **How we'll know it's working.** Each quarter we report the trend in AgentScore by category, the pass rate of our key journeys tested with AI agents, agent traffic from our logs (verified and impostors), and visits and orders from AI assistants. We'll present AI referral revenue as a floor, not a total.

**The ask.** [Time, tools or decisions for this stage, such as developer time for the fixes above], reviewed on [date]. One accountable owner: [name, usually the head of e-commerce or digital]. A decision from legal and security on AI training crawlers and verified agents by [date].

---

**Notes for the presenter**

- *Are we letting AI companies take our content?* No. Training crawlers and the assistants that fetch pages for a customer use different names, so we can block one and allow the other. That's a policy choice we make once, with legal.
- *Does this open us up to bots?* Not if it's done properly. We let in the agents we want, checked by verified identity, and keep blocking the rest.
- *What happens if we do nothing?* Probably nothing we'll notice, which is the problem. Some customers' assistants will fail on our site and choose a competitor.
- If you quote any outside figure, cite the source on the slide. If you can't, describe the trend in words instead.

Based on How to explain agent readiness to your board, Who owns agent readiness?, Agent readiness KPIs: what to report each month, Should you block AI crawlers? A decision guide for leaders, A 90-day agent readiness plan for e-commerce teams, Tracking visits and sales that come from AI assistants, AgentScore: Can AI agents use your website?.

Questions for your CDN, bot protection or platform vendor

Whoever manages your CDN, bot protection or e-commerce platform, to send in writing before a renewal, a new contract or a change to bot rules.

Download as a text file

# Questions for [vendor name] about AI agents

Sent to: [named contact]. Date: [date]. Please answer in writing.

Before sending, agree internally which kinds of agent you want: AI assistants that fetch pages for a person, AI search crawlers, training crawlers and browser agents. Our decision: [allow AI assistants and AI search; training crawlers: allow / block].

## Verifying AI agents

1. Which AI agents do you verify, and how: published IP ranges, reverse DNS or signatures? Where is that list kept?
2. Can our rules use categories such as "AI assistants" and "AI search", so we don't maintain a list of names ourselves? How quickly do new agents and changed IP ranges reach your list?
3. Do you verify signed agent requests (Web Bot Auth)? If not yet, what do you use instead?

## AI crawler controls

4. Which agents does your "AI bots" setting cover, and can we treat training crawlers, AI search crawlers and AI assistants differently?
5. Does that setting change our robots.txt, and does it apply automatically to agents you add to a category later?

## Challenges, CAPTCHAs and checkout

6. What does a verified AI assistant get when it hits a challenge rule?
7. Which of our pages have stricter rules or CAPTCHAs by default, including cart and checkout, and how do we switch each one off?
8. Do you add challenges automatically during traffic spikes or sales events?

## Rule order and defaults

9. In what order do managed rules, our custom rules, bot scoring and rate limits run on our plan? Please send the sequence in writing.
10. Does an "allow" for verified bots skip only bot checks, or all security? Which managed rules are on by default for us, and which affect AI agents?
11. Can we run a new rule in log-only mode first, and see what it would have caught?

## Logs and data

12. Do our logs record whether a request was a verified bot and its category, the action taken and the ID of the rule that took it? Can we export full logs rather than samples, and how long are they kept?

## For an e-commerce platform

13. Are product pages rendered on the server with Product structured data (price, currency, availability) per variant? When apps or plugins change prices, does the data use the same source as the displayed price?
14. Can shoppers check out without an account, and is that our default?

---

**What a useful answer looks like.** It names a setting, a page or a document we can check. "We're agent-ready" or "agents are on the roadmap" isn't an answer, so ask again.

**Then check the answers yourself.** Run a free AgentScore scan of [your site] and compare its findings with the answers. Follow up on any answer the results contradict, and repeat after major vendor or platform changes.

Based on Questions to ask your CDN or bot protection vendor, Questions to ask your e-commerce platform about AI agents, Setting up your CDN for AI agents, Bot protection and CAPTCHAs: stop blocking the agents you want, How to tell if an AI crawler is real, Guest checkout: why AI shopping agents need it, Product data that AI shopping agents can read, AgentScore: Can AI agents use your website?.

Agency brief: audit and fix agent readiness

E-commerce and digital leads handing agent readiness work to a web, SEO or development agency or a freelance developer.

Download as a text file

# Brief: agent readiness audit and fixes for [your site]

**From:** [name, role]   **To:** [agency or developer]   **Date:** [date]

## Goal

AI agents (assistants such as ChatGPT, Claude and Perplexity, and browser agents) can reach, read and use our product pages, cart and checkout, so they can recommend us and help shoppers buy.

## Background

- Baseline AgentScore report dated [date], attached. Score [score] out of 100. Main findings: [list].
- Our decision on AI crawlers: [allow AI assistants and AI search; training crawlers: allow / block].
- Platform: [platform name]. Answers from our platform and CDN vendor, where we have them: [attached / to follow].

## In scope

- **Templates:** home, category or collection, product, cart and checkout (where our platform lets you change it)
- **Site files:** robots.txt, sitemap, llms.txt
- **Shared components:** header, navigation, search, pop-ups and cookie banner, variant picker, add-to-cart button
- **Settings:** guest checkout, CAPTCHA settings, [other platform admin settings]

## Out of scope, and who owns it

- CDN and bot protection rules: [security team / CDN vendor, contact]
- Payment provider settings: [finance, contact]
- [Other area]: [owner]

If a finding sits in an area you can't change, raise it with the owner above and record it in your reporting. Please don't park it.

## Deliverables

1. **Audit.** A review of the baseline report that assigns every finding to you or to a named owner.
2. **Fixes.** Changes to the templates, files, components and settings in scope.
3. **Change list.** For each fix: what changed, the pages and components it touched, and the check or journey it was for.
4. **Blockers.** What couldn't be fixed and why, with the owner it was handed to and the date.
5. **Final results.** A final scan report of the live site, and the results of each named journey test.
6. **Upkeep note.** What to re-check after future releases, such as theme updates, new apps or new pop-ups.

## Journeys to test

- [Find a product and reach checkout]
- [Use search to find a product in a given size]

Test with an AI agent, using test data, and stop before payment. Run each journey several times, because AI agents vary.

## How we'll measure success (acceptance criteria)

1. These checks pass in a scan of the live site: [list AgentScore check titles, such as "Product pages give price and stock in a form agents can read"].
2. No check that passed in the baseline scan now warns or fails.
3. Each named journey passes in every run, not just some.
4. Any check marked "not tested" comes with the scan's reason and a manual test.

We'll judge the work by these checks and journeys, not by a target score.

## Timeline

- **Week 1:** Baseline. Scan, journeys and brief agreed.
- **Weeks 2 to 4:** Fixes. Change list updated as work ships.
- **Week 5:** Acceptance. Final scan and journeys against the criteria.
- **After:** Upkeep. Re-check after each release.

## Contacts

- Our owner: [name]
- Security or CDN: [name]
- Platform: [name]

Based on How to brief your agency on agent readiness, Who owns agent readiness?, Reading your AgentScore report: what to fix first, How to test your key journeys with AI agents, Questions to ask your CDN or bot protection vendor, Accessibility work is agent readiness work, AgentScore: Can AI agents use your website?.

Monthly agent readiness scorecard

The owner of agent readiness, to report the same measures on one page each month and compare them with last month.

Download CSV for a spreadsheet

MetricDefinitionTargetThis monthLast monthOwner
AgentScore (overall)Overall score out of 100 and its band from a scan on the same day each month (80 and up Good, 60 to 79 Fair, 40 to 59 Weak, below 40 Poor)Steady or rising, with every drop explained[score, band][score, band][name, e-commerce or digital lead]
AgentScore by categoryScores for Access, Readability and Navigability; note whether Task completion ran, so months compare like for likeSteady or rising[Access / Readability / Navigability][Access / Readability / Navigability][name, e-commerce or digital lead]
Findings fixed and newNumber of scan findings closed this month, and number of new onesNo critical findings open for more than a month[fixed / new][fixed / new][name, e-commerce or digital lead]
Agent visits by typeRequests from search crawlers, AI training crawlers, AI assistants and autonomous agents, from server or CDN logsAI assistant and AI search traffic holding steady or growing[requests by type][requests by type][name, analytics or digital lead]
Verification shareOf requests claiming to be a known agent, the share verified, the share that couldn't be verified, and the share spoofedSpoofed traffic close to zero, or falling[verified / unverified / spoofed %][verified / unverified / spoofed %][name, security or CDN admin]
Blocked agent requestsShare of agent requests answered with 401, 403 or 429, and the agents and pages most affectedBlocks of verified AI assistants near zero[%][%][name, security or CDN admin]
Agent 404 and server error ratesShare of agent requests that got a 404 or a server error, compared with the rate for peopleAbout the same as people; agent 404s trending down[404 % / server error %][404 % / server error %][name, developers]
Journey pass rateFor each key journey tested with AI agents (such as checkout, product search or sign-up): passing, flaky or failing, its pass rate, and where failures clusterMoney journeys passing; failures fixed within a sprint[journey: status, pass rate][journey: status, pass rate][name, developers; journeys chosen by the business]
AI referral visitsVisitors who arrived from AI assistants' answers, by assistant, from your analyticsGrowing from whatever base you start at[visits by assistant][visits by assistant][name, marketing or analytics]
AI referral conversion rateConversion rate of visitors from AI assistants' answersHolds up against your other referral sources[%][%][name, marketing or analytics]
Orders and revenue from AIOrders and revenue from AI referrals, reported as a floor, not a totalGrowing from whatever base you start at[orders / revenue][orders / revenue][name, e-commerce or digital lead]
What changedReleases, bot protection changes, new apps, new agents and campaigns this month, linked to the numbers they movedEvery movement above explained[notes][notes][name, e-commerce or digital lead]

Based on Agent readiness KPIs: what to report each month, Why your analytics can't see AI agents, and how to measure agent traffic, How to tell if an AI crawler is real, Finding the errors AI agents hit, in your server and CDN logs, How to test your key journeys with AI agents, Tracking visits and sales that come from AI assistants, Reading your AgentScore report: what to fix first, Who owns agent readiness?.