Save, update, preview, and publish

Page Builder dialogs, the WordPress post, and the public page are three different checkpoints. Use them in order to avoid believing that an unsaved editor change is already live.

Save a component

The save button inside a component dialog returns the edited values to the builder canvas. Repeat this for every open dialog before saving the post.

Save the WordPress post

The available action depends on status and permissions:

• Save Draft preserves an unpublished draft.
• Publish makes an eligible page public.
• Update saves changes to an existing page.
• Submit for Review sends the draft into the editorial workflow without publishing it.

Wait for WordPress to confirm the save before closing the tab or switching editor modes.

Preview

Preview renders the current post for review. Use it after a coherent change and check:

1. content and heading order;
2. links, forms, menus, tabs, and other interactions;
3. wide and narrow viewports;
4. image crop and background readability;
5. visibility rules.

The preview should reflect the current Page Builder row and column spacing without an extra save. After Save Draft, Publish, or Update, one successful post save is enough to refresh the page-specific styles used by the public URL.

Gutenberg blocks and legacy shortcodes can coexist in the same page. Saving combines their page-specific styles into one stylesheet; disabling the legacy Page Builder interface does not disable shortcode spacing. Preview uses the content supplied by WordPress for that preview and does not replace the saved page's styles. Existing page-level custom CSS keeps its configured append or replacement behavior.

Preview can reflect a draft or a logged-in session. It is not the final public verification.

Verify the public result

After publishing or updating:

1. open the public permalink in a private browser window;
2. reload it after the save completes;
3. confirm that the latest content is visible;
4. test the important action as a signed-out visitor.

If the editor and public page differ, use Troubleshoot the published page.

Create recoverable milestones

Save after completing a meaningful section, not after every keystroke and not only at the end of a large rebuild. Builder Undo and Redo cover the current editing session; WordPress revisions cover saved milestones where revisions are enabled.