Docs
← Back to site

Deploying Rules to Your SitesNew

4 min readUpdated November 18, 2026

A deploy sends the five WAF rules on your screen to the Cloudflare zones you pick. It takes a few seconds per zone, and your other custom rules in Cloudflare stay where they are.

Token permissions: Zone → Zone WAF → Edit and Zone → Zone → Read.

Deploy the rules#

  1. Go to WAF Manager → WAF Rules and check the settings on the Configure Rules tab.
  2. Click Deploy Rules to Your Sites in the bar at the bottom. The Select Sites to Deploy To panel opens.
  3. Tick the zones to deploy to. Type in Filter zones… to search by name or flare, or click Select All Zones.
  4. Check the list under Rules to be deployed in order.
  5. Click Deploy to N Zones.
Deploy panel with three sites selected and the Replace all custom rules option

The deploy uses the settings on the screen, saved or not. To keep them for next time, click Save in the bottom bar as well.

What happens to your other custom rules#

The five rules are placed first in each zone’s custom rules, so Rule 1 runs before anything else. Custom rules you created in Cloudflare are kept after them. Earlier copies of the plugin’s rules are updated in place, so their history in Cloudflare is kept.

Rate limiting rules, managed rules and IP Access Rules are never touched by a deploy.

Replace all custom rules in the zone deletes the zone’s other custom rules during the deploy. Use it when you want a clean zone, or when a Free plan zone has no room: the Free plan allows five custom rules in total, and the plugin uses all five.

Warning

Replace all can’t be undone from the plugin. Check the zone’s rules on the Zone Rules tab first, and copy any rule you want to keep.

Read the results#

Each zone gets a result line under the panel:

  • 5 rule(s) deployed. The rules are live.
  • 5 rule(s) deployed. 1 other custom rule(s) kept after them. The rules are live and your own rules still run after them.
  • An error from Cloudflare, with its code. Nothing was changed on that zone.
Deploy results: five rules deployed to two zones, with one other custom rule kept

If a deploy fails on a zone that has other custom rules, the message says how many. On the Free plan this usually means 5 plugin rules plus your own add up to more than 5: remove some rules in Cloudflare, or deploy again with Replace all custom rules in the zone ticked.

If a zone has no custom rules yet, the plugin creates the ruleset. On plans that can’t skip some security features, the plugin removes those from Rule 1 and tries again on its own.

Deploy to the same group again#

A Domain Profile saves a set of ticked zones, such as “WooCommerce clients” or “Staging”. Pick one from Domain Profile at the top of the panel to tick its zones, click + New Profile to save the current ticks, and Save to update a profile. See Profiles Overview.

Check what is live on a zone#

Open the Zone Rules tab, choose a zone and click Load Rules. It lists every custom rule on that zone in the order Cloudflare runs them, including rules the plugin didn’t create. The plugin’s rules start with [CF WAF].

Zone Rules tab showing the custom rules live on a zone, including one kept from Cloudflare

Change or remove a rule later#

  • Change a rule: change it on Configure Rules and deploy again. The plugin replaces its own copy.
  • Remove one rule: turn the rule off with the switch on its card and deploy again. Rules 4 and 5 are also left out when nothing in them is ticked.
  • Remove all the plugin’s rules: delete the rules starting with [CF WAF] in Cloudflare under Security → WAF → Custom rules.

After a plugin update#

When an update changes the rules, its changelog entry says “Redeploy to your zones”. Your saved settings are updated for you; deploy again to send the new rules to Cloudflare. Updates that don’t change the rules, such as 1.0.27 and 1.0.27.1, need no redeploy.

Rule too long#

Cloudflare allows 4,096 characters per rule expression. The Expressions tab shows each rule’s length, and the deploy stops before contacting Cloudflare when a rule is too long. Long IP lists are the usual cause: move IPs to IP Access Rules, or turn off a published IP list you don’t need in Rule 1.

Share:

Was this helpful?

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only