Why Are My WordPress Changes Not Showing Up on the Live Site?
You edited your homepage and hit Update, but your WordPress changes are not showing up. The dashboard says “saved”, but the live site shows the old version – same stale headline, same old image.
Take a breath. You didn’t break anything, and your work isn’t lost.
When WordPress changes are not showing up on the live site, the cause is almost always cache. There isn’t just one cache either – there are 3, stacked on top of each other, and each has to be cleared before your edit reaches a real visitor. The fix takes 5 minutes once you know which buttons to press.
Why are my WordPress changes not showing up?
The short answer: something between you and your visitor is serving an older copy of the page.
Cache is just a saved snapshot. Instead of building your homepage from scratch every visit, WordPress (and your host, and your browser) saves a finished HTML version and hands it out for the next 60 minutes or so. It makes the site fast. But it also means your edit can sit there for an hour before anyone sees it.
There are 3 cache layers I check, in this order:
- Browser cache – your own Chrome or Firefox is showing you a saved copy
- Server cache – your host or a caching plugin is serving an old HTML snapshot
- CDN cache – Cloudflare or your host’s edge network is holding the old version
Most of the time, the culprit is layer 2. But you have to rule out layer 1 first, because if your browser is the problem, you’ll keep “fixing” the server cache and seeing no result.
How do I do an incognito test?
This is the single best diagnostic step, and it takes 10 seconds.
Open a new incognito window (Chrome: Ctrl+Shift+N, Firefox: Ctrl+Shift+P) and visit your site. If the new version shows up in incognito but not in your normal browser, the problem is your browser cache. Skip to the next section.
If incognito shows the OLD version too, your browser is innocent. The stale page is coming from somewhere outside your computer – your server cache or your CDN. Move on to layer 2.
I run this test every single time, before I touch any plugin settings. It saves me from chasing problems that don’t exist. And it works on phones too – just open a private tab in Safari or Chrome mobile.
One small catch: incognito only bypasses your browser cache, not the server or CDN. So if all 3 layers are stale, incognito will also show the old version – which still tells you the problem isn’t local to your machine.
How do I clear my browser cache?
If incognito fixed it, this is the fast layer.
For most edits, a hard refresh is enough. On Windows or Linux, press Ctrl+Shift+R. On Mac, press Cmd+Shift+R. This tells your browser to ignore its saved copy and ask the server for a fresh one.
If that still shows the old page, do a deeper clear. In Chrome, press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac), set the time range to “Last hour,” check “Cached images and files,” and click Clear data. Reload your site and the new version should appear.
One thing I learned the hard way: browser cache is also why your phone, laptop, and work computer can all show different versions of the same site. Each browser has its own cache. To confirm a fix is really live, ask a friend on a different network to check, or use webpagetest.org to load the URL fresh from a remote server.
How do I clear my WordPress server cache?
Layer 2 is where most “WordPress changes not showing up” problems actually live. Server cache comes from 2 places: your hosting company, and your caching plugin. Often both at once.
Your host’s cache
Managed WordPress hosts run their own cache layer that you can’t turn off. Here’s where to find the purge button on the popular ones:
- SiteGround: Dashboard > SG Optimizer > Caching > Purge SG Cache
- WP Engine: Top admin bar > WP Engine > Caching > Purge all caches
- Kinsta: Top admin bar > Kinsta icon > Clear Cache
- Cloudways: Cloudways panel > pick your app > Application Settings > Purge Varnish Cache
- Bluehost / HostGator: Dashboard > Bluehost menu > Caching > Purge All
On a generic shared host like Hostinger, Namecheap, or DreamHost, the host cache is usually off by default and the caching plugin is doing all the work.
Your caching plugin
If you installed a caching plugin to make the site faster, that’s another snapshot layer to clear. The 3 you’ll most often see:
- WP Rocket: Top admin bar > WP Rocket > Clear and preload cache
- LiteSpeed Cache: Top admin bar > LiteSpeed Cache icon > Purge All
- W3 Total Cache: Top admin bar > Performance > Purge All Caches
Not sure which caching plugin you have? Go to Plugins > Installed Plugins and look for anything with “cache” in the name. WP Super Cache, WP Fastest Cache, and Cache Enabler all work the same way: there’s a “purge” or “clear” button somewhere obvious.
After clearing both your host cache and your plugin cache, do another incognito test. If the new version is there, you’re done. If you’re still seeing the old page, layer 3 is involved.
One trick I rely on: when I’m making 10+ small edits in a row, I temporarily turn the caching plugin off until I’m done, then turn it back on and clear once. Saves 20+ purge clicks per session. Just remember to switch it back on – I’ve left WP Rocket disabled for a week before, and the site got noticeably slower until I caught it.
How do I clear my CDN cache?
A CDN (Content Delivery Network) is the third layer – it stores copies of your site on servers worldwide so visitors get a fast load no matter where they are. The most common one for small WordPress sites is Cloudflare. Some hosts also have their own edge caching that acts the same way.
Not sure whether you have a CDN? Check your domain’s DNS – if your nameservers point to Cloudflare, you have Cloudflare in front of your site. Or ask your host’s support chat: “Do you have edge caching enabled on my account?”
Clearing Cloudflare cache
This is the one I clear the most:
- Log in at dash.cloudflare.com and pick your site
- Click Caching in the left sidebar, then Configuration
- Click Purge Everything and confirm in the popup
It takes about 30 seconds for the purge to roll out worldwide. Then test in incognito again.
Host edge caches
Kinsta, WP Engine, and Cloudways all run their own CDN-style caches that aren’t the same as the WordPress cache covered above. If clearing the regular host cache didn’t work, look for a separate option called “CDN cache,” “edge cache,” or “static cache” and clear that too. WP Engine splits “Page cache” and “CDN cache” into 2 separate purge buttons inside the same menu.
If you have a dedicated CDN plugin (Cloudflare’s official plugin, or BunnyCDN), most add a purge button to your WordPress admin bar. Use that – it’s faster than logging into the CDN dashboard.
What if I still don’t see my changes?
If you’ve cleared all 3 layers and the old version is still showing, I look at 4 less-common culprits:
1. Object cache. Some hosts run Redis or Memcached for database queries. If your text changes are there but a setting (like a customizer color) won’t apply, this is often why. WP Rocket has a “Clear object cache” option, or your host can flush it – just open a support ticket and ask them to “flush Redis.” If you ever see a 500 internal server error after a Redis flush, that’s a separate fix.
2. CSS/JS minification cache. Caching plugins often combine and minify your CSS files into one, and that combined file can stay stale after a theme tweak. In WP Rocket, go to Settings > WP Rocket > File Optimization and toggle CSS minification off, save, then back on – that forces a rebuild. Same idea for LiteSpeed and other caching plugins.
3. Customizer not saving. If your changes never actually saved, that’s a different problem. The Kadence Customizer occasionally fails to save in Chrome – my fix for Kadence Customizer not saving changes covers that. If the customizer is broken so badly the site won’t load, my notes on what to do when WordPress recovery mode isn’t working get you back in.
4. You’re editing the wrong page. I’ve done this. WordPress lets you have a “Home” page in Pages > All Pages that isn’t actually your homepage – if Settings > Reading points to a different page, your edits go nowhere visible. Same trap can hit the blog page if your posts aren’t showing up.
One more edge case: search engines. Google can take 1-3 weeks to recrawl your page, so even after the live site updates, your search snippet or old logo can stick around in Google’s results until they refresh. That’s not something you can fix from your dashboard.
FAQ
Why is my WordPress not updating changes?
I see this happen most often because of caching. Your browser or server is holding onto an older snapshot of your page instead of fetching the new one. Clearing your caches usually fixes it instantly.
How long does WordPress take to publish changes?
When you hit Update, your changes save to the database instantly. If you don’t see them on the front end right away, a caching layer is delaying the display. Once you clear that cache, the live site updates immediately.
Why do my changes appear in preview but not on the live site?
WordPress preview mode is smart enough to bypass your site’s cache so you can see your work. The live site, however, serves the cached version to keep things fast for visitors. You just need to purge your server cache to force the live site to catch up.
Why is WordPress not saving my changes?
If the dashboard itself isn’t saving and you get an error when you click Update, you might be out of server memory or have a plugin conflict. But if it says “saved” and you just can’t see it on the front end, it’s almost definitely a caching issue.
Your changes are there – the cache is just hiding them
Here’s the takeaway. When WordPress changes are not showing up on the live site, your work isn’t lost and your site isn’t broken. There’s just a stale snapshot somewhere between you and your visitor.
Run the incognito test first. Then clear browser, then server (host plus plugin), then CDN. One of those purges will reveal your edit. And once you’ve done it 2 or 3 times, the whole sequence takes under 5 minutes.
Before bigger changes – swapping a theme, editing the header, redoing your homepage – I’d also back up your WordPress site first. Cache is easy to fix. Accidentally deleting a section is harder.
