Website Changes Not Showing or Visitors See an Old Version: What to Check
When website changes are not showing, the change has almost always been saved correctly and a cache is still handing out an older copy of the page. A cache is a stored copy kept to make the site load faster, and one can sit in the visitor's browser, in a CDN such as Cloudflare, in a caching plugin or on the server, or in DNS after a site move. The fix is to find which layer holds the old copy and clear only that one.
Every check below can be done from a browser or a dashboard, without touching code.If your site runs on WordPress and this keeps happening, it is usually a setup issue that a WordPress development team can correct once.
Why is my website still showing the old version after I updated it?
It is showing the old version because at least one cache between your server and the visitor has not yet replaced its stored copy. MDN's HTTP caching guide describes two kinds: a private cache, which is tied to one client and is typically the browser, and shared caches that sit between the visitor and the server, including CDNs. A stored copy is treated as "fresh" for a set time and reused without asking your server again.
The four places an old copy can live
- The visitor's browser. It keeps pages, images, stylesheets and scripts on that one device.
- A CDN such as Cloudflare. It keeps copies in data centers around the world and serves them to everyone.
- A caching plugin or server cache. It keeps ready-made copies of whole pages on your hosting.
- DNS, after a move to new hosting. Some visitors are still being sent to the old server.
One useful detail: Cloudflare's documentation says its CDN does not cache HTML by default, but it does cache files such as CSS, JavaScript and images. So if your new text appears but the layout, colors or pictures are still old, a CDN or browser copy of those files is the likely cause.
What can I safely check in 10 minutes to find which cache is stale?
You can narrow it down by loading the page in ways that skip one cache layer at a time. None of these steps changes anything on your site.
- Open the page in a private or incognito window. If the change appears there, the old copy is in your own browser. A force reload (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) asks the browser to bypass its stored copy.
- Check on a phone using mobile data, with Wi-Fi off. This is a different device and a different network. If the phone shows the new version, the problem is local to your computer or office network.
- Log out, or ask someone who has never logged in. Many caching plugins skip the cache for logged-in administrators, so you may see the new page while the public sees the old one.
- Look at your caching plugin or hosting control panel. Note whether page caching is switched on and whether there is a clear or purge button. Do not press it yet.
- Log in to your CDN dashboard. In Cloudflare, check that the site is active and find the Purge Cache area on the caching Configuration page.
- Ask whether the site moved recently. If hosting or the domain setup changed in the last few days, DNS is a candidate. Just note the date; do not edit any records.
If every device and network shows the old version, the stale copy is on the server side: the plugin, the host or the CDN.
Is it safe to purge or clear the website cache?
Yes, purging from the CDN's or plugin's own button is normally safe, because it removes stored copies only and leaves your real pages, files and database untouched. Cloudflare describes purging as removing cached content from its servers so that updates are reflected immediately; the next visitor's request fetches a new copy from your server.
Prefer the smallest purge that solves the problem. Cloudflare offers a purge by single URL as well as Purge Everything, and it warns that after purging everything, every request goes to your server until the cache refills, which on a high-traffic site can slow it down or overload it. On a busy store, purge the affected pages only or do it at a quiet hour.
Purge in order from the server outward: plugin or host cache first, then the CDN. Otherwise the CDN may simply collect the old page again from the plugin.
Why do some visitors see the change before others?
Visitors see the change at different times because each browser and each cache stored its copy at a different moment and each copy expires on its own clock.
You cannot reach into a visitor's browser. Cloudflare states that purging its cache does not affect assets stored by a visitor's browser, and its documentation lists a default Browser Cache TTL of 4 hours (checked October 6, 2026). After a hosting move, the delay is different in kind: DNS records carry a time to live that controls how long each record is cached, so for that period some networks still point at the old server.
What should I not do when website changes are not showing?
Do not start changing things at random, because the original edit is very likely fine. In particular:
- Do not make the same edit again and again, or re-upload files repeatedly. You can end up with duplicate or conflicting versions.
- Do not deactivate or delete the caching plugin on a live site to "test" it. That can change how the site behaves under load.
- Do not change DNS records or nameservers, and do not pause the CDN, unless a developer tells you to.
- Do not restore a backup. This is not data loss, and a restore can remove the very change you made.
When should I call a developer, and what should I send?
Call a developer if the old version still appears on every device after you have purged the plugin cache and the CDN, or if the site moved recently and different people are seeing two different sites. Those cases need someone to inspect response headers, server-level caching or DNS, which are not owner tasks.
Send the exact page address, what you changed and when, which devices and networks show old or new, screenshots of both versions, which caches you purged and at what time, the names of your host, CDN and caching plugin, and the date of any recent hosting or domain change.
How do I stop old versions of my site being shown again?
You stop it by having the site built so that changed files get new addresses and caches are cleared automatically on publish. MDN calls the first technique cache busting: a version number or hash is placed in the file name, so an updated stylesheet has a new URL and no cache can serve the old one.
Ask your developer to confirm three things: assets are versioned, the caching plugin purges the affected pages when content is saved, and the CDN is purged as part of every release. This belongs in routine upkeep; see our guide to software maintenance and support.
Quick answers
Why are my website changes not showing up?
A cache is serving an older stored copy of the page or its files. The copy may be in your browser, a CDN such as Cloudflare, a caching plugin or server cache, or DNS if the site recently moved.
Does purging the cache delete my website content?
No. Purging removes only the stored copies held by the CDN or caching plugin, and the next request fetches the current version from your server. Your pages, files and database are not touched.
Why can my customers still see the old site after I purged Cloudflare?
Cloudflare states that purging its cache does not affect assets already stored in a visitor's browser. Those visitors keep the old files until their browser copy expires or they force a reload.
How long do DNS changes take to reach everyone after a site move?
It depends on the time to live (TTL) set on the DNS records, which controls how long each record is cached. Until that time passes, some visitors can still be sent to the old server.
Conclusion
A site that shows an old version is nearly always a caching question, not a lost edit. Work out which layer holds the stale copy with a private window and a second network, purge the plugin or host cache and then the CDN using their own buttons, and leave DNS, code and backups alone.
If the old version persists and you have no developer available, you can contact Entrant Technologies and we will take a look. Have the page address, screenshots and the list of what you purged ready.