# Cloudflare wants your site agent-ready. Here is what that takes. > In August Cloudflare set out its plan for the agentic internet: pages that agents can read and act on, plus a dashboard to measure visibility. Some of it is product you can switch on today. Here is what is actually in it, and the prerequisite most coverage skips. **Côme Chevalier**, Product Manager, CrawlerPal · September 22, 2026 · Technical GEO Canonical: https://crawlerpal.com/blog/cloudflare-agent-ready-what-it-takes --- In August, Cloudflare published The Agentic Internet, its case that AI agents are a new kind of visitor and that websites need new plumbing to serve them. Much of the post is vision. Some of it is product you can switch on today. Those are worth separating, because the product part changes what the technical side of GEO looks like. ## What is actually in it Cloudflare names a lot of pieces. Grouped by the job each one does, they look like this. | Job | Cloudflare piece | What it does | | --- | --- | --- | | Readable pages | Markdown for Agents | Serves an agent-friendly Markdown version of a page from the edge, so an agent does not have to parse your HTML | | Actions agents can take | WebMCP | The site registers explicit tools with a schema, so an agent calls a booking or an enquiry directly instead of guessing at a form | | Knowing who visits | Web Bot Auth | Crawlers prove who they are cryptographically, so you allow or block by identity rather than by a user agent string anyone can fake | | Getting paid | Wallets, Monetization Gateway, x402 | Agents pay for content and APIs | | Measuring it | AEO dashboard | Tracks how visible a brand is across the models and agents its customers use | There is also AI Search, which Cloudflare describes as available today, along with Code Mode and anonymous access tokens for trusted agents. Every one of these is opt-in. Nothing switches on by default. ## The prerequisite most coverage skips The managed features live at the edge of Cloudflare's network. They work for sites that route their traffic through Cloudflare. If your site sits behind another CDN or on your own hosting, those features do not reach you until you move your DNS and proxy across. Two of the pieces are open standards rather than Cloudflare products. MCP and the x402 payment standard can be implemented anywhere. The switch-it-on convenience is Cloudflare's, though, and that convenience is most of what is on offer. Moving a site's proxy is rarely a marketing decision. For most mid-market brands it belongs to IT and carries its own risk. It deserves to be decided on those terms, and not folded into a GEO project because one feature looked useful. So the useful first question is simple: are you on Cloudflare already? If you are, most of this is configuration. If you are not, it is a migration with a case of its own to make. ## What is quietly missing The post never mentions llms.txt. Cloudflare's answer to making a site readable to agents is Markdown for Agents, generated on request at the edge, rather than a text file sitting at the root of your site. That is worth noticing from a company that says it sits between billions of people and the sites they visit. Serving your content in a form an agent can use is a different thing from publishing a file that points at your content. Only the first one actually puts something in front of the agent. ## One word worth watching Cloudflare expands AEO to Agent Engine Optimization. Most of the industry uses the same letters for Answer Engine Optimization. The two overlap heavily without being identical. Optimising for agents includes letting one complete a booking on your site, which is a separate job from getting your brand named in an answer. When AEO shows up in a proposal, ask which one is meant. ## What it does not do Cloudflare supplies the pipes. It does not decide what flows through them. Markdown for Agents hands an agent a cleaner copy of your page, and a clean copy of a weak page is still a weak page. Bot identity tells you which agent is knocking, while the call on which ones to let in stays with you. The dashboard can show that you are hard to find without telling you why. The content engines quote, and the outside sources that mention you, are still the work. The infrastructure makes that work easier to deliver. It does not do it for you. ## What I would do If you are already on Cloudflare, turn on Markdown for Agents and look at which bots are actually hitting you before you decide what to block. Both are cheap, and the second one usually surprises people. If you are not, do not migrate for this on its own. Fix what agents read on the setup you already have, because the pages matter more than the pipe. Either way, be careful with the dashboard number until you know exactly what it counts. A bot fetching your page is a different event from your page being cited in an answer, and a lot of visibility reporting quietly treats them as one. ## Frequently asked questions ### Do I need to be on Cloudflare to use this? For the managed features, yes. Markdown for Agents, bot verification and the AEO dashboard run at Cloudflare's edge and only reach sites that route their traffic through it. MCP and the x402 payment standard are open standards you could implement elsewhere, but the switch-it-on setup is Cloudflare's. ### Does Markdown for Agents replace llms.txt? They are different mechanisms. llms.txt is a file that points agents at your content. Markdown for Agents serves the content itself in a cleaner format. Cloudflare's announcement does not mention llms.txt at all, which says something about where it thinks the real work happens. ### Is Cloudflare's AEO the same as answer engine optimization? Not quite. Cloudflare means Agent Engine Optimization, which includes letting agents take actions on your site, such as completing a booking. Answer engine optimization is about being named and cited inside AI answers. The two overlap heavily, so it is worth checking which one a proposal means. ### Will the AEO dashboard tell me whether I am being cited? It reports visibility. Before relying on the number, find out exactly what event it counts. A crawler fetching your page and an engine citing your page inside an answer are very different things, and visibility reporting does not always keep them apart. --- CrawlerPal · https://crawlerpal.com