Are bots 35.5% of traffic, or 61.9%? Cloudflare gave both answers for the same week of August 2026. The difference is not the source but whether you count all requests or only page requests.
Below: both figures with their denominators, our own robots.txt measurement across 600 hosts in four zones, and a finding we did not expect — GPTBot is named in robots.txt more often than Googlebot or Yandex.
Free online tool — HTTP header checker: instant results, no signup.
"Bots are now the majority of traffic" is true and false at once, and the difference is not the source but what gets counted. Cloudflare Radar gives two answers for the same week (20–26 August 2026):
| What is counted | Humans | Bots |
|---|---|---|
| All HTTP requests (pages, images, scripts, APIs) | 64.5% | 35.5% |
| HTML page requests only | 38.1% | 61.9% |
The HTML breakdown goes further: non-AI bots 52.8%, humans 38.1%, AI bots 5.7%, mixed-purpose 3.4%.
The reason is simple: a person pulls dozens of images and scripts per page, while a crawler usually takes the HTML alone. Counted in requests, humans win; counted in pages, they lose.
The denominator is mandatory. Any bot-share figure that does not say whether it counts all requests or only pages is misleading — regardless of who published it.
Cloudflare found 4,365 robots.txt files among the ten thousand largest domains (data as of 24 August 2026) and published the rank order of the most-disallowed AI agents: GPTBot, ClaudeBot, CCBot, Google-Extended, Bytespider, meta-externalagent, Amazonbot, Applebot-Extended. Their per-agent counts are encoded in a chart in a way that cannot be read unambiguously, so we give the order only.
We measured the same thing on our own sample — 600 hosts, 150 per zone, on 27 August 2026, parsing groups per RFC 9309 (consecutive User-agent lines share one rule set):
| Zone | Has robots.txt | Disallows at least one AI crawler | Share |
|---|---|---|---|
| .org | 80 | 10 | 12.5% |
| .com | 85 | 8 | 9.4% |
| .net | 44 | 4 | 9.1% |
| .ru | 97 | 8 | 8.2% |
A caveat without which the table must not be read: each zone has only 4–10 blocking sites. At those counts the zones cannot be told apart — the spread from 8.2% to 12.5% sits inside chance. Only one thing here is solid: roughly one site in ten that has a robots.txt at all closes itself to AI crawlers, and that holds equally across all four zones.
A side observation the numbers support better: robots.txt is more common on .ru sites than on .com — 97 against 85 out of 150.
We counted which agents are mentioned at all in the collected files — not necessarily disallowed, simply named. There were 230 distinct agents. The top of the list (sites out of 600):
| Agent | Sites | Whose |
|---|---|---|
| GPTBot | 41 | OpenAI, training |
| Yandex | 38 | search |
| ClaudeBot | 34 | Anthropic |
| Google-Extended | 34 | Google, AI training |
| CCBot | 29 | Common Crawl |
| meta-externalagent | 29 | Meta |
| Bytespider | 28 | ByteDance |
| Amazonbot | 27 | Amazon |
| Googlebot | 26 | search |
| Applebot-Extended | 26 | Apple, AI training |
Seven of the ten places belong to AI crawlers, and GPTBot outranks both Googlebot and Yandex. That is indirect but telling: site owners now write rules more often for the machines that train models than for the machines that bring visitors.
On Yandex specifically: its agents appear across all four zones, but in our data no site closes access to it outright — the mentions come alongside indexing settings, not prohibitions.
A Cloudflare press release dated 13 July 2026 puts automated traffic at roughly 57%, and a 1 July blog post says "more than 50% of traffic on the Internet is now non-human". Neither states a measurement period, a population or a methodology, and neither reconciles with Cloudflare Radar’s own data for the same months (35.5% across all requests).
There is a counterweight too. Akamai — a vendor with every commercial incentive to say the opposite — puts AI bots at nearly 1% of all bot traffic on its network. The widely quoted "300% growth in AI bots" is measured from that base, but retellings never carry the base itself.
The general rule for this topic: every available figure measures a particular vendor’s customer base, not the internet. Cloudflare sees sites behind Cloudflare; Imperva sees those who bought bot protection, i.e. those who already had a problem; Fastly sees its own applications. No neutral measurement of the whole internet exists, and that deserves saying out loud.
The easiest way to see what your own site gets is your logs. To check the file itself is well-formed, use the robots.txt checker.
Reverse DNS lookup on the IP + check it resolves back to google-crawler.google.com. Only after verification treat as legit.
Depends. If you want citations in Perplexity/ChatGPT — allow them. If content is paid/proprietary — block via robots.txt or CF rule.
Yes, global average 40-50%. Trend upward due to AI scraping and AI-content monetisation.
Access logs + robots.txt audit. Plus Enterno Pro dashboard shows bot % by User-Agent.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.