Migration field notes · Updated 10 November 2026

How to create a website migration redirect map

A redirect map pairs each old URL with its intended new destination. Create it before launch, review content relevance, record pages with no replacement, and test the implemented redirects afterwards.

1. Build an inventory worth preserving

Combine a crawl and sitemap with URLs found in analytics, Search Console and backlink records. A sitemap alone can miss old posts, files and pages that still receive visits. Deduplicate exact URLs while keeping meaningful distinctions such as path case, trailing slashes and query strings.

2. Use final production destinations

The new inventory should contain URLs intended to return useful content on the production site. Staging domains are useful for review but should not accidentally become production redirect targets. Optional page titles help narrow candidates when paths change.

3. Match meaning, then record the decision

For each old page, inspect the candidate destination. An exact slug can still hide changed content. If two products have similar names, verify the product itself. Mark a row approved only when the destination is suitable.

If a page has no relevant replacement, record an exclusion and explain it. Redirecting unrelated pages to the homepage can be treated as a soft 404. A genuine 404 or 410 may be appropriate for removed content.

4. Check the map’s structure

Each source should have one clear destination. Remove self redirects, conflicting duplicates, loops and unnecessary chains. Keep hostnames explicit when several domains are involved.

5. Give the developer a complete handoff

Supply the map, recorded exclusions, domain scope and implementation notes. CSV is an interchange format, not an installed redirect rule. Your developer must translate it into your hosting platform’s supported configuration.

6. Test after deployment

Check actual responses from old URLs, the final destination, permanent redirect status where appropriate, canonical tags, indexability and internal links. Update sitemaps and monitor the migration in Search Console. A local map checker cannot perform these live checks.

Example

old_url,new_url
https://old.example.com/blog/tea,https://new.example.com/guides/tea

These are illustrative URLs. Keep a discontinued sale page out of the map if no relevant replacement exists; record why it was excluded.

References and next steps

Google Search Central: site moves with URL changes. Use the free redirect-map template and structural checker, or get the offline workbench to keep the review record together.