X thread — Agent Readiness Report: Cloudflare
7 tweets. Tweet 1 leads with score + dominant theme + tags. NO link in tweet 1 (X throttles link-leading threads). Link lands in tweet 7. Tags @Cloudflare and @CloudflareDev on tweet 1.
Tweet 1 (271 chars)
@Cloudflare wrote the Agent Readiness Score post the industry now cites.
We pointed our scorer at theirs first.
40/100. Level 2.
One subdomain works. Two don’t. The blog hosting that very post lands at Level 1.
The story is the variance: 40 / 25 / 15.
@CloudflareDev
Tweet 2 (254 chars)
developers.cloudflare.com is the high water mark.
Real /llms.txt, structured, per-product split + a full-archive file for large-context models.
Hit any docs URL with Accept: text/markdown and you get markdown. Not HTML.
20/20 on content-accessibility.
Tweet 3 (264 chars)
Cloudflare’s robots.txt declares Content-Signal: ai-train=yes, search=yes, ai-input=yes — their own protocol.
Our rubric didn’t credit it. We shipped v0.1.2 to fix that.
Even after the fix: blog.cloudflare.com lands at 15/100. Same protocol, almost nothing else.
Tweet 4 (276 chars)
Fix #1: ship an MCP Server Card from cloudflare.com. Reference it from the homepage hero.
Cloudflare already runs MCP servers in prod.
An agent reading cloudflare.com cannot tell. The capability is real. The signal isn’t.
Worth 30 points across every surface.
Tweet 5 (265 chars)
Fix #2: lift /llms.txt to the blog and ship /AGENTS.md on all three surfaces.
The dev subdomain has the pattern. cloudflare.com publishes /llms.txt. The blog still doesn’t.
Same hosting, same robots.txt. Add the file. Add the rules.
Lowest-effort fix.
Tweet 6 (267 chars)
Fix #3: keep Content-Signal AND add per-named-bot blocks.
GPTBot. ClaudeBot. anthropic-ai. Google-Extended. PerplexityBot. CCBot.
Belt and suspenders. Content Signals is good. While adoption is early, the named-bot block is what other rubrics still score.
Tweet 7 (240 chars)
First in a bi-weekly Agent Readiness Reports series. Scoring named products against the Agents First framework.
Full report — rubric, raw probe data, top fixes:
https://agentsfirst.dev/reports/cloudflare/
Tweet count: 7. All tweets under 280 chars.
Tags: @Cloudflare and @CloudflareDev on tweet 1; report URL only on tweet 7 (X throttles link-leading threads ~40%).
Note: tweet body is the text shown to the reader between > lines, including blank lines as \n chars. The > markdown markers and “Tweet N” labels are NOT part of the tweet.