I Made Changes to My Site But They're Not Showing — Why Do I See the Old Version?

You changed a price, uploaded a new photo, fixed a phone number — you refresh the page and the old version is still there. It's one of the most frustrating moments for a site owner, especially when you start worrying you broke something or that your edit didn't save.

The good news: almost always the site is fine and your change really was saved. What you're seeing is an old copy kept somewhere on the road between the server and your screen — this is called cache. There are several places this copy can hide, and in this article we go through them one by one and show you exactly how to force the new version to appear, without breaking anything.

What cache is and why it exists

Cache is a temporary copy of the page, kept closer to the visitor so it loads faster. The idea is good: instead of asking the server for everything on every visit, the browser or an intermediate service reuses what it has already seen. A site with good caching opens almost instantly.

The problem shows up when you make changes. When you edit something, the new version is on the server, but the old copy lives on for a while in other places and keeps being shown until it expires or you clear it manually.

There are generally three layers where the old version can get stuck:

• your browser (on your own computer or phone);
• a cache plugin or service on the server (common on WordPress);
• the CDN, a network that serves the site from multiple locations.

We'll tackle them one at a time, from the simplest.

First suspect: your own browser (hard refresh)

In most cases, the old version is being held by the browser on your own device. You've opened the page many times, so the browser reuses it from memory. Other visitors, arriving for the first time, already see the new version — so it's not a disaster, it's just on your end.

The quick fix is a hard refresh, a reload that ignores the local copy:

• on Windows: Ctrl + F5 (or Ctrl + Shift + R);
• on Mac: Cmd + Shift + R;
• on a phone: fully close the tab and reopen the page.

If you still see the old version, the decisive test: open the site in a private/incognito window, or from another device or on mobile data. If it looks correct there, the problem was just your browser's cache and the site is perfectly fine.

Second suspect: cache on the server (WordPress and others)

If you see the old version even in incognito and from another phone, then the copy is higher up — on the server. Many sites, especially those on WordPress, use a cache plugin (for example WP Rocket, W3 Total Cache, LiteSpeed Cache) or caching from the host.

In this case you have a clear-cache button in the admin panel:

• look in the top bar or the menu for something like "Clear cache" or "Purge cache";
• if it's from the host, it's often in cPanel or the hosting dashboard.

Click clear, wait a minute, then do a hard refresh again. Careful: don't delete other things and don't tick options you don't understand — clearing cache is safe and reversible (it rebuilds itself), but the other settings there are not.

Third suspect: the CDN (Cloudflare and similar)

A CDN is a network that copies your site to many locations around the world so it loads fast anywhere. It's great for speed, but it adds one more place where the old version sits. Cloudflare is the most common.

If you have a CDN, it has to be cleared there too:

• in Cloudflare: the Caching section, then "Purge Everything";
• for a single page, you can use "Purge by URL", which is more precise and safer.

One important detail: some images and files (logo, CSS) have a deliberately long expiry time, precisely for speed. That's why sometimes the text updates immediately but the photo stays old for a few hours. After you clear the CDN and hard refresh, everything should be current. If you're not sure where the panel is, that's a sign it's worth asking whoever built your site before pressing anything at random.

How to avoid the frustration next time

A few simple habits save you a lot of headaches:

• Always check changes in incognito or on another device — that way you see what customers actually see, not the copy in your browser.
• Remember the order: hard refresh, then server cache, then the CDN. In most cases you stop at step one.
• Don't press things at random in panels you don't know — clearing cache is safe, but other buttons there are not.

At MPO Web Studio we build sites where exactly these things are handled from the start: cache configured correctly, so your changes appear quickly and predictably, with no surprises. We work entirely remotely, with transparent pricing, and if you'd like you can first see a pre-built demo at no cost. If you're stuck with an edit that won't show, message us on WhatsApp — often we can tell you in two minutes exactly which button to press.