Someone running an SEO agency asked a blunt question in r/aeo on November 3. Were other agencies actually using the agent readiness checker that Frase had folded into its free tools? Or was everyone still guessing?
Three people replied over the next two days. Not one of them said yes with any confidence. They talked about crawl logs and robots.txt instead.
That mix-up is the whole story. A new kind of free tool showed up in SEO kits this year. Most people writing about it still confuse it with the AI visibility trackers they already run. An agent readiness checker doesn't ask whether ChatGPT mentions your brand. It asks whether an AI agent can get into your site at all, and once it's in, whether it can do anything useful.
What an agent readiness checker actually tests
The best-known version launched April 17, 2026, when Cloudflare put a free scanner at isitagentready.com. Enter a URL, and it grades the site across four areas.
| Area | What it looks for |
|---|---|
| Discoverability | robots.txt, sitemap.xml, link headers |
| Content | Pages served as markdown when an agent asks for one |
| Bot access control | Content Signals, AI-specific robots rules, Web Bot Auth |
| Capabilities | Agent Skills, an API catalog, OAuth discovery, MCP server cards |
Cloudflare's own write-up of the launch is worth reading past the headline. It reported that 78% of sites have a robots.txt file. Most of those were written for Googlebot, years before an AI agent ever read one. Only 4% have declared any AI preference through the newer Content Signals standard, Cloudflare found, and fewer than 15 sites worldwide support MCP server cards or an API catalog at all.
Frase and Lumar built their own lighter versions soon after. Both aim at marketers rather than developers. Neither goes as deep into the capabilities layer as Cloudflare's does.
Our own AI search readiness checklist already covers the crawler and content side of this. It works bottom-up through five layers before content quality enters the picture at all. An agent readiness checker lives almost entirely inside that checklist's first layer, with the newer agent-protocol items stacked on top.
What agencies are already checking by hand
The most useful reply in that r/aeo thread skipped the new standards almost entirely. One agency owner described what they walk through for every client instead.
Start with robots.txt, plus whatever sits in front of it. Bot protection at the CDN or firewall level blocks crawlers even when robots.txt looks clean on its own. Turn JavaScript off next. If the page's real text and prices vanish, an agent sees a mostly empty shell.
After that, check whether pricing, contact and booking are reachable through plain links. Buttons that only fire once a script loads don't count. A sitemap and an llms.txt file help too, the agency owner wrote, but called them nice to have, not the main thing. Scripted, multi-step agent journeys, an agent actually completing a purchase end to end, got flagged as interesting but still too early to build a standard check around.
That's four checks, run by hand. Together they cover most of what the automated scanners above also test. The real difference is cadence. A person doing this once a quarter catches what the next rebuild breaks. A scanner you ran once and never opened again won't.
The same site, five different scores
A developer named Aman Jha ran five of these free checkers against one site, gifsy.fun, on the same afternoon. He wrote up what happened on Dev.to. Cloudflare gave it 20 out of 100, and Frase gave it 81. A tool called Actuity gave it 87, and Google's Lighthouse agentic-browsing audit passed it outright.
His conclusion was blunt. No tool was wrong, he said. They were measuring different things, and most of the field tests one of two separate questions without saying which one.
Cloudflare's harsh score came from grading against brand-new standards, MCP and WebMCP, that almost nothing on the web supports yet. Frase and Lighthouse stuck closer to basics. They check whether real content renders without JavaScript and whether a bot gets blocked outright. Actuity did something none of the others did. It sent an actual agent to try to finish a task on the site, instead of just reading the page's signals.
That last distinction matters more than any single score. Reading a page and acting on a page are not the same skill. A checker built for one tells you almost nothing about the other.
If you only have time to run one, run Cloudflare's. It grades against where the standards are heading, not where most of the web sits today. A passing score there carries more weight than a passing score anywhere else.
How often does ChatGPT mention your brand?
Most founders have no idea. The answer might surprise you.
It answers a different question than AI visibility does
One reply in that original r/aeo thread put the split better than most explainers manage. A client asking whether AI agents can use their site usually means one of two things, the commenter said. Either they want an agent to complete an action, like booking or buying something. Or they just want to come up when someone asks an AI engine a question about their category.
The first is what an agent readiness checker grades. Can a crawler reach the page, read it, and find a documented way to act on it? The second has nothing to do with robots.txt. It's whether AI visibility tracking across ChatGPT, Perplexity, Gemini and Claude shows your brand actually getting named for the questions buyers ask.
A site can pass every protocol check and still never get mentioned by an AI engine. Citation depends on trust signals and third-party coverage that a scanner never looks at. A brand-new SaaS with a flawless llms.txt file and zero reviews anywhere else will score well on a readiness checker. It can still lose to a five-year-old competitor every AI engine already trusts.
The opposite happens too. A brand that gets cited often can still block the very crawlers doing the citing, usually by accident, through a bot rule nobody reviewed before it shipped. A marketing team can spend a quarter earning mentions while a security team quietly locks the front door.
Why this became its own category in 2026
Readiness checkers exist because AI agents stopped being a future thing to plan for. ChatGPT, Perplexity and Claude each run crawlers that fetch pages with no browser behind them. A short list of new standards is trying to give those crawlers a cleaner way to ask for what they need, instead of scraping a page built for a person.
What's easy to miss is how far the phrase has traveled outside SEO already. Clerk, the developer authentication company, now ships a weekly "Agent Readiness" update to its own product. A recent one covered letting an agent create a user or deploy code on a customer's behalf. The term has started to mean something closer to "can software act here" than "will an AI engine cite me." That's part of why the two keep getting mixed up.
Cloudflare's scanner also tracks a newer set of commerce standards. Things like x402 and an emerging Agentic Commerce Protocol would let an agent actually pay for something on a site. Support is rare enough that Cloudflare doesn't count it toward the main score yet, which says plenty about how early this still is.
15 hours a week manually. Or 15 minutes with RankControl.
Track citations, monitor competitors, and fix content gaps across every AI search engine. Automatically.
A score from today won't hold next month
A free, one-time report can't fix the part that actually breaks things later. A CDN rule change or a new firewall vendor can undo a passing score without anyone noticing for weeks. The checkers themselves are static snapshots of a system that keeps moving underneath them.
This is a monitoring problem that gets sold as a one-time audit. Running two or three of these checkers and fixing what they flag is maybe half a day of work the first time.
Watching whether that fix survives the next infrastructure change is the part nobody puts on a calendar. That's where most of the real risk sits.
RankControl doesn't sell a standalone protocol scanner like Cloudflare's, and we wouldn't claim to. What we check every week instead is whether ChatGPT, Perplexity, Claude, Gemini, Grok and Google's AI surfaces are actually citing you. That sits a layer above the plumbing these tools grade. For the plumbing itself, our free AI crawler checker and llms.txt generator cover the two most common failure points, any time you've just changed infrastructure and want a fast answer.
You can run all of this by hand, on your own schedule, a checker here and a crawler log review there. Or you can let the citation half run on its own every week, while the protocol half stays on a simpler cadence, since that layer changes far less often.
Do you actually need one
Yes, probably, and it costs nothing to find out. Run one before a launch. Run one right after switching CDN or firewall providers, or anytime a developer mentions tightening up bot rules without saying which bots got caught in the net. It takes less time than writing the ticket to ask someone else to check.
What it won't tell you is whether the fix holds. It also won't tell you whether any of this moves AI engines any closer to recommending you. That needs a check that runs on a schedule, not a URL box you visit once and forget.
A short list to run this week
Here's the order that actually covers both halves of the problem.
- Run your homepage and your two or three most important pages through a free checker, and write down what fails.
- Open
robots.txtand confirm OAI-SearchBot, PerplexityBot, ClaudeBot and Googlebot aren't blocked by a rule meant for something else. - Check your CDN or firewall for a bot rule that blocks those same crawlers at a layer
robots.txtcan't see. It's the most common false pass. - Add an
llms.txtfile if you don't have one yet. Most sites still don't. - Separately, check whether any AI engine currently names your brand for the questions buyers actually ask. A clean protocol score says nothing about this.
AI search traffic grew 835% this year. Is your content ready?
RankControl generates 26 content formats optimized for ChatGPT, Claude, and Perplexity. Published on your domain, matched to your brand.
