Active installations7K+Adoption metric — not a quality score
WordPress.org rating4.7 / 5 from 12 ratings
Official packageDirect from WordPress.org
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records Booter – Bots & Crawlers Manager version 1.6.1 as active, updated 4mo ago and tested up to WordPress 7.0.
Overview
About this plugin
Booter – Bots & Crawlers Manager is a preventative measure (treatment in advance) and treatment of damages caused by crawlers and bots.
The plugin uses a number of existing technologies which are known by crawlers and bots and takes them one step forward – smartly and almost completely automatically.
To allow the plugin to function correctly, you must follow the instructions and manually enter some data (which must be done by a human being to avoid errors).
The plugin includes local bot and referrer lists and does not fetch these lists from external services.
At the prevention level
Booter allows you to manage and create an advanced dynamic robots.txt file.
View a 404 error log to see the most common bad links.
Blocking bad bots that cause high server loads due to very frequent page crawls, or are used to search for security vulnerabilities.
At the treatment level
Booter allows you to limit the amount of requests from crawlers and bots, if or when they exceed the specified amount of requests per minute, it will be rejected for a specified period of time.
Rejecting links that we do not want in the fastest way, not by just blocking but by sending the appropriate HTTP status code to make search engines forget them.
Instructions for use in case of damage treatment
Activate the plugin.
Enable the 404 error log option.
Set the access rate limit.
Watch the 404 log, try to find common parts in the URLs that repeats most often.
Enter the common parts to the “reject links” page, and ensure the rejection code is 410.
Clear the 404 error log.
Repeat the process once every few hours until the 404 error log remains blank.
Check the status of your website’s index coverage every few days.
Source Code
The plugin includes human-readable source files for the bundled JavaScript and CSS assets under assets/src/.
The production assets under assets/dist/ are generated from these source files using Laravel Mix and npm.
WordPress.org metadata
Plugin tags
Topics listed for this plugin in the WordPress.org directory.
rate limit
hosting
request
security
upress
Compatibility & maintenance
Compatibility & maintenance
Tested up to WordPress 7.0
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.
Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 6.2 · PHP not listed
Update activity24 Jun 20264mo ago
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
Changes recorded by WP PlugIndex
Recent tracked changes
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
Tracking & source
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.