Admin path: Site → Path redirects (usually /admin/settings/redirects).
Use this to send an old public URL on with a permanent redirect (308) to a new path or an external https:// URL. It fits a redesign, an old campaign link, or a move from another system where you still need the old URL.
Who can change it? Same as site-wide SEO: owners and editors can write, by default.
Three kinds of redirect. Keep them apart
| Kind | Where | What it is for |
|---|---|---|
| Public path redirects (this page) | Site settings → Path redirects | Any old path → a new path or an external URL |
| Automatic slug redirects | The system | After you change the URL segment of a page, news article, product, and so on, the old path goes to the new one |
| Docs redirects | Docs → redirects | Only old paths under the docs prefix |
Add one
- Fill in From path. No locale prefix and no query string. Example:
/old-about(not/en/old-about). - Fill in To path / URL: an on-site path such as
/about, or a fullhttps://…URL. - After you save, a visit to the from path 308s to the target. Browsers and search engines treat that as permanent.
The button is Add redirect. Success says “Redirect created”. Delete asks you to confirm.
How to check
- Open the from path in a private window. It should jump to the target at once.
- Do not add a locale prefix or a
?query to the from path. - If the target is on this site, that page must be published.
Limits. Read these first
- A path that already has published content cannot be a from path. If
/aboutis published, you cannot also say “redirect away from/about”. - If the from path collides with an automatic slug redirect, save is refused.
- Later, if you try to publish content on a path that is already a redirect source, save is blocked and you are asked to delete or change the redirect first. The rule is not removed for you.
- A redirect is one hop. A→B→C is not chained for you.