Website settings and domains
Change page, post and product URLs
Open Settings > Permalinks to choose the public URL presets for pages, posts and products. Existing websites keep their current presets until someone confirms a change.
Preview a change
- Select the required preset for each content type.
- Select Preview URL changes.
- Review the number of pages, posts and products affected, the redirects Nune will create, redirects already protecting an address, and any warnings.
- Open Review affected URLs to compare current and proposed addresses. Download the CSV when you need the complete report or an approval record.
- If Nune finds redirect conflicts or chains, open the conflict list and confirm the stated replacements or disabled redirects.
- Select Apply permalinks and redirects.
The preview does not publish or change anything. Applying the change updates the permalink settings and their 301 redirects in one transaction. Historical paths point directly to the newest canonical address rather than through avoidable redirect chains.
Redirect conflicts
An old URL may already have a manually created redirect. The audit shows its current destination before asking permission to replace it. A proposed canonical URL may also have an active redirect; Nune disables that redirect so the real content address remains authoritative.
All generated redirects remain visible under Settings > SEO > Redirects, where ordinary individual redirects are managed.
Change history and rollback
The Permalinks page records the previous and new presets, affected URL counts, redirect changes, date and administrator. Use Roll back on the change matching the current settings to restore its previous presets and redirects.
Rollback is deliberately guarded. If one of the redirects has been edited since the permalink change, Nune stops without applying a partial rollback. Review that redirect and decide whether to restore it manually before trying again.
Slug safety
Pages, posts and products use globally unique slugs. Nune also reserves system paths such as /admin, /checkout and /shop. Resolve any duplicate legacy slugs reported on the Permalinks page before moving a content type to root-level URLs.