Site Migration SEO: The Redirect Mistakes That Cost Rankings and How to Avoid Them

Site migrations lose SEO value in predictable, preventable ways

The patterns of SEO damage in site migrations — URL restructures, domain changes, CMS switches, HTTPS rollouts — repeat across organisations of every size. The underlying causes are usually the same: redirect maps built in a hurry, high-value pages overlooked, redirect chains not collapsed, and post-migration monitoring that starts too late.

Understanding these patterns in advance turns a migration from a stressful recovery exercise into a managed transition.

---

The most expensive redirect mistakes

Redirecting to the homepage

This is the most common and most damaging redirect pattern in migrations. When a URL changes and no direct equivalent exists on the new site, redirecting to the homepage is tempting — it's easy, it doesn't 404, and it "works" in the sense that something loads. But from Google's perspective, the homepage usually has nothing to do with the original page's content.

When a product page or blog post that has accumulated backlinks over years is redirected to the homepage:

• The link equity from those backlinks is passed to the homepage instead of a relevant destination
• The original page's keyword associations are lost
• Google treats this as a "soft 404" — it may eventually deindex the redirected URL and discount the backlinks

The fix: map every old URL to its best equivalent on the new site. For pages with no direct equivalent, find the most topically relevant page. If truly nothing relevant exists, 404 is often better than a misleading homepage redirect for high-authority pages.

Redirect chains

When redirects build on top of each other:

/old-url → /intermediate-url → /new-url

Each hop loses some link equity and adds latency. Three or more hops in a chain is common on sites that have been through multiple migrations without cleanup.

How chains accumulate: Site A redirects /page-1 to /page-2. A year later, /page-2 is migrated and redirected to /page-3. Nobody updated the original redirect. Now /page-1 → /page-2 → /page-3.

The fix: after every migration, audit all existing redirects and update each to point directly to the final destination. Tools like Screaming Frog can crawl redirect chains and identify multi-hop paths.

Missing redirects for high-value pages

A migration covers the main site structure but misses orphaned content: old blog posts, category pages from a discontinued product line, tag archives. These pages may have accumulated years of backlinks.

How to prevent it:

• Pull all URLs currently indexed in Google Search Console before migration
• Pull all URLs that have inbound links from Ahrefs or Semrush
• Cross-reference against the new site structure
• Any URL with inbound links that doesn't have an equivalent on the new site needs special consideration

A single high-authority blog post redirected to nothing can cost more link equity than the entire rest of the migration.

---

Preserving link equity through domain migrations

Domain migrations (moving from one domain to another) are the highest-risk type of migration because all the accumulated domain authority must transfer through redirects.

The transfer timeline:

• Immediately after redirects: Google follows the 301s and begins re-crawling
• 2–4 weeks: rankings typically drop as Google processes the change
• 2–3 months: rankings begin recovering toward pre-migration levels
• 4–6 months: full recovery for well-executed migrations

The recovery period is why domain migrations should be planned carefully and executed once — not repeated.

During a domain migration:

• 301 redirect every page to its direct equivalent on the new domain
• Keep redirects live for at least 1–2 years (some indefinitely for high-link-value URLs)
• Update all internal links on the new domain to point directly to new URLs (not through redirects)
• Submit the new sitemap to Google Search Console
• Add the old domain as a property in Search Console and submit a change of address notification

---

The redirect mapper workflow

Before any migration, the redirect map should exist as a document:

Old URL	New URL	Redirect type	Priority
/old-product-page	/products/new-name	301	High (has backlinks)
/category/old-name	/category/new-name	301	Medium
/discontinued-page	/similar-page	301	Low

Priority is determined by:

• Number and quality of external backlinks (from Ahrefs, Semrush, or Google Search Console links report)
• Organic traffic volume before migration
• Internal links from other pages

High-priority pages (significant backlinks or traffic) deserve individual attention for destination mapping. Low-priority pages with no inbound links or traffic can be handled with wildcard/pattern redirects.

---

Technical redirect implementation

Apache (.htaccess)

# Single URL redirect
Redirect 301 /old-page https://example.com/new-page

# Pattern redirect (all blog posts)
RedirectMatch 301 ^/blog/(.*)$ https://example.com/articles/$1

# Subdomain redirect
RewriteEngine On
RewriteCond %{HTTP_HOST} ^old-subdomain\.example\.com$
RewriteRule ^(.*)$ https://example.com/$1 [R=301,L]

Nginx

# Single URL
rewrite ^/old-page$ /new-page permanent;

# Pattern
rewrite ^/blog/(.*)$ /articles/$1 permanent;

# Domain redirect
server {
    listen 80;
    server_name old-domain.com;
    return 301 https://new-domain.com$request_uri;
}

Cloudflare Bulk Redirects

For large-scale redirects (hundreds or thousands of URLs), Cloudflare's Bulk Redirects feature allows uploading a CSV of source → destination pairs. This avoids server-side configuration entirely and handles redirect logic at the CDN edge.

---

Post-migration monitoring

The migration isn't complete at go-live — it's complete when rankings, traffic, and crawl coverage have recovered. Monitoring should start immediately:

Day 1–7:

• Google Search Console → Index Coverage: are the new URLs being indexed?
• Crawl errors: are there unexpected 404s or server errors?
• Core traffic pages: are their rankings stable?

Week 2–4:

• Organic traffic comparison: week-over-week and year-over-year
• Rankings for key pages: monitor the 20–30 most important pages specifically
• Search Console → Links: are links being credited to new URLs?

Month 1–3:

• Overall organic traffic trend
• Index coverage: all important pages indexed under new URLs?
• Old URLs: are they being deindexed correctly?

---

How to use the Redirect Mapper on sadiqbd.com

1. Enter source URLs — old URLs to be redirected
2. Enter destination URLs — their new equivalents
3. Select redirect type — 301 for permanent, 302 for temporary
4. Generate the redirect map — structured documentation ready for developer handoff
5. Use the chain checker — enter any URL to follow the redirect chain and verify it reaches the intended destination

---

Frequently Asked Questions

How long should 301 redirects be kept live? Permanently, or as close to it as operational feasibility allows. Old URLs continue to appear in bookmarks, external links, and cached pages indefinitely. Removing redirects after a year or two causes those paths to 404 unnecessarily. Storage and computational cost for redirect rules is trivial compared to the link equity risk of removing them.

Does HTTPS migration require redirects? Yes — HTTP URLs should 301 to their HTTPS equivalents. Most modern server configurations and CDNs handle this automatically. Verify that all HTTP → HTTPS redirects are in place and that no mixed content remains on the HTTPS pages.

Is a 302 ever appropriate for SEO purposes? Only for genuinely temporary redirects — A/B test variants, seasonal pages, maintenance redirects. 302s don't transfer link equity and tell Google to keep the original URL indexed. Using 301 for permanent changes and 302 for genuinely temporary ones is the correct pattern.

Is the Redirect Mapper free? Yes — completely free, no sign-up required.

---

The investment in a thorough redirect map before migration is returned many times over in avoided ranking drops and link equity preservation. Treating it as a rushed post-migration activity produces the 2–6 month recovery periods that give site migrations a bad reputation.

Try the Redirect Mapper free at sadiqbd.com — plan, document, and audit URL redirects for any site migration, instantly.