WordPress Changes Not Showing on Site: 7 Proven Fixes
Few things are more stressful than WordPress changes not showing on site after you’ve hit Update, especially when a wrong price or an expired sale banner is still live and costing you orders. You refresh, clear something, refresh again, and nothing moves. The good news is that in almost every case your edit saved correctly and an old copy is simply being served. This guide walks through each cause in the order a senior engineer would check them, so you can fix it in minutes rather than hours.
See how our Website Edits service handles this →
Quick answer: When you find WordPress changes not showing on site, an old cached copy is usually being served. Hard-refresh your browser, purge your caching plugin, then clear your host and CDN cache (such as Cloudflare). If it still looks old, check you edited the right page, template or theme, and that you actually published it.
1. Your browser is showing you an old copy
Symptom: the change shows up on your phone or for a colleague, but not on your own computer. Or the text has updated but a new logo or stylesheet hasn’t.
Why it happens: browsers keep images, CSS and JavaScript on your computer so pages load faster. As a result, your browser may keep using yesterday’s files even though the server already has the new ones. This is the most common reason the person who made the edit sees WordPress changes not showing on site.
How to check
- Open the page in a private or incognito window.
- Load it on your phone using mobile data, not your Wi-Fi.
- If the change appears there, the problem is only your browser.
How to fix it
- Do a hard refresh: Ctrl + Shift + R on Windows, or Cmd + Shift + R on Mac.
- If that fails, clear cached images and files in your browser settings (you can keep your passwords and cookies).
- Reload the page and check again.
This is the fastest check, so always start here before you touch anything on the server.
2. A caching plugin is serving the old page
Symptom: you see the change while logged in to WordPress, but logged-out visitors and incognito windows still get the old version. If only your customers are affected, this is the cause to check first.
Why it happens: plugins such as LiteSpeed Cache, WP Rocket, W3 Total Cache or WP Super Cache save a finished HTML copy of every page. Most of them bypass the cache for logged-in admins, which is exactly why you see one version and your customers see another. Many plugins clear the cache automatically when you update a page. However, edits to menus, widgets, the Customizer or a global header often don’t trigger that clear.
How to check
- Look in your admin toolbar for a cache menu, or find the plugin’s own menu in the dashboard.
- In an incognito window, view the page source and look near the bottom for a comment that names a cache plugin and gives a timestamp.
How to fix it
- Use the plugin’s Purge All or Clear Cache option, not just “purge this page”.
- If the plugin also keeps a separate cache of optimised CSS and JavaScript, clear that as well.
- Reload in incognito. If the change now shows, turn on automatic purging for menu and widget saves in the plugin settings, if it offers that option.
3. WordPress changes not showing on site because of server or CDN cache
Symptom: you’ve purged your plugin, yet the old page keeps coming back. Sometimes the change appears in one country or on one network but not another.
Why it happens: many hosts run their own cache layer, such as Varnish, NGINX FastCGI cache or a built-in “site accelerator”. On top of that, a CDN such as Cloudflare keeps copies of your files on servers around the world. Each layer has to be cleared separately, and your WordPress plugin can’t always clear them for you.
How to check
- Log in to your hosting dashboard and look for a cache, performance or speed section.
- If you use Cloudflare, check whether a cache rule or a “Cache Everything” setting is active.
How to fix it
- Clear the server cache from your hosting panel.
- In Cloudflare, open the Caching section and choose Purge Everything (or purge just the affected URL).
- Wait a minute, then test in incognito on mobile data.
The official WordPress cache documentation explains how page, object and browser caching fit together. If you run your own server, our WordPress on a VPS setup guide shows where server caches live and how to clear them.
4. The edit was never actually published
Symptom: the page looks exactly as it did before on every device, even after you’ve cleared every cache. When WordPress changes not showing on site survive a full purge, publishing is usually the problem, not caching.
Why it happens: this is more common than people admit. Typical culprits include:
- You clicked Save Draft or Preview instead of Update.
- The post is Scheduled for a future date.
- Your Customizer changes were saved as a draft or scheduled instead of published.
- In Elementor or Divi, you closed the tab before the save finished.
- Someone else had the page open and saved over your work.
How to check
Open the page in the editor and check its status and the Revisions panel. Revisions show who saved what and when.
How to fix it
- Reopen the page, confirm your change is there, and click Update or Publish.
- If your edit was overwritten, restore the right version from Revisions.
- Ask anyone else editing the site to close the page while you work.
5. You edited the wrong page, template or site
Symptom: your edit is saved and published, yet the live page hasn’t changed at all. This is a classic reason for WordPress changes not showing on site, and it has nothing to do with cache.
Why it happens: modern themes build each page from several parts. Your header might come from an Elementor Theme Builder template, a Kadence Element, a Divi Theme Builder layout or a block theme’s template part. Likewise, the layout of WooCommerce product pages often comes from one shared template rather than from each product. And sometimes you’re simply logged in to a staging copy, or editing an old duplicate page with a similar URL.
How to check
- Compare the URL in your browser’s address bar with the URL of the page you edited. Watch for slugs like /shop-2/ or /home-old/.
- Check the domain: are you on a staging address or the live site?
- In your page builder, open the Theme Builder or template list and see which template’s display conditions match that page.
How to fix it
- Make the edit in the template that actually controls that section.
- Delete or redirect duplicate pages so nobody edits the wrong one again.
- If you made the change on staging, push it to live with your host’s staging tool, or repeat it on the live site.
6. Page builder or theme CSS files are stale
Symptom: text changes appear, but colours, spacing, fonts or the mobile layout stay the same. Occasionally the page looks half-updated or broken.
Why it happens: Elementor, Divi and many themes save your design settings into generated CSS files, and optimisation plugins then minify and combine those files. Consequently, if the generated file isn’t rebuilt, you get WordPress changes not showing on site even though the setting saved correctly.
How to check
Right-click the element, choose Inspect, and see which CSS rule is being applied. If the old value comes from a file with a long, random-looking name, that file is probably out of date.
How to fix it
- Elementor: go to Elementor, then Tools, and click Regenerate CSS & Data.
- Divi: in Theme Options, open Builder, then Advanced, and click Clear next to Static CSS File Generation.
- Kadence and block themes: re-save the page or Customizer setting, then purge your cache plugin.
- Clear the minify or combine cache in your optimisation plugin, then purge your CDN.
Also check that a mobile or tablet setting isn’t overriding the desktop value. Builders let you set different values for each device, and a forgotten mobile value will override the desktop one on phones.
7. Code changes went to the wrong file or were overwritten
Symptom: custom CSS or PHP you added worked yesterday and vanished today, or never worked at all. Code is a quieter source of WordPress changes not showing on site, because nothing warns you when it fails.
Why it happens: edits made directly in a parent theme are wiped out by the next theme update. Custom CSS can lose out to a more specific rule elsewhere, and some snippet plugins switch a snippet off automatically after an error. On sites with an object cache such as Redis, old settings can also stay in memory after you change them.
How to check
- Find out whether your code lives in a child theme or the parent theme.
- Open your snippets plugin and confirm the snippet is still active.
- Look for an object cache option in your hosting panel or caching plugin.
How to fix it
- Move custom code into a child theme or a snippets plugin so updates can’t erase it.
- Make your CSS selectors more specific rather than adding
!importanteverywhere. - Flush the object cache after changing settings that are stored in the database.
If a code edit led to a crash or white screen, our WordPress memory exhausted error fix covers one of the most common errors. If you need to undo the damage, you can roll back with our guide on how to restore a WordPress site from backup.
Troubleshooting table: symptom, cause and fix
Use this table to go straight to the most likely cause of WordPress changes not showing on site.
| What you see | Likely cause | Quick fix |
|---|---|---|
| Change visible on your phone, not your computer | Browser cache | Hard refresh (Ctrl/Cmd + Shift + R) |
| New when logged in, old when logged out | Caching plugin | Purge All in the cache plugin |
| Old page returns after purging the plugin | Host or CDN cache | Clear host cache, then Purge Everything in Cloudflare |
| No change anywhere, even with caches cleared | Not published, or wrong page | Check status, Revisions and the URL |
| Header, footer or product layout unchanged | A Theme Builder template controls it | Edit the template, not the page |
| Text updates, styling doesn’t | Stale generated CSS | Regenerate builder CSS, clear minify cache |
| Custom code disappeared after an update | Code was added to the parent theme | Move code to a child theme or snippets plugin |
The right order to clear caches
Order matters. If you purge Cloudflare first and your plugin second, Cloudflare can store the old page again before the plugin has cleared it. Therefore, start with the layer closest to WordPress and work outwards:
- Builder CSS (regenerate)
- Object cache (if you have one)
- Caching plugin (Purge All)
- Host server cache
- CDN (Cloudflare or similar)
- Your browser (hard refresh or incognito)
Following this order fixes most cases of WordPress changes not showing on site in under ten minutes.
When to call in a pro
Sometimes you’ve cleared every cache, checked every template, and you still have WordPress changes not showing on site. Or perhaps you know exactly what needs changing but don’t want to risk breaking checkout in a busy week. Either way, it’s sensible to stop there and hand it over.
Our Website Edits service takes care of it for you. Here’s what you get:
- Layout, content and design changes are built and tested on a staging copy, not on your live store.
- You approve the result before anything goes live.
- We work with Elementor, Kadence, Divi, Gutenberg and custom themes.
- Optional 24-hour delivery is available when it’s urgent.
- Pricing starts from $90.
Not sure what’s causing the problem? Just describe what you’re seeing on WhatsApp and we’ll send you a no-obligation quote.
Leave your name and what is happening on WhatsApp — we diagnose it, talk it through and send you a quote. No obligation, no jargon.
Message us on WhatsAppFrequently asked questions
Why do I see my changes but my customers don’t?
Most caching plugins bypass the cache for logged-in administrators. As a result, you see the fresh page while visitors get the cached copy. Purge your caching plugin and any host or CDN cache, then check in an incognito window.
How long does it take for WordPress changes to appear?
Without caching, changes appear instantly. With caching, they appear when the cached copy expires or is purged, which can take anywhere from minutes to a day. A manual purge makes them appear straight away. If you still have WordPress changes not showing on site after a purge, check the publish status and the template.
Will clearing the cache break my site or delete content?
No. Clearing the cache only removes stored copies of pages and files. Your posts, products and orders stay safely in the database. The first page load afterwards may be slightly slower while the cache rebuilds.
Why are my WordPress changes not showing on site only on mobile?
Usually there’s a mobile-only setting in your page builder, or your phone’s browser is holding an old copy. Check the mobile and tablet values in your builder, then test in a private tab on mobile data.
Should I disable my caching plugin to stop this happening?
No. Caching keeps your site fast, and a fast site sells more. Instead, turn on automatic purging when you update content, and purge manually after editing menus, widgets or templates.






