BotBase for Operators integrates submission tracking directly into the Cloudflare dashboard interface

Site administrators have historically relied on Cloudflare's BotBase to differentiate between meaningful automated traffic and meaningless background noise. Tools like the bot directory combined with Business Insights previously offered operators clear ways to inspect crawler behavior. Despite these capabilities, the submission process for operators felt disconnected and mysterious. Submitting information meant filling out a form located at Manage Account → Configurations and then waiting through an undefined period without receiving any automated progress updates.

The submission process has shifted to a new home within the console. Operators can now navigate to Protect & Connect → Application Security → BotBase to manage submissions, placing this workflow alongside existing trust and security management tools. The interface organizes the experience into three primary segments:

1. Bots directory: A catalog allowing users to search and filter the same bots that Cloudflare Radar tracks.
2. Submission form: An optimized interface designed for the addition of new bot entries.
3. Submission history: A comprehensive ledger tracking every submission associated with a specific account.

The Submission history tab introduces a new level of clarity for operators. Previously, users were forced to send manual emails to support teams when they needed to verify the status of a request, which often led to delays or vague answers. Users can now see their requests categorized by one of three distinct statuses:

• Waiting for review: The request is acknowledged and placed in the queue.
• Accepted: The submission has passed review and now exists in the directory.
• Rejected: Modifications are required, and the system provides reasons and steps for resolution.

Every record in the log includes granular details, such as specific rejection explanations or any adjustments to classification made during the internal review process. Operators can also utilize a My bots filter to isolate and view only the submissions associated with their active account.

This transparency feature specifically tracks activity starting from the launch date forward. Legacy submissions made before this update will not appear in the interface, meaning operators managing older bots must continue to coordinate through support tickets. The transition of this feature to the dashboard provides an intuitive experience, grouping the tools near WAF rules and other critical security components where administrators conduct their daily work. While status changes are not instantaneous, submissions typically transition from Waiting for review to Accepted or Rejected within a few hours. The rejection messages provide actionable guidance to help users correct issues.

This update provides a much-needed increase in operational transparency. Cloudflare operators managing bots on the platform should navigate to dash.cloudflare.com/?to=/:account/bot-management/bots/submission to explore these new tracking capabilities. The shift represents a significant improvement for anyone overseeing bot traffic, as it removes the burden of manual status checks and provides clear feedback loops for rejected submissions. By unifying the submission workflow within the existing security suite, the platform ensures that bot management is no longer a secondary or hidden task. Operators should familiarize themselves with the new log to better understand how their entries are processed and to ensure their configurations stay current with the standards of the directory. Those with pending requests should verify their status through this new portal to determine if immediate action or modification is required for their entries to be accepted into the system. As the directory continues to track the same data as Cloudflare Radar, the consistency between these tools offers a more reliable experience for site owners looking to refine their automated traffic management strategies. The transition demonstrates an ongoing commitment to simplifying the complex process of bot identification, allowing for more precise control over the automated interactions that impact site performance and security. Every operator currently utilizing the platform for bot management will find that this streamlined approach reduces the overhead previously associated with tracking submission status and resolving classification conflicts. As you monitor the status of your records, remember that the history log acts as a permanent record of your interactions with the platform, providing a clear audit trail that was previously unavailable to the user community.