BotBlocker for WordPress Plugin Directory
BotBlocker is the #89 ranked spam app on WordPress, with a 1.6 average rating from 10 reviews, as of Aug 31, 2026.
BotBlocker is a WordPress Plugin Directory app by Brandon Fenning. With a rating of 1.6★ from 10 reviews, it currently ranks #89 in the Spam category.
AppRanks data: BotBlocker ranks #89 in Spam on WordPress Plugin Directory, placing it in the top 17% of that category.
AppRanks verdict
Generated from live marketplace data — refreshed daily
BotBlocker is a mixed-rating WordPress app with a limited review volume. It is listed in the Spam category on WordPress Plugin Directory, which AppRanks treats as the canonical taxonomy node for ranking and competitor comparison. 10 reviews put it in the early-traction tier — useful for early-stage stores willing to be on the leading edge. Early-traction review counts are sensitive to single launch periods or feature events, so a 30-day re-check before bigger commitments often resolves whether the trend is sustained. Paid-only pricing means evaluating fit on the marketplace listing or via the developer's documentation before installing. AppRanks tracks rating, review count, pricing tier, and category position daily — the figures on this page reflect the most recent scrape from the canonical WordPress Plugin Directory listing.
Pros
- +Published by Brandon Fenning — established developer track record
Cons
- −Average rating below 4.0 (1.6★) — read recent low-star reviews before committing
- −Limited review base (10) — ratings can shift significantly with new feedback
Looking to switch from BotBlocker?
See BotBlocker's alternatives ranked by audit score, rating, and review velocity.
How BotBlocker works
Since the vast majority of WordPress spam is automated in nature, the goal of BotBlocker is to block comment spam bots and not hinder users. This is accomplished through the use of honeypot technology, which tricks the spambot into identifying itself by performing actions that a human could not.
BotBlocker’s features include:
Works out of the box to block spam
Automatically stops spam-bots from commenting
Zero hindrance to users: no CAPTCHAS, math questions, passwords or extra input required
Zero false positives and ignores registered users
Can be configured to completely block spam-bots or flag comments as spam
Spam detection messages can be easily adjusted
No javascript or cookies required
Hooks into wp-comments-post.php to prevent spam-bots from directly submitting spam comments
Should work fine with most customized comment forms
No API keys required
http://www.lform.com/botblocker/ for more information.
Plugin by LFORM, a web design company in New Jersey.
Category rankings
As of Sep 4, 2026- Spam#89of 541Top 17%
See 90-day rank history for each category
Track daily rank changes, category shifts, and position volatility.
Competitors & alternatives
BotBlocker doesn't have curated competitor matchups yet. Other tracked spam apps on WordPress:
Where BotBlocker stands in the Spam category
BotBlocker ranks #89 of 541 apps in the Spam category, placing it in the top 17% of the listing.
Frequently asked questions
What is BotBlocker?
BotBlocker is an app for WordPress. It currently holds a 1.6-star rating from 10 merchant reviews, and AppRanks has been tracking its public marketplace data on the refresh cadence published in our methodology. It is listed under the Spam category on AppRanks, where you can see its current category position, review-velocity trend, and how it compares against the top alternatives in the same space. Developed by Brandon Fenning.
Who uses BotBlocker?
Currently around 200 active stores have installed BotBlocker. Its review base is still building, which usually maps to early-stage merchants and stores piloting a new workflow. It is part of the Spam category on WordPress.
Where does BotBlocker rank on WordPress?
BotBlocker currently sits at position #89 in the Spam category on WordPress. That places it in the top 16% of 541 apps tracked in the same category. Category positions are read from the live marketplace ranking and refresh on each scrape, so the number you see here reflects the most recent crawl rather than a long-running average.