Publish a Site

Publish Site creates one coordinated live release for eligible pages and global design. Use it only when the connected draft scope is ready; an isolated page change should not automatically become a complete-site release.

Read the pre-publish check before confirming

Open the publishing controls for the exact site and inspect the dialog from top to bottom. The prepared state keeps the confirmation unchecked and Publish disabled, so it documents the boundary without performing a release.

Review the dialog in order

Start with the changed-surface summary. Compare the edit domain with the live domain. Read the Private-page warning. Only after those checks should the required confirmation be selected and the Publish action become available.

Understand the site-wide consequence

A complete-site release synchronizes eligible page drafts with the current global Navbar, Footer, theme colors, fonts, presets, and other connected site design. Private content is not intentionally exposed as a public page, but it still deserves review so release expectations are clear.

Prepare the release

Inventory the pages and global surfaces intended to ship. Check navigation hierarchy, copy, metadata, links, forms, media, workflow state, domains, and representative Desktop, Tablet, and Mobile Views. Resolve page locks and name the release owner.

Verify after a future publication

Open the live domain in a fresh session. Test the homepage, changed pages, navigation and mobile menu, calls to action, forms, Footer links, custom domains, and the most important responsive paths. Record follow-up work as a new draft cycle.

Common mistakes

Publishing the wrong site; ignoring the edit/live domain difference; treating Private pages as ready; forgetting global design; confirming before checking changed surfaces; or assuming the release is complete without testing the live result.

Release checklist

Exact site and live domain. Changed surfaces reviewed. Private warning understood. Required confirmation deliberate. Desktop, Tablet, and Mobile passed. Locks resolved. Release owner named. Post-publish routes and interactions prepared for verification.

Next steps

Return to Content Workflow for ongoing revisions and Private & Published for page-level state. Use page publication when the next change is truly isolated.