Page Rules Migration
Cloudflare has deprecated Page Rules. Their replacements (Single Redirects, Cache Rules and others) have higher limits and more options on every plan. The Page Rules screen finds every Page Rule across your zones and moves redirects and cache settings to the modern rules in one click.
Nothing is deleted. New rules are added after your existing ones, and each old Page Rule stays on until you turn it off.
Go to WAF Manager → Page Rules. It covers every active zone your active Cloudflare account can see.
Token permissions#
| Feature | Permission |
|---|---|
| Scan | Zone → Page Rules → Read |
| Turn a Page Rule off or on | Zone → Page Rules → Edit |
| Migrate Forwarding URLs | Zone → Single Redirect → Edit |
| Migrate cache settings | Zone → Cache Rules → Edit |
Step 1: Scan#
Click Scan all zones. Nothing loads until you do; afterwards the button reads Scan again. Only zones with Page Rules is ticked by default; untick it to see every zone.

The tiles show Zones with Page Rules, Page Rules found, Can migrate automatically and Already migrated.
Each zone card shows how many Page Rules, Single Redirects and Cache Rules it has against its plan’s limits:
| Plan | Page Rules | Single Redirects | Cache Rules |
|---|---|---|---|
| Free | 3 | 10 | 10 |
| Pro | 20 | 25 | 25 |
| Business | 50 | 50 | 50 |
| Enterprise | 125 | 300 | 300 |
Each Page Rule shows its URL pattern, priority, whether it’s on, and every setting with its modern replacement. Click Rescan on a zone card to check just that zone again.
What migrates automatically#
Only Page Rules that are turned on can migrate.
| Page Rule | Becomes |
|---|---|
| Forwarding URL (301 or 302) on its own | A Single Redirect with the same status code. Wildcards like $1 carry over. Query strings are kept by default |
| Cache Level: Cache Everything, with or without Edge Cache TTL and Browser Cache TTL | A Cache Rule that makes matching requests eligible for cache, with the same TTLs |
| Cache Level: Bypass on its own | A Cache Rule that bypasses the cache |
Anything else shows Migrate manually with the reason and a How to migrate link to Cloudflare’s migration guide. Common reasons: Forwarding URL combined with other settings, unusual URL patterns, or settings that map to other rule types (such as Origin Rules for Host Header Override or Configuration Rules for Security Level).
Step 2: Preview and migrate#
- Click Preview & migrate on a Page Rule.
- Check the new rule: When incoming requests match shows the match expression, and the target or cache settings appear below. For redirects, untick Preserve query string if you don’t want it.
- Click Create Single Redirect or Create Cache Rule.
To migrate every eligible rule in a zone at once, click Migrate all eligible (N) on the zone card and confirm. It stops at the first failure.
Good to know:
- Single Redirects only work on hostnames proxied through Cloudflare (orange cloud).
- A new Cache Rule applies straight away, because modern rules take priority over Page Rules.
- Cache Everything caches every matching response, including HTML. Make sure the matched URLs never show logged-in or personal content, such as cart, checkout or account pages.
- If a zone has reached its plan’s limit of Single Redirects or Cache Rules, remove one in Cloudflare first.
Step 3: Test, then turn the old rule off#
After migrating, the row says a matching rule is in place.
- Test the site: the redirect goes to the right place, or pages are cached as expected.
- Click Turn Page Rule off and confirm.
If something’s wrong, click Re-enable Page Rule to turn it back on. Delete old Page Rules in the Cloudflare dashboard once you’re happy.
Hiding the screen#
Hide Page Rules in Settings → Menu Display → Hide other screens once all your zones are migrated.
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!