SEO

Website Migration SEO: How to Move Your Site Without Losing Traffic or Rankings

Website migration SEO done right: a step-by-step plan covering redirect mapping, pre-launch checks and post-launch monitoring so you keep your traffic and rankings.

Obinna
November 12, 2026 · 13 min read
Website migration SEO: Website Migration SEO: How to Move Your Site Without Losing Traffic or Rankings

Website migration SEO is the discipline of moving a site to a new platform, domain or URL structure without destroying the organic traffic you spent years earning. Done badly, a migration can wipe out 30 to 70 percent of your search visibility within weeks. Done well, you lose almost nothing and often gain ground.

Most traffic losses are not caused by Google being unpredictable. They come from preventable errors: missing redirects, blocked staging rules left in production, changed URLs with no mapping, and no one watching the data after launch. This guide gives you the exact process we use at Lucanix to plan and run migrations for SMBs and startups across the US, Canada and the UK.

What Counts as a Migration and Why the Risk Is Real

A migration is any change that alters how search engines find, crawl and understand your pages. That includes switching CMS platforms (for example WordPress to Next.js), moving to a new domain, changing your URL structure, moving from HTTP to HTTPS, merging two sites, or redesigning with new navigation and templates.

Each type carries different risk. A domain change is the highest risk because every URL changes at once. A platform change with identical URLs is lower risk but still dangerous, because templates, internal links, metadata and rendering all change underneath. A redesign sits in between, since it often alters navigation and content without anyone flagging it as a migration.

The core problem is simple. Google has built a map of your site over time: which URLs exist, which pages are authoritative, which keywords each page earns. A migration tears up that map. Your job is to hand Google a clear, accurate replacement so it can transfer the signals quickly.

Treat website migration SEO as a project with its own owner, timeline and sign-off checklist, not as a task bolted onto the end of a development sprint. The sites that keep their traffic are the ones where SEO has a seat at the table from the first planning meeting.

Step 1: Set Goals, Scope and a Safe Launch Window

Start by defining what you are migrating and why. Write down the change type, the target launch date, who approves go-live, and what success looks like. A reasonable success target is retaining at least 95 percent of organic sessions within 30 days and full recovery within 90 days.

Pick your launch window carefully. Avoid peak revenue periods such as Black Friday for ecommerce, end-of-quarter for B2B, or any seasonal spike in your niche. Launch early in the week so your team is available to fix problems, never on a Friday afternoon.

Assign clear roles. You need a project owner, a developer who controls redirects and server configuration, an SEO lead who owns the redirect map and QA, and a stakeholder with authority to delay launch. If the redesign is part of the same project, review our website redesign checklist alongside this guide, and consider whether the redesign and migration should happen together or in separate phases. Splitting them reduces the number of variables if something goes wrong.

Finally, agree a rule up front: no launch without SEO sign-off. This single rule prevents most migration disasters.

Step 2: Crawl and Benchmark Your Current Site

You cannot protect what you have not measured. Before touching anything, crawl the full existing site with a tool such as Screaming Frog or Sitebulb and export every URL with its status code, title, meta description, H1, canonical tag, indexability and internal link count.

Then capture performance benchmarks from three sources:

  • Google Search Console: export 16 months of query and page data, including clicks, impressions, CTR and average position.
  • Google Analytics: record organic sessions, conversions and revenue by landing page.
  • Backlink data: export all referring domains and the specific URLs they link to, using Ahrefs, Semrush or Search Console’s links report.

Rank your pages by value. A simple scoring model combines organic traffic, backlinks and conversions. The top 20 percent of pages typically drive 80 percent of results, and those pages get the most careful treatment during migration.

Also capture your current technical baseline: page speed, Core Web Vitals, structured data and XML sitemaps. Our technical SEO audit checklist covers the 20 issues worth documenting before you begin, so you can compare like with like after launch.

Step 3: Build a Complete 301 Redirect Map

Redirect mapping is the single most important task in website migration SEO. Every old URL that has traffic, links or indexed status needs a one-to-one 301 redirect to its closest equivalent on the new site. A 301 tells search engines the move is permanent and passes the large majority of ranking signals to the new URL.

Build the map in a spreadsheet with these columns: old URL, new URL, redirect type, page value score, and notes. Pull the old URL list from your crawl, Search Console, your sitemap, your analytics landing pages and your backlink export. Combining all five catches URLs that any single source would miss.

Follow these rules for 301 redirect mapping:

  1. Redirect each old URL to the most relevant new page, not the homepage. Mass redirects to the homepage are treated as soft 404s.
  2. Avoid redirect chains. A to B to C wastes crawl budget and dilutes signals. Point A straight to C.
  3. Keep URLs identical where you can. The safest redirect is the one you never need.
  4. If a page has no equivalent, return a 410 or redirect to the closest parent category, and document the decision.
  5. Preserve parameters, trailing slash behaviour and case rules consistently.

Google’s own guidance on site moves with URL changes confirms that permanent server-side redirects are the preferred method. Plan to keep these redirects live for at least 12 months, and longer for URLs with strong backlinks.

Step 4: Protect Content, Metadata and On-Page Signals

A migration is not the moment to rewrite your content. Changing URLs, templates and copy all at once makes it impossible to diagnose a traffic drop. Keep the content of high-performing pages as close to identical as possible, and save improvements for a later phase.

Check that these elements carry over to the new site exactly:

  • Title tags and meta descriptions
  • H1 and heading hierarchy
  • Body copy, including text inside tabs and accordions
  • Image alt text and file names
  • Internal links and anchor text
  • Structured data and schema markup
  • Canonical tags pointing to the new URLs, not the old ones
  • Hreflang tags for international sites

Pay special attention to rendering. If you are moving from WordPress to a JavaScript framework, make sure the content is present in the server-rendered HTML and not only injected client-side. Our comparison of Next.js and WordPress explains how each platform handles rendering, which matters for crawlability.

Also protect your internal linking. Update every internal link to point directly to the new URL rather than relying on redirects. Internal links that bounce through 301s slow crawling and waste signals.

Work with Lucanix

Ready to migrate without losing rankings?

Lucanix plans and runs SEO-safe migrations for businesses in the US, Canada and the UK. Book a free consultation and we will review your risk before you commit.

Start a project projects@lucanix.com

Step 5: Set Up a Staging Environment and Test Everything

Build and test the new site on a staging environment that mirrors production. Block it from search engines using password protection (HTTP authentication), which is far safer than a robots.txt rule or a noindex tag alone. Staging sites that leak into Google’s index create duplicate content problems.

Run a full crawl of the staging site and compare it against your baseline crawl. You are looking for differences. Check that every important URL returns a 200 status, that metadata matches, that canonicals are correct and that no unexpected noindex tags exist.

Test your redirect map on staging before launch. Load the full list of old URLs and confirm each one resolves to the intended new URL in a single hop with a 301 status. Fix every chain, loop and 404 now, while it costs nothing.

Also verify:

  • XML sitemap contains only canonical, indexable, 200-status URLs
  • robots.txt on the new site allows crawling (staging rules not copied over)
  • Analytics, tag manager and conversion tracking fire correctly
  • Forms, checkout and key user journeys work end to end

Speed matters too. A new platform that is slower than the old one can undo your hard work. Review our guide to Core Web Vitals optimization and confirm the new site passes LCP, INP and CLS before go-live.

Step 6: Run the Pre-Launch Checklist

In the 48 hours before launch, run a final structured check. This is your website migration SEO safety net. Print it, assign owners and tick every item.

Check What to confirm Owner
Redirect map All old URLs mapped, tested, no chains or loops SEO lead
Robots.txt No Disallow: / rule carried over from staging Developer
Noindex tags None on pages that should rank SEO lead
Canonicals Self-referencing and pointing to new domain or URLs Developer
XML sitemap Updated, clean, ready to submit SEO lead
SSL certificate Valid on all variants (www, non-www) Developer
Analytics Tracking live and verified Analytics lead
Page speed Core Web Vitals pass on key templates Developer

Lower your DNS TTL to a short value, such as five minutes, a day or two before launch. This lets you roll back quickly if something breaks. Prepare a rollback plan and agree the exact conditions that would trigger it.

If you are changing domains, set up the new domain in Google Search Console as a property in advance and verify ownership. You will need it for the Change of Address tool.

Step 7: Execute the Launch Day Sequence

Launch day should be calm and scripted. Follow a fixed order so nothing is skipped under pressure.

  1. Freeze content. Stop publishing on the old site so the redirect map stays accurate.
  2. Deploy the new site and switch DNS or the platform cutover.
  3. Activate redirects and confirm they work on production, not just staging.
  4. Remove staging protections and double-check robots.txt and meta robots.
  5. Submit the new XML sitemap in Search Console. For a domain change, also submit the Change of Address request.
  6. Keep the old sitemap submitted for a while so Google discovers the redirects faster.
  7. Spot-check your top 50 URLs by hand, plus key conversion pages.

Do not delete the old site or let the old domain expire. Keep the old domain registered and its redirects active for at least a year. Letting it lapse severs the link equity you were trying to preserve.

If you change domains, also update high-value external profiles you control: Google Business Profile, social accounts, email signatures, directory listings and ad destination URLs. For local businesses, this step is critical, and our local SEO strategy guide explains how consistent business information protects map rankings.

Work with Lucanix

Want a second pair of eyes on your launch plan?

Lucanix reviews redirect maps and pre-launch checks for growing businesses. Get a fixed-price proposal before you flip the switch.

Start a project projects@lucanix.com

Step 8: Monitor Closely in the First 30 Days

The work is not finished at launch. Post-launch monitoring is where you catch problems while they are still cheap to fix. Check data daily for the first two weeks, then weekly through day 90.

Watch these signals in Google Search Console:

  • Page indexing report: look for spikes in “Not found (404)”, “Crawled, currently not indexed” and “Blocked by robots.txt”.
  • Crawl stats: confirm Googlebot is crawling the new URLs and that server response times are healthy.
  • Performance report: compare clicks and impressions against your benchmark, page by page.
  • Sitemaps report: check that submitted URLs are being discovered and indexed.

Expect some turbulence. Rankings often dip 10 to 20 percent in the first one to three weeks as Google reprocesses the site, then recover. A dip beyond that range, or one that does not begin recovering after three to four weeks, signals a real issue.

Re-crawl the live site weekly and compare against your pre-launch baseline. Look for new 404s, redirect chains, missing metadata and pages that dropped out of the sitemap. Check server logs too, since they show exactly which old URLs Googlebot still requests and whether they resolve correctly.

Set up alerts for sudden traffic drops so nobody discovers a problem a month late. If you want to tie recovery to revenue, our guide on how to measure SEO ROI shows how to connect organic performance to business outcomes.

Once the dust settles, move into optimisation. Work through every 404 reported in Search Console and either add a missing redirect or confirm the page was intentionally removed. Prioritise by the number of backlinks and the traffic the old URL used to receive.

Reach out to the owners of your highest-value backlinks and ask them to update their links to the new URLs. Redirects pass most signals, but a direct link is always stronger and removes a dependency. Focus on your top 20 referring domains first. For fresh ideas on earning new links after the move, see our guide to backlink building for small businesses.

Audit your internal links again. Any that still point to old URLs should be updated to the final destination. Check your XML sitemap, canonical tags and hreflang annotations for leftover references to the old structure.

Then document what you learned. Record which URLs were affected, what the traffic curve looked like, how long recovery took and what you would change next time. A written post-mortem turns one migration into institutional knowledge, which matters if you ever move again.

Common Migration Mistakes That Cost Traffic

After running and rescuing many migrations, the same errors appear again and again. Knowing them in advance is half the defence.

  • Launching with a staging robots.txt. A single Disallow: / line can deindex a site within days.
  • Redirecting everything to the homepage. Google treats this as a soft 404, and the page-level equity is lost.
  • Forgetting non-HTML assets. PDFs, images and downloads that earn links need redirects too.
  • Changing too much at once. New URLs, new copy and new design together make diagnosis impossible.
  • Skipping the benchmark. Without baseline data, you cannot prove or locate a loss.
  • Dropping redirects too early. Removing them after a few months throws away accumulated link equity.
  • Ignoring mobile and speed. A slower, heavier new site loses rankings regardless of how clean the redirects are.

Migrations also expose hidden weaknesses, so treat the project as an opportunity to fix technical debt. For ongoing health after launch, a structured website maintenance plan keeps redirects, uptime and technical SEO under watch long after the project closes.

The pattern across all of these is the same: they are process failures, not technical mysteries. A clear owner, a tested redirect map and a written checklist prevent nearly every one.

How Long Recovery Takes and When to Worry

Realistic expectations help you stay calm and act decisively. For a well-executed migration with identical content and clean redirects, most sites see traffic return to baseline within two to eight weeks. Domain changes and large structural changes typically take longer, often three to six months for full stabilisation.

Use these rough benchmarks to judge progress:

Timeframe Healthy sign Warning sign
Week 1 Indexing of new URLs begins; small dip Sharp drop above 40 percent
Weeks 2 to 4 Rankings stabilise and start climbing Continued decline, rising 404s
Months 2 to 3 Traffic at or near baseline Still below 80 percent of baseline
Months 4 to 6 Traffic matches or exceeds baseline Persistent gaps on key pages

If you see a warning sign, diagnose methodically. Compare the affected pages against your baseline crawl, check that redirects resolve, confirm no accidental noindex or canonical errors exist, and test rendering using the URL Inspection tool. Most recoveries come from fixing a small number of specific faults.

A migration is also a chance to improve. Once rankings are stable, you can invest in the upgrades you deliberately deferred: better content, stronger internal linking and faster performance. If your migration moved you into a new CMS, consider how it fits your longer-term plan, for example in our look at headless WordPress versus traditional CMS.

Frequently Asked Questions

Frequently Asked Questions

How long does website migration SEO recovery take?

For a clean migration with matching content and correct 301 redirects, most sites recover within two to eight weeks. Domain changes and large URL restructures can take three to six months to fully stabilise. A temporary dip of 10 to 20 percent in the first few weeks is normal.

Will I lose rankings when I change my domain name?

You will almost always see some volatility, but you do not have to lose rankings permanently. Use page-to-page 301 redirects, submit the Change of Address tool in Google Search Console, update external profiles, and keep the old domain active for at least 12 months.

How many 301 redirects can a site have?

There is no hard limit on the number of 301 redirects. What matters is that each one is accurate, resolves in a single hop and points to a relevant page. Large sites with tens of thousands of redirects migrate successfully every year when the map is well organised.

Should I redesign and migrate at the same time?

It is safer to separate them. Changing platform, URLs, design and copy together creates too many variables, so you cannot tell what caused a drop. If budget forces a combined project, keep content and URL structure as stable as possible and benchmark everything first.

How long should I keep 301 redirects in place?

Keep them for at least 12 months, and indefinitely for URLs with strong backlinks or steady direct traffic. Google has said it may take a year or more to fully process a site move, and removing redirects early can cost you the link equity you were trying to preserve.

Do I need to submit a new sitemap after migrating?

Yes. Submit the new XML sitemap in Google Search Console on launch day, and keep the old sitemap submitted for a while so Google can discover your redirects faster. Make sure the new sitemap lists only canonical, indexable URLs that return a 200 status.

Work with Lucanix

Plan your migration with a team that protects your rankings

Book a free consultation or request a fixed-price proposal and Lucanix will map your redirects, test your launch and monitor recovery from day one.

Book a free consultation projects@lucanix.com