Protect organic visibility by inventorying current URLs and signals, deciding the destination of every indexable page, implementing direct server-side redirects, preserving valuable content, validating canonicals and internal links, and monitoring the migration after launch.
Key takeaways
- Crawl and export before the old site changes.
- Every indexable URL needs a deliberate migration decision.
- Redirect directly to the closest equivalent page.
- Validate production behavior and monitor beyond launch day.
Who this is for: SEO, marketing and engineering teams preparing a redesign, CMS migration or URL change.
Before design and development
SEO migration begins while the sitemap is being decided, not after development is complete.
- Crawl all indexable URLs
- Export Search Console landing pages and queries
- Export analytics entrances and conversions
- Identify linked and high-value pages
- Capture titles, descriptions, canonicals and structured data
- Record status codes, robots directives and sitemap membership
Map every URL
Classify each page as keep, improve, consolidate or retire. Redirect to the closest true replacement rather than the homepage.
| Old URL decision | Action | Validation |
|---|---|---|
| Keep | Preserve URL and intent | Content and canonical remain appropriate |
| Improve | Preserve URL; update content | Metadata, links and intent verified |
| Consolidate | 301 to strongest equivalent | Old content represented on destination |
| Retire | 404/410 or relevant replacement | No misleading soft-404 behavior |
Technical implementation
Use direct, permanent server-side redirects where URLs change. Remove redirect chains and update internal links to point directly at final URLs.
- Self-referencing canonical on new pages
- Correct robots directives
- Updated navigation and contextual links
- Valid structured data
- Current XML sitemap
- No production references to staging domains
/old-service -> 301 -> /services/new-service
/old-guide -> 301 -> /blog/consolidated-guide
/dead-offer -> 410 (no valid replacement)Launch validation
Run an automated crawl and manual checks immediately after release.
- 1Verify priority old URLs redirect once to the intended destination.
- 2Check new pages return the correct status and canonical.
- 3Test robots.txt, sitemap and noindex directives.
- 4Validate analytics, forms and conversion events.
- 5Inspect representative URLs in Search Console.
- 6Monitor 404s, coverage, impressions and conversions over subsequent weeks.
Common migration failures
Most losses come from avoidable execution gaps rather than the idea of redesign itself.
- Redirecting everything to the homepage
- Changing URLs without business value
- Launching with missing content
- Blocking production crawling
- Leaving canonicals on the old or staging domain
- Removing internal links to important pages
- Changing platform, content and domain simultaneously without control
How to use this guide with your team
Technical search work should be translated into user and business consequences. A redirect is not merely a status code; it determines whether a customer or search engine reaches the correct replacement for an old resource.
Create a shared validation sheet that content, SEO and engineering teams can understand. Mark the expected behavior, actual result, owner and resolution instead of exchanging screenshots without decisions.
Monitor after release because crawling, indexing and user behavior continue beyond launch day. A technically correct configuration still needs production evidence.
Practical next steps
Use the following actions as a short working session. Record decisions, owners and unresolved questions so the article becomes an implementation aid rather than passive reading.
- 1Explain every technical task in business terms.
- 2Test representative URLs and templates.
- 3Record expected and actual behavior.
- 4Assign resolution ownership before launch.
- 5Monitor search and conversion evidence afterward.
Frequently asked questions
How long should redirects remain?
Keep them for as long as users and external links may use the old URLs; long-term redirects are often appropriate for permanent URL changes.
Should the sitemap include old URLs?
After migration, the main sitemap should contain current canonical URLs, not redirected legacy URLs.
Sources and further reading
Last reviewed: September 1, 2026
