SEO Migration Checklist: How to Move a Website Without Losing Rankings

Moving a website can be exciting. You may be changing your domain, switching hosting providers, moving from one CMS to another, restructuring URLs, or launching a completely redesigned website.

But there is one question every website owner should ask before pressing the launch button:

What happens to my Google rankings?

A website migration without proper SEO planning can result in broken URLs, lost backlinks, indexing problems, duplicate pages, and significant drops in organic traffic.

The good news is that most migration-related SEO problems are preventable.

The key is to treat your website migration as an SEO project as well as a technical project.

Use this SEO migration checklist before, during, and after your website move.

What Is an SEO Migration?

An SEO migration is the process of moving a website while protecting its existing search engine visibility, URLs, content, backlinks, and other SEO signals.

A migration can involve:

Changing the domain name
Moving from HTTP to HTTPS
Changing your CMS
Moving to a new hosting provider
Changing URL structures
Redesigning the website
Combining multiple websites
Moving from one subdomain to another
Changing website architecture

Some migrations involve several of these changes simultaneously.

The more elements you change at once, the more carefully the migration needs to be planned.

Before Migration: Create Your SEO Backup

Before touching the live website, document what is already working.

This is one of the most important steps in the entire process.

Export or record:

Top organic landing pages
Ranking keywords
Organic traffic
Indexed URLs
Existing redirects
Backlinks
Title tags
Meta descriptions
H1 headings
Canonical URLs
XML sitemap
Robots.txt
Internal links
Structured data
Important images
Conversion pages

Google Search Console and your analytics platform can help you identify pages that currently generate search traffic.

Don’t assume every important SEO page is obvious from your navigation menu.

A blog post that receives thousands of monthly visitors may be more valuable from an SEO perspective than a page that receives very little traffic.

Build an Old-to-New URL Mapping

If URLs are changing, create a complete URL mapping before the migration.

For example:

Old URL	New URL	Redirect
/seo-services	/seo-services-usa	301
/local-seo	/local-seo-services	301
/wordpress-seo	/wordpress-seo-services	301

Every important old URL should have a clear destination.

The ideal destination is the closest relevant equivalent page, not automatically the homepage.

A 301 redirect tells search engines that the old URL has permanently moved.

Avoid redirect chains such as:

Old URL → Page A → Page B → Final Page

Whenever possible:

Old URL → Final Page

Google recommends permanent redirects such as 301 or 308 for permanent URL changes and advises avoiding unnecessary redirect chains.

Crawl the Existing Website

Before migration, crawl the old website and save the results.

Record:

Status codes
URLs
Page titles
Meta descriptions
H1s
Canonicals
Word counts
Internal links
Images
Indexability

This gives you a reference point.

After the migration, crawl the new website again and compare the two versions.

The comparison can reveal problems that may otherwise remain hidden.

Check Your New Website on Staging

Never launch a major migration without testing the new website first.

Your staging website should be checked for:

Indexing

Make sure accidental noindex directives aren’t going to remain after launch.

Canonicals

Confirm that canonical tags point to the correct preferred URLs.

Robots.txt

Check that important sections aren’t accidentally blocked.

Internal links

Make sure links point to the new URLs rather than outdated addresses.

Navigation

Important SEO pages should remain accessible through a logical site structure.

Structured data

Check whether schema markup from the old website has been removed or broken.

Don’t Delete Valuable Content Without a Reason

One of the biggest migration mistakes is combining a technical migration with aggressive content removal.

A business may decide:

“We’re redesigning the website, so let’s remove all the old pages.”

That can eliminate pages that rank for valuable long-tail searches.

Before deleting content, examine:

Organic traffic
Rankings
Backlinks
Conversions
Search impressions
Business relevance

If an old page has SEO value, consider improving or consolidating it rather than simply deleting it.

Implement 301 Redirects

Once your URL mapping is finalized, implement the redirects before or at the time of launch.

Test them individually and in bulk.

Check that:

Old URL → 301 → Correct new URL

Not:

Old URL → 404

and not:

Old URL → Homepage

A redirect is especially important for URLs that have earned backlinks.

Otherwise, valuable external links may continue pointing toward dead pages.

Update Internal Links

Redirects can preserve old URLs, but your new website shouldn’t depend on them unnecessarily.

Update internal links so they point directly to the new URLs.

Check:

Main navigation
Footer links
Blog articles
Category pages
Service pages
Product pages
Breadcrumbs
Related-content sections

This improves crawling efficiency and creates a cleaner website architecture.

Update Your XML Sitemap

Your new XML sitemap should contain the current canonical URLs that you want Google to discover.

Don’t leave old URLs in the sitemap after migration.

For example, if:

/old-seo-page/

has moved to:

/seo-services/

the new sitemap should reference the new URL.

Submit the updated sitemap through Google Search Console after launch.

Monitor Google Search Console Immediately

Your work doesn’t end when the new website goes live.

The first few days and weeks are particularly important.

Monitor:

Indexing
Page indexing errors
404 errors
Redirect errors
Crawled but not indexed pages
Search impressions
Clicks
Average position
Sitemap status

Use URL Inspection to test important pages individually.

Don’t wait until organic traffic has collapsed before checking Search Console.

Monitor Rankings and Traffic

Compare post-migration performance against your pre-migration baseline.

Look at both overall and page-level data.

For example:

Before migration

Organic traffic: 50,000/month

After migration

Organic traffic: 39,000/month

That tells you something has changed, but it doesn’t tell you why.

Now examine individual landing pages.

You might discover that:

One category lost 70% of traffic
Blog traffic remained stable
Service pages lost rankings
Several old URLs became 404s
One important directory wasn’t indexed

Page-level analysis makes troubleshooting much easier.

Keep the Old Website Data

Don’t immediately delete your migration records.

Keep:

Old URL list
New URL list
Redirect map
Old sitemap
New sitemap
Crawl reports
Ranking reports
Analytics data
Search Console data

You may need these records weeks or months later when investigating ranking changes.

Avoid Making Multiple Major Changes After Launch

If your traffic drops after migration, resist the temptation to immediately rewrite every page.

First identify the cause.

Was it:

Redirect failure?
Lost content?
Incorrect canonical?
noindex?
Robots.txt?
Broken internal links?
Poor server performance?
URL restructuring?
Indexing delay?

Fix technical migration problems first.

Then address content and ranking improvements.

SEO Migration Checklist

Before launching, make sure you can check every box:

☐ Export important URLs
☐ Record rankings and organic traffic
☐ Identify high-value landing pages
☐ Export backlink information
☐ Crawl the old website
☐ Crawl the staging website
☐ Create an old-to-new URL map
☐ Implement 301 redirects
☐ Test redirects
☐ Check canonical tags
☐ Check robots.txt
☐ Check noindex directives
☐ Preserve important content
☐ Update internal links
☐ Check structured data
☐ Create the new XML sitemap
☐ Test mobile usability
☐ Test page speed
☐ Launch the website
☐ Submit the new sitemap
☐ Monitor Google Search Console
☐ Monitor rankings and organic traffic
☐ Fix crawl and indexing issues quickly

Final Thoughts

A successful website migration should be almost invisible to users—and as seamless as possible for search engines.

The biggest mistake is treating migration as something that happens on launch day.

SEO migration starts before development and continues after launch.

By documenting your existing SEO performance, mapping URLs, implementing proper redirects, preserving valuable content, testing technical settings, and monitoring Google Search Console, you can dramatically reduce the risk of losing organic visibility.

And remember: don’t measure the success of a migration by how good the new website looks. Measure it by whether the new website improves the user experience without sacrificing the search visibility you’ve already earned.