Site Migrations and Canonicalization: Managing URLs and Preserving SEO Value
Two related problems sit at the heart of URL management. Canonicalization is choosing the single authoritative URL when the same content is reachable at several addresses. Site migrations are large-scale changes — to structure, domain, or platform — that alter many URLs at once. Both decide whether ranking signals stay consolidated or leak away. A botched migration can erase organic traffic overnight; a solid canonical strategy quietly prevents duplicate-content dilution every day.
Canonicalization: solving duplicate content
A canonical URL is the version you want search engines to index and rank when near-identical content exists at multiple URLs. Duplicates arise constantly:
- HTTP vs. HTTPS, and WWW vs. non-WWW
- URLs with tracking parameters (
example.com/page?source=email) - Printer-friendly variants
- Content syndicated to other sites
The primary control is the rel="canonical" tag in the page <head>:
<link rel="canonical" href="https://example.com/page" />
Getting canonicals right consolidates link signals into one URL, prevents keyword cannibalization between competing pages, lets you syndicate content while keeping credit on the original, and improves crawl efficiency by pointing engines at the pages that matter.
Four rules keep it reliable:
- Use absolute URLs, not relative ones.
- Point only at genuinely duplicate or highly similar content.
- Self-reference — a page’s canonical should normally point to itself.
- Don’t mix signals — avoid one canonical in the sitemap and a different one in the HTML.
Site migrations: a framework for change
A migration is any change substantial enough to affect search visibility — one of the riskiest activities in SEO.
| Migration type | Description |
|---|---|
| Protocol change | HTTP to HTTPS. |
| Domain change | old-brand.com to new-brand.com. |
| Structure change | Moving between subdomains and subfolders (e.g. blog.example.com → example.com/blog). |
| Platform / CMS change | Replatforming (e.g. Drupal to WordPress), which usually changes URLs. |
| Redesign | Major changes to design, content, or structure even if URLs stay the same. |
Done without planning, any of these can cause severe traffic and ranking loss, leaked link equity from broken redirects, 404 spikes, and duplicate-content or indexing problems.
The three-phase checklist
Phase 1 — Pre-migration (plan).
1. Crawl the existing site (Screaming Frog, Sitebulb) to inventory every URL, title, meta, and header. This is your baseline.
2. Benchmark performance — rankings for top keywords, organic traffic, and conversions.
3. Build the 301 redirect map — the single most critical deliverable: every old URL mapped to its best new URL.
4. QA the new site on staging — check for broken links, wrong canonicals, and stray noindex tags.
5. Update internal links to point at the new structure, not the old.
Phase 2 — Launch.
1. Pick a low-traffic window to minimize disruption.
2. Deploy the 301 redirects from the map.
3. Submit new XML sitemaps to Google Search Console and Bing Webmaster Tools.
4. Verify robots.txt on the new site isn’t blocking important resources.
5. Use the Change of Address tool in Search Console for a domain change.
Phase 3 — Post-migration (monitor).
1. Re-crawl old and new URLs — confirm every old URL redirects and the new site is 404-free.
2. Watch Search Console — the Pages (indexing) and redirect reports for error spikes.
3. Track rankings and traffic against your benchmarks — some flux is normal; a sustained drop is a signal.
4. Check server logs — how Googlebot is crawling the new site and where it stumbles.
5. Update high-value backlinks — ask your most important linking sites to point at the new URLs.
Tools
| Tool | Key use |
|---|---|
| Google Search Console | Index status, crawl errors, sitemap submission; URL Inspection for checking canonicalization. |
| Site crawlers (Screaming Frog, Sitebulb) | Building URL inventories, auditing redirects and canonicals, finding broken links. |
| Ahrefs / Semrush / Moz | Benchmarking performance and prioritizing top pages by backlinks. |
| Spreadsheets (Sheets, Excel) | Building and managing the 301 redirect map. |
Key takeaways
- Canonicalization is ongoing; migration is an event — master the first to prevent daily dilution, the second to survive major change.
rel="canonical"is your everyday tool for declaring the authoritative URL.- The 301 redirect map is the migration’s critical document — every old URL mapped to a relevant new one.
- Planning and monitoring matter as much as launch day — the work before and after is where migrations are won or lost.
- Pair Search Console with a crawler for a complete view of URL health.
