Website Migration SEO Checklist: How to Move Without Losing Rankings

Website migrations are absolutely brutal if you mess them up. One day you’re ranking nicely for your key terms, the next you’ve vanished from Google entirely because someone forgot to map the redirects properly. We’ve seen businesses lose years of organic growth in a single weekend when they tried to handle a rebrand or platform switch without proper planning. Whether you’re moving domains, changing CMS platforms or merging sites together, the technical complexity can be overwhelming. That’s why working with a team that understands professional SEO services often means the difference between keeping your rankings and starting from scratch.

Think of this as your migration bible. We’ll cover everything from initial planning through to the weeks after launch when you’re frantically checking Google Search Console for drops in traffic.

What Counts as a Website Migration?

Here’s the thing about migrations: they’re not all created equal. Moving to a new host while keeping everything else identical? That’s pretty straightforward (assuming your developer knows what they’re doing with DNS). But combine a domain change with a complete platform overhaul and new URL structure? You’re looking at a completely different beast altogether.

Stack too many changes together and you’re asking for trouble. A simple hosting move might cause a brief blip if the DNS propagation goes wonky, but most sites recover within days. Change your domain, rebuild on WordPress instead of Shopify, restructure your entire URL hierarchy and launch new page templates all at once though and you’ve got multiple failure points where your rankings can disappear.

Pre-Migration Planning: The Foundation of a Successful Move

Most migrations fail because people skip the boring stuff at the start. You can’t just wing it and hope everything works out fine when you flip the switch. Get a proper handle on where your site stands right now before you change a single thing.

Fire up Ahrefs Site Audit or Screaming Frog and crawl every corner of your existing site. What you’re after is a complete map of URLs, status codes, canonicals, meta tags and how everything links together internally. Save that data somewhere safe because you’ll need it later to check if anything went sideways.

Google Search Console becomes your best friend here. Pull out at least six months of performance data so you know exactly which keywords you’re ranking for, what content brings in the traffic and any featured snippets you’ve managed to grab. Without this baseline, you’re flying blind when it comes to measuring what the migration actually did to your visibility.

Which pages actually matter to your business? The ones pulling serious organic traffic, hoarding backlinks or converting visitors into customers need your full attention. These aren’t the pages where you experiment or take shortcuts with redirects. Mess up the URL structure on your money pages and you’ll feel it in the traffic reports for months. A solid technical SEO strategy here keeps your most important content safe during the move.

Redirect Mapping: The Most Critical Technical Step

Get this wrong and your migration’s dead in the water. Every single URL that’s currently driving traffic, earning backlinks or sitting in Google’s index needs a proper 301 redirect to its new home. You can’t wing this bit or do it “roughly” and hope for the best because search engines need that crystal-clear roadmap showing exactly where everything’s moved.

Your redirect map lives in a spreadsheet with old URLs in one column and new URLs in the next. But on bigger sites, we add page titles, traffic numbers, backlink counts and priority ratings so we know which redirects to tackle first when testing starts.

Whatever you do, don’t just point everything at your homepage. Google treats that exactly like a soft 404, which defeats the entire point. Match each old URL to its closest equivalent on the new site and when there’s no perfect match? Send it to the most relevant category or section page you’ve got.

Apache servers handle redirects through the .htaccess file. Here’s what individual 301 redirects and pattern-based redirects actually look like in practice.

# Individual page redirects
Redirect 301 /old-page-url https://newsite.co.uk/new-page-url
Redirect 301 /blog/old-post https://newsite.co.uk/insights/new-post

# Pattern-based redirect for blog section
RedirectMatch 301 ^/blog/(.*)$ https://newsite.co.uk/insights/$1

Nginx servers work the same way but with different syntax. Every old URL still needs somewhere to go. When you’re dealing with massive sites (think thousands of pages), server-level regex patterns can handle bulk redirects without making you want to tear your hair out. Google’s own documentation on 301 redirects breaks down all the technical bits you need to know.

Technical Checklist: What to Verify Before Launch

Right before you go live, there’s a checklist of technical bits that absolutely can’t be skipped on your staging site.

• Verify all 301 redirects are working correctly by testing a sample of high-priority URLs
• Check that the new site has a valid XML sitemap and submit it to Google Search Console
• Confirm robots.txt is not blocking critical pages or resources
• Ensure canonical tags on every page point to the correct new URL
• Validate that all meta titles and descriptions have been carried across accurately
• Test internal links to make sure none point to old URLs that would create redirect chains
• Check structured data markup is present and valid on the new site
• Confirm HTTPS is enforced site-wide with no mixed content warnings
• Verify hreflang tags if the site serves multiple languages or regions
• Run a full crawl of the staging site to catch broken links and missing pages

Check your robots.txt file allows search engines full access to the new site. We’ve seen it happen more times than we’d like to admit, someone leaves a staging robots.txt file that blocks everything and suddenly Google can’t see any of your content. Here’s what a proper production robots.txt should look like.

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://yoursite.co.uk/sitemap_index.xml

And while you’re at it, make sure your web design keeps the internal linking structure clean and logical. Migrations give you a perfect chance to fix messy site architecture, but that only works if you’ve actually planned the new structure properly and updated all those internal links to match.

Launch Day: Executing the Migration

Launch day timing can make or break your migration. Peak traffic periods are your enemy here, schedule for a Tuesday or Wednesday morning instead. That gives your team the entire working week to spot problems and fix them before everyone disappears for the weekend. And make sure everyone’s actually available (development team, SEO specialists, hosting support) because you’ll need them all on standby.

First priority after going live? Double-check those redirects are actually working in production. Staging environments lie sometimes. Pick a decent sample of your URL mappings and test them manually, visit the old addresses, confirm they hit the right new pages with proper 301 status codes. Moz’s redirect guide walks you through verifying redirect chains properly.

Get that new XML sitemap submitted through Google Search Console straight away. Changed domain completely? Use the Change of Address tool to tell Google what’s happened, most people forget this step but it speeds up the transfer of ranking signals massively. Don’t ignore Bing Webmaster Tools either.

Server logs become your best friend for the next 48 hours. You’re hunting for 404 error spikes, weird redirect chains or crawl errors that scream “missed redirect”. Google Search Console’s URL Inspection tool shows you exactly how Google’s seeing individual pages on the new site, which beats guessing every time.

Post-Migration Monitoring: The First 90 Days

Launch day isn’t the finish line (though it might feel like it after weeks of prep work). Those first 90 days are when you’ll catch the problems that matter before they turn into proper headaches. Rankings will jump around a bit in the early weeks, but don’t panic. Google’s just doing its thing, recrawling everything and figuring out where your content lives now.

Daily Search Console checks for the first week, then scale back to twice weekly. After month one? Weekly monitoring does the job unless something’s clearly gone wrong and needs your attention.

What should you actually be watching? Organic traffic per landing page, keyword positions for terms that matter to your business, Search Console crawl data, indexed page counts and whether your backlinks are still pointing where they should. Semrush Position Tracking handles the before-and-after ranking comparisons without you having to export dozens of spreadsheets.

Pages dropping in rankings after migration? Start with the redirects. Are they actually working and pointing to the right place? Then check whether the new page content matches what was there before. Change the URL and the content at the same time and Google might decide you’ve created something completely new rather than just moved the original.

Common Mistakes That Cause Rankings to Drop

Migrations go wrong. That’s just the reality of moving websites, no matter how much planning you’ve done beforehand. But here’s what we’ve noticed after handling dozens of these projects, the same handful of mistakes keep popping up again and again.

Missing redirects will absolutely kill your rankings and it happens more often than you’d think. Sure, everyone remembers to redirect their main pages, but what about that blog post from 2019 that still gets 500 visits a month? Or those campaign landing pages buried three levels deep in your site structure. PDF downloads, old product pages, forgotten category pages, they all need redirects if they’re bringing in any organic traffic. We always run a full crawl of the old site first, then check every single URL against our redirect list.

Watch out for redirect chains too. Page A redirects to page B, which redirects to page C, which finally lands on page D, and suddenly Google’s having to make three extra requests just to reach your content. Each hop weakens the link value that gets passed through, plus it slows down crawling. Search Engine Journal backs this up, keep your redirects to one hop whenever possible.

Don’t change everything at once. Moving your domain is already a big signal to search engines that something’s changed. Start rewriting all your content at the same time and you’ve given Google almost nothing to work with when it’s trying to figure out if your new pages match the old ones. Get the migration sorted first, wait for rankings to settle, then tackle content improvements.

Those external backlinks you’ve earned over the years? They’re pointing at your old URLs right now. Without proper redirects, all that ranking juice just vanishes (and trust me, watching your traffic tank because of broken backlinks hurts). Once you’re live, dig into your backlink profile and contact the sites linking to your most valuable pages. Ask them to update their links to point directly to your new URLs. Sure, redirects will handle this automatically, but direct links beat redirected ones every single time.

When to Bring in Professional Support

Moving a basic brochure site to new hosting without changing URLs? Your team can probably handle that. But migrations involving domain changes, platform switches or major restructuring are a different beast entirely.

Professional migration teams don’t just map your redirects and disappear. They’ll crawl your existing site, plan the technical approach, monitor everything post-launch and fix problems when they surface. And they actually talk to your developers throughout the process, which prevents the usual miscommunication disasters we see during CMS migrations. If you’re working with a WordPress development team, having SEO expertise baked in from day one makes everything run smoother.

Website migrations don’t have to tank your rankings. Get your planning right, map those redirects properly, execute the technical side without cutting corners and monitor everything like a hawk afterwards. This checklist gives you the framework to migrate without losing the organic visibility you’ve worked so hard to build.