WordPress changes not showing after you save: five places where the old version hides
When WordPress changes are not showing after you save, it is almost always the cache, a copy of the page from before the change. It can sit in the browser, in a cache plugin, on the host's server or in a CDN. Check the page in a private window, then clear the layers from browser to CDN. Less often, the problem is in the editor.
Author: The TellMyShop team. A guide for WordPress site and WooCommerce store owners: the cause, the manual fix and the same work in a chat conversation.
Last updated: · 6 min read
First, establish whether it saved or not
This question separates two different problems. Open the page in the editor again, after refreshing.
- The editor has the new version, the site the old one. The change saved to the database, and something along the way is showing an old copy. That is the cache, and the rest of this article.
- The editor has the old version too. The change didn't save. Most often it is an expired session, a plugin conflict or a server error when saving. Then see the section on the editor at the end.
A second quick check: open the page in a private browser window or on a phone with Wi-Fi off. Cache plugins usually bypass logged-in users, so logged in you see the fresh page, while the customer sees the copy.
Five layers from the browser to the CDN
The old version of a page can sit in one of five places. Each is cleared somewhere different, by someone different.
| Layer | How you can tell | Where to clear it | Who |
|---|---|---|---|
| 1. Browser | a private window shows the new version | hard refresh or clearing the site data | you |
| 2. Cache plugin | logged in you see the new one, in a private window the old one | button on the dashboard's top bar or the plugin settings | you |
| 3. Server cache | plugin cleared, still old | hosting panel, cache section | you or your host |
| 4. CDN | different versions in different places, the address goes through Cloudflare or a similar service | CDN panel, purging selected addresses | you or whoever manages the domain |
| 5. Optimised CSS and JS files | new content, old look | optimisation plugin settings, regenerating the files | you |
The WordPress documentation on caching explains that cache plugins save finished pages as files, so the server doesn't have to build them every time. That is why the copy has to be refreshed after a change. The Liquid Web guide to caching plugins shows how the most popular ones work and what each option clears. Most plugins refresh the copy themselves when a post is saved, but not always for changes to widgets, menus, the footer or theme settings.
The order of clearing, step by step
Clear from the layer closest to you. After each step, check the page in a private window so you know which layer was to blame. That will help next time.
- Hard refresh in the browser. On a Windows computer it is usually Ctrl and F5, on a Mac Cmd, Shift and R.
- Clear the cache plugin. WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache and similar have a button on the dashboard's top bar. Choose clearing everything, not one page, if you changed the menu or footer.
- Clear the host's cache. Many hosts have their own server cache, turned on in the panel. If you can't find the button, ask your host.
- Clear the CDN. In Cloudflare you can purge selected addresses instead of the whole site. The instructions are in the documentation on purging single files in Cloudflare.
- Regenerate the CSS and JS files. If you changed the look rather than the content, clear the combined style files in the optimisation plugin's settings.
If the page is still old after all five steps, the problem isn't the cache.
When it isn't the cache: editor, theme and templates
A few situations look like the cache but have another cause.
You are editing the wrong page. This happens with page copies, language versions or a draft sitting next to the published page. Check the address in the browser bar and in the editor.
The content comes from a template. The header, the footer and some homepage sections in block themes are part of the template, not the page. You change them in Appearance, Editor, not in the page editor.
You are changing a file of a theme that isn't active. If the site uses a child theme, changes in the parent theme may be overridden. The other way round too: a change in a parent theme file disappears when it updates.
The save failed. When the change isn't there after refreshing the editor, check in Tools, Site Health whether the REST API works, and ask whoever looks after the site for the error log. The block editor saves through the REST API, so a security plugin or the server blocking it produces this symptom.
How the chat checks what a visitor sees
The hardest part is working out which layer is to blame. The TellMyShop plugin for WordPress and WooCommerce lets your chat (Claude or ChatGPT) compare two things: the content saved in the database and the page a logged-out visitor gets. Both work in the free TellMyShop Free, together with the plugin list, which shows which cache plugin is installed.
You: I changed the opening hours on the Contact page, but customers still see the old ones.
Your chat: In the database the Contact page has the new hours, from 9 to 18. The page a logged-out visitor gets shows the old ones, from 8 to 16. The plugin list shows LiteSpeed Cache is active.
Your chat: Conclusion: the change is saved, and visitors are most likely getting an old copy from the plugin's cache. I can clear it once you turn on the Theme switch. Preview:
You: I've turned it on. Clear it.
Your chat: Cleared. I checked the Contact page again logged out: visitors see the new hours.
Card status: waiting for your “yes”old version: WordPress cache and LiteSpeed Cache: saved copies of pages
new version: cache cleared, pages will be rebuilt
The hours and dates in this conversation are illustrative. Clearing the WordPress cache and popular cache plugins works in TellMyShop Pro after you turn on the Theme switch. The switch lasts 24 hours and requires a database backup from today. Like every save, clearing has a preview and waits for your ‘yes’. You clear the host's cache and the CDN in their own panels, because the plugin has no access to them.
If you often change the same texts on many pages, the guide on how to edit a WordPress page will help. When the page doesn't show at all, not just in an old version, go to the article WordPress site not showing in Google. You can compare Free and Pro in the pricing, download the free version on the TellMyShop Free page, and find more guides on the blog.
Questions and answers
Why can I see the changes but my customer can't?
Cache plugins often don't show the saved copy to logged-in users. You, logged in, see the fresh page, while the customer gets a copy from before the change. Always check the result in a private window, logged out.
How do I clear the cache in WordPress?
It depends on where the cache is. A cache plugin has a clear button on the top bar of the dashboard or in its settings. You clear the host's cache in the hosting panel, and a CDN, such as Cloudflare, in its own panel. WordPress itself has no single button for all layers.
My CSS changes don't work. What should I check?
First the browser cache and the plugin that combines and minifies CSS files, because it keeps the old version of the file. Then make sure you are editing the additional CSS or the child theme of the active theme, not a theme that is merely installed.
Can clearing the cache break anything?
Usually not. The site may run slower for a moment while the copies are rebuilt. But don't turn off the cache plugin permanently just to see your changes, because the site will be slower for everyone.
I clicked Update, and after refreshing the editor the changes are gone. Is that the cache too?
Probably not. If the change vanished in the editor itself, it didn't save to the database. Common causes are an expired login session, a plugin conflict or a server-side block on saving. Check Tools, Site Health and the error log.
WordPress is a trademark of the WordPress Foundation. WooCommerce is a trademark of Automattic Inc. Claude is a trademark of Anthropic PBC. ChatGPT and OpenAI are trademarks of OpenAI. TellMyShop is not affiliated with these companies.