DeusHorizon/agent-web-index

Agent Web Index — how much of the web can AI assistants actually read?

48,154 domains measured live. 25% of them cannot be read by at least one of ChatGPT, Claude, Perplexity or Gemini. Updated daily. Live index: https://shop.lumnika.com/ai-readiness/

Every row here is the result of real HTTP requests, not an estimate and not a re-publication of someone else's crawl: each domain's homepage is requested once as a browser and once as each of the published AI crawler user-agents, its robots.txt, llms.txt and sitemap are read, and the answers are compared.

The number that exists nowhere else

robots.txt says the crawler may come in — and the server refuses it anyway. You can only see this by making the request as that crawler, which is why no robots.txt study reports it.

Crawler	Domains measured	Served	robots.txt says no	Server says no anyway
claudebot	48,154	84%	2,001	6,800
gptbot	48,154	85%	2,526	6,464
oai-searchbot	48,154	90%	783	4,570
perplexitybot	48,154	90%	1,194	4,453
meta-externalagent	39,409	89%	1,119	3,923
amazonbot	39,409	86%	1,208	5,187
bytespider	22,438	88%	585	2,520
applebot	22,438	96%	87	932

Broken down by whoever answers in front of the site (read from the response headers of the same request: cf-ray, akamai-grn, x-amz-cf-id, x-fastly-request-id…). Unit: one domain × one crawler, counted only where that site's robots.txt allows that crawler — so every refusal below contradicts the site's own stated policy, and is almost always an edge default nobody chose.

Edge in front of the site	Domains	Requests robots.txt allows	Refused anyway
Akamai	788	4,376	38%
Google	791	4,978	33%
Sucuri	64	393	21%
AWS CloudFront	3,141	17,208	16%
Azure Front Door	311	1,611	11%
no known edge	12,212	70,190	11%
Cloudflare	26,923	186,953	10%
DDoS-Guard	304	1,747	10%
Varnish	408	2,101	8%
Fastly	1,475	7,710	8%

no known edge is an upper bound, not a vendor: response headers are not kept, so a domain read before a signature was added to the table stays in that bucket until it is re-requested (a 250-domain sample on 19 Sep 2026: 14% already carry a signature the current table recognises). A weekly pass re-reads them, so the named vendors above are undercounts.

Files

File	What it is
agent-web-index.csv	one row per domain: score, grade, per-check breakdown, per-crawler verdict, edge vendor, date
aggregate.json	today's aggregate, exactly as the live index publishes it
daily/<date>.json	the immutable daily snapshot of the aggregate — this directory is the series

Method, and what it does not cover

• One vantage point (Europe), one page per domain (the homepage), 12-second timeout per request.
• Rank-bearing domains come from the Tranco research list (30-day average of five rankings); the rest come from public e-commerce platform seeds.
• Google-Extended and Applebot-Extended never make requests — they are robots.txt opt-out tokens — so for those only robots.txt is reported and no "served" verdict exists.
• Domains that answer with HTTP 429 are excluded from that pass rather than counted as blocking.
• 15,947 measured hosts are infrastructure (CDNs, telemetry, resolvers) rather than sites and are counted apart; 22,667 failed to answer and are excluded from every percentage.
• Blocking AI crawlers is a legitimate choice, not a failure. This dataset records what is true, not what should be.

Citing

Agent Web Index, 2026-09-22. 48,154 domains. https://shop.lumnika.com/ai-readiness/

Licence: CC BY 4.0 — use it, say where it came from.

Audit a single site live, for free, no signup: https://aivis.lumnika.com/en?src=agentindex#scan