by
witenlabs
0 (0 reviews)
Witen Blocker – Block AI Crawlers, Limit Login Attempts & 2FA
Block AI crawlers like GPTBot and ClaudeBot, one by one. Lock out password guessers, add 2FA, and stop comment spam. No account needed.
Witen Blocker ranks #52,676 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Oct 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v0.6.53
Current Version v0.6.53
Updated 1 week ago
Last Update on 28 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#3,855 of 5,058 in Security
Downloads +64.9% this week
Actively maintained
Rank
#52,676
—
No change
Active Installs
0+
-100%
KW Avg Position
150.8
0.5 worse
Downloads
528
+81 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
25,108
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 6 more installs to reach 10+
Rank Changes
Current
#52,676
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.6.53
- Last Updated
- Oct 28, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.1.4
- PHP Version
- 8.1 or higher
- Author
- witenlabs
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about Witen Blocker – Block AI Crawlers, Limit Login Attempts & 2FA
robots.txt states your preference, and crawlers that honor it follow it. Witen Blocker enforces your choice: a crawler you block gets an HTTP 403, and a crawler you allow passes. Use both if you like.
Everything local: AI crawler and bot controls, login lockout, two-factor sign-in, comment spam checks, exploit blocks, file and malware scans, and the .htaccess editor. A Witen account adds shared blocklists and reporting.
No. Request checks use local data and never wait on a remote service. Blocklist updates, reporting, and scans run in background jobs.
Yes. If both plugins handle two-factor, login limits, bot rules, or .htaccess, turn each feature on in one plugin only, then test your login.
Open Witen > Login > Login lockout to set the failure window, failure count, and ban duration. Defaults are 5 failures in 5 minutes and a 1-hour ban. Saved settings override WITEN_LOGIN_WINDOW_SEC, WITEN_LOGIN_MAX_FAILURES, and WITEN_LOGIN_BAN_SEC in wp-config.php. Every failure from an address counts toward its ban. Signing in clears only the failures against your own account and never lifts a ban. Keep your 2FA recovery codes. If you lock yourself out, wait for the ban to expire or follow the recovery guide, which covers WP-CLI and SFTP. Deactivating the plugin leaves existing .htaccess and Warden firewall rules in place; the guide shows how to remove them.
No. A finding is a file worth a look, and legitimate customizations can trigger one. Witen Blocker shows you which files to check. It doesn't clean an infected site for you.
Your site stays protected. Local protection keeps running, cached blocklists stay in use until they expire, and reports queue and retry in the background. Sites that report through a local Warden agent wait for Warden rather than reporting to Witen directly.
Yes. Each site has its own settings, connection, logs, and jobs. The main site's network administrator controls the shared .htaccess, and user accounts and two-factor setup are network-wide. If you use a local Warden agent, connect each site separately.
