Going Live

Click Go Live in the top-right of the Editor when you are ready to publish. A confirmation screen shows exactly what changed since your last publish.

Reviewing changes

The confirmation screen lists every section you have changed, worked out by comparing your draft against what is currently live — so it is what actually differs, not everything you happened to open.

Read it before confirming. It is the last point at which a change is still private.

What happens next

Your website updates immediately — usually within 1–2 seconds. Your draft is cleared, because it has become the live version, and a new entry appears in version history.

Nothing else about your site changes. Publishing content does not touch your domain, your team, your billing or which modules are switched on.

Version history

Your last ten published versions are kept. Publishing an eleventh drops the oldest.

That is worth knowing if you are about to make a run of small publishes to fix something: ten quick corrections will push out the version you might have wanted to go back to. If you are experimenting, stage the changes as one draft and publish once.

If Go Live is greyed out

Two things disable it, and they mean opposite things.

You have no unpublished changes. Your live site already matches your draft. Nothing to do.

Someone else edited the same content while you had it open. The editor stops you publishing rather than letting one version quietly overwrite the other. Reload to pick up their version, reapply your change, and the button comes back. See Saving and Drafts for what happens in that situation.

If the button is grey and you are certain you changed something, this second case is usually why.

If you publish something by mistake

Restore an earlier version from version history. Restoring does not change your live site on its own — it loads that older content back into your draft, replacing whatever draft you had. Your visitors keep seeing the mistake until you click Go Live again.

That is deliberate: it gives you a chance to look at the restored content before it goes back out. But it does mean a restore is two steps, not one, and the fix is not live until you publish it.