Description
Blockbots protects your WordPress site from bots, scrapers, and spam traffic. It filters unwanted automated requests while letting real visitors and trusted search engine crawlers through without interruption.
Local Protection (no account required)
- Filter Known Bad Bots — Block malicious bots while allowing legitimate crawlers (Google, Bing, Facebook, Twitter, and more).
- Protect Login Page — Add bot filtering to
wp-login.phpto stop brute-force and credential-stuffing attacks. - Ignore Logged-In Users — Skip verification for authenticated users so their experience is never affected.
- Allowed User Agents — Add custom user agents that should always be allowed through (one per line).
BlockBots Cloud Service (cloud account required)
Blockbots can connect to the BlockBots cloud service to perform advanced bot detection remotely. When your cloud API key is configured, the plugin acts as a thin client — visitor requests are analysed by BlockBots servers and a verification decision is returned to your site.
Bot detection, fingerprinting, and traffic analysis all happen on BlockBots infrastructure, not on your server.
Cloud-based capabilities managed from your BlockBots cloud account:
- Real-Time Cloud Protection — Block bots in real time using a continuously updated cloud database.
- Deep Bot Detection — Identify bots by behavioral signatures and browser fingerprinting.
- VPN Detection — Identify visitors connecting through VPN services.
- Proxy Detection — Detect connections routed through proxy servers.
- Emulator Detection — Identify headless browsers and browser emulators.
- Cloud Account Panel — Manage allowed countries, custom rules, bot signatures, and traffic analytics from your BlockBots cloud account at panel.blockbots.org.
Connect your cloud account at blockbots.org.
External Services
This plugin loads the BlockBots SDK from the BlockBots CDN in order to provide cloud-based bot protection and browser fingerprint analysis.
The SDK is required because the bot detection engine is maintained and updated remotely as part of the BlockBots cloud service.
This plugin connects to the BlockBots cloud service when a cloud API key is configured.
Why the service is required:
Bot fingerprinting, behavioral analysis, VPN/proxy detection, and real-time threat database lookups require server-side infrastructure that cannot run inside a WordPress plugin. These functions are performed by BlockBots servers and the results are returned to your site.
What processing happens remotely:
When cloud protection is active and a visitor has not yet been verified, the plugin presents a verification page. The BlockBots JavaScript SDK communicates with BlockBots servers to analyse visitor signals and determine whether the visitor is a legitimate human or a bot. Verified visitors receive a signed JWT session cookie; subsequent requests are validated locally without contacting the cloud service again.
What data is transmitted:
* Visitor IP address
* Browser signals collected by the BlockBots JavaScript SDK (fingerprint data)
* Your site domain name
* Your BlockBots cloud API key (used to authenticate requests)
When data is transmitted:
Data is only sent to BlockBots servers when cloud protection is active and a visitor has not yet been verified. Logged-in WordPress users and whitelisted bots are never submitted to the cloud service.
Service status checks:
When a cloud API key is configured, the plugin contacts BlockBots servers twice daily to verify that the cloud service connection is functioning correctly. This check transmits your API key and domain name only.
Service endpoints used:
* Cloud verification: https://blockbots.org/ and subdomains
* Service status check: https://panel.blockbots.org/api/service/status
* Cloud account panel: https://panel.blockbots.org
Terms of Service: https://blockbots.org/terms-of-service
Privacy Policy: https://blockbots.org/privacy
This plugin does not store visitor personal data in the WordPress database.
Installation
- Upload the
blockbotsfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Go to Blockbots Settings to configure local protection options.
- (Optional) Enter your BlockBots cloud API key on the Cloud Service tab to enable cloud-based bot detection.
FAQ
-
Will Blockbots affect real visitors?
-
No. By default, logged-in users are skipped entirely. Local filtering works silently in the background. Cloud verification is designed to be seamless for genuine human visitors.
-
Which bots are allowed through by default?
-
Google, Bing, Facebook, Twitter, and other major platform crawlers are allowed by default and will never be blocked. You can add additional user agents to the allowed list from the Local Protection tab.
-
Do I need a cloud account to use Blockbots?
-
No. All local protection features work without a cloud account or API key. A cloud account is only required to enable cloud-based bot detection and the advanced features managed in the BlockBots cloud account panel.
-
What is the cloud API key for?
-
The API key authenticates your WordPress site with the BlockBots cloud service. It is not a plugin license key — it identifies your site to the cloud service so that bot detection results and traffic analytics are associated with your account.
-
Can I use Blockbots alongside the separate BlockBots Pro plugin?
-
No. The two versions cannot be active simultaneously. If the separate Pro plugin is active, this plugin will be automatically deactivated.
-
Is Blockbots compatible with caching plugins?
-
Yes. Blockbots includes compatibility handling for WP Fastest Cache and similar caching plugins to ensure bot checks are not bypassed by cached responses.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Blockbots” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Blockbots” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.6
- Minor improvements and bug fixes.
1.0.5
- Improved bot blocking: disallowed bots now receive a 403 error response.
1.0.4
- Minor improvements and bug fixes.
1.0.3
- Minor improvements and bug fixes.
1.0.2
- Minor improvements and bug fixes.
1.0.1
- Refactored architecture to comply with WordPress.org serviceware guidelines.
- Renamed “PRO Features” to “Cloud Service” throughout admin UI.
- Rewrote admin notices to use dismissible, informational service-status language.
- Added External Services section to readme.
1.0.0
- Initial public release.
