Website Changes Not Showing Up
You edited your site — new text, new photo, new price — but the live page still shows the old version. Almost always, this is caching.
Common signs of this issue
- You saved a change in your website editor, but the live page looks the same as before.
- The change shows on your computer but not on your phone — or the other way around.
- It shows when you're logged in to the site, but visitors still see the old version.
- New images don't appear, or an old price/phone number stubbornly hangs on.
- The change finally appears hours later on its own.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Do a hard refresh on the page: Ctrl+F5 on Windows, Cmd+Shift+R on Mac. If the change appears, it was only your own browser's memory.
- Open the page in a private/incognito window, or on your phone using mobile data. That shows you roughly what a fresh visitor sees.
- Confirm the change was actually saved and published — in WordPress, check the page shows "Published" and view it from the public link, not the editor preview.
- If you use a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache), look for its "Clear cache" or "Purge" button and use it once.
- If your site uses Cloudflare, its cache is another layer — in the Cloudflare dashboard there's a "Purge cache" option. ("Purge everything" once is safe; the site may load slightly slower for a few minutes afterward.)
- Make sure you're editing the right site — it sounds silly, but staging copies, old duplicates, and similar domains catch people constantly. Check the address bar of the editor.
- If only one image is stuck, it may have been uploaded with the same filename as the old one — re-upload it under a new filename.
What this usually means
Websites are deliberately served from saved copies — caches — so pages load fast. There can be three or four layers of them: your browser, a caching plugin on the site, your hosting server, and a service like Cloudflare. Your change is almost certainly saved; one of these layers is just still handing out the old copy.
This is why you and a customer can see different versions of the same page at the same time: you're each being served by different cache layers with different expiry times.
If clearing caches doesn't help and the change is missing even in the editor, that's the rarer case — the save didn't happen (a session timed out, a staging site was edited, or a plugin conflict blocked the save). That's worth investigating rather than re-clearing caches forever.
What not to do
- Don't make the same edit five more times before checking caches — you can end up with conflicting revisions and real confusion about what's live.
- Don't uninstall your caching plugin just because it held an old copy — caching is why your site loads fast. Clear it, don't remove it.
- Don't 'purge everything' on a large site during your busiest hour; pages rebuild on first load and the site slows briefly.
- Don't edit theme or template files directly to force a change through — that's how small updates turn into broken sites.
When to get help
If a hard refresh, plugin cache purge, and Cloudflare purge still leave old content live after an hour, the layers are misconfigured — often a server-side cache your host controls, or a plugin caching pages it shouldn't. That's a quick diagnosis for someone who knows the stack, and worth a short session if stale prices or contact details are actively misleading your customers.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
How long does it take for website changes to show up?
With caching working normally: instantly after the right cache is cleared, or within a few hours as caches expire on their own. If it routinely takes days, a cache layer is set to keep copies far too long.
Why do changes show on my computer but not my phone?
Each device has its own browser cache, and mobile networks sometimes add their own. It's the same page — you're just seeing two differently-aged saved copies.
What is a hard refresh and is it safe?
Ctrl+F5 (Windows) or Cmd+Shift+R (Mac) tells your browser to throw away its saved copy of the page and fetch a fresh one. Completely safe — it only affects your own browser.
I cleared every cache and the old content is still there. What now?
Verify the edit exists in the editor itself. If it does, a server-level cache (managed by your host) is the likely holdout — ask your host whether server caching is on. If the edit is gone from the editor, the save failed and that's the real problem.
Does clearing caches hurt my SEO?
No. Google fetches pages fresh on its own schedule. Keeping pages current helps SEO far more than any cache-clearing could hurt it.