ScraperGuard - AI Scraper Blocker

开发者	kneet
更新时间	2026年3月14日 09:02
PHP版本:	7.4 及以上
WordPress版本:	6.9
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

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).
.htaccess blocking works on Apache hosting only, and requires a writable .htaccess file.
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.

安装:

Upload the folder scraperguard to 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 .htaccess blocking (fastest) if your host supports it, and/or
Enable WordPress-level blocking (for basic stats).

升级注意事项:

1.0.0 Initial release. Block AI scrapers by User-Agent with optional .htaccess or WordPress-level blocking.

常见问题:

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.

更新日志: