Resources · 100
URL migration: prepare mappings and test redirects
Change domain or URL structure while preserving useful destinations for old pages and their language editions.
· 3 min
What this guide helps achieve
- Inventory entry points
- Choose relevant destinations
- Test responses and signals
- Check journeys after switching
- Preserve traceability
Quick check
- Can every page redirect to the homepage?
- Can internal links remain old?
- Must every language be checked?
Step-by-step method
- 01
Inventory entry points
Combine sitemap, navigation, published pages and important older links. Include useful images, downloads and campaign links. Classify pages as retained, merged or removed; do not assume the sitemap contains every entry point.
Deliverable: inventory with a decision per URL.
- 02
Choose relevant destinations
Map each old page to content serving the same need. Handle languages separately. For a merger, check that the destination actually covers the subject. Removal without an equivalent needs an explicit response rather than an arbitrary redirect.
Deliverable: source, target, language and rationale.
- 03
Test responses and signals
Check permanent redirects, final destination, status, canonical and hreflang. Look for loops and intermediate steps. Update internal links and sitemap to point directly to new addresses; inspect controllable external citations too.
Deliverable: results by route family.
- 04
Check journeys after switching
Test search, forms, downloads and mobile variants. Inspect errors and unexpected destinations on old URLs. Compare page families separately so an aggregate total does not hide an omitted language.
Deliverable: error monitoring and assigned actions.
- 05
Preserve traceability
Keep the mapping and correction history. Retain redirects according to search-engine guidance and observed use without promising a universal stabilisation time. Document old-domain management and renewal responsibilities.
Deliverable: maintained migration register.
Choose the response for an old URL
Each branch represents a testable editorial decision.
Equivalent exists
Redirect directly to the right page in the right language.
Subjects merged
Check that the target retains the expected information.
No equivalent
Document removal and correct internal links to that page.
Illustrative case: a retained technical page should reach its new equivalent; removed content without a successor should not be sent arbitrarily to the homepage.
Reusable worksheet
Complete with your authorised observations. These fields are a working template, not observed results.
| Field | Information to record |
|---|---|
| Source | Old URL and language |
| Decision | Retention, merger or justified removal |
| Verification | Final target, status, canonical and alternatives |
Distinguish the mechanisms
| Mechanism | Purpose | Check or limitation |
|---|---|---|
| Retained page | Direct equivalent destination | Check content and language |
| Merger | Page actually covering the combined subjects | Avoid an overly general target |
| Removal | Consistent status without an artificial equivalent | Remove outdated internal links |
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Mappings | URLs with a decision and tested destination | Handle missed entry points |
| Chains | URLs with unnecessary steps or loops | Correct to the final destination |
Common pitfalls
- Check content and language
- Avoid an overly general target
- Remove outdated internal links
Frequently asked questions
Can every page redirect to the homepage?
That is not a relevant editorial mapping. Choose a destination meeting the need, or document removal where no equivalent exists.
Can internal links remain old?
Update them to the final destination. Redirects help older links but do not replace coherent internal linking.
Must every language be checked?
Yes. A French target does not automatically replace a Japanese page; preserve actual equivalents and available alternatives.
Official references
References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.






