Continuous accountability for Verified bots
- ID
- 36227
- Status
- summarized
- Published
- 16 Oct 2026, 9:00 PM
- Fetched
- 16 Oct 2026, 10:06 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/verified-bots-accountability/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 5.5
- Created
- 16 Oct 2026, 10:07 PM
- Tags
- Audience
- developersai_agent_userssaas_startup_founders
What happened
Cloudflare announced a system that continuously evaluates Verified bot behavior, moving its Verified Bot program from one-time identity checks to an explainable 'trust band' that measures how consistently a crawler respects site preferences. Initial signals are whether the bot respects instructions and whether it responds to direct feedback; Cloudflare says scores will later be published publicly on Radar, with more measurement methods to come. The post cites a precedent: Perplexity's bot was de-listed from Cloudflare's Verified bot list in 2025 after accessing sites that had opted out of scraping and then attempting to circumvent controls when blocked.
Why it matters
If you run a crawler, scraper, or AI agent that fetches third-party sites, Cloudflare is signaling that identity verification alone will no longer buy you trusted status — observed behavior (honoring robots/preferences, responding to operator feedback) becomes a scored, eventually public signal on Radar. If you run a site behind Cloudflare, this is the vendor's answer to opt-out compliance, but it is a future feature with no API, no score thresholds, and no enforcement details published yet, so there is nothing concrete to integrate against today.
Discussion angle
Is an explainable, non-permanent trust band actually enough deterrent for a crawler that ignores opt-outs, or does it just document the problem — and what would you want to see in the published Radar scores before you'd treat them as a signal in your own allow/deny logic?