Changes not showing after you publish

You edited a page, clicked publish, and the live site still shows the old version. This is one of the most common support questions, and it's almost never a lost edit — it's a caching or publish-state issue with a predictable fix.

#Symptoms

• You edited text, an image, or a section, but the live page still shows the old content.
• Changes appear for you but not for a client, customer, or coworker.
• Changes appear on your phone but not your laptop (or vice versa).
• The page looks right in the editor's preview but wrong on the actual published URL.
• Global or reusable sections you updated in one place didn't update everywhere they're used.

#Likely causes

1. You edited a draft but never published it. Saving inside the builder stores your changes as a draft version; the live page keeps showing the last published version until you explicitly publish.
2. Your own browser cached the old page. Browsers store copies of pages, images, and scripts locally so repeat visits load faster — which means you can be looking at a stale copy of your own site.
3. A CDN is caching the page at the edge. Pages are also cached on content-delivery network servers, which are geographically distributed copies of your site that need their own refresh separate from any single visitor's browser.
4. You're looking at a preview link, not the live URL. Preview links can point to a specific saved version and won't reflect later publishes.
5. A global or saved section wasn't re-synced. Reusable sections update everywhere they're used once saved, but each page still needs to be republished (or re-load) to reflect it depending on how caching is layered on top.
6. DNS or domain caching (rare) — if you recently changed which page a domain points to, see domain and SSL problems instead; that's a different layer.

#Step-by-step fixes (most common first)

#1. Confirm you actually published

Open the page in the builder and check the publish status. If it says Draft or shows unsaved/unpublished changes, click Publish (not just Save). Saving and publishing are two different actions — saving protects your work-in-progress, publishing pushes it live.

#2. Hard refresh your browser

A normal refresh (F5) often reloads from cache. Force a real reload:

• Windows/Linux: Ctrl + Shift + R
• Mac: Cmd + Shift + R

If that doesn't work, open the page in a private/incognito window, which starts with no cache at all. If it looks correct there, the issue is confirmed to be your local browser cache — clear your browsing cache and cookies for that site and reload normally.

#3. Test on a different device or network

If it looks wrong for a client but right for you, have them hard-refresh too, or check the page yourself on your phone using cellular data (not your office Wi-Fi). This rules out anything cached on your specific device or local network.

#4. Wait a few minutes for edge/CDN cache to clear

Even after a clean publish, distributed cache copies of the page can take a short time to refresh. If a hard refresh in a private window still shows the old version, wait 5–10 minutes and try again before assuming something is broken.

#5. Re-check global or saved sections

If you updated a header, footer, or other section that's reused across multiple pages, confirm the section itself was saved (not just the one page you were editing), then republish the specific pages that use it if they don't pick up the change automatically.

#6. Make sure you're testing the live URL

Double-check the address bar. Preview links, staging links, or bookmarked builder URLs can differ from the actual published domain path. Always do your final check on the real public URL a visitor would use.

#7. Rule out DNS-level staleness

If you recently repointed a domain to a different funnel or website, or moved a domain between accounts, that's a DNS change, not a page-publish change, and can take longer to resolve. See domain and SSL problems.

#How to verify it's fixed

1. Open the live URL in a private/incognito window.
2. Confirm the change (text, image, section) matches what you published.
3. Reload once more with a hard refresh to be sure it's stable, not a one-time fluke.
4. Ask one other person (or check on a second device on a different network) to confirm they see the same thing.

Tip: Keep a simple habit — after every publish, immediately open the live URL in a private window before telling a client it's done. It takes ten seconds and avoids most "it's still showing the old version" messages.

#When to contact support

Contact support if you've confirmed the page shows Published (not Draft), you've hard-refreshed in a private window, waited at least 15 minutes, and checked from a second network — and the live page still doesn't match what's in the builder. Include:

• The exact page or funnel step URL.
• What you changed and when you published it (approximate time).
• A screenshot of the builder showing the change and publish status.
• A screenshot of what the live URL currently shows.
• Whether the issue affects everyone or only specific visitors.

#Related articles

• Fix domain and SSL connection problems
• Broken links, 404s, and redirects after renaming pages
• Layout looks wrong on mobile or a specific browser

#Frequently asked questions

#Why does incognito mode fix so many of these issues?

A private/incognito window starts with an empty cache and no stored cookies, so it always requests a fresh copy of the page. If the problem disappears there, the cause was something cached on your regular browser, not the published content itself.

#I published five minutes ago — how long should I really wait?

Most changes are visible within a minute or two after a proper publish and a hard refresh. If it's been over 15 minutes and a private window still shows the old version, treat that as a real issue rather than normal caching delay.

#Does clearing my cache affect what other visitors see?

No. Browser cache is local to your own device. If a change isn't showing for a customer, they need to refresh or clear their own cache — you can't do it for them remotely, but a proper publish combined with normal cache expiration will resolve it for them within a short window on its own.

#Why did my global header change on one page but not another?

Sections shared across pages sync their content, but each page that displays them may still need to be reloaded or republished to reflect the update, especially if that page hasn't been opened or saved since the section changed.