Metadata and packaging only. No change to how rules are evaluated.<\/p>","1.2.0":"
Internal prefix change. Your settings, log and block list are migrated automatically on the first page load after the update.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3687464,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3687464,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3687464,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3687464,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.4.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3687464,"resolution":"1","location":"assets","locale":"","width":1440,"height":1180},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3687464,"resolution":"2","location":"assets","locale":"","width":1440,"height":700},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3687464,"resolution":"3","location":"assets","locale":"","width":1440,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3687464,"resolution":"4","location":"assets","locale":"","width":1440,"height":980},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3687464,"resolution":"5","location":"assets","locale":"","width":1440,"height":1000}},"screenshots":{"1":"Overview: per-rule, per-IP, per-path and per-user-agent breakdown of the last 7 days. \/ \u6982\u8981\u753b\u9762\u3002\u30eb\u30fc\u30eb\u5225\u30fbIP\u5225\u30fb\u30d1\u30b9\u5225\u30fbUser-Agent\u5225\u306e\u96c6\u8a08\u3002","2":"Rules: the four built-in rules, each with its own paths, threshold and action. \/ \u30eb\u30fc\u30eb\u753b\u9762\u30024\u7a2e\u306e\u6a19\u6e96\u30eb\u30fc\u30eb\u3002","3":"Access log: filter by IP, by rule, or by whether the request was blocked. \/ \u30a2\u30af\u30bb\u30b9\u30ed\u30b0\u3002IP\u30fb\u30eb\u30fc\u30eb\u30fb\u906e\u65ad\u6709\u7121\u3067\u7d5e\u308a\u8fbc\u307f\u3002","4":"Server-side blocking: ready-to-paste .htaccess and nginx snippets for the blocked IPs. \/ \u30b5\u30fc\u30d0\u30fc\u5074\u3067\u906e\u65ad\u3002.htaccess \/ nginx \u7528\u30b9\u30cb\u30da\u30c3\u30c8\u3002","5":"Settings: mode switch, exclusions, bad user-agent signatures, trap URL, notifications. \/ \u8a2d\u5b9a\u753b\u9762\u3002\u30e2\u30fc\u30c9\u30fb\u9664\u5916\u30fb\u7f72\u540d\u30fb\u7f60URL\u30fb\u901a\u77e5\u3002"}},"plugin_section":[],"plugin_tags":[2359,1174,171765,600,599],"plugin_category":[54],"plugin_contributors":[268210],"plugin_business_model":[],"class_list":["post-364676","plugin","type-plugin","status-publish","hentry","plugin_tags-bot","plugin_tags-firewall","plugin_tags-rate-limit","plugin_tags-security","plugin_tags-spam","plugin_category-security-and-spam-protection","plugin_contributors-watrix","plugin_committers-watrix"],"banners":{"banner":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/banner-772x250.png?rev=3687464","banner_2x":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/banner-1544x500.png?rev=3687464","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/icon-128x128.png?rev=3687464","icon_2x":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/icon-256x256.png?rev=3687464","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/screenshot-1.png?rev=3687464","caption":"Overview: per-rule, per-IP, per-path and per-user-agent breakdown of the last 7 days. \/ \u6982\u8981\u753b\u9762\u3002\u30eb\u30fc\u30eb\u5225\u30fbIP\u5225\u30fb\u30d1\u30b9\u5225\u30fbUser-Agent\u5225\u306e\u96c6\u8a08\u3002"},{"src":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/screenshot-2.png?rev=3687464","caption":"Rules: the four built-in rules, each with its own paths, threshold and action. \/ \u30eb\u30fc\u30eb\u753b\u9762\u30024\u7a2e\u306e\u6a19\u6e96\u30eb\u30fc\u30eb\u3002"},{"src":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/screenshot-3.png?rev=3687464","caption":"Access log: filter by IP, by rule, or by whether the request was blocked. \/ \u30a2\u30af\u30bb\u30b9\u30ed\u30b0\u3002IP\u30fb\u30eb\u30fc\u30eb\u30fb\u906e\u65ad\u6709\u7121\u3067\u7d5e\u308a\u8fbc\u307f\u3002"},{"src":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/screenshot-4.png?rev=3687464","caption":"Server-side blocking: ready-to-paste .htaccess and nginx snippets for the blocked IPs. \/ \u30b5\u30fc\u30d0\u30fc\u5074\u3067\u906e\u65ad\u3002.htaccess \/ nginx \u7528\u30b9\u30cb\u30da\u30c3\u30c8\u3002"},{"src":"https:\/\/ps.w.org\/watrix-bot-guard\/assets\/screenshot-5.png?rev=3687464","caption":"Settings: mode switch, exclusions, bad user-agent signatures, trap URL, notifications. \/ \u8a2d\u5b9a\u753b\u9762\u3002\u30e2\u30fc\u30c9\u30fb\u9664\u5916\u30fb\u7f72\u540d\u30fb\u7f60URL\u30fb\u901a\u77e5\u3002"}],"raw_content":"\n
Pages that hold a single form \u2013 a contact page, a quote request, a download gate \u2013 get hammered by scanners and spam bots. The first real damage is to your analytics: page views are inflated and you can no longer read what visitors actually do.<\/p>\n\n
Watrix Bot Guard catches the source of that traffic with four kinds of rules<\/strong> and lets you decide how to deal with it:<\/p>\n\n Rules can be added, edited and disabled individually, each with its own paths, threshold, action and block duration.<\/p>\n\n Right after activation the plugin runs in log-only mode<\/strong>: every rule records what it sees and nobody is blocked. Look at the dashboard after a few days, see whether the traffic comes from a handful of IPs or is spread out, and only then switch to enforce mode<\/strong> \u2013 or take the generated The plugin stores the IP address, request path, user agent and referrer of requests that match a rule, in your own database, for the retention period you set (30 days by default). Nothing is sent to WATRIX or to any third party. If you configure a webhook URL, block notifications are sent to that URL and nowhere else. An optional \"anonymize IP\" setting masks the last octet before storing.<\/p>\n\n The verified-crawler check performs DNS lookups (reverse and forward) against the visitor's IP. Results are cached for 12 hours.<\/p>\n\n\n Not in log-only mode \u2013 nothing is blocked at all. In enforce mode the default thresholds (20 hits on one page within 60 minutes, 30 404s within 10 minutes) are far beyond what a human does. Logged-in users and verified search-engine crawlers are excluded, and you can add your own IP ranges to the allow list. If your monitoring service fetches your site with REMOTE_ADDR by default. Only switch to Blocking happens inside WordPress, so a blocked request still reaches PHP (but stops on Rule evaluation runs on uncached requests only. Cached pages served by a caching plugin or CDN are never counted, so the plugin is most effective on pages that are not cached, such as forms.<\/p><\/dd>\n The admin interface is currently written in Japanese and is fully translatable through the \n
\/contact\/<\/code>) too many times in a short window<\/li>\nrobots.txt<\/code>; only bots that ignore it will ever follow it<\/li>\nRecord first, block later<\/h4>\n\n
.htaccess<\/code> \/ nginx snippet and block those IPs in front of PHP.<\/p>\n\nWhat else is included<\/h4>\n\n
\n
init<\/code>, before the main query runs<\/li>\n.htaccess<\/code>, nginx deny<\/code>, and a plain IP list for your analytics tool's internal-traffic filter<\/li>\nwp bot-guard top | blocks | block | unblock | mode | export | settings | cleanup<\/code><\/li>\nWhat it deliberately does not do<\/h4>\n\n
\n
Privacy<\/h4>\n\n
\n
\/wp-content\/plugins\/<\/code> or install it from the Plugins screen.<\/li>\n\/contact\/<\/code>).<\/li>\n\n
Will it block real visitors?<\/h3><\/dt>\n
curl<\/code> or a similar tool, add its IP to the allow list or remove that signature from the bad user-agent list.<\/p><\/dd>\nWhich IP address does it use?<\/h3><\/dt>\n
CF-Connecting-IP<\/code> or X-Forwarded-For<\/code> if your site actually sits behind Cloudflare or another reverse proxy \u2013 those headers can be forged by clients otherwise.<\/p><\/dd>\nDoes it reduce server load?<\/h3><\/dt>\n
init<\/code>, before the query). To keep the load off entirely, paste the generated .htaccess<\/code> or nginx snippet into your server configuration.<\/p><\/dd>\nDoes it work with page caching?<\/h3><\/dt>\n
Can I use it in Japanese?<\/h3><\/dt>\n
watrix-bot-guard<\/code> text domain.<\/p><\/dd>\n\n<\/dl>\n\n\n1.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
wp bot-guard ai<\/code> to show the status, --refresh<\/code> to fetch now, and --check=<ip> --ua=<user-agent><\/code> to test a single request.<\/li>\n\/product\/%E6%A5%B5hepa\/<\/code> was recorded as \/product\/-\/<\/code>, so non-ASCII slugs could not be logged or matched correctly. Paths are now decoded before they are stored and compared.<\/li>\n<\/ul>\n\n1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
wag_<\/code> to wxag_<\/code> to comply with the WordPress.org guidelines. Existing options and tables are migrated automatically.<\/li>\n1.1.0<\/h4>\n\n
\n
init<\/code>.<\/li>\n1.0.0<\/h4>\n\n
\n