AI crawler access on next.js sites
252 of the 1,638 sites measured in this segment refuse a request from an identified AI user agent at the edge, 15% of the segment, against 7% whose robots.txt disallows an answer engine at the site root. The block that costs these sites citations is not the one written in the file. That answer-engine rate is level with the corpus rate of 6%, which is itself measured across 30,342 domains.
Mean AI access score across those 1,638 sites is 75.1 of 100, 258 of them publish an llms.txt (16%), and 892 publish structured data an answer engine can parse (54%).
Block rate by crawler, inside this segment robots.txt at the site root
| Crawler | Operator | Content used for | Block rate | Blocking | Measured |
|---|---|---|---|---|---|
| CCBot | Common Crawl Foundation | archive | 10.6% | 173 | 1,638 |
| Bytespider | ByteDance | training | 10.3% | 169 | 1,638 |
| GPTBot | OpenAI | training | 10.3% | 168 | 1,638 |
| ClaudeBot | Anthropic | training | 8.4% | 138 | 1,638 |
| Applebot-Extended | Apple | training | 7.6% | 125 | 1,638 |
| Meta-ExternalAgent | Meta | training | 7.6% | 124 | 1,638 |
| Google-Extended | training | 7.2% | 118 | 1,638 | |
| Amazonbot | Amazon | training | 7.2% | 118 | 1,638 |
| anthropic-ai | Anthropic | training | 5.5% | 90 | 1,638 |
| cohere-ai | Cohere | live retrieval | 4.9% | 81 | 1,638 |
| omgilibot | Webz.io | training | 4.8% | 78 | 1,638 |
| FacebookBot | Meta | training | 4.7% | 77 | 1,638 |
| SemrushBot-OCOB | Semrush | training | 4.6% | 75 | 1,638 |
| omgili | Webz.io | training | 4.4% | 72 | 1,638 |
| Diffbot | Diffbot | training | 4.4% | 72 | 1,638 |
| ChatGPT-User | OpenAI | live retrieval | 4.4% | 72 | 1,638 |
| PerplexityBot | Perplexity | answer index | 4.0% | 65 | 1,638 |
| Timpibot | Timpi | training | 3.7% | 60 | 1,638 |
| Scrapy | Zyte (open-source framework) | training | 3.1% | 50 | 1,638 |
| ImagesiftBot | ImageSift (Hive) | training | 3.0% | 49 | 1,638 |
| AI2Bot | Allen Institute for AI | training | 3.0% | 49 | 1,638 |
| Perplexity-User | Perplexity | live retrieval | 2.7% | 45 | 1,638 |
| cohere-training-data-crawler | Cohere | training | 2.7% | 45 | 1,638 |
| YouBot | You.com | answer index | 2.7% | 44 | 1,638 |
| OAI-SearchBot | OpenAI | answer index | 2.4% | 39 | 1,638 |
| Claude-User | Anthropic | live retrieval | 2.2% | 36 | 1,638 |
| MistralAI-User | Mistral AI | live retrieval | 2.0% | 33 | 1,638 |
| Meta-ExternalFetcher | Meta | live retrieval | 2.0% | 32 | 1,638 |
| Claude-SearchBot | Anthropic | answer index | 2.0% | 32 | 1,638 |
| Google-CloudVertexBot | live retrieval | 1.7% | 28 | 1,638 | |
| PanguBot | Huawei | training | 1.6% | 27 | 1,638 |
| DuckAssistBot | DuckDuckGo | live retrieval | 1.5% | 25 | 1,638 |
| Kangaroo Bot | Kangaroo LLM | training | 1.3% | 21 | 1,638 |
| TikTokSpider | ByteDance | live retrieval | 1.0% | 17 | 1,638 |
| Applebot | Apple | answer index | 0.8% | 13 | 1,638 |
| Meta-WebIndexer | Meta | answer index | 0.5% | 9 | 1,638 |
| GoogleOther | training | 0.5% | 8 | 1,638 | |
| Amzn-SearchBot | Amazon | answer index | 0.4% | 7 | 1,638 |
| Meta-ExternalAds | Meta | training | 0.3% | 5 | 1,638 |
| Amzn-User | Amazon | live retrieval | 0.2% | 3 | 1,638 |
| Googlebot-News | answer index | 0.1% | 2 | 1,638 | |
| Googlebot | answer index | 0.1% | 2 | 1,638 | |
| msnbot | Microsoft | answer index | 0.1% | 1 | 1,638 |
| facebookexternalhit | Meta | live retrieval | 0.1% | 1 | 1,638 |
| Bingbot | Microsoft | answer index | 0.1% | 1 | 1,638 |
| OAI-AdsBot | OpenAI | live retrieval | 0.0% | 0 | 1,638 |
| MistralAI-Training | Mistral AI | training | 0.0% | 0 | 1,638 |
| MistralAI-Index | Mistral AI | answer index | 0.0% | 0 | 1,638 |
Block rate is the share of this segment's domains holding a policy record for that agent whose robots.txt disallows it at the site root, shown with its numerator and denominator. Denominators differ between agents because a record only exists once a domain has been measured for it. A domain serving no robots.txt counts as allowing everything, which is what the standard specifies.
Most accessible
| Domain | Score | Engines blocked | llms.txt | |
|---|---|---|---|---|
| 1 | testmuai.com | 99 | 0 | yes |
| 2 | lambdatest.com | 99 | 0 | yes |
| 3 | vast.ai | 98 | 0 | yes |
| 4 | pipedrive.com | 97 | 0 | yes |
| 5 | promptwatch.com | 97 | 0 | yes |
| 6 | rss.app | 97 | 0 | yes |
| 7 | beautyplus.com | 97 | 0 | yes |
| 8 | ujet.co | 97 | 0 | yes |
| 9 | candid.org | 97 | 0 | yes |
| 10 | bankaletihad.com | 97 | 0 | yes |
| 11 | konghq.com | 96 | 0 | yes |
| 12 | midphase.com | 96 | 0 | yes |
| 13 | turkcell.com.tr | 96 | 0 | yes |
| 14 | exclaimer.net | 96 | 0 | yes |
| 15 | myob.com | 96 | 0 | yes |
Highest AI access scores among the 1,638 sites measured in this segment.
Least accessible
| Domain | Score | Engines blocked | llms.txt | |
|---|---|---|---|---|
| 1 | education.gov.in | 30 | 0 | no |
| 2 | mohfw.gov.in | 30 | 0 | no |
| 3 | dord.gov.in | 31 | 0 | no |
| 4 | bmstu.ru | 32 | 0 | no |
| 5 | voi.com | 33 | 0 | no |
| 6 | pancakeswap.finance | 34 | 0 | no |
| 7 | gartic.io | 37 | 0 | no |
| 8 | spa.gov.sa | 37 | 0 | no |
| 9 | garticphone.com | 40 | 0 | no |
| 10 | strategy.com | 40 | 0 | no |
| 11 | duetapp.net | 41 | 0 | no |
| 12 | azarlive.com | 41 | 0 | no |
| 13 | fireant.vn | 42 | 0 | no |
| 14 | 1000kitap.com | 44 | 0 | no |
| 15 | podbay.fm | 45 | 0 | no |
Lowest AI access scores among the same 1,638 sites.
Compare with the rest of the grouping publishing platform segments
The largest 10 other segments in this grouping, ordered by size. The share beside each is that segment's own answer-engine block rate over its own count. Full table on the segments index.
What this segment does not tell you read this before citing it
Platform detection relies on a generator meta tag, so coverage is partial and skewed. A site that strips the tag, or a system that never writes one, is invisible here. These rows therefore over-represent platforms that advertise themselves and say nothing at all about the ones that do not.
Measure your own domain
The audit that produced every number on this page runs on any domain in about six seconds: robots.txt resolved for 48 agents, then live requests sent as four of them to see whether the edge agrees with the file.