What Changed: From Black Box to Submission History
For bot operators, submitting a bot to Cloudflare’s BotBase directory used to feel like sending a message into a void. After pressing submit, there was no way to check status, understand a rejection, or update an entry. The only recourse was emailing support. On August 28, 2026, Cloudflare launched BotBase for Operators to close that gap, giving operators transparency into the submission process.
The submission form has a new home in the Cloudflare dashboard: Protect & Connect → Application Security → BotBase. Previously, the form lived under Manage Account → Configurations, which tied the bot to your account but didn’t connect it to the broader bots ecosystem. Now, BotBase for Operators is split into three sections: Bots directory (browse and search known bots), Submission form (submit a new bot), and Submission history (track everything you’ve submitted).
The key addition is the Submission history tab. Every submission from your account now shows a clear status: Waiting for review, Accepted, or Rejected. If rejected, you’ll see the specific reason and actionable steps to fix it. If accepted but Cloudflare adjusted how your bot is classified, you’ll see what changed. This directly addresses the feedback Cloudflare heard from operators: submitting a bot felt like a black box.
How It Works: Editing, Canceling, and Keeping Info Current
Bot identification details change over time. Your website might move an IP list to a new endpoint, or you might switch from an IP allowlist to signing traffic with Web Bot Auth. Previously, reflecting such changes meant filling out the entire form again and creating a brand-new entry. Now, you can edit a submission you’ve already made. You can also cancel a submission that’s still waiting for review.
Cloudflare emphasizes that accurate information is key to earning and keeping Verified status. Verified bots are more likely to be allowed by site owners based on behavior, though the final decision always rests with the individual site owner. Keeping your bot’s details current is now much easier.
A New Taxonomy: Behavior, Content Use, and Operator Type
The new submission form replaces the old single-label approach with a three-part description that matches how bots actually behave. This aligns with the behavior and content use model Cloudflare introduced on July 1, 2026.
First, what your bot does. You can select multiple behaviors: indexing pages for search, acting on a user’s behalf, collecting data, training models, supporting SEO tools, and more. No more squeezing your bot into a single closest match.
Second, how it uses what it reads. A crawler that skims a page for a search snippet is different from one that stores the page to train a model. You declare the level of content use your bot needs, using the same Content Signals model that website owners use to set rules in robots.txt. For example, a site might declare Content-Signal: search=yes, ai-train=no, use=reference, meaning it’s fine to index for search and keep a reference, but not to train a model. Your bot’s content-use declaration is checked against exactly that kind of preference.
Third, who’s actually running it. You choose between direct (you operate the bot from your own infrastructure, like a search engine building its own index) and intermediary (you run a platform that other companies build on, carrying their traffic without being the one who decided to send it). For example, a general-purpose AI assistant operator might provide the infrastructure, but a different company’s app built on that API triggers the actual requests.
This three-part description gives website owners a clearer picture of your bot, enabling more accurate decisions about how to treat it.
Faster, More Consistent Review
The volume of new bot submissions has grown sharply—about 7 times since 2023—and manual review doesn’t scale. Cloudflare rebuilt the review process to run automatically. Submissions now go through a series of automated checks: Is it a duplicate of an existing entry? Is the user-agent pattern specific enough to avoid overlap? Most importantly, does the claimed verification method hold up? The system automatically fetches your IP list, confirms reverse DNS, or validates Web Bot Auth signatures—no more manual checks.
If everything passes, your bot can be tracked right away. If something needs a closer look, it’s routed to the team with the specific reason already flagged, rather than landing as a blank entry in a queue. For operators, this means most submissions move faster than before.
Limitations and Trade-offs
While BotBase for Operators is a significant step, it’s important to note what it doesn’t do. First, acceptance into the directory doesn’t guarantee that any website will allow your bot. Site owners retain full control over what traffic they permit. Second, the automated review process may not catch every nuance, and some submissions will still require human review, which could take longer. Third, the new taxonomy, while more flexible, still requires you to accurately self-describe; misrepresentation could lead to rejection or loss of Verified status. Finally, the features are currently available only through the Cloudflare dashboard; there’s no mention of a public API for submissions or status checks.
Takeaway: A Model for Transparent Bot Management
BotBase for Operators is a practical example of turning a one-way submission into an ongoing relationship. For product builders, the key takeaway is the value of transparency in automated traffic management. By providing status tracking, editable entries, and a structured taxonomy, Cloudflare reduces friction for bot operators and helps website owners make more informed decisions.
If your product involves crawlers, agents, or automated traffic, consider how you can apply these principles: give operators visibility into where their submission stands, allow them to update information easily, and use structured, behavior-based classification instead of vague labels. This approach not only improves operator experience but also builds trust across the ecosystem.
Cloudflare’s roadmap includes ownership and observability (claiming bots, managing live directory entries, understanding how sites treat your bot) and eventually conversation (a sustainable way for operators to request access by demonstrating value). For now, BotBase for Operators is a solid first step toward a more collaborative bot ecosystem.
Sources
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.