# Cache Rules are the current caching config

Page Rules are deprecated. For caching behavior, the current product is **Cache Rules**, which control cache eligibility, edge TTL, and browser TTL per request match.

## Execution order matters

Rules features execute in a fixed order: Single Redirects, URL Rewrite, Configuration Rules, Origin Rules, Bulk Redirects, Managed Transforms, Request Header Transforms, Cache Rules, then Snippets. The listed products take precedence over Page Rules: if a Cache Rule and a Page Rule both match, the Cache Rule wins.

Within Cache Rules, for non-terminating actions the last change made wins (later rules overwrite earlier ones in the same phase).

## The migration trap

Teams with old Page Rules for caching ("Cache Everything" on `/static/*`) add a Cache Rule and assume both apply. They do not: on conflict the newer product wins, and on non-conflict both can stack in surprising ways. The clean move is to migrate each Page Rule to its replacement product, then delete the Page Rule.

## Checklist

- Audit existing Page Rules before adding Cache Rules; record which ones handle caching.
- Use Cloudflare Trace to confirm which rule actually fired for a given URL.
- Set edge TTL and browser TTL deliberately and separately: a long edge TTL with a long browser TTL means a bad deploy is cached in two places you must purge.