You change a sentence on your website, click Update, and open the page. The old sentence is still there. You try again, then wonder whether WordPress saved anything at all.
Before you make another edit, follow one identifiable change from the saved page to the public page. An outdated copy can sit in several places, and clearing the wrong cache won’t tell you where the disagreement started.
Check the saved version first
Choose something specific from the edit you already made: a heading, a sentence, or an image. Reopen the editor and confirm that change is still saved. Check the page’s address and publication state, too. A preview of a draft, an edit on a staging site, and an update to the public page are three different things.
If the saved change has disappeared, investigate the save before touching caches. If it’s present, make sure that editor controls the section you’re looking at. A homepage may use a template, a reusable block, or a page builder section instead of the page content you just edited. The same wording can exist in more than one place.
My first question would be, “Can we identify the exact saved change and the exact public URL where it belongs?” That gives the next check something concrete to prove.
Compare what different visitors receive
Open the exact public URL in a private window without an administrator login. Then compare it with your normal browser. If possible, have someone else check that same URL and sentence. Ask what they actually see; “looks fine” doesn’t distinguish the versions.
A private window helps separate some browser state, but it can still receive an old copy from the website or a content delivery network. A phone on a different connection adds another observation. Neither check, by itself, identifies the faulty component.
MDN’s HTTP caching guide distinguishes private caches, such as a browser’s cache, from shared caches used to serve multiple visitors. Managed caches can also have their own clearing controls. That’s why reloading your browser and purging a host’s page cache aren’t interchangeable actions.
- If only your normal browser shows the old version, investigate its stored state first.
- If logged-in visitors see the edit but ordinary visitors don’t, ask whether the site treats those requests differently, including its caching rules.
- If everyone sees the old version, return to the publishing target and shared delivery path.
These are directions for investigation, not verdicts. Personalization, language settings, and different URLs can also produce different pages.
Separate old content from old styling
Sometimes the words have changed but the layout hasn’t. That points to a different question: is the browser receiving the updated stylesheet, script, or image?
For example, replacing an image while keeping its URL can leave an older copy visible somewhere in the delivery path. A page builder may also need its documented process for regenerating generated styles. Ask your maintainer to compare the actual resource URLs and responses. Repeatedly changing the page text won’t repair a stale stylesheet.
Don’t rename files or install another caching plugin just to see what happens. First establish which resource is different and which supported control manages it.
Clear the smallest relevant cache, then repeat the check
Use the documented page-specific purge when your host, caching plugin, or delivery provider supports it. Record what you cleared and when, then check the same public URL and identifiable edit again. Broaden the purge only when the result or the provider’s instructions justify it.
If the problem keeps returning, preserve a small evidence record: saved text, URL, time, login state, browser, and the result before and after the purge. Your maintainer can use that to investigate invalidation rules instead of making cache clearing a permanent chore. Include a public-view check in your WordPress maintenance routine after changes that affect delivery.
You’re finished when the saved change appears where an ordinary visitor should see it, and you understand the step that made it appear. If it still doesn’t, send the comparison record to the person responsible for the publishing or caching layer. That is a much better starting point than another round of edits.
TechDex Presents…
Flashback to the ’90s
Get 2026 services at 1990s prices.
For a limited time, I’m rolling prices back on six focused small-business services. Choose one service for $800, or choose two for $1,200. Nothing is purchased here—I’ll review your request and confirm the scope with you first.
For related website work, explore this Rewind service:
The campaign form lets you choose one or two services and request a follow-up. It isn’t a checkout, and you won’t be billed when you submit it.