Cloudflare adds operator tools to make bot submissions less opaque

Cloudflare has launched BotBase for Operators, a new dashboard area that gives bot and AI agent operators a clearer path into Cloudflare's directory of known automated traffic. The company says all customers can access the tool from Protect & Connect, then Application Security, then BotBase.

The update matters because the argument over web crawling is no longer only about blocking bad traffic. Search crawlers, AI assistants, SEO tools, data collectors and user directed agents can all look similar at the network edge unless they identify themselves well. Cloudflare is trying to turn BotBase into a shared directory where site owners can decide what to allow, while operators explain what their systems do and how they use content.

What Changed

Cloudflare says the operator experience now has three main parts. A bots directory lets customers browse, search and filter bots Cloudflare already tracks. A submission form lets operators register a new bot. A submission history tab shows what has been submitted from an account and whether each entry is waiting for review, accepted or rejected.

That status tracking is the practical change for teams that run crawlers or agents. Cloudflare says operators previously had little visibility after pressing submit, and sometimes had to contact support just to learn whether a submission was reviewed. Rejections now include reasons and steps to act on. Accepted submissions can show classification changes made during review.

Operators can also edit an existing submission or cancel one that is still waiting for review. Cloudflare frames that as important because bot details can change, including IP list locations, reverse DNS behavior or a move to Web Bot Auth signatures.

Why It Matters

The strongest signal in the announcement is scale. Cloudflare says new bot submissions have increased about seven times since 2023, which made a fully manual review path harder to maintain. The rebuilt process now checks for duplicate bots, specific user agent patterns and claimed verification methods. Cloudflare says it can automatically fetch IP lists, confirm reverse DNS or validate Web Bot Auth signatures before routing edge cases to a human reviewer.

For publishers and developers, the decision value is simple. Bot operators that want durable access to websites need cleaner identity and content use declarations. Site owners still make the final access decision, but a directory with current operator supplied behavior data should make blanket blocking less attractive when a bot is useful and properly identified.

The open question is adoption. BotBase becomes more useful only if serious operators keep records current and if website owners trust the classifications enough to use them in policy. For now, this is a workflow change, but it points toward a web where bot access depends less on mystery traffic and more on declared behavior, verification and owner choice.

Sources

• blog.cloudflare.com

Cover photo by Kindel Media on Pexels, used under the Pexels License.