ScraperGuard – AI Scraper Blocker
Block “good bots” (AI scrapers) by User-Agent. Optional Apache .htaccess rules and WordPress-level blocking with basic stats.
Consider an alternative
ScraperGuard shows warning signs in 2026 — compare the alternatives below before installing. Was last updated 7 months ago, and scores 36/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
- Only tested up to WordPress 6.9 (latest is 7.1)
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where ScraperGuard stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| AI | >100 |
| bots | >100 |
| htaccess | >100 |
| scraper | #50 |
| user agent | >100 |
About ScraperGuard – AI Scraper Blocker
From the official readme · v1.0.0Description
ScraperGuard helps you block known AI scrapers (often called “good bots”) by matching their User-Agent string.
You can:
- Select specific bots to block, or block all known bots.
- Add your own custom User-Agent substrings (one per line).
- Block via Apache
.htaccess(fast, before WordPress loads) or via WordPress-level blocking (can show basic stats).
Important notes:
- This plugin can block “good bots” that identify themselves. It cannot stop “bad bots” that ignore rules and/or spoof User-Agents. For that you may need additional security measures (WAF, rate limiting, bot protection).
.htaccessblocking works on Apache hosting only, and requires a writable.htaccessfile.- WordPress-level blocking only affects requests that reach WordPress (it won’t block direct hits to static files unless they route through WordPress).
- Country blocking (geo blocking) can use a country header (fast) or an IP lookup (works without Cloudflare but is slower).
The settings page is under Tools → ScraperGuard.
External Services
This plugin can optionally connect to third-party IP geolocation services to determine the visitor’s country for country-based blocking. This feature is disabled by default and only activates when you explicitly enable “Country blocking” in the settings.
When country blocking is enabled and the “Country detection method” is set to “Auto” or “IP lookup”:
- Service used: The plugin uses either ipwho.is or ipapi.co (configurable in settings)
- Data sent: The visitor’s IP address is sent to the selected service
- When data is sent: Only when a request is received and no country header is available from your server/proxy
- Purpose: To determine the visitor’s country code (ISO-2) for geo-blocking
- Caching: Results are cached locally for 24 hours by default (configurable 1-168 hours) to minimize requests
- Privacy: IP addresses are sent to external services. Ensure compliance with your privacy policy and local regulations.
ipwho.is (default provider):
* Service provider: ipwho.is
* Privacy policy: https://ipwho.is/
* Terms of service: https://ipwho.is/
* No API key required
ipapi.co (alternative provider):
* Service provider: ipapi.co
* Privacy policy: https://ipapi.co/privacy/
* Terms of service: https://ipapi.co/terms/
* No API key required for basic usage
Important: If you keep the “Country detection method” set to “Header only” (the default), or if you don’t enable country blocking at all, no data is sent to external services.
Installation
- Upload the folder
scraperguardto your/wp-content/plugins/directory. - Activate the plugin in WordPress.
- Go to Tools → ScraperGuard.
- Choose which bots you want to block (or “block all known bots”).
- Pick your blocking method:
- Enable Apache
.htaccessblocking (fastest) if your host supports it, and/or - Enable WordPress-level blocking (for basic stats).
- Enable Apache
Frequently asked questions
Can I block all AI scrapers at once?
Yes. Enable “Block all known AI/archiver bots”.
Will this stop malicious bots?
Not reliably. “Bad bots” may ignore robots.txt and can spoof User-Agent strings. Consider a WAF, rate limiting, login protection, and server-side security rules.
Can I block whole countries?
Sometimes. The plugin supports optional country blocking at WordPress level. For best results, set “Country detection method” to “Auto” or “IP lookup”. Note that IP lookup needs outbound HTTPS from your server and may have privacy implications.
Does `.htaccess` mode work on every host?
No. It requires Apache + AllowOverride + a writable .htaccess. On Nginx, .htaccess is ignored; use WordPress-level blocking or configure your server rules manually.
Why don’t the stats include `.htaccess` blocks?
Because .htaccess blocks requests before WordPress runs. WordPress cannot count requests it never sees. Use your server logs for that.
Can I see traffic / blocks in a graph?
The plugin includes a simple “last 14 days” bar overview and a small table for WordPress-level blocks. For accurate totals (including .htaccess blocks), use server logs or analytics.
Changelog
Initial release. Block AI scrapers by User-Agent with optional .htaccess or WordPress-level blocking.
1.0.0
- Initial release.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best ScraperGuard alternatives
All AI plugins →
FAQ
ScraperGuard – AI Scraper Blocker: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 1, 2026
Is ScraperGuard free?
Yes. ScraperGuard is free to download and use from the official WordPress.org plugin directory.
Is ScraperGuard safe to use in 2026?
ScraperGuard shows warning signs in 2026 — compare the alternatives below before installing. Was last updated 7 months ago, and scores 36/100 on our health check.
How many websites use ScraperGuard?
ScraperGuard is active on <10 WordPress websites and has been downloaded 397 times since it launched in March 2026. It was downloaded 42 times in the last 30 days.
Does ScraperGuard work with WordPress 7.1?
ScraperGuard is officially tested up to WordPress 6.9.9, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does ScraperGuard need?
ScraperGuard requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was ScraperGuard last updated?
The latest version, 1.0.0, was released on March 14, 2026 (7 months ago).
Who makes ScraperGuard?
ScraperGuard is developed and maintained by KNEET.
What are the best alternatives to ScraperGuard?
The most popular alternatives to ScraperGuard are Elementor Website Builder (10M+ installs), All in One SEO (2M+ installs) and AI Agent by SiteGround (1M+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
