Website Migration SEO: How to Protect Your Rankings

You’ve worked on a new website, and it’s WAY better than the last one. But as soon as you launch, your search engine rankings fall off a cliff. It’s a story as old as… search engines.

And some sort of rankings impact is unavoidable. But there’s also no reason why your rankings should drop through the floor. If your migration has been thorough, any rankings dip should recover pretty quickly, before returning to or even surpassing previous levels.

In this guide, we'll cover why website migrations impact search rankings, why it so often goes wrong, why it doesn’t have to, and - most importantly - how you can protect your rankings with a structured approach to migration.

But first, a bit of background…

 

What is a Website Migration?

In brief, a website migration is a broad term that encompasses any significant change to your website that affects how it’s structured, accessed, or presented. 

Website migrations come in many forms. And, as such, the SEO implications vary significantly between the different types. 

What doesn’t change, however, is the thought and planning you should put into each and every migration. 

It may sound obvious, but SEO should be part of the conversation with any website migration. And it so often isn’t, even at enterprise-scale businesses. Trust us; we’ve seen it firsthand.

💡 Further reading: Migrating from WordPress to Craft CMS: A Complete Guide

 

The Different Types of Website Migration

As mentioned above, identifying the type of migration you're planning is the first step to understanding the level of SEO risk involved.

 

Domain Migration

Moving to a new domain - or making URL changes like switching from HTTP to HTTPS - is one of the higher-risk migration types. Your existing domain has built up its own authority over time. 

Links from other websites, your ranking history, and trust signals with search engines like Google all impact that authority. Your aim when you migrate is to preserve as much of that authority in the new domain as possible.

 

Platform or CMS Migration

Switching CMS - from WordPress to Craft CMS, for instance - often results in URL structure changes. That makes redirects (and getting them right) essential. There are other elements it can affect as well: pagespeed, crawlability, and metadata management.

 

Structural Redesign

Even if your domain and platform stay the same, a significant restructure of your site's navigation or URL structure counts as a migration. Pages move, URLs change, and content gets consolidated. All of these things have SEO implications you should be wise to.

 

Content Migration

Content migration encompasses content consolidation, page removal, or merging sections of your website. These are typically lower risk than a full platform switch, but a plan is still advised. And that’s particularly the case if you’re making changes to pages that rank well.

 

Why Migrate Your Website?

As you can see, there are any number of reasons why you might need to undertake a website migration. None of them should be taken lightly. At the end of the day, all migrations are driven by a business need:
 

• Moving to a new domain
• A CMS that no longer suits your needs
• Performance issues
• Business ambitions that require scale
   

None of those are bad reasons to migrate. The point isn't to avoid migrations; it's to do them properly. Because handled well, a migration shouldn't just protect your existing rankings. It should set you up to improve on them.

 

Why Do Website Migrations Impact SEO?

Google - other search engines are available - spends a lot of time getting to know your website. How it performs, what content you’ve got, and how good that content is; everything it needs to know to rank your website. Migrations tend to disrupt that process.

 

Changes to URLs

An example of this, and likely the most common culprit, is changes to URLs. If a page that previously lived at /services/web-design has moved - or no longer exists - search engines could lose track of it. Without the correct redirects in place, the ranking history and authority attached to that URL simply disappear.

 

Backlinks

Then you need to consider backlinks. These are links from other websites that point to your content. They are one of the most valuable signals in SEO. Instead of saying “look at me, I’m great”, they say “look at that guy, he’s great” - a far more compelling recommendation.

If those links now point to pages returning a 404 error because the URLs have changed, that value is gone. And unlike a rankings dip, broken backlinks don't automatically recover.

 

Content Changes

Similarly with content changes. In the rush to get a new site live, or even just as a matter of course, content can get rewritten, shortened, or even lost. If a page ranked well for a particular search term, significant content changes can affect that ranking quickly and without warning.

 

Technical Issues

As a final example, technical issues on your new platform can compound issues. Underwhelming page speed, crawl errors, and broken internal links can come together to make the job of search engines that bit more difficult. 

To add to that, many of these technical considerations are direct ranking factors themselves. You need to make sure that your new website isn’t just fancy looking, but also quick out of the blocks and optimised to compete.

 

How Long Does SEO Recovery Take After Migration?

How long is a piece of string? The only honest answer here is: it depends.

For a well-planned, managed, and executed migration - redirects are done properly, content is preserved, and technical issues are mitigated - the impact should be minimal. Recovery often begins within weeks, but full stabilisation can take several months, especially for large or complex sites.

For a poorly managed migration where SEO simply hasn’t been considered and there’s no real plan in place, recovery can take months. Or years. Or never happen. In the worst cases, where content has been lost, backlinks have all broken, and redirects haven’t been put in place, rankings may never recover. 

It’s worth knowing that none of this is immediate. Google won’t process your migration all at once. It will recrawl and reassess your site over time, which is why recovery tends to be gradual (even after a great migration), rather than an overnight miracle. Be patient.

As we said at the very top, it’s pretty much impossible for a migration to have no negative impact on search rankings. Disruption is inevitable. And you will find things you missed. Your objective is to minimise the dip when it happens and to hasten recovery.

 

SEO Migration Checklist

Hopefully, it’s now clear that having a structured plan in place reduces the SEO risks associated with migration and speeds up recovery. Every migration is different, but the steps below cover the core of protecting your rankings.

 

Before Migration

Action
Crawl your existing site and export all indexable URLs
Benchmark current rankings, organic traffic, and indexed pages
Identify your highest-value pages (traffic, backlinks, conversions)
Audit your backlink profile to identify the most valuable pages
Create a full URL mapping spreadsheet (old URLs → new URLs)
Back up your site files, database, and existing sitemap
Ensure all key content, metadata, canonicals, and structured data will migrate intact
Confirm robots.txt rules and indexing settings for launch
Agree on a clear go-live timeline with developers and other stakeholders
Verify access to Google Search Console and analytics platforms (GA4)

 

During Migration
 

Action
Block search engines from crawling the staging environment
Implement 301 redirects for every changed or removed URL
Update internal links to point directly to new URLs (avoid redirect loops)
Check titles, meta descriptions, canonicals, and schema have migrated correctly
Test page speed, Core Web Vitals, and mobile performance on the new platform
Confirm the new site is running on HTTPS
Thoroughly test redirect logic before you launch

 

After Migration
 

Action
Submit your updated XML sitemap in Google Search Console
Crawl the new site immediately and resolve any errors
Cross-check live URLs against your pre-migration crawl
Monitor Google Search Console closely for crawl errors and indexing changes
Track rankings and organic traffic weekly for the first three months
Identify high-value backlinks still pointing to old URLs and update
Monitor indexation to ensure key pages are being discovered

 

Before You Migrate: The Groundwork

Doing the proper groundwork before a migration is where many projects stumble. And it’s difficult. SEO is often an afterthought for teams that are too busy or don’t necessarily have 

 

Crawl & Benchmark

You can’t measure the impact of anything without a benchmark. That means crawling your existing site - we recommend Screaming Frog - to capture every live URL. You’ll also want to keep track of current rankings and performance levels. 

 

Map your URLs

Many migrations involve URL changes. Assuming that’s the case, you’ll want to map every URL in a spreadsheet before anything changes. Trust us, it’s easier this way. 

Don’t over-complicate it. Put every current URL on the left and its new destination on the right. Every URL that changes needs a new destination. If you’re removing a page, redirect it to the closest equivalent. Try to avoid sending everything to your homepage. 

 

Audit Your Backlink Profile

If you’re serious about SEO, you’ll already have a tool like Ahrefs or SEMrush. Use one of these to export your existing backlink profile. Identify the pages that have the most valuable external links pointing to them.

This process helps you identify the highest-priority pages when it comes to redirection. You don’t want these pointing to a 404. Give them some extra love. 

 

During the Migration: Getting it Right

Hopefully, you’ve absolutely nailed the groundwork by this point, and the plan is solid. Now it’s over to your development team. But there are a few key points to consider.

 

Block Search Engines from Staging

Your staging site should be invisible to search engines. If Google ends up crawling your staging site, it’s possible you’ll end up with duplicate content issues. 

The minimum requirement is a robots.txt disallow. But you can also add password protection for extra safety. If you make sure your solution is in place from the start, there’ll be no issue.

 

Implement 301 Redirects

This is the big one. Remember that mapping document you made? Well, it’s about to come in handy. A 301 redirect tells search engines that a page has permanently moved to a new location. It passes the majority of the ranking authority from the old URL to the new one.

Keep an eye out for redirect chains - where one URL redirects to another, which redirects to another, etc… - which should be avoided. Redirect loops, where two pages redirect to each other, will break the page entirely. Test before launch. 

 

Verify Your Metadata

Before migration is complete, every page on the new site should have its title tag, meta description, and canonical tag intact. 
It's surprisingly common for metadata to get dropped or defaulted during a platform migration. Different platforms handle metadata differently; there’s no guarantee everything will carry over automatically.

 

After the Migration: Monitoring & Recovery

Don’t forget about all of this once your site is live. There are still a few crucial bits and pieces to get done. And, no doubt, you’ll pick up a few things you missed the first time round. 

 

Submit Your Sitemap

The first thing to do is to submit an updated XML sitemap to Google Search Console. This tells Google something has changed and gives it a clear map of what needs to be indexed.

And GSC isn’t a one-and-done either. It’s actually a very useful website management tool. It’s worth checking daily, especially in the first few weeks after launch. For overall performance, but also for crawl errors, indexing issues, or any sudden changes.

 

Crawl Your Site

Don’t wait for Google to crawl your website and find errors. Do ot yourself. You can use tools like Screaming Frog - an SEO favourite - to catch any erroneous 404 errors, broken links, or missing metadata. 

Cross-reference your post-launch crawl against your pre-migration URL list. Everything that should be live should be live. Everything that's moved should have a redirect in place.

 

Should You Migrate Your Website Yourself?

Technically speaking, with enough research, learning and time, you absolutely can handle most migrations yourself. But there’s potentially a lot of complexity involved, and there’s even more at stake if it goes wrong.

The main challenge is that there’s a lot going on and there are a lot of moving parts involved. Our usual recommendation is to work with a partner if possible. You may have the expertise in-house, but it’s definitely worth the investment of working with someone who has done it all before.

Just remember that the cost of a migration going wrong will almost always exceed the cost of getting it right the first time.

This is something we’ve done many times over the years, and we have specific expertise when it comes to migrations involving Craft CMS. So, if you do want to explore migrations but need some support, just reach out.