How long does it take to recover traffic after an SEO migration?

A well-executed SEO migration typically sees traffic stabilize within 2 to 6 months. Some fluctuation in the first 2-4 weeks is normal as Google recrawls and reindexes your pages. If proper 301 redirects and URL mapping are in place, most sites recover 90% or more of their organic traffic within 3 months. Poorly executed migrations, however, can result in permanent traffic loss.

Do I lose all my backlinks when I change my domain name?

No, you don't lose your backlinks if you implement proper 301 redirects from every old URL to its corresponding new URL. A 301 redirect passes approximately 90-99% of link equity to the new page. Additionally, you should update backlinks manually where possible—especially high-authority ones—by contacting webmasters directly. Tools like Ahrefs or Moz can help you identify your most valuable backlinks to prioritize outreach.

Should I migrate my domain and CMS at the same time?

It's generally recommended to avoid changing both your domain and CMS simultaneously. Each change introduces its own set of risks—URL structure changes, content rendering differences, internal linking shifts—and combining them makes it extremely difficult to diagnose issues if traffic drops. If both changes are necessary, stage them at least 3-6 months apart so you can isolate variables and monitor recovery between each migration phase.

SEO Migration: How to Change Domain or CMS Without Losing Traffic

Why SEO Migrations Are High-Stakes (And Why Most Fail)

Changing your domain name, switching CMS platforms, or restructuring your site architecture can feel like performing open-heart surgery on your online presence. One wrong move and you could flatline your organic traffic overnight.

The numbers are sobering: according to a study by Ahrefs, over 60% of site migrations result in measurable traffic loss, and many never fully recover. Yet migrations are sometimes unavoidable. Businesses rebrand. Technology evolves. A legacy CMS becomes a bottleneck.

The good news? With rigorous planning, meticulous execution, and disciplined post-launch monitoring, you can migrate your site without losing the traffic and rankings you’ve spent years building.

This guide walks you through the entire SEO migration process—from pre-migration audits to post-launch recovery—with concrete examples, actionable checklists, and the hard-won lessons from hundreds of migrations.

Understanding the Types of SEO Migration

Not all migrations are created equal. The level of SEO risk depends on what exactly you’re changing.

Domain Migration

This is the highest-risk migration type. You’re moving your entire site from olddomain.com to newdomain.com. Google essentially treats the new domain as a new entity, so you’re asking search engines to transfer all trust signals—backlinks, domain authority, ranking history—to a completely new address.

Common scenarios:

Company rebranding (e.g., cheapflights.com → momondo.com)
Moving from a country-code domain to a generic TLD (e.g., .co.uk → .com)
Consolidating multiple domains into one

CMS Migration

Switching from one content management system to another—say, from Magento to PrestaShop, or from Joomla to WordPress—usually changes URL structures, page templates, internal linking patterns, and sometimes content rendering.

Common scenarios:

Moving from a legacy or custom CMS to WordPress or PrestaShop
Upgrading from an outdated e-commerce platform (e.g., OpenCart to PrestaShop 8)
Migrating to a headless CMS architecture

Protocol and Structure Migrations

These are lower-risk but still significant:

HTTP to HTTPS (protocol migration)
Subdomain to subdirectory (e.g., blog.site.com → site.com/blog)
URL structure overhaul (e.g., changing /product.php?id=42 to /blue-running-shoes)

Migration Type	Risk Level	Traffic Recovery Timeline	Key Challenge
Domain change	🔴 High	3–6 months	Transferring domain authority
CMS change	🟠 Medium-High	2–4 months	URL mapping & content parity
HTTP → HTTPS	🟡 Medium	2–6 weeks	Certificate & mixed content issues
URL restructure	🟠 Medium-High	2–4 months	Comprehensive redirect mapping
Subdomain → subfolder	🟡 Medium	2–6 weeks	Internal linking & canonicalization

Phase 1: Pre-Migration Audit and Planning

The migration itself is only as good as the preparation that precedes it. At Lueur Externe, having managed migrations for e-commerce sites with 50,000+ product URLs, we’ve learned that 80% of migration success is determined before a single redirect is written.

Crawl and Benchmark Your Current Site

Before touching anything, create a complete snapshot of your current SEO performance:

Full site crawl: Use Screaming Frog, Sitebulb, or Lumar to crawl every URL. Export all live pages, their status codes, titles, meta descriptions, H1 tags, canonical tags, and internal links.
Keyword rankings: Export your current keyword positions for at least your top 500 keywords using SEMrush, Ahrefs, or Google Search Console.
Traffic baseline: Record organic traffic for the last 12 months (monthly and weekly granularity). Note seasonal patterns.
Backlink profile: Export all referring domains and their target pages using Ahrefs or Majestic.
Top pages: Identify your top 100 pages by organic traffic. These are your highest-priority pages during migration.

Build a Complete URL Mapping Document

This is the single most critical deliverable in any migration. Every URL on the old site must map to a corresponding URL on the new site.

# Example URL mapping (CSV format)
# old_url, new_url, status_code, notes

/old-category/blue-widgets, /shop/blue-widgets, 301, top traffic page
/blog/2022/seo-tips, /resources/seo-tips, 301, update internal links
/about-us.html, /about, 301, template change
/discontinued-product-x, /shop/alternative-product, 301, closest match
/legacy-page-no-equivalent, -, 410, no relevant new page

For large e-commerce sites, this mapping document can contain tens of thousands of rows. Automate where possible using regex patterns, but always manually verify your top 200-500 pages.

Content Parity Check

One of the most common migration mistakes is inadvertently changing on-page content during the CMS switch. Ensure:

Title tags remain identical (or are intentionally improved)
H1 headings match the original
Body content is fully transferred—no truncated text, no missing sections
Images have the same alt text and are properly loaded
Schema markup is replicated or improved
Hreflang tags are maintained for multilingual sites

Phase 2: Technical Implementation

Setting Up 301 Redirects

The 301 redirect is the workhorse of SEO migration. It tells search engines and users that a page has permanently moved to a new location, and it passes approximately 90–99% of link equity to the destination URL.

Here’s an example of server-level 301 redirects in an .htaccess file (Apache):

# Individual page redirects
Redirect 301 /old-page-1 https://www.newdomain.com/new-page-1
Redirect 301 /old-page-2 https://www.newdomain.com/new-page-2

# Pattern-based redirects using RewriteRule
RewriteEngine On
RewriteRule ^blog/([0-9]{4})/(.*)$ /resources/$2 [R=301,L]

# Catch-all for unmatched URLs (use cautiously)
RewriteRule ^(.*)$ https://www.newdomain.com/$1 [R=301,L]

For Nginx servers:

# Individual redirects
rewrite ^/old-page-1$ https://www.newdomain.com/new-page-1 permanent;

# Pattern-based redirect
rewrite ^/blog/[0-9]{4}/(.*)$ /resources/$1 permanent;

Critical rules for redirects:

Never use 302 (temporary) redirects for permanent migrations
Avoid redirect chains (A → B → C). Every old URL should redirect directly to its final destination
Don’t redirect everything to the homepage—this is a “soft 404” in Google’s eyes and you will lose page-level rankings
Keep redirects active for at least 2 years; ideally, indefinitely

Update Google Search Console

Verify the new domain/property in Google Search Console
Use the Change of Address tool (for domain migrations)
Submit the new XML sitemap
Monitor the Index Coverage report daily for the first month

Update XML Sitemaps and Robots.txt

Remove the old sitemap from the old domain’s robots.txt
Ensure the new domain’s sitemap only contains new, canonical URLs
Verify robots.txt on the new domain isn’t accidentally blocking critical sections
Submit the new sitemap through Search Console immediately after launch

Internal Links

Don’t rely solely on redirects for internal links. Update every internal link on the new site to point directly to the new URLs. Redirected internal links:

Add unnecessary server load
Slow down page rendering
Waste crawl budget
Create a fragile dependency on redirect rules

Phase 3: The Migration Launch

Timing Matters

Choose your migration date wisely:

Avoid peak traffic periods (e.g., Black Friday for e-commerce, January for fitness sites)
Launch early in the week (Tuesday or Wednesday) so you have business days to troubleshoot
Avoid Fridays—you don’t want to discover critical issues over the weekend
Coordinate with marketing—pause paid campaigns briefly to avoid sending ad traffic to broken pages

Launch Day Checklist

Phase 4: Post-Migration Monitoring

The first 90 days after migration are critical. This is where many teams fail—they celebrate the launch and stop paying attention.

Week 1: Daily Monitoring

Check Google Search Console for crawl errors, indexation issues, and 404s
Monitor organic traffic in real-time via Google Analytics
Spot-check top 50 pages in incognito to verify they render correctly
Test redirect mapping with a crawl tool (Screaming Frog in list mode)

Weeks 2-4: Indexation Tracking

Track how many new URLs have been indexed vs. old URLs deindexed
Use the site:newdomain.com operator to check index count
Monitor for unwanted indexation of old URLs (especially if both domains are still live)
Check for duplicate content issues between old and new domains

Months 2-3: Ranking Recovery

Compare keyword rankings against your pre-migration baseline
Identify pages that haven’t recovered and investigate (missing redirects, content changes, technical issues)
Update high-value backlinks by contacting webmasters with the new URLs
Monitor Core Web Vitals—a CMS change can significantly impact page speed

At Lueur Externe, our standard migration monitoring protocol runs for a minimum of 90 days, with weekly reports that track over 40 KPIs including indexation rate, ranking distribution shifts, crawl budget utilization, and redirect chain analysis.

Common Migration Mistakes That Destroy Traffic

Having audited dozens of failed migrations from other agencies, here are the most devastating errors we see:

1. No URL Mapping (or Incomplete Mapping)

If even 10% of your high-traffic pages don’t have proper redirects, you could lose 30-40% of your organic traffic. Every single URL must be accounted for.

2. Redirecting Everything to the Homepage

This is the #1 cardinal sin. When Google sees thousands of pages all redirecting to one URL, it interprets them as soft 404s. You lose all page-level ranking signals.

3. Changing Content During Migration

A migration should change where your content lives, not what the content says. Resist the urge to “improve” page copy, rewrite title tags, or restructure content hierarchy simultaneously. Change one variable at a time.

4. Ignoring JavaScript Rendering

Modern CMS platforms (especially headless or React-based frameworks) may render content via JavaScript that Googlebot can’t efficiently process. Always test your new site with Google’s URL Inspection tool and the Mobile-Friendly Test to verify content is rendered and indexable.

5. Dropping Structured Data

If your old site had rich snippets (reviews, FAQs, product markup), ensure the new site replicates all Schema.org structured data. Losing rich snippets can reduce click-through rates by 20-30%, even if rankings remain stable.

Real-World Migration Results: What Success Looks Like

To set realistic expectations, here’s what a well-executed migration trajectory typically looks like:

Week 1: Traffic drops 10-20% as Google recrawls and reprocesses pages
Weeks 2-4: Traffic stabilizes, with some keywords fluctuating ±5 positions
Month 2: 70-85% of pre-migration traffic restored
Month 3: 90-100% of traffic restored, often with improvements if technical SEO was enhanced
Month 6: Full stabilization; new URL structure benefits become visible in rankings

Conversely, a poorly executed migration can look like this:

Week 1: Traffic drops 40-60%
Month 1: No recovery; Google continues to index old URLs returning 404s
Month 3: 50% of original traffic at best; massive keyword position losses
Month 6+: Partial recovery at best, with some losses becoming permanent

The difference between these two outcomes is almost always planning and redirect quality.

Special Considerations for E-Commerce Migrations

E-commerce migrations carry additional complexity due to the sheer volume of URLs and the dynamic nature of product catalogs:

Product URLs: Map every product, including discontinued items, to relevant alternatives
Category and filter pages: Faceted navigation often generates thousands of URLs that need careful handling
Pagination: Ensure paginated category pages are properly redirected or recreated
Product reviews and UGC: User-generated content contributes to long-tail rankings; don’t lose it
Checkout and conversion tracking: Verify that conversion funnels remain intact post-migration

As a certified PrestaShop expert agency, Lueur Externe has managed complex e-commerce migrations involving catalogs of 100,000+ products, multi-currency setups, and multilingual architectures—all while maintaining organic traffic continuity.

Tools Every Migration Needs

Here’s the toolkit we recommend for a smooth migration:

Screaming Frog SEO Spider – Full-site crawling, redirect testing, and URL mapping validation
Google Search Console – Index coverage, Change of Address tool, sitemap management
Ahrefs / SEMrush – Keyword tracking, backlink monitoring, and competitive analysis
Google Analytics 4 – Real-time traffic monitoring and conversion tracking
Sitebulb or Lumar – Advanced crawl analytics and JavaScript rendering checks
Redirect Path (Chrome extension) – Quick redirect chain testing in the browser
Wayback Machine – Reference for historical content if pages were lost during migration

Conclusion: Don’t Gamble With Your Organic Traffic

An SEO migration is not a weekend project. It’s a strategic operation that demands the same rigor you’d apply to any major infrastructure change. The difference between a migration that preserves your traffic and one that destroys it comes down to three things: exhaustive planning, precise technical execution, and relentless post-launch monitoring.

If you’re planning a domain change, a CMS switch, or a major site restructure, don’t leave it to chance. The cost of a botched migration—in lost revenue, lost rankings, and the months of recovery work—far exceeds the cost of doing it right the first time.

Ready to migrate without the risk? The team at Lueur Externe has been helping businesses navigate complex SEO migrations since 2003. With deep expertise in PrestaShop, WordPress, AWS infrastructure, and technical SEO, we ensure your traffic, rankings, and revenue make the journey safely. Get in touch with us today for a free migration assessment.