| 开发者 |
supersoju
codestic |
|---|---|
| 更新时间 | 2026年8月17日 01:51 |
| PHP版本: | 3.0.2 及以上 |
| WordPress版本: | 7.0.3 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
HTTP_REFERER header to advertise their own site in your traffic logs and analytics. They're good enough at simulating real visits that they show up in Google Analytics right alongside genuine traffic — this plugin blocks the known offenders before they're ever logged, and needs no configuration to start working.
Two blocking modes cover different hosting setups:
RewriteCond rules to .htaccess so spam requests are rejected by the web server itself, before WordPress even loads. Fastest option, and the default when your host is detected as Apache.wp plugin install block-referer-spam --activateThis plugin merges several public referer-spam block lists rather than relying on just one, refreshed automatically once a day, to keep coverage broad.
Block Referer Spam prevents new spam hits from being logged — it doesn't retroactively clean up analytics data you already have. To filter out existing spam entries in Google Analytics, see this tutorial.
A few common causes:
.htaccess isn't writable, or you're not on Apache, use WordPress mode instead.Rewrite mode does, since it blocks before caching applies. WordPress mode can be bypassed by full-page caching — the plugin detects common caching plugins and shows a warning on its settings page if you're running WordPress mode alongside one, so you can switch to Rewrite mode if your host supports it.
Please report it — we aim to fix reported issues quickly.
.htaccess rules, and the scheduled cron event.htaccess rewrite rules are kept ahead of caching-plugin rules, so Rewrite mode still blocks spam when a caching plugin is active