Cloudflare page rules and cache rules control exactly how specific URLs on your site are cached and handled at the edge, and configuring them precisely — rather than relying on defaults — can meaningfully improve performance while avoiding the common mistake of caching something (like a checkout page) that should never be served stale.
Cloudflare page rules & cache rules setup
Page and cache rules configured precisely — with checkout and account pages never cached.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Delegated access to your Cloudflare account with appropriate permissions
- Confirmation of any URLs that should never be cached (checkout, account pages, admin areas)
- Confirmation of your Cloudflare plan tier, since page rule quotas vary by plan
This or something else?
| You want specific page and cache rules configured for particular URLs on your site | This fix covers it |
| You want a full Cloudflare configuration audit, not just page and cache rules specifically | Cloudflare full configuration audit & setup, the broader version |
| Caching is causing visitors to see stale or incorrect content somewhere | Still covered by this fix, treated as a correction rather than a fresh setup |
| You’re not currently using Cloudflare and want it set up from scratch | A larger, related setup beyond just rule configuration |
What we do
- Confirm which URLs need specific caching behaviour, and which must never be cached
- Configure page rules and cache rules accordingly within your plan’s rule quota
- Verify sensitive or dynamic pages (checkout, account areas) are correctly excluded from caching
- Test that cached pages serve correctly and update appropriately when content changes
- Test that excluded pages always serve fresh, live content
- Document the configuration for future reference
What is included
- Page rules and cache rules configured for your specified URLs
- Verified exclusion of sensitive or dynamic pages from caching
- Tested confirmation of both cached and excluded page behaviour
- A written note on the configuration
Not included
- A full Cloudflare configuration audit beyond page and cache rules specifically
- Rules beyond what your current plan’s quota allows — an upgrade would be your decision with Cloudflare directly
- Broader site performance optimisation beyond Cloudflare-level caching
- Ongoing adjustment as your site’s URL structure changes significantly
Questions about this fix
What happens if I don't exclude my checkout page from caching?
A cached checkout page could serve stale content — like an outdated cart total or an old session state — to a visitor, which is a genuine, serious problem for an e-commerce site, so this is one of the first things we check and correctly exclude.
How many page rules can I actually set up?
This depends on your Cloudflare plan tier, which sets a specific rule quota — we'd work within whatever your current plan allows, and flag if you're at the limit.
Will this definitely make my site load faster?
Correctly configured caching for genuinely cacheable content generally improves loading speed, though the actual improvement depends on your specific site and what wasn't previously cached efficiently.
Can this accidentally break dynamic functionality on my site?
That's exactly the risk we test against — incorrectly caching something that should always be fresh could break dynamic behaviour, which is why we specifically verify sensitive and dynamic pages remain correctly excluded.
Do I need to update these rules if I add new pages later?
Only if the new page needs specific caching behaviour different from your existing rules' general coverage — otherwise, existing rules typically apply automatically based on the URL patterns they're configured against.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.