[IMPORTANT] Page Rules Deprecation

Hi Cloudflare Community!

We’re reaching out to inform you that legacy Page Rules are being deprecated.

For new Cloudflare accounts and zones, Page Rules will be disabled starting July 1st, 2024. For existing accounts and zones, the creation of new Page Rules will no longer be available from January 6th, 2025 onward. Existing rules will be migrated to our new Rules portfolio on a best-effort basis throughout 2025. We encourage you to start transitioning to our new Rules products immediately using our migration guide.

ACTION: Please review our migration guide and transition to using our new Rules products instead of legacy Page Rules going forward.

In 2022, we announced in our blog “The future of Page Rules” that Page Rules would be replaced with a suite of dedicated products, each built to be best-of-breed and put more power into the hands of our users. The new Rules products — Cache Rules, Configuration Rules, Compression Rules, Origin Rules, Redirects and Transform Rules — are now generally available and have already been adopted by tens of thousands of Cloudflare customers.

Why Deprecate Legacy Page Rules?

Legacy Page Rules had several fundamental limitations, triggering solely based on URL patterns and being capped at 125 per zone to avoid performance issues. Debugging was also complex when multiple legacy Page Rules were applied to a single request.

What’s Different with New Rules?

Our new Rules, powered by the Ruleset Engine, offer versatile configuration with a robust language supporting various parameters like HTTP request headers and body, as well as response fields.

Scalability has significantly improved, with increased quotas for all plans: Enterprises now enjoy up to 760 Cloudflare Rules combined per zone, Business plan zones go from 50 to 310 rules per zone, Pro from 20 to 155 and Free from 3 to 65.

Execution is predictable as each rule operates independently, simplifying troubleshooting. The Trace feature helps understand rule interactions.

New Rules also ensure consistency, with common fields and capabilities shared across products, offering a seamless experience and predictable Terraform configurations.


It’s time to replace legacy Page Rules with our suite of new Rules products for increased flexibility, scalability, and ease of use.

While we’ll make every effort to migrate existing legacy Page Rules, it’s essential to understand the correlation between legacy Page Rule types and new Rules products, and how to implement new Rules products in your account ahead of time. In situations when an automated migration of eligible Page Rules is not possible, we will reach out to affected accounts in January 2025 so that you can take appropriate action on your end.

Multiple email and dashboard-wide communications announcing different stages of Page Rules deprecation will launch this week. For more information on the transition, refer to our migration guide.


Hi there,

When will the Cloudflare API (Cloudflare API Documentation) be updated to create those new Redirect Rules?
We currently use Page Rules (important: this product is deprecated, read more here https://developers.cloudflare.com/rules/reference/page-rules-migration/) (via the CF API) to create simple redirects. I can’t see any information in the API docs on how to create Redirect Rules.


Redirect Rules use the rulesets engine, see here…

We are also working on migration guide for API and Terraform users, aiming to have this information present directly on the developer documentation in a few weeks.


Hello there. In the instructions provided in the link, specifically in the section Page Rules migration guide · Cloudflare Rules docs, it is stated that the settings listed there will be migrated to the new Rules. In particular, it mentions Always Use HTTPS, Automatic HTTPS Rewrites, and SSL (SSL/TLS encryption mode, if I understood correctly). These settings are not explicitly categorized under Page Rules (important: this product is deprecated, read more here https://developers.cloudflare.com/rules/reference/page-rules-migration/) in the admin panel. Will they also undergo migration? Will their current API functionality eventually cease to work, requiring the use of new functionality to manage them?

@multitool.testdev, so Always Use HTTPS, Automatic HTTPS Rewrites, and SSL mode are all standalone zone-level settings located under the SSL tab, but Page Rules allow to control these on specific URLs as opposed to your entire zone.

If you have a Page Rule that, for example, enables automatic HTTPS rewrites or changes SSL mode for a specific subdomain, we advise you to proactively migrate these to Configuration Rules.

When it comes to Always Use HTTPS, we currently recommend Dynamic Redirects, however we have a simpler and more straightforward solution coming later this year that will allow users to deploy a configuration like this in one click.

To confirm, standalone zone-level settings that you can find under SSL tab or elsewhere in the dashboard (apart from the Rules tab itself) are not subject to any changes during this deprecation, and we will not perform any migration or changes on your behalf without prior notification.


Hey there, the documentation was helpful, especially the visual guides. Thank you for those!

Here are some questions:

  1. How can we exclude subdomains? The documentation mainly focuses on one use case, like example.com, but we need more flexibility. We reached out to support, but they couldn’t confirm whether (http.host eq "example.com") will only affect the main domain or also impact subdomains when using “Migrate Cache Level (Cache Everything)”.

Alternatively, would this rule work: (http.host eq "example.com") || (http.host eq "www.example.com")?

  1. In the “Migrate Bypass Cache on Cookie” visual guide, is it necessary to include “hostname contains,” or can the rule work without it?

  2. A note to warn that not all plans include all operators would also be helpful. We encountered an error on some Free accounts: “not entitled: the use of operator Matches is not allowed; a Business plan or a WAF Advanced plan is required.” It’s worth mentioning that this error occurred when trying to add a Caching → Cache Rule, not a WAF rule. Or WAF Advanced plans include more operators including for Cache Rules?

It’s a strict match. If it was “contains”, then it would affect subdomains also.

It can work without it. It’ll just apply to all hostnames in the zone.

1 Like

Hello again, there is a phrase in your guide :
“For new Cloudflare accounts and zones, PageRules will be disabled starting July 1st, 2024.”
Do I understand correctly that for new zones that I create after July 1st on already existing accounts, PageRules will be unavailable? Only on accounts and zones existing before this date will I be able to continue using them?

Also, an API question - is any update planned for Cloudflare SDK (GitHub - cloudflare/cloudflare-php: PHP library for the Cloudflare v4 API) in connection with the new changes?

1 Like

Correct. We are aiming to disable Page Rules for new zones (and subsequently new accounts) first, ensuring that new users are adopting modern technology instead of a legacy one. At the same time, we are committed to providing wildcard support before making any changes to Page Rules for existing zones.

Not at the moment, as our priorities are UI, API and Terraform. From what I can see, I don’t believe PHP binding is actively supported anyway, and in the future all our SDKs should definitely be auto-generated: Lessons from building an automated SDK pipeline.

1 Like