After you change an About page from /about to /about-us, the old /about may not open. First decide which kind of redirect you need.
The system often redirects for you
After you change the URL slug of a page, article, or product and save, the system usually sends the old path to the new path on its own. Open the old path in a private window and see whether it jumps to the new page.
If the old path is an immediate 404, with no jump, use the manual redirect below.
Do not put the three kinds of redirect on the wrong page
| Situation | Where |
|---|---|
| Any old path (a redesign, an old printed flyer, a move from another system) | Public path redirects |
| Only one document path changed | Redirect a document |
| You only changed the slug and are waiting for the automatic redirect | Do not add a manual row as well (it can conflict with the automatic rule, and then save fails) |
On public path redirects, put /old-about in the source (no locale prefix, no ? query). Put /about-us or a full https://… in the target. The button is Add redirect.
Other reasons for a public 404
- The content is still a draft, or it is not published yet. See Published, but visitors still see the old site.
- The slug is wrong, the letter case is wrong, or there is an extra slash.
- A module already uses that path (the shop, sign-in, the news prefix, and similar). Do not use those as a page slug.
- If a published page already lives on the source path, you cannot also use that path as a redirect source.
How to check
- Open the old URL in a private window. It should jump to the new page with a 308 (or the system’s automatic redirect).
- The new URL itself is published and opens.
- If the menu, the announcement bar, or a shortcut button still has the old path typed in, change those too. See Edit the menu and Conversion tools overview.