Publish, versions and redirects
Run the readiness check, publish a page, take a site offline, restore a version and send old URLs to new pages.
Updated November 10, 2026
Who can use this: Publishing needs permission to publish sites. The workspace owner's e-mail address must be verified.
Put a page live, roll back to an earlier version, and keep old links working.
Publish a page
Open the page in the editor and click Publish at the top right.
In the menu, click Publish, Save & publish or Publish changes. The page is saved and checked.
Review the results. The dialog shows a score, and the errors and warnings found in images, links, collections, components and color contrast.
Fix what you can:
Show jumps to the block with the problem.
Fix corrects one issue automatically, where that is possible. Auto-fix corrects all of them.
HTML Report opens the full results in a new tab.
Click Publish. If issues remain and your site's rules allow it, the button says Publish anyway.
Each page is published separately. To take one page down, click Unpublish in the same menu.
Decide what blocks publishing
Open Site Settings, then Advanced, then Quality & Publishing.
Under Publish Gates, set Block publish on error and Block publish on warning. By default errors block publishing and warnings do not.
Under Accessibility Policy, choose Strict (the default), Balanced or Light. Choose Custom to set the severity of each rule yourself.
Take the whole site offline
Open Site Settings, then General.
Under Site status, click Unpublish site.
Visitors see a temporary unavailable page. Your pages keep their published state and come back as soon as you click Publish site.
Restore an earlier version
Open History in the left rail.
Click a version to preview it on the canvas.
Click Restore this version, or Exit to go back.
Restoring replaces your draft. It reaches visitors only when you publish again.
History holds published versions, restored versions, versions you named, and automatic checkpoints. To keep a checkpoint, hover over it and click the pencil to name it. Automatic checkpoints expire after 30 days; the others are kept.
Add a redirect
Open Site Settings, then SEO, then Redirects.
Click Add redirect.
Enter the old path in From and the new path or a full URL in To.
Choose how to match:
Exact match: only that path.
Prefix match: every path that starts with this text. Do not add a
*.Regex match: a regular expression. You can use capture groups in the target.
Choose a code: 301 (permanent), 302 (temporary), 307 or 308.
Leave Preserve query string on to keep URL parameters, then click Save redirect.
When a path matches more than one rule, the exact match wins, then the longest prefix, then the first regex.
To add many at once, click Import CSV. The format is from,to[,status_code][,match_type], with an optional header row.
Fix broken links
The 404 errors tab lists the paths visitors could not reach, with hit counts and referrers. Click Redirect on a row to send that path somewhere else, or hide it with the ignore button.
Limits and good to know
Renaming the path of a published page creates a 301 from the old path automatically. It appears as Auto (slug change).
Redirects run before pages. A manual redirect on the path of a published page sends visitors away from that page, so delete the rule if you want the page back.
Automatic redirects are different: they are removed when you publish a page at their old path.
Redirects you add by hand are not checked for loops or chains. Test them after you save.
Paths that start with
/api,/app,/apps,/cdn,/sanctumor/broadcastingare reserved. A page cannot use them.
Troubleshooting
The Publish button is missing in the dialog. Errors are blocking publishing under your site's rules. Fix them, or change Publish Gates.
Publishing fails with a message about verifying e-mail. The workspace owner needs to confirm their address first. See Create your workspace.
Related
Questions about building on PraismaHub? We're happy to help.
Contact us
