Separate reader traffic
Cloudflare Radar's Bot Directory makes bot names, categories, and sources searchable, which turns suspicious-traffic review into a repeatable verification step.
Operators can combine the directory with user agents, paths, countries, devices, and log samples before changing access rules.
Requests are not readers
The useful question is not whether traffic looks busy; it is which activity represents readers, monitoring, crawlers, retries, or system errors.
Check the logs first
- Create a review table with bot name, category, target path, frequency, and policy action
- Keep the test narrow: one low-risk task or tool entry before connecting permissions, logs, failure handling, and human takeover to production
What still needs proof
Request volume alone can mix crawlers, monitoring, and unusual traffic into reader growth. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.