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… See the full description on the dataset page: https://huggingface.co/datasets/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.
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.
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
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-ExtendedandApplebot-Extendednever 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>
