CB Bot Guard
Bad bots don’t just spam forms. They hammer search pages, product filters and add-to-cart links, and every one of those requests makes WordPress and WooCommerce build a full page. On shared hosting and small VPS plans, that is what pushes memory over the limit and takes the site down. CB Bot Guard s
Bad bots don’t just spam forms. They hammer search pages, product filters and add-to-cart links, and every one of those requests makes WordPress and WooCommerce build a full page. On shared hosting and small VPS plans, that is what pushes memory over the limit and takes the site down.
CB Bot Guard spots these clients and answers them with a tiny 403 or 429 response, before your theme and plugins do any work. Real visitors are not affected.
What it detects
- Request floods. Too many requests per minute from one IP.
- Heavy-page floods. Searches, product filter and sort combinations, add-to-cart, checkout, login and comment posts have their own, lower limit. These are the usual cause of RAM spikes on WooCommerce stores.
- Scraping tools and attack scanners by user agent (python-requests, curl, sqlmap, WPScan and more), plus requests with no user agent.
- Aggressive SEO crawlers that never send you visitors (optional list, on by default).
- AI crawlers (optional list, off by default).
- Fake Googlebot, Bingbot, Applebot and Yandex. Anything claiming to be a search engine must pass a reverse DNS check. Genuine crawlers are remembered and never rate limited, so your SEO is safe.
- Vulnerability probes for files like .env , .git , phpMyAdmin, Adminer and common web shells.
- XML-RPC abuse, failed logins and 404 floods.
- Spam forms. A hidden honeypot field on comment and registration forms (WordPress and WooCommerce). Comments that your anti-spam plugin marks as spam also count against the sender.
Each event adds points to the IP. When it reaches the threshold (10 by default) the IP is blocked for 24 hours. Repeat offenders are blocked for 7 days, then permanently. Every number is adjustable.
Built to save resources
- Early blocking (one click). An optional must-use loader runs the blocklist check before other plugins load. In testing, a blocked request used about 3 MB of memory instead of a full page load, with no measurable cost for real visitors.