Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix Changes Not Showing on the Live Site in WordPress

Short answer

First check that you clicked Update or Publish and that the page status is Published, not Draft. Then open the exact live URL in a private window, hard refresh your browser, and clear the page cache, host cache and CDN cache in that order. Retest the same URL after each step to find the layer that held the old copy.

Key takeaways

  • A saved draft or autosave does not change the live page until you click Update or Publish.
  • Check the exact live URL in a private window before you clear any cache.
  • Clear caches in order: browser, page cache plugin, host cache, then CDN cache.
  • Cloudflare Development Mode bypasses edge caching for 3 hours while you test changes.
  • After a Cloudflare purge, the next request for a page should return a CF-Cache-Status of MISS.
  • If the change shows while logged in but not while logged out, a shared cache is the likely cause.

Why are my WordPress changes not showing on the live site?

Your edit is usually saved, but an old copy is still being served from a cache layer between WordPress and the visitor.

A cache is a stored copy that lets a later request load faster instead of building the page again. WordPress.org's hosting handbook lists the layers in order: browser cache, CDN, full page cache, static cache, opcode cache, object cache and fragment cache (Performance handbook).

That order matters because each layer can hold a different version. Your browser may hold one copy, your caching plugin another, and your CDN a third. Clearing only one layer leaves the others in place.

Did I actually publish the change?

No, not until you click Update on a published page or Publish on a new page, and see the status change to Published.

Open the page in the editor and look at the status in the Page or Post settings sidebar. A draft, pending or private page is not visible to the public in the same way as a published page. Click Update, wait for the saved notice, then use View Page to open the exact live URL.

WordPress also saves autosaves while you work, but they do not change the live page. WordPress.org's revisions documentation states that autosaves are enabled for all posts and pages but do not overwrite published content (Revisions).

If the editor shows your new text but the live page does not, use Revisions to confirm what was saved. Open the Settings sidebar, select the Page or Post tab, and click the number next to Revisions. The screen shows each saved draft or published update, and you can restore one if needed.

WordPress.org also notes that there is only ever a maximum of 1 autosave per user for any given post. A new autosave overwrites the old one, so an autosave alone never proves that your latest edit went live.

How do I check if the problem is only my browser?

Open the exact live URL in a private window; if the change appears there, your normal browser cache is the cause.

A private window starts without your usual stored files, so it shows what a new visitor sees. Copy the URL from View Page and paste it into the private window. Do not test a preview link or a different domain.

If the private window shows the new version, hard refresh the normal window. On Windows and Linux, press Ctrl + Shift + R or Shift + F5. On a Mac, press Cmd + Shift + R.

If the hard refresh does not help, clear cached images and files for that site in your browser settings. Leave cookies alone at this stage, because clearing them signs you out of sites. Then load the page again in the normal window.

Test on a second browser or phone only after the private-window test.

How do I clear the WordPress page cache?

Use the purge control in the caching plugin that is already active, starting with the single page you changed.

WordPress does not add a persistent full page cache by itself. The hosting handbook notes that a plugin, host or CDN usually supplies it, so look for the control in the plugin you already use. Do not install a second caching plugin just to find a purge button, because two caching plugins can conflict.

PluginWhere to purgeButton to use
WP RocketSettings → WP Rocket, Dashboard tabClear Cache
LiteSpeed CacheLiteSpeed Cache → Toolbox, Purge tabPurge All - LSCache
WP Super CacheSettings → WP Super Cache, Easy tabDelete Cache

WP Rocket clears related pages when you update content. Its documentation states that when you publish new content or update existing content, the cache for that post or page, the homepage and related content will be cleared (How often is the cache cleared?).

LiteSpeed Cache gives you a targeted choice first. Its Toolbox documentation states that Purge All - LSCache purges all cache entries related to the current WordPress installation (Toolbox). Use Purge Front Page if only the front page is stale, and Purge All - LSCache for a wider problem.

WP Super Cache generates static HTML files from your dynamic WordPress pages. Its WordPress.org plugin page states that 99% of visitors will be served static HTML files (WP Super Cache). That is why Delete Cache on the Easy tab matters after an edit.

How do I clear the host or server cache?

Open your hosting control panel, find its cache or performance section, and purge the cache for the page you changed.

Many managed hosts add a server cache on top of any plugin cache. The control may be labelled Purge Cache, Flush Cache or Dynamic Cache. It may sit in the hosting dashboard, in cPanel, or in the WordPress admin bar.

The hosting handbook recommends asking your host about server-side options such as Varnish and NGINX, which usually work faster than plugins and file-based full page caching. A server cache can serve a stored page without starting WordPress at all, so a plugin purge alone may not reach it.

If your host offers a single-page purge, use it first. A full purge forces the server to rebuild every cached page, which can slow the site for a short time. Save the full purge for a site-wide change, such as a theme change or a menu change that appears on many pages.

For background on how caching layers fit together, read our guide on how to speed up WordPress.

How do I purge the Cloudflare cache?

Purge the single URL first in Cloudflare, and use Purge Everything only when many pages are stale.

Cloudflare strongly recommends single-file purging instead of a complete cache purge. Its purge documentation states that purging everything instantly clears all resources from your CDN cache in all Cloudflare data centers (Purge everything).

To purge one page, log in to your Cloudflare dashboard, select the domain, go to Caching, then Configuration, and use Custom Purge with the exact URL. To purge everything, use the same Caching and Configuration screen, select Purge Everything, and confirm the warning window.

After a full purge, the next request for each resource should return a CF-Cache-Status header of MISS. That header means Cloudflare fetched a fresh copy from your origin server. You can see it in your browser developer tools under the Network tab.

If you are still editing, turn on Development Mode instead of purging again and again. Cloudflare's Development Mode documentation states that it temporarily suspends edge caching and Polish features for 3 hours unless you turn it off first (Development Mode).

Development Mode bypasses the cache but does not purge cached files, so turn it off when you finish testing. Our guide to how to set up Cloudflare for WordPress explains the main settings to check before you rely on the CDN cache again.

Why does the change show when I am logged in but not logged out?

Many caching systems skip the page cache for logged-in users, so the editor view is not proof that visitors see the new page.

When you are logged in, WordPress may build the page fresh for you. When you log out, the server or CDN may serve a stored copy instead. That split is a strong clue: if the logged-in view is new and the logged-out view is old, a shared cache is holding the old version.

Test this the same way every time. Log out, or open the exact URL in a private window, and compare the two views side by side. Do not rely on the Preview button, because a preview shows the draft to a logged-in user.

What if I edited the wrong page or the homepage?

Check the URL, the page status and the homepage setting before you clear anything else.

Open Pages in the dashboard and search for the page title. If two pages have similar titles, such as Home and Home 2, you may have edited the copy that is not linked from the menu. Open the live page, copy its URL, and match it to the page you edited.

Next, check Settings → Reading. Under Your homepage displays, WordPress lets you show your latest posts or a static page. If you chose A static page, the Homepage dropdown picks the page at your main address.

Also check the menu and any page builder template assigned to the page. A menu link may point to an old URL, a custom link, or a different page with the same name. Fix the link or the assignment, then purge the page cache once more.

How do I know the fix worked?

Load the exact live URL in a private window, confirm the new text or image is there, and repeat the check after 2 minutes.

Use this short checklist after each purge step, not only at the end:

  1. Open the exact live URL in a private window.
  2. Confirm the changed text, image or link is visible.
  3. Hard refresh once with Ctrl + Shift + R on Windows and Linux, or Cmd + Shift + R on a Mac.
  4. Check the same URL on a second browser or phone if the first check is unclear.

If the change appears in the private window but not in your normal window, the site is fixed and only your browser needs its stored files cleared. If it appears nowhere, the next cache layer is still serving the old copy.

For Cloudflare, check the CF-Cache-Status header after a purge. A value of MISS on the first load after the purge means Cloudflare fetched a fresh copy. A later load may show HIT, which is normal once the new copy is stored again.

When should I contact my host?

Contact your host when the change is published, every cache you control is purged, and logged-out visitors still see the old page after 30 minutes.

Before you contact support, gather 3 facts: the exact live URL, the time you clicked Update or Publish, and which caches you already purged. Support can then check server logs and any cache layer you cannot see, such as a reverse proxy or a host-level CDN.

Also contact your host if you cannot find a purge control or if the purge button returns an error. A page that keeps reverting may point to a server cache with a long lifetime or a second CDN.

Ask support to confirm whether the site uses Varnish, NGINX caching, Redis, or a host CDN. The hosting handbook lists those as common server-side layers, and each one needs its own purge step. A plugin purge cannot clear a layer that sits in front of WordPress.

What mistakes should you avoid?

Do not edit the same page again and again while an old cache is still being served.

Repeated edits create new revisions without fixing the stored copy, and they make it harder to tell which version is live. WordPress.org's revisions documentation notes that the default setting stores every revision, so repeated saves add to that history without changing what visitors see (Revisions).

Avoid these common errors:

  • Clearing only the browser cache when a plugin, host or CDN cache holds the old page.
  • Purging everything for a one-page edit, which forces the whole site to rebuild.
  • Testing a preview link or a URL with a query string instead of the exact live URL.
  • Installing a second caching plugin to find a purge button.
  • Leaving Cloudflare Development Mode on after testing, which keeps edge caching off for 3 hours.

Make a backup before you change cache settings or disable a plugin. Our guide on how to back up WordPress shows the steps. A backup does not fix a stale cache, but it protects you if a settings change causes a wider problem.

If you use a caching plugin, learn its own purge controls before the next edit. Our guide to WP Rocket settings explains the main options.

Our guide to LiteSpeed Cache settings covers that plugin in the same way.

Our guide to Cloudflare cache rules for WordPress covers CDN caching in more detail.

Frequently asked questions

How long does it take for WordPress changes to show on the live site?

A published change should show at once once every cache holding the old copy is cleared. If it still does not show after 30 minutes, a server cache or CDN cache is likely still serving the old page. Purge each layer in order and retest the exact live URL in a private window after each step.

Why can I see my edit in the WordPress editor but not on the live page?

The editor shows your saved draft or published content, while visitors may receive a stored copy from a browser, plugin, host or CDN cache. Autosaves also do not change the live page. Click Update, then test the exact live URL while logged out or in a private window.

Does clearing the cache delete my posts or pages?

No. Clearing a cache deletes stored copies of pages and files only. Your posts, pages, media and settings stay in the database and in your uploads folder. The next visit rebuilds a fresh cached copy from the live content.

Should I purge everything in Cloudflare for one changed page?

No, purge the single URL first. A full purge clears the whole zone and forces every page to be fetched fresh from your origin server, which can add load. Use Purge Everything only when many pages are stale or you cannot tell which URLs changed.

What should I do if the change shows on desktop but not on my phone?

Check the same live URL on the phone in a private browser tab, and hard refresh if the browser allows it. Mobile browsers keep their own stored files, and some sites serve a separate mobile cache. If the phone still shows the old page, purge the page cache and CDN cache again.

Sources

  1. Revisions WordPress.org
  2. Performance Make WordPress Hosting
  3. Purge everything Cloudflare Docs
  4. Development Mode Cloudflare Docs
  5. How often is the cache cleared? WP Rocket
  6. Toolbox LiteSpeed Documentation
  7. WP Super Cache WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test