Slugs, canonical URLs, and redirects

Documentation / Search visibility and sharing

A slug is a page's own path value. Its complete public address can also include a collection prefix, tree ancestors, and a language prefix. The canonical URL identifies the preferred public address in page metadata.

Edit the right address

Use the page URL field for its slug and the collection's Base path for the shared prefix. In a tree, root-file ancestry contributes to the computed path. Moving a branch can therefore change descendant addresses without changing each descendant's own slug.

The engine builds canonical URLs from the primary site domain and current public path, removing trailing slashes except at the homepage. The verified page SEO tab does not expose a custom canonical-address override.

Redirect changed addresses

Site settings provide redirect rules using the format /old-path -> /new-path 301. The supported codes are 301 and 302, with 301 used when the code is omitted. Add explicit rules for established addresses rather than assuming a slug change creates them automatically.

On eligible public production requests to the primary hostname, the engine also consolidates trailing slashes and the primary domain's www variant with 308 redirects. That normalization does not cover every alias, staging hostname, preview, or hosting-level redirect.

Page-picker links use stable page references and can resolve changed localized destinations. External links and bookmarks still need redirect planning.

Validate the complete chain

Open the old URL and confirm the status and final destination. Check query parameters, the new canonical tag, and links from listings and navigation. Avoid unnecessary redirect chains.

See Collections and content trees, Languages and translations, and Site administration and domains.