Why does my site still show old prices or text after I changed them?

You changed the price on your menu, hit save, and closed the laptop feeling good. The next day a customer calls to say the site still shows the old amount. You reload it on your own phone and — of course — it looks correct to you. Frustrating, but almost always there's a simple, fixable reason.

The usual culprit is called "cache" (temporary memory). To load pages fast, several systems keep a copy of your site and serve that instead of asking for the fresh version every time. When you change something, those copies sometimes lag behind. In this article I'll show you exactly which cache layers exist, why you see something different from your customer, and how to clear them in the right order without breaking anything.

What caching is, briefly, and why it fools you

A "live" site would be rebuilt on every visit: server → page → browser. That's slow. To stay fast, systems save a snapshot of the page and serve it ready-made. That's the cache.

The trouble starts when you edit content: the old snapshot lives on for hours or days, depending on the settings. You often see the new version simply because your browser — the one that made the change — was forced to reload. The customer, who hasn't visited in a week, gets the old copy.

Remember this: it's not one cache but several layers stacked on top of each other. If you clear only one, the others can still serve the old text. That's where the "nothing is changing" feeling comes from.

The cache layers, from your site out to the customer

It's worth knowing them one by one, because each clears differently:

• Your browser cache — the most common cause of the "but it's fine on mine" illusion.
• Plugin cache (on WordPress: WP Rocket, LiteSpeed, W3 Total Cache) — holds whole pre-built pages.
• Server/hosting cache — many hosts have their own layer, independent of the plugin.
• The CDN (Cloudflare, the Vercel network, etc.) — copies of your site spread worldwide so it loads fast everywhere.
• App cache, on modern sites (Next.js and others) — the page must be regenerated or redeployed to reflect new data.
• The WhatsApp/Facebook preview — stores the share title and image separately.

Practical rule: clear from the site outward — server and plugin first, then the CDN, and your own browser last.

First check the obvious: did you actually save and publish?

Before any cache clearing, rule out the boring cause, which is surprisingly often the real one.

• On WordPress and similar platforms, "Save draft" is not the same as "Publish"/"Update". The change exists only for you, logged in.
• If you have two similar products or pages, make sure you edited the exact one that's live, not a copy or an old page still sitting in the menu.
• On sites built from code that "redeploy" (many modern sites, including the ones we deliver), a change in the source only appears live after the deploy runs. If the deploy didn't run or failed, the old text stays no matter how much you reload.

A quick test: open the site in an incognito window or on mobile data, logged out. That shows you what a real customer sees, not your privileged version.

How to clear each layer, in order

Do them one at a time and check after each, in incognito:

• Cache plugin: look for the "Clear cache" / "Purge all" button in the top bar or the plugin settings. It's the most common culprit on WordPress.
• Hosting: in your host's panel look for "Clear cache" / "Purge". If you can't find it, ask support — it takes them a minute.
• CDN (Cloudflare): in the panel, Caching → "Purge Everything".
• Your browser: force a reload with Ctrl+F5 (Windows) or Cmd+Shift+R (Mac). To be safe, test everything in incognito anyway.
• Modern code-based site: trigger a redeploy or page regeneration; at MPO we handle that for you.

Don't randomly clear everything a dozen times. Go in order, otherwise you won't know which layer was the real problem.

Special cases: Google, the WhatsApp thumbnail, and "only some customers"

Three situations that regularly confuse people:

• Google still shows the old price: the search result is a copy Google refreshes when it revisits your site. That's not your cache — it aligns itself once Google recrawls the page. You can request reindexing in Google Search Console, but it still takes time.
• Sharing a link on WhatsApp/Facebook shows the old title or image: the networks store that preview separately. Fix it with the platform's debug tool, or simpler, it clears itself after a while.
• "Only some customers see the old version": that's normal — each has their own browser and local copy, which expire at different times. It settles as their caches expire.

If you've done all of the above and still see the old text in incognito, it's most likely a layer you don't have access to — server or deploy. That's where we step in: we deliver remotely, nationwide, and can check exactly which layer is blocking you. One WhatsApp message and we'll look together.