Drafts and Publishing
Save drafts, preview changes, and publish pages.
How drafts work
Website Pages saves your work as a draft. Use Save Draft to save manually, and drafts are auto‑saved while you edit.
Preview before publishing
- Preview Page opens a preview of the current draft.
- Published preview actions open a fresh published preview when you need to verify the live version immediately after publishing.
- Internal links clicked inside the preview stay in the same draft or published preview context, which helps you test navigation without leaving the builder.
- Use preview to check layout, links, and mobile spacing before you publish.
Publish a page
1
Open a page in the editor
Go to Website Pages and select a page.
2
Save Draft
Click Save Draft to store your changes.
3
Preview Page
Use Preview Page to verify before publishing.
4
Publish Page
Click Publish Page to make changes live.
Unpublish or discard drafts
- Unpublish removes a page from the live site and clears the public cached version, including funnel-step paths when the page is part of a funnel.
- In Manage Pages, use a page menu's Activate or Inactivate action when you only need to change whether a page is live.
- Inactivating a page also turns off sitemap, robots, and LLMS discovery inclusion for that page. Activating it turns those discovery controls back on.
- The homepage must stay active. Set another page as the homepage before making the current homepage inactive.
- Discard Draft reverts to the last published version.
- In Manage Pages, inactive pages are dimmed with a hidden-page icon and sorted below active pages inside the same folder.
Verify after publishing
- Check key pages (Home, Contact, Booking)
- Fresh published previews are built from the newly published page version, so use them when you need to confirm visitors will see the latest copy, widgets, and page settings.
- Publishing also refreshes the public page path, so using Publish Page again can help when a live page appears stale after recent edits.
- Dashboard publishes and approved Website API Key page publishes use the same public refresh path, so repeated publishes can act as a reliable refresh signal for stale public views.
- If you publish header, footer, menu, or popup changes, spot-check more than one page because shared layout and display changes appear across the public site.
- Test on mobile
- Use a private window to avoid cached content
- Recheck SEO output with Page SEO Health and mobile layout with Responsive Design.
Related Help Docs
Updated Jun 16, 2026
Was this helpful?