Why changes not showing — and how to fix it

How to fix changes that aren't showing on the live site

You edited the your business homepage hero — changed the call-to-action copy from "Shop Now" to "Order Online", clicked Save, saw the green banner, then opened the public site. The old text is still there. This guide walks every reason that can happen and the fastest way to confirm which one it is.

Work through the seven checks below in order. Most cases resolve at check 1, 2, or 3. If you reach check 7 you have encountered a save-handler quirk; the fix is a deliberate clean re-save.

What is this for?

This guide is for SGEN admins who completed a save action — on a page, post, global setting, Custom CSS snippet, Custom Code, or an SG-Builder block — and the change has not appeared on the public-facing URL. It covers the full pipeline between "you click Save" and "a visitor sees the result", flags every point where that pipeline can stall, and gives you one concrete action to confirm or rule out each stage.

The guide assumes you completed the save and the admin showed a success banner. If the admin showed a red error banner when you clicked Save, start with the error text — that is a different path.

There are seven possible causes, listed from most to least common. You will rarely need to go past check 3. When you do, each subsequent check takes under two minutes.

Good use cases

Example 1: Homepage CTA text not going live. your business updated the hero CTA from "Shop Now" to "Order Online" inside SG-Builder, clicked the in-builder Save button, and then checked the public site. The old copy was still there. Check 4 identified the surface: SG-Builder has two separate actions — the in-builder Save (records the change in the builder session) and the Publish button (regenerates the public page). The in-builder Save had been clicked but Publish had not. Clicking Publish pushed the change live within 30 seconds.