---
title: "Continuous accountability for Verified bots"
description: "Cloudflare introduces a system to continuously evaluate whether Verified bots honor website preferences, moving beyond identity verification to sustained trust by measuring compliance with robots.txt directives and HTTP 429 rate-limit responses over time. The system looks for repeated patterns of disregard rather than isolated violations, lowering a bot’s trust band if it ignores site preferences or fails to slow down after receiving rate-limit responses, while consistent compliance increases trust. Cloudflare previously de-listed Perplexity’s bot in 2025 for seeking to access opted-out resources and attempting to circumvent controls when blocked, illustrating the need for ongoing accountability. The company plans to share these trust scores publicly on Radar and eventually let customers choose the trust threshold for handling Verified bot traffic on their websites. This forms an accountability loop with Bot Preference Sync and Bot Management, ensuring trust is earned through sustained behavior rather than assumed from identity alone."
---

# Continuous accountability for Verified bots

[Cloudflare](https://yomu.fyi/company/cloudflare) · Chris Tsoukaladelis · Oct 16, 2026

**Type:** Announcement

## Summary

Cloudflare introduces a system to continuously evaluate whether Verified bots honor website preferences, moving beyond identity verification to sustained trust by measuring compliance with robots.txt directives and HTTP 429 rate-limit responses over time. The system looks for repeated patterns of disregard rather than isolated violations, lowering a bot’s trust band if it ignores site preferences or fails to slow down after receiving rate-limit responses, while consistent compliance increases trust. Cloudflare previously de-listed Perplexity’s bot in 2025 for seeking to access opted-out resources and attempting to circumvent controls when blocked, illustrating the need for ongoing accountability. The company plans to share these trust scores publicly on Radar and eventually let customers choose the trust threshold for handling Verified bot traffic on their websites. This forms an accountability loop with Bot Preference Sync and Bot Management, ensuring trust is earned through sustained behavior rather than assumed from identity alone.

## Context

Cloudflare’s Verified bot program previously focused on identity verification, but trust requires ongoing behavior evaluation. The post introduces a system to measure bot compliance with site preferences like robots.txt and HTTP 429 responses, using a trust band to reflect sustained behavior.

## Approach / What changed

Cloudflare developed a system that evaluates Verified bots based on two initial signals: respect for robots.txt directives and response to HTTP 429 rate-limit responses. The system builds a trust band over time, lowering trust for repeated disregard and increasing it for consistent compliance. Plans include public scores on Radar and customer-configurable trust thresholds.

## Takeaways

- Cloudflare’s system evaluates Verified bots on how consistently they respect robots.txt directives and respond to HTTP 429 rate-limit responses, looking for repeated patterns rather than isolated violations.
- A bot’s trust band is adjusted over time: consistent compliance increases trust, while ignoring site preferences or failing to slow down after 429s lowers it.
- Cloudflare plans to share trust scores publicly on Radar and eventually let customers choose the trust threshold for handling Verified bot traffic, forming an accountability loop with Bot Preference Sync and Bot Management.

## FAQ

### What signals does Cloudflare use to evaluate Verified bot behavior?

The system initially evaluates two signals: whether the bot respects robots.txt directives and whether it responds appropriately to HTTP 429 rate-limit responses by slowing down or pausing.

### How does Cloudflare handle bots that repeatedly ignore site preferences?

Bots that show repeated patterns of disregarding site preferences or failing to slow down after 429s will have their trust band lowered, and Cloudflare may de-list them from the Verified bot list, as happened with Perplexity in 2025.

### Will customers be able to control how Verified bot traffic is handled based on trust?

Yes, Cloudflare plans to eventually let customers choose the trust threshold used to decide how Verified bot traffic is handled, giving site owners more control over automated traffic.

**Tags:** [Bot Management](https://yomu.fyi/topic/bot-management), [Bots](https://yomu.fyi/topic/bots), [Cloudflare](https://yomu.fyi/topic/cloudflare), [Radar](https://yomu.fyi/topic/radar), [Trust](https://yomu.fyi/topic/trust)

- Source: [Cloudflare](https://blog.cloudflare.com/verified-bots-accountability)
- Source URL: https://blog.cloudflare.com/verified-bots-accountability
- Ingested by Yomu: 2026-10-16T15:00:12.526Z

[Read original post](https://blog.cloudflare.com/verified-bots-accountability)