How much traffic loss should I expect during a website migration?

A well-executed migration typically causes 10-20% temporary traffic loss during the 2-6 week re-crawl period, then full recovery as Google re-indexes your new URLs. A poorly executed migration can cause 30-80% traffic loss that takes months to recover. Domain migrations carry the highest risk: even perfect migrations typically see some temporary dip before link equity fully transfers via 301 redirects, which can take 12-18 months for complete recovery.

Do 301 redirects pass SEO value (link equity)?

301 redirects pass approximately 90-99% of link equity (PageRank) from the old URL to the new URL, according to Google's own statements. Historically, there was a penalty for redirect hops, but Google has confirmed that a single 301 passes essentially full equity. What you should avoid is redirect chains (A → B → C) — each hop in the chain loses a percentage of equity. Always redirect directly to the final destination.

How long should I keep 301 redirects in place after a migration?

For at least 12 months after migration, ideally permanently. Redirects serve two purposes: passing link equity from external backlinks (which you can't control) and providing the correct URL to users who have bookmarked old URLs. High-authority backlinks may never be updated; the 301 will serve those visitors forever. The cost of keeping redirects is minimal (server overhead for a cache lookup); the cost of removing them prematurely is losing link equity and creating 404s for bookmarked URLs.

What is the most common cause of ranking drops after a website migration?

The most common causes are: (1) incomplete redirect mapping — some URLs returning 404 instead of redirecting; (2) robots.txt blocking the new site (accidentally left from staging); (3) noindex tags left on production pages from development; (4) duplicate content from old and new URLs both being accessible; and (5) significantly slower page load times on the new platform. A thorough pre-launch audit using Screaming Frog on the staging environment catches most of these before they affect real users and Googlebot.

SEO Migration Services: Protect Rankings

Website migrations are among the most technically complex SEO projects you can undertake. Done correctly, a migration preserves your organic search rankings, traffic, and the authority you've built over years. Done incorrectly, it can result in ranking drops of 30-80% that take 6-18 months to recover from.

This guide explains what SEO migration services involve, when you need them, the critical steps that protect your rankings, and what to look for in an SEO migration partner. Whether you're replatforming, redesigning, consolidating domains, or moving to a new TLD, the principles are the same.

What Is SEO Migration?

SEO migration is the process of planning and executing a website change while preserving or improving your organic search performance. The "SEO" qualifier distinguishes it from a standard technical migration — which focuses on getting the new site to work — and emphasizes maintaining the signals Google and other search engines have built up for your current URLs.

Every website change that alters URLs, content structure, or domain is a migration risk. The scale of that risk depends on how many URLs change, how much content changes, and whether the authority signals (backlinks, canonical signals, internal links) are properly transferred.

When Do You Need SEO Migration Services?

Platform Migration (Replatforming)

Moving from one CMS or e-commerce platform to another — WordPress to SvelteKit, Magento to Shopify, a custom CMS to Sanity — almost always changes URL structures. Even if you try to keep URLs identical, differences in URL generation (trailing slashes, query parameters, case sensitivity) can create duplicate content and split link equity.

Website Redesign

A redesign that changes URL structure, removes pages, or significantly alters content (not just layout) carries SEO risk. A layout-only redesign with identical URLs and content is low risk. But many "redesigns" combine UX changes with structural changes — navigation restructuring, content consolidation, section reorganization — that create migration-level SEO risk.

Domain Change

Moving from an old domain to a new one is the highest-risk migration type. Domain authority is one of the strongest ranking signals, and it takes time to transfer via 301 redirects. A proper domain migration requires a complete 1-to-1 redirect mapping, updated canonical tags, updated internal links, and outreach to high-authority backlink sources to update their links directly.

HTTPS Migration

Moving from HTTP to HTTPS is now a baseline requirement (Google has used HTTPS as a ranking signal since 2014). While most HTTPS migrations are low risk if done correctly, common mistakes — missing redirects, mixed content warnings, updating Google Search Console — still cause unnecessary ranking volatility.

Domain Consolidation or Content Merger

Merging two websites (after an acquisition, for example) requires deciding which URLs to keep, which to redirect, and how to handle overlapping or duplicate content. This is one of the most complex migration types, requiring careful evaluation of which pages have the strongest rankings and backlink profiles.

The Critical Steps of a Successful SEO Migration

1. Pre-Migration URL Audit

Before touching anything, export a complete inventory of every URL on your current site that has organic traffic, backlinks, or both. Use Google Search Console, Screaming Frog, and your server log files. Rank each URL by SEO value (organic traffic + link equity). The highest-value URLs need the most careful treatment.

This audit also identifies problem URLs you shouldn't migrate: thin content pages, duplicate content, outdated product pages with no traffic. Migration is an opportunity to clean up a bloated site architecture.

2. URL Mapping

Create a complete map from every current URL to its corresponding new URL. This mapping is the most critical deliverable in any migration project. The rules:

1-to-1 mapping: Every URL with SEO value should map to exactly one new URL. Avoid mapping multiple old URLs to one new URL unless the content genuinely merges.

Permanent 301 redirects: Use 301 (not 302 or meta refresh) for all redirects. 301s transfer approximately 90-99% of link equity.

No redirect chains: Old URL → new URL directly. Old URL → intermediate URL → new URL wastes crawl budget and loses a percentage of link equity at each hop.

No redirect loops: Test every redirect before going live. URL A → URL B → URL A will break crawlers and browsers.

3. Redirect Implementation

Server-level redirects (via web server config or CDN rules) are faster and more reliable than application-level redirects. For most modern frameworks, CDN-level redirect rules (Cloudflare, Vercel, Netlify) are the recommended approach: they execute before your application starts, eliminate server-side overhead, and are easy to audit.

For large sites (thousands of URLs), redirect management should be centralized in a CMS or configuration file — not scattered across multiple files or hardcoded in application logic. Sanity CMS, for example, allows non-technical team members to manage redirects collaboratively without code deployments.

4. Content Migration and Preservation

Content is your core SEO asset. During migration, ensure:

Title tags and meta descriptions: Migrate to the new platform without truncation or default replacement. Verify all title tags appear correctly in crawl tools post-launch.

Heading structure: Preserve H1/H2/H3 hierarchy. Many CMS migrations accidentally flatten or alter heading levels.

Structured data: Migrate all JSON-LD schemas (Article, Product, FAQPage, Organization, etc.). Validate in Google's Rich Results Test post-launch.

Internal links: Update all internal links to use the new URLs. Old internal links using old URLs add unnecessary redirect hops for Googlebot and users.

Image alt text: Verify alt attributes are present on all important images. Alt text is both an accessibility requirement and an SEO signal.

5. Technical SEO Verification Pre-Launch

Before going live, verify on the staging environment:

Crawl the staging site with Screaming Frog or similar. Check for 404s, 500s, redirect chains, and blocked resources. Verify canonical tags point to the correct final URLs. Confirm the robots.txt does not block important pages. Test structured data with Google's Rich Results Test. Run Core Web Vitals in PageSpeed Insights — migration is the right time to address performance issues.

6. Post-Launch Monitoring

The first 2-4 weeks post-launch are critical. Monitor daily:

Google Search Console: Coverage errors, crawl anomalies, index counts, and click/impression data in Performance reports. A temporary traffic dip is normal (re-crawl lag); a sustained drop indicates a problem.

Crawl tool re-run: Run Screaming Frog against the live site within 48 hours of launch to catch production-specific issues (misconfigured redirects, caching problems).

Ranking tracker: Monitor rankings for your highest-value keywords daily for the first month.

Log file analysis: Verify Googlebot is crawling the new URLs and not returning errors.

Timeline Expectations

Google re-crawls and processes changes at different rates depending on your site's crawl budget and authority:

High-authority sites (10M+ pages indexed, major brands): 2-4 weeks for full re-crawl of most pages.

Mid-tier sites (50K-1M pages): 4-8 weeks for most pages to be re-crawled and re-indexed.

Smaller sites (<10K pages): 2-6 weeks for complete re-index.

Ranking volatility during this period is normal. Traffic typically dips 10-20% during the re-crawl phase even on a perfect migration. If you're seeing 40%+ drops after 4 weeks, investigate immediately — something is wrong.

For domain migrations specifically, partial ranking recovery happens within 3-6 months; full recovery (including all backlink equity transfer) typically takes 12-18 months. This is why domain migrations require more planning than platform migrations.

Common SEO Migration Mistakes

No Pre-Launch Staging Verification

Launching without crawling the staging environment first is the most avoidable cause of migration disasters. A 2-hour crawl pre-launch catches issues that would otherwise take weeks of post-launch troubleshooting.

Incomplete Redirect Mapping

Forgetting to map paginated pages, filtered/faceted navigation URLs, old campaign landing pages, or image URLs is common. The URL inventory step (using both Search Console and Screaming Frog, not just one) catches these edge cases.

Using 302 Instead of 301 Redirects

302 (temporary) redirects transfer significantly less link equity than 301 (permanent) redirects. Always use 301 for permanent URL changes. The "permanent vs temporary" distinction isn't just semantic — it affects how much authority passes through the redirect.

Forgetting to Update Internal Links

Redirects handle external backlinks, but internal links should point to the final URLs directly. Every redirect hop Googlebot traverses while crawling your own site wastes crawl budget. After migration, run a site-wide internal link audit and update links that still point to old (now redirected) URLs.

Launching on a Friday

Plan your go-live for Tuesday or Wednesday morning. You need your full team available for post-launch monitoring and rapid response. Migration issues found at 9 AM Thursday give you two full days to resolve before the weekend.

How iConcept Handles SEO Migrations

At iConcept, every website development project that involves a platform migration includes a structured SEO migration phase. We don't treat SEO preservation as an optional add-on — it's a core deliverable of every replatforming project.

Our SEO migration process includes a pre-migration URL audit using Screaming Frog and Google Search Console, complete redirect mapping with chain verification, structured data migration and validation, post-launch monitoring with weekly reporting for the first month, and issue resolution within 24-48 hours for any critical post-launch problems.

If you're planning a website migration and need to protect your organic traffic, contact our team for an initial SEO migration assessment.

Conclusion

SEO migration is not glamorous work — it's detailed, methodical, and largely invisible when done correctly. The goal is that search engines don't notice you've moved. Ranking stability through a migration is the sign of excellent execution.

The fundamental principles are simple: inventory everything before touching it, create a complete redirect map, preserve your content's signals (titles, structure, schema), verify on staging before launching, and monitor obsessively post-launch. It's the execution that separates migrations that preserve rankings from those that cause months of recovery work.

SEO Migration Services: Protecting Your Rankings During a Website Move