Since Cloudflare deprecated Page Rules, which Rules products replace their settings, and how does matching change when you migrate?
answer
- one product per job
- first match versus last match
- URL pattern becomes filter expression
- http*:// and a trailing *
- Workers no longer suppress them
basics
~20 sPage Rules split into dedicated products: Single Redirects for Forwarding URL, Origin Rules for Host and resolve overrides, Configuration Rules for per-path settings, Managed Transforms for header settings, Cache Rules for caching. Modern rules stack rather than stopping at the first match.
solid answer
~40 sCloudflare now steers every configuration to Rules products built on the Ruleset Engine. A Page Rule's **Forwarding URL** and **Always Use HTTPS** become Single Redirects; **Host Header Override** and **Resolve Override** become Origin Rules; **Security Level**, **SSL**, **Rocket Loader** and similar switches become Configuration Rules; **True Client IP Header** and **IP Geolocation Header** become Managed Transforms; cache settings become Cache Rules. Matching changes in three ways. Page Rules apply only the first match, while modern rules stack and the last match wins for non-terminating settings. A URL pattern becomes a filter expression, so `http.request.full_uri wildcard` needs `http*://` and a trailing `*` to ignore scheme and query string. And modern rules take precedence over Page Rules and still run when a Worker handles the request. **Disable Security** and **Disable Performance** are not migrated at all.
go deeper
Know that Page Rules are deprecated and name the product that now handles a redirect, a Host header override and a per-path setting such as Security Level.
Explain the correspondence and the three matching changes: first match versus stacking with last match winning, URL pattern versus filter expression, and modern rules taking precedence over Page Rules.
Show the migration discipline: build the new rule, turn the Page Rule off, verify with Cloudflare Trace, then delete it, and catch scheme and query string gaps in full_uri expressions.
Weigh migrating now against waiting for the automatic migration, and decide who owns the several small rules in different products that replace one Page Rule.
## Why Page Rules are being retired **Page Rules** were Cloudflare's original way to change behaviour for a URL pattern: one rule could redirect, override the `Host` header, change the security level and set caching at once. They are now deprecated. Cloudflare recommends the dedicated **Rules** products for every new configuration and has announced that it will migrate existing Page Rules automatically, with advance notice to each account. The successors all run on the **Ruleset Engine**, the system that evaluates rules written in the Rules language, so they share one expression syntax, one API shape and one debugging tool, **Cloudflare Trace**. The reasons Cloudflare gives are concrete. Page Rules can only match on a URL pattern. They are capped per zone by default (3 on Free, 20 on Pro, 50 on Business, 125 on Enterprise). And when several could apply to a request, working out which one acted is hard. ## What each Page Rule setting becomes | Page Rule setting | Successor | |---|---| | Forwarding URL, Always Use HTTPS | Single Redirects | | Host Header Override, Resolve Override | Origin Rules | | Security Level, SSL, Rocket Loader, Polish, Email Obfuscation, Browser Integrity Check, Opportunistic Encryption, Disable Apps, Disable Zaraz | Configuration Rules | | True Client IP Header, IP Geolocation Header | Managed Transforms (part of Transform Rules) | | Cache Level, Edge Cache TTL, Browser Cache TTL, Custom Cache Key and the other cache settings | Cache Rules | A long run of Forwarding URL rules that each move one page fits **Bulk Redirects** better than a pile of Single Redirects, and anything a rule cannot express can move to **Snippets** or a Worker. ## How matching changes 1. **First match versus stacking.** Only the highest-priority matching Page Rule takes effect. Modern rules are stackable: every matching rule in a product applies in order, and for non-terminating settings the last match wins. Terminating actions such as a redirect still stop evaluation at the first rule that matches. 2. **A fixed execution order.** A Page Rule ran its actions in the order its author chose. Modern products run in a fixed sequence of phases: Single Redirects, URL Rewrite Rules, Configuration Rules, Origin Rules, Bulk Redirects, Managed Transforms, Request Header Transform Rules, Cache Rules, then Snippets. You choose the order of rules only inside one product. 3. **Precedence.** When a Page Rule and a modern rule both match and set the same thing, the modern rule wins. 4. **Workers.** A request handled by a Worker suppresses Page Rules actions, but it does not suppress the actions of modern Rules products. ## Converting a URL pattern into an expression A Page Rule URL such as `example.com/*/downloads/*.txt` becomes a filter expression. The usual conversion uses the `http.request.full_uri` field with the `wildcard` operator, which must match the entire field value: ```plaintext http.request.full_uri wildcard "http*://example.com/*/downloads/*.txt*" ``` Two details catch people: - `http.request.full_uri` includes the scheme, and the Page Rule pattern did not unless you wrote one, so start the pattern with `http*://` to cover both `http` and `https`. - The field also includes the query string, which the Page Rule ignored unless it was in the pattern, so end the pattern with `*`, or requests carrying `?utm_source=...` stop matching. Single Redirects and URL Rewrite Rules offer a **Wildcard pattern** view in the dashboard that hides the expression, but the same two details apply to the pattern you type there. ## Settings with no direct successor Some settings are deprecated and will not be migrated: **Disable Security**, **Disable Performance**, **Disable Railgun**, **Response Buffering** and **Web Application Firewall**. The first two bundled several features into one switch, and the replacement is to turn each feature off on its own: - Polish and Rocket Loader, which Disable Performance switched off, become two settings in one Configuration Rule. - Email Obfuscation and Hotlink Protection, part of what Disable Security covered, become Configuration Rule settings. - Skipping WAF managed rules for a path becomes a WAF exception, which belongs to the WAF rules rather than to the request rules. ## A safe migration order 1. List the zone's Page Rules and map each setting to its product with the table above. One Page Rule often becomes several rules in different products. 2. Build the new rules. 3. Turn the Page Rule off rather than deleting it, and check the behaviour with Cloudflare Trace and real requests. 4. Delete the Page Rule once the new behaviour holds; a disabled Page Rule still counts against the zone's quota. Done this way, nothing depends on the timing of the automatic migration, and every new rule is one the team has read and tested.
- If a Page Rule's Forwarding URL and a Single Redirect both match the same URL, which redirect does the visitor get?The Single Redirect. Modern Rules products take precedence over Page Rules, and a redirect stops evaluation once it fires. That is why the migration guide says to turn the Page Rule off and test before deleting it: while both exist, the old rule is shadowed for the URLs the new rule matches but still acts on everything else.
- A Page Rule used Disable Security on /admin. What do you build instead?Nothing migrates it, because the setting is deprecated. Turn individual features off with a Configuration Rule, such as Email Obfuscation, Hotlink Protection or Browser Integrity Check, and where a WAF managed rule really must be bypassed, scope a WAF exception to that path. The exception is WAF configuration, so it is reviewed with the security rules.
- Why does a migrated expression on http.request.full_uri miss requests the old Page Rule caught?Because the field holds the whole URI, scheme and query string included, and the wildcard operator must match all of it. A Page Rule ignored the scheme unless written and ignored the query string unless it was in the pattern. Start the pattern with http*:// and end it with * so requests with ?utm_source=... still match.
- Page Rules are still the right place to add a new redirect or header override.
- Configuration Rules stop at the first match, just as Page Rules did.
- A Page Rule URL pattern can be pasted unchanged into a full_uri wildcard expression.
- Every Page Rule setting, Disable Security included, has a one-to-one modern replacement.
- A Worker on the route turns modern Rules products off, just as it suppressed Page Rules.
Assumes Cloudflare as of 2026-10-10: Page Rules are deprecated and migrated automatically, except Disable Security, Disable Performance, Disable Railgun, Response Buffering and Web Application Firewall.