---
title: "Is Your Site Agent-Ready?"
description: "Cloudflare quietly shipped a scanner that scores how well your website serves AI agents, and hands you a fix list your coding agent can act on directly."
url: "https://hoeijmakers.net/is-your-site-agent-ready/"
date: 2026-06-18
author: "Rob Hoeijmakers"
site: "hoeijmakers.net"
language: "en"
tags: ["AI in Practice"]
---

# Is Your Site Agent-Ready?

I went back into Cloudflare's AI Crawl Control dashboard to check on bot traffic, the way I do most weeks now, and found a new tab: Optimization. Tucked inside it, a single line: "Check your site." A link to a tool I hadn't seen before, on its own domain: [isitagentready.com](https://isitagentready.com).

## A scanner, not a vibe check

It is a scanner. You give it a URL, it checks the site against a growing list of emerging standards for how AI agents discover and use websites, and it returns a score and a level, from "Basic Web Presence" up to "Agent-Native." Five categories: Discoverability, Content Accessibility, Bot Access Control, API/Auth/MCP/Skill Discovery, and Commerce.

What's interesting is what's actually inside each category. This isn't a vague "AI readiness" score built on vibes. It checks for [robots.txt](https://developers.cloudflare.com/) rules and sitemaps, yes, but also for Markdown content negotiation, MCP server cards, OAuth discovery, Agent Skills, Web Bot Auth, and commerce protocols like x402 that almost nobody has heard of yet. Most of these aren't formal standards. Several are proposals still finding their feet. The scanner doesn't pretend otherwise, but it treats them as real enough to measure, which is itself a useful signal about where things are heading.

## Reachable, not just built

Running it on my own blog turned up something I'd missed. I'd already built Markdown output for AI agents months ago, a `/{slug}.md` route that serves clean Markdown instead of HTML. The scanner pointed out that this only helps an agent that already knows the convention exists. An agent that simply does correct HTTP, sending `Accept: text/markdown` on the normal page URL, got HTML back regardless. The fix was small: one check at the top of the request handler, routing negotiated requests into the Markdown rendering that already existed. The expensive part, parsing the page into clean Markdown, had been built once. Making it reachable a second way cost almost nothing.

That's the pattern worth taking from this, more than the score itself. Most of the categories the scanner checks aren't about building new things. They're about making capabilities you already have reachable through the channel an agent actually uses, rather than the one you assumed it would use.

I wrote earlier about why Markdown keeps winning as the format AI systems converge on, in [Markdown, the WD-40 of Digital Information](https://hoeijmakers.net/markdown-the-wd-40-of-digital-information/). The scanner's content negotiation check is that argument turned into something measurable.## Built for the other window

The tool has a second feature that matters more than the score: a button that generates a full set of fix instructions, written to be copied straight into a coding agent. Not a checklist for a human to interpret and translate into code, but instructions a coding agent can act on directly. That's a small detail, easy to miss, but it says something about who this is actually built for. Not developers researching a topic. Developers who will hand the output straight to whatever Claude or Cursor or Copilot is already open in the other window.

Five categories, most sites starting near zero. Worth ten minutes to see where yours lands.