Cloudflare Cache Problems and Solutions
Ibrahim Monir
Full-Stack Developer

Fix the most common Cloudflare caching issues — stale content after updates, cached cart/checkout pages, CSS/JS not refreshing, low cache hit ratio, and cached errors — with the exact purge steps, cache rules, and a best-practice setup, plus an FAQ.
Most Cloudflare cache problems come down to five issues: stale content after you update your site, dynamic pages (cart, checkout, login) being cached, CSS/JS changes not showing, a low cache hit ratio, or cached error and redirect pages. Nearly all of them are fixed by purging the cache correctly and setting the right page rules so Cloudflare caches static files but never dynamic ones. This guide covers each problem and its exact solution.
Cloudflare's cache is what makes your site fast — but when it serves the wrong version of a page, it can be confusing and frustrating. Here's how to diagnose what's happening and fix it.
How Cloudflare caching works (in one minute)
Cloudflare stores copies of your static files — images, CSS, JavaScript, fonts — on its global network and serves them from the data center closest to each visitor. By default it does not cache HTML unless you tell it to. Understanding this matters, because most "cache problems" are really about the wrong content being cached or an old copy not being cleared.
You can see what's happening by checking the cf-cache-status response header in your browser's Network tab:
- HIT — served from Cloudflare's cache.
- MISS — fetched from your server, then cached.
- BYPASS — intentionally not cached.
- DYNAMIC — not eligible for caching (default for HTML).
Common Cloudflare cache problems and their solutions
1. You updated your site but still see the old version
The most common complaint. Cloudflare (or your browser) is serving a cached copy from before your change.
Solution: Purge the Cloudflare cache. In the dashboard go to Caching → Configuration → Purge Cache. Use Purge Everything after a big change, or Purge by URL for a single page. Also hard-refresh your browser (Ctrl/Cmd + Shift + R) to rule out local caching. If you use WordPress, the official Cloudflare plugin can purge automatically when you update content.
2. Cart, checkout, or login pages behave strangely
Dynamic pages should never be cached. If Cloudflare caches them, users see other people's sessions, empty carts, or failed checkouts.
Solution: Create a Cache Rule (or page rule) to Bypass Cache for /cart/*, /checkout/*, /my-account/*, and /wp-admin/*. Cloudflare also automatically bypasses caching when certain cookies (like WordPress login or WooCommerce session cookies) are present — make sure those aren't being stripped.
3. CSS or JavaScript changes aren't showing up
After a design tweak, the site still loads old styles because the CSS/JS files are cached with a long expiry.
Solution: Purge the cache, then use cache-busting — append a version query string (e.g. style.css?v=2) so the browser and Cloudflare treat it as a new file. If you enabled Auto Minify or Rocket Loader and something looks broken, disable them and re-test.
4. Low cache hit ratio (Cloudflare isn't caching enough)
If most requests show MISS or DYNAMIC, Cloudflare is passing traffic to your server instead of serving from cache, so you lose the speed benefit.
Solution: Add a Cache Rule to "Cache Everything" for your static, non-personalized pages, and set an appropriate Edge Cache TTL. Make sure your server isn't sending no-cache or private cache-control headers on assets. Check the Caching analytics in the dashboard to measure improvement.
5. Cloudflare cached an error page or a redirect loop
Sometimes a temporary 500/404 error or a bad redirect gets cached and keeps showing even after you fix the underlying issue.
Solution: Purge the affected URL(s). For redirect loops, check your SSL/TLS mode — using "Flexible" when your host already has SSL is the classic cause; switch to Full (Strict). By default Cloudflare doesn't cache most error responses, so purging usually clears it.
6. Changes work for you but not for other visitors (or vice versa)
This points to a caching layer somewhere, not a code problem.
Solution: Remember there are usually three caches: your browser, your WordPress/caching plugin, and Cloudflare. Clear all three in order. Enable Cloudflare Development Mode (Caching → Configuration) to temporarily bypass the edge cache for three hours while you actively work — then turn it off.
Best-practice caching setup to prevent problems
- Cache static assets (images, CSS, JS, fonts) with a long Edge Cache TTL.
- Never cache cart, checkout, account, admin, or any personalized page.
- Purge automatically on content updates using the Cloudflare plugin or API.
- Use versioned asset URLs so updates bust the cache automatically.
- Set SSL to Full (Strict) to avoid redirect-loop caching issues.
- Monitor
cf-cache-statusand the Caching analytics to confirm it's working.
Frequently asked questions
How do I clear the Cloudflare cache?
In the Cloudflare dashboard, go to Caching → Configuration → Purge Cache. Use "Purge Everything" for site-wide changes or "Purge by URL" for a single page. On WordPress, the official Cloudflare plugin can purge automatically whenever you update content.
Why does my site still show old content after purging Cloudflare?
Because another cache is involved. Clear your browser cache (hard refresh), your WordPress caching plugin's cache, and any hosting-level cache in addition to Cloudflare. If it persists, verify you purged the correct URL and that Development Mode isn't masking the real cache state.
Should Cloudflare cache my WooCommerce checkout page?
No. Cart, checkout, my-account, and admin pages must never be cached, or customers will see broken sessions and failed orders. Create a Cache Rule to bypass cache on those URLs, and rely on Cloudflare's automatic bypass for logged-in and session cookies.
What does cf-cache-status DYNAMIC mean?
DYNAMIC means Cloudflare did not cache the response — the default behavior for HTML pages. It isn't an error. If you want those pages cached, create a "Cache Everything" rule for the appropriate URLs and set an Edge Cache TTL.
Final thoughts
Cloudflare cache problems feel mysterious but are almost always one of two things: an old copy that needs purging, or the wrong type of page being cached. Set up clean cache rules — cache static assets aggressively, bypass all dynamic pages, and purge automatically on updates — and most issues disappear for good. When something looks wrong, check cf-cache-status, clear all three cache layers, and you'll almost always find the culprit in minutes.


