BlockBots
Stop bots, fake traffic, VPNs, and scrapers in real time.
5 followers
Stop bots, fake traffic, VPNs, and scrapers in real time.
5 followers
BlockBots detects and blocks AI bots, click fraud, VPNs & proxies in real time. Protect your ad budget from invalid traffic and fake clicks. Start free.
BlockBots — filter traffic by geo, language, and bots. No code changes.
Every site gets traffic it never asked for: crawlers, scrapers, VPN sessions, regions you don't sell to. The usual fix is a pile of .htaccess rules or a hand-rolled User-Agent regex that nobody maintains and everybody is afraid to
touch.
BlockBots moves that into campaigns. One snippet per site — everything after that is configured from the dashboard, no
deploy.
What's new in this release:
🤖 Captcha instead of a hard block for VPN and suspicious traffic
The choice used to be binary: let it through or cut it off. Now questionable visits can be handed a captcha — real
people behind a VPN get through, automation doesn't. One toggle per campaign.
📋 New list interface for geo, languages, and bots
Dropdowns are gone, replaced by a twin-select: catalog on the left, your selection on the right, search on both sides,
add-all and remove-all in the middle. Every list works in allow or exclude mode via a switch next to it. An empty
list means "allow everything," so you only configure what you actually restrict.
🔄 The bot catalog is live now
It's pulled from the maintained dataset instead of a hardcoded array. Stale patterns left over
from older versions no longer ride along silently in your saved settings.
Setup takes a few minutes: create a campaign, point it at your domain, paste the snippet. Changes apply on the fly.
Where we're stuck right now — and where you can help
Our WordPress plugin is still sitting in the review queue. It's built, it works, and we can't ship it through the
official directory yet. For the largest group of people who'd benefit from this, the easiest install path is the one
we can't offer.
So for now: WordPress users can run BlockBots via the standalone snippet, which works the same way and takes about as
long to set up. We'd rather say that plainly than pretend the plugin is around the corner.
If you've been through WordPress plugin review — especially for anything that touches request filtering or external
APIs — we'd genuinely like to hear what tripped you up. And if the standalone route is a dealbreaker for you, say so
in the comments. That tells us how hard to push on this.