What changed · 8-12 September 2026

Half the new surfaces were not there

The instrument changed this week, and the numbers got worse because of it. Every movement is now asked for a path that cannot exist before anything it publishes is believed. The raw comparison between the 8 and 12 September passes found 247 new surfaces. 79 of them sat on servers that answer as if publishing when asked for a file that is not there, and 50 more did not hold up on a second live query. 118 survived. Last week the same check passed 69% of arrivals; this week it passes 48%. The web did not get worse at publishing. We got better at not counting servers that answer anything. Among what did survive, the clearest single movement is un.org, which still serves a robots.txt and no longer names a single AI crawler in it. That is not a closure: nothing in that file blocks the whole site. It is the end of treating AI crawlers as a separate case. Counts cover only surfaces read successfully on both passes.

Started publishing 118

Domains that did not have the file on the earlier pass and did on the later one. Not "they published it this week": it is when we saw it.

SurfaceDomains
/llms.txt83
robots.txt AI directives15
/agents.md6
/.well-known/ai-catalog.json6
/.well-known/mcp.json3
/.well-known/ard.json3
DNS-AID record1
/.well-known/agent-card.json1

Withdrawn 78

The file was there and is now gone: a 404 or 410, an empty file, or an HTML page where a text file used to be. A failed read does not count as a withdrawal, and neither does a server that answers every path we ask it for.

SurfaceDomains
robots.txt AI directives54
/llms.txt16
/.well-known/agent-card.json3
/.well-known/ard.json2
/.well-known/ai-catalog.json1
/agents.md1
/.well-known/mcp.json1

Edited 3614

Same file, different content. Immune to a server flapping: it only counts when both reads succeeded and the bytes differ.

SurfaceDomains
robots.txt AI directives2598
/llms.txt961
/agents.md26
/.well-known/mcp.json10
/.well-known/ard.json8
/.well-known/ai-catalog.json7
/.well-known/agent-card.json4

Download every domain that moved (CSV) · raw JSON

How this is measured

To put a number in context: 118 new publishers is 0.023% of what we could compare. The interesting weeks in this series are likely to be the quiet ones.
Corrections: checkpoint.com appeared this week as a new /llms.txt and is not counted below. Last week's edition reported the same domain as a withdrawal and corrected that by hand. Checked again on 13 September: a GET follows to www.checkpoint.com and returns a real 12.5 KB file, while a HEAD to the same path still answers HTTP 202 with an AWS WAF challenge header. The file was most likely there the whole time and what changed is that we could read it. Publishing as an arrival what we published as a withdrawal seven days ago would be reporting our own instrument, so the movement is reclassified as blocked rather than deleted. · The percentages here are not comparable with the previous edition. That one was measured with crawler 2eb4a18e7079's predecessor, before the canary existed. Within this edition both passes share an instrument, which is what makes the counts valid; across editions the instrument moved, which is what makes the trend meaningless.

Same crawler and methodology as the monthly census. Who runs this and where the data lives: about.

Free check
Is AI recommending your site? Ask one question to one engine, three samples, free.
Same measurement as the paid watch: a failed sample is never counted as a zero.
Run the free check →