BotBlocker provides an extended set of maintenance, cleanup, and configuration-management tools designed to keep your security environment stable, optimized, and fully controllable. These utilities help resolve structural issues, improve performance, and ensure that your security configuration can be safely transferred or restored at any time.
The database section brings together the most important tools for maintaining the integrity and performance of BotBlocker’s internal storage. Each option serves a specific purpose, and using them correctly helps avoid data loss, slowdowns, or unexpected plugin behavior. These tools are available directly from the BotBlocker admin panel and require no technical knowledge to operate.
This function recreates all BotBlocker database tables from scratch. It should be used if the data structure becomes corrupted, after major updates, or when you need to completely reset the plugin’s internal storage. Re-installation does not affect WordPress core tables or other plugins.
This option is particularly relevant after a failed update or if you notice that certain BotBlocker features stop recording data properly. Running a re-install restores the correct table structure without touching anything outside the plugin’s own scope. Among all available tools, this one has the most significant effect on the plugin’s internal structure, so it should be treated as a last resort rather than a routine operation. Before using it, make sure to export your current settings so that you can restore them immediately after.
This option triggers the built-in WordPress database repair and optimization tool. WordPress performs a structural check of its tables and attempts to repair inconsistencies, as well as optimize table indexes and storage overhead. This process can resolve issues related to failed writes, unexpected errors, or performance degradation. It is a safe and standard maintenance operation provided directly by WordPress.
Regular use of this option is recommended on high-traffic sites where the database is under constant load. Over time, table fragmentation can slow down queries and affect both the speed of BotBlocker checks and the overall response time of your WordPress site. Running this repair periodically keeps the database lean and responsive.
Deletes all recorded visitor entries from the BotBlocker database tables. This is useful when revisiting analytics from scratch, testing new security configurations, or removing accumulated logs on high-traffic sites.
If you have recently changed your traffic filtering rules or added new bot detection logic, clearing visitors data gives you a clean baseline. Any statistics or logs collected before the rule change would otherwise mix with new data and make it harder to evaluate how well the updated configuration is working.
Removes expired or temporary transient records created by WordPress. Over time, transients can accumulate and affect performance. Clearing them ensures that BotBlocker and other parts of the system operate without unnecessary overhead.
Transients are often overlooked during routine site maintenance, but they can quietly build up in the database over weeks and months. On busy sites, this accumulation can add noticeable weight to database queries. Cleaning transients regularly is a straightforward step that keeps the system running smoothly without any risk to your data or configuration.
Beyond the core database tools, BotBlocker includes a set of additional maintenance options that address common operational needs. These tools cover everything from cookie management to cache control, giving administrators full control over the runtime environment.
Deletes all cookies created by BotBlocker for visitor identification, verification, or session tracking. This is helpful during debugging or when deploying new configuration rules.
When you update your verification logic or change how BotBlocker identifies returning visitors, old cookies from the previous configuration may interfere with the new behavior. Clearing them ensures that all visitors go through the updated identification process from the start, which makes testing and rollout much more predictable.
Forces WordPress to rebuild all permalink rewrite rules. This can resolve issues with URL access, custom redirects, or security rule changes that rely on the rewrite system. The operation is equivalent to manually saving permalinks in WordPress settings.
This step is often necessary after installing or updating BotBlocker on sites that use custom permalink structures. If you notice that some protected URLs are returning 404 errors or that redirect rules are not applying correctly after a configuration change, resetting rewrite rules usually fixes the problem within seconds.
Clears the WordPress object cache to ensure that all system changes, plugin updates, and configuration adjustments are applied immediately. This is particularly important when using persistent object caching solutions like Redis or Memcached.
Persistent object caches store copies of database query results and computed values so that WordPress does not have to repeat expensive operations on every page load. While this improves speed under normal conditions, it can delay the effect of configuration changes. After updating BotBlocker settings, clearing the object cache ensures that the new configuration takes effect right away across the entire site.
The import and export system is one of the most practical capabilities in BotBlocker’s management toolkit. It gives administrators a reliable way to back up, move, and restore the entire plugin configuration without manual data entry. These tools work together as a pair and are most effective when used as part of a regular maintenance routine.
Generates a backup file containing all BotBlocker settings, configuration values, and internal data. This export can be stored as a restore point, used during migration to another WordPress installation, or applied before reinstalling the plugin.
It is good practice to export your settings before making any significant changes to the configuration. If something goes wrong after an adjustment, having a recent export means you can return to a working state in seconds. The exported file is compact and easy to store alongside other site backups in your standard backup routine.
Restores configuration and data from a previously exported backup file. This function is essential when re-deploying BotBlocker after reinstallation, transferring settings between environments, or quickly recreating a tested configuration without manual setup.
The import process handles all settings in a single operation. There is no need to go through each configuration section manually or remember which options were active. This makes it especially useful when setting up BotBlocker on a staging environment that needs to match a production site, or when handing off a site to a new administrator who needs to work with an already-tested configuration.
Import and Export together create a complete portability mechanism, ensuring that your security environment can be reproduced on any site within seconds.
Knowing which maintenance action to take and when is just as important as having access to it. The tools described above are designed to be used in specific situations, and matching the right tool to the right problem saves time and prevents unnecessary disruption. Below is a practical guide for the most common situations.
Each of these options is designed to be used independently or in combination depending on the situation. None of them affect WordPress core tables, other plugins, or your site content. The tools operate entirely within BotBlocker’s own data scope, which makes them safe to use at any time without risk to the rest of your WordPress environment.
