TLDR
There are four places WordPress cache lives: your browser, your caching plugin (page cache), WordPress object cache, and your CDN or host-level cache. Changes not showing up usually mean one of those is serving the old version. The fix is to clear each layer, from the outside in, until the new content appears.
This post explains each cache layer in plain English, shows how to clear it in the most common plugins and hosts, and lists the four mistakes that leave beginners convinced a change broke their site when it was really just cached.
You make a change, hit save, reload the page, and nothing has updated. You check again, maybe even log into a different browser, same old version. This is cache doing its job too well.
WordPress sites can have cache at four different layers, and they stack. Understanding which one is stale saves a lot of panic.
The four layers of WordPress cache
- Browser cache. Files stored on the visitor’s computer so the next visit is faster. Cleared per browser.
- Page cache (plugin layer). Your caching plugin saves a full HTML snapshot of each page and serves it until you invalidate. WP Rocket, W3 Total Cache, LiteSpeed Cache and others sit here.
- Object cache. WordPress caches the results of database queries. Not always in play, but most managed hosts enable it.
- Server or CDN cache. Your host’s edge cache (Pressable, Kinsta, WP Engine) or a CDN in front of the site (Cloudflare, BunnyCDN). Can serve a cached page even after you clear the plugin cache.
How to clear each cache, from the outside in
1. Clear your browser cache first
Before anything else, make sure your own browser is not the one fibbing. The fastest check is a hard refresh: Ctrl+F5 on Windows, Cmd+Shift+R on Mac. If that does not work, open the page in an incognito or private window. An incognito window ignores most browser caching.
2. Clear your page cache plugin
Most caching plugins add a “Clear cache” link at the top of the admin bar. The exact path by plugin:
- WP Rocket. Admin bar, WP Rocket, Clear cache. Or Settings, WP Rocket, Dashboard, Clear cache.
- LiteSpeed Cache. Admin bar, LiteSpeed Cache, Purge all. Or LiteSpeed Cache, Toolbox, Purge.
- W3 Total Cache. Admin bar, Performance, Purge all caches.
- WP Super Cache. Settings, WP Super Cache, Delete Cache.
- Autoptimize. Settings, Autoptimize, Delete Cache.
3. Clear your server or CDN cache
Most good managed hosts cache at the server edge, which survives a plugin cache clear. Check these:
- Pressable, Kinsta, WP Engine. Admin bar usually has a “Host” or “Hosting provider” item with a Clear cache button. Or log into your host dashboard and clear from there.
- Cloudflare. Log into Cloudflare, go to Caching, Configuration, Purge Everything. For a single URL, use Purge Cached Content, Purge by URL.
- BunnyCDN or KeyCDN. Similar pattern: log into the dashboard, find the Purge or Clear Cache action, select the whole zone or specific URLs.
Common mistakes beginners make here
- Assuming “Clear cache” in the admin also clears your CDN. Almost never true. Always clear both layers when a change is not showing up.
- Clearing cache every time you make a small edit. Most plugins auto-purge the cache for a page when that page is updated. Repeated manual clears slow the site down for real visitors.
- Disabling the caching plugin to “fix” a display bug. Now your site is slow for every visitor. Better to clear and reload than disable.
- Forgetting the logged-in admin view is not cached. You are seeing the live version. Check in an incognito window to see what visitors actually see.
Clearing cache from the command line
For developers with SSH access, WP-CLI has a one-liner for most caches:
wp cache flush, clears the WordPress object cache.wp w3-total-cache flush all, for W3 Total Cache.wp rocket clean, for WP Rocket.wp litespeed-purge all, for LiteSpeed Cache.
Running these as part of a deploy script means every update goes live with a clean cache automatically.
When to cache and when to exclude
Not every page should be cached. The most common exclusions:
- Shopping cart, checkout and my-account pages in WooCommerce (caching them can serve one customer’s cart to another).
- Pages with forms that rely on a nonce (the nonce can expire while cached).
- Member-only content behind a login.
- Admin area (always excluded by default, check your settings if not).
All good caching plugins exclude these by default. If you have a custom cart or member area, add its URL pattern to the caching plugin’s exclude list.
Try it yourself this week
Make sure you know where every cache layer on your own site lives.
- Log into your WordPress admin, note which caching plugin is active.
- Log into your hosting dashboard, find the “Clear server cache” button and take a screenshot.
- If you use a CDN, log in and find its purge option. Take a screenshot.
- Add all three links to a single note you can reach in ten seconds. Next time a change does not show up, you have the whole chain at hand.
Three minutes of preparation, zero panic the next time something looks wrong.
Prefer a human to help?
If the steps above are not enough, or you are short on time, the team behind WP Clipboard runs a Liverpool WordPress agency that has been fixing sites for small businesses and charities since 2012. Fixed-price quotes, no long tie-in.
Visit Marketing The ChangeFrequently Asked Questions
Do I need to clear cache every time I update a post?
No, every good caching plugin auto-purges the cache for a page when that page is saved. You only need to manually clear if the auto-purge misses something (often when the change is in a shared header, footer or sidebar that affects many pages at once).
Why does my site still show the old version after clearing the WordPress cache?
Nine times out of ten, a CDN or host-level cache is still serving the old version. Clear those layers too. The tenth time, your own browser is holding an older copy, try an incognito window.
Is it safe to clear all caches at once?
Yes, completely safe. The only cost is that the next few visits will be slightly slower while the caches rebuild. On a healthy site that takes a few seconds and a handful of visits.
What is object cache, and do I need it?
Object cache stores the results of database queries in memory so WordPress does not have to re-query the same data on every page. Most managed hosts enable Redis or Memcached object cache by default. If yours does not and you have a busy site, turning it on can noticeably speed up the admin and dynamic pages.
Will clearing cache affect my SEO?
Not directly. Google re-crawls your pages regardless of whether you have cleared your cache. A cached page serving the right content to Google is identical to a fresh page serving the right content to Google. Only worry if your cache is serving broken or stale content over the long term.