Collect URLs before changing the menus
Start with the existing sitemap, a crawl, the content inventory and any available analytics. Search Console and traffic reports, where you have access, can help identify important landing pages. The main navigation alone misses old campaigns, guides and addresses still used by external links.
Preserve the original URL accurately and record the page’s purpose. A maintenance-interval guide does not become equivalent to a contact page just because the old guide is being removed. Either a new resource answers that question or the content decision needs reconsidering. The map is an editorial document as well as a technical one.
Match the purpose rather than the nearest convenient page
Keep established addresses when there is no useful reason to change them. A permanent server-side redirect can handle an actual permanent move. It should lead to the intended final destination rather than a series of previous moves. Canonical is a different signal and does not move a visitor to the right page.
If one old article becomes two new resources, select the destination that best answers the original main question, or retain a genuinely useful overview. Do not match an old Swedish page to a new English one merely because the topic names look similar. Language and visitor intent belong in the decision.
| Old address | Decision | Reason |
|---|---|---|
| /services/maintenance/ | Keep where practical | The same service remains |
| /articles/old-guide/ | Move to an updated equivalent | The same main question is answered |
| /expired-campaign/ | Assess whether a replacement exists | No automatic homepage redirect |
| /old-contact/ | Move to the actual contact page | A direct functional equivalent |
Test the complete journey
Test old URLs against the environment that actually applies the redirects. Record the initial status, any chain, the final address and its status. The final page also needs the correct canonical, language and indexing decision. A rule written in a file is not proof that the hosting platform applies it.
Update internal links and the sitemap to use the final addresses. Visitors should not rely on a redirect for each internal click. Have someone read the destination too: an automated check may report HTTP 200 even when the content no longer helps someone following the original link.
- Check trailing-slash variants against your URL policy.
- Avoid loops and unnecessary chains.
- Test each language separately.
- Keep the map with the delivery version.
Assign follow-up before launch
After a separately authorized launch, someone needs to review unexpected 404 responses, remaining old paths and relevant indexing reports. A correct map cannot guarantee unchanged rankings. If the project is still local, that follow-up is a plan rather than measured search performance. Assign the work before the move so gaps do not remain unresolved between editorial and development teams.