Quick StartUpdated
In about 10 minutes you’ll deploy the five firewall rules to one zone and check they work. You need the plugin installed and a Cloudflare account connected (see Connecting to Cloudflare).

The five rules run in a fixed order. Allow comes first, then Block, then Challenge:
- Allow Good Bots lets Cloudflare verified bots, services with a published IP list and your own servers skip every other rule.
- Block Aggressive Crawlers & WordPress Paths blocks scrapers, curl, exploit scanners and WordPress attack paths.
- Block or Challenge Web Hosts / TOR & Exploit URIs handles traffic from hosting companies, attack networks and TOR, and blocks exploit patterns from any IP.
- Challenge Large Providers / Country challenges AWS, Google Cloud and Azure, and optionally visitors outside your countries.
- Challenge VPN Connections & wp-login challenges VPN traffic and protects the login page.
Before you start: your other custom rules are kept#
A deploy puts the five rules first in the zone’s custom rules and keeps the rules you made in Cloudflare after them. Rate limiting rules, managed rules and IP Access Rules aren’t touched.
On the Cloudflare Free plan a zone can have only five custom rules, and the plugin uses all five. If a Free zone already has its own rules, the deploy fails with a message saying so. Open the Zone Rules tab, choose the zone and click Load Rules to see what’s there. Then either delete rules in Cloudflare, or tick Replace all custom rules in the zone when you deploy. See Cloudflare Free plan limitations.
Step 1: Open WAF Rules#
Go to WAF Manager → WAF Rules and stay on the Configure Rules tab. All five rule cards are on by default.
Step 2: Tune Rule 1 (the important step)#
Rule 1 decides what the other rules never touch. With Allow every Cloudflare verified bot on (the default), search engines, uptime monitors such as UptimeRobot and Pingdom, SEO tools, security scanners such as Wordfence and Sucuri, link previews, Jetpack and MainWP are already allowed. The Covered by Cloudflare verified bots list shows them.
Then add what verified bots don’t cover:
- Services with a Published IP List: turn on each one the site uses, such as ManageWP, ShortPixel, Imagify, EWWW Image Optimizer, Patchstack or WP Umbrella.
- Your server IPs: this site’s own server IP, so cron, loopback and cache-preload requests are never challenged, plus your office IP. Do the same for backup tools that run from your server, such as BackupBuddy.
- Custom User Agents to Allow: a tool that publishes no IPs, such as UpdraftPlus. A user agent is easy to fake, so use it only when there’s no IP.
- Custom Allow Expressions: webhook paths, for example
starts_with(http.request.uri.path, "/surecart/webhooks").
A missing service is the most common cause of a failed backup or a false “site down” alert.
Step 3: Check Rules 2 to 5#
The defaults suit most WordPress sites. Three things to look at:
- Rule 2: turn off Block curl user agents on API or app hosts that people call with curl, or list those hostnames under Except these hostnames. Leave Block WP-JSON (REST API) off if the site uses the block editor, WooCommerce, a mobile app or a headless setup.
- Rule 3: if a service you use runs on Hetzner, DigitalOcean or another host in the list, allow it in Rule 1 or untick that host.
- Rule 4: tick Challenge visitors from outside your selected countries only if the site serves specific countries. Then pick them in the country picker that opens below the card.
Step 4: Save#
Click Save in the bar at the bottom of the screen. The button shows the active profile’s name, such as Save: Default.
Step 5: Preview the expressions (optional)#
Open the Expressions tab to see the exact rule text that will go to Cloudflare, with each rule’s length and a Copy button.
Step 6: Deploy to one zone#
- Click Deploy Rules to Your Sites at the bottom of the screen.
- Tick one zone, ideally a low-traffic one.
- Check the Rules to be deployed in order list.
- Click Deploy to 1 Zone.

A line for the zone reports 5 rule(s) deployed., and says how many of your own rules were kept. The deploy starts as soon as you click; there’s no extra confirmation.
Step 7: Check it worked#
Open the Zone Rules tab, choose the zone and click Load Rules. You should see the five [CF WAF] rules marked Active, followed by any rules of your own. You can also check in Cloudflare under Security → WAF → Custom rules.
Step 8: Watch for 24 to 48 hours#
- Look out for failed backups, monitor alerts, broken webhooks or contact forms.
- Check Cloudflare Security → Analytics → Events, or the plugin’s Security Events screen on Pro zones, for real visitors being challenged.
- If something legitimate is blocked, allow it in Rule 1, save and deploy again.
Roll out to every site#
Once the first zone looks good, open Deploy Rules to Your Sites again, tick the other zones (or Select All Zones) and deploy. To deploy to the same group of sites again later, save them as a Domain Profile. For clients with different needs, save a Rule Profile per setup. See Profiles Overview and Deploying Rules to Your Sites.
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!