Site Migration SEO Checklist: Protect Your Rankings

Why Site Migrations Are High-Risk for SEO

A site migration is one of the most consequential events in a website's lifecycle. Whether you are moving to a new domain, changing your CMS, restructuring URLs, or switching hosting providers, the potential for organic traffic loss is significant. Google's own documentation acknowledges that temporary ranking fluctuations are expected during migrations – but "temporary" can become permanent if the migration is handled poorly.

We have seen businesses lose 30–60% of their organic traffic overnight because of avoidable mistakes: broken redirect chains, missing canonical tags, orphaned pages, or simply failing to notify Google of the change. The good news is that with rigorous planning and execution, you can migrate your site without sacrificing the rankings you have spent years building.

This checklist covers every phase of a site migration – from initial planning through to post-launch monitoring – so you can move with confidence.

Pre-Migration Planning

Define the Scope of the Migration

Before anything else, you need to be absolutely clear about what is changing. Migrations come in many forms:

Domain change – moving from one domain to another (e.g., oldbrand.co.uk to newbrand.co.uk)
Protocol change – HTTP to HTTPS (still relevant for some legacy sites)
CMS change – WordPress to Shopify, Magento to WooCommerce, or similar
URL restructure – changing your site architecture and URL patterns
Design overhaul – new templates with potential content and internal linking changes
Hosting change – moving to a new server or CDN

Each type carries different risks. A simple hosting change with no URL changes is relatively low-risk. A combined domain change, CMS migration, and URL restructure is about as high-risk as it gets. Document exactly what is changing and what is staying the same.

Benchmark Your Current Performance

You cannot measure the impact of a migration without a clear baseline. Before you touch anything, record the following:

Total organic sessions (monthly, for the last 12 months)
Top landing pages by organic traffic (at least the top 100)
Current keyword rankings for your most valuable terms
Total indexed pages in Google Search Console
Crawl stats from Search Console
Backlink profile – which pages have the most external links
Core Web Vitals scores for key page templates
Conversion rates from organic traffic

Export all of this data and store it somewhere safe. You will need it for comparison after launch.

URL Mapping and Redirect Strategy

Crawl the Existing Site

Use a crawler like Screaming Frog to generate a complete inventory of every URL on your current site. This includes HTML pages, images, PDFs, and any other assets that might have external links pointing to them. Do not rely on your sitemap alone – it often misses orphaned pages, non-canonical URLs, and legacy content that still receives traffic.

Build a Comprehensive URL Map

Create a spreadsheet that maps every old URL to its corresponding new URL. This is the single most important document in the entire migration process. For each URL, record:

The old URL (full path)
The new URL (full path)
The redirect type (almost always 301 – permanent)
Monthly organic sessions to that page
Number of external backlinks
Notes on any content changes

Pay particular attention to your highest-traffic and highest-authority pages. These are the ones where a broken redirect will cause the most damage.

Implement 301 Redirects Correctly

Every old URL must 301 redirect to the most relevant equivalent on the new site. Key rules:

Redirect to equivalent content – do not redirect everything to the homepage. Google treats this as a soft 404.
Avoid redirect chains – if page A already redirects to page B, and now page B is moving to page C, update the redirect so A goes directly to C.
Use server-side redirects – 301 redirects implemented at the server level (htaccess, nginx config, or your hosting platform's redirect tool). Never rely on JavaScript redirects or meta refresh tags.
Handle trailing slashes consistently – decide whether your new URLs use trailing slashes or not, and redirect accordingly.
Redirect old sitemaps – if your sitemap URL is changing, redirect the old sitemap URL to the new one.

Content Audit Before Migration

A migration is an excellent opportunity to audit your content. Not every page deserves to make the journey to the new site.

Keep and migrate – pages with organic traffic, backlinks, or clear business value
Consolidate – merge thin or duplicate pages into stronger, more comprehensive pages
Remove and redirect – outdated or low-value pages that should redirect to a relevant alternative
Remove and 410 – truly irrelevant content with no traffic or links (return a 410 Gone status)

For any page you remove, ensure it has a proper redirect if it has any backlinks or residual traffic. The goal is to preserve link equity across the migration.

Staging Environment Testing

Build and Test on Staging First

Never migrate directly to production. Build the new site on a staging environment and test exhaustively before going live. Your staging checklist should include:

Robots.txt – ensure staging is blocked from search engines (noindex, disallow). You will need to remove these blocks before launch.
Crawl the staging site – check for broken links, missing pages, incorrect canonical tags, and missing metadata.
Compare page-by-page – verify that your top 50–100 pages have correct titles, meta descriptions, H1 tags, and on-page content.
Check structured data – validate JSON-LD and other schema markup on key templates.
Test internal links – ensure navigation, footer links, breadcrumbs, and in-content links all point to the correct new URLs.
Verify hreflang tags – if you have international versions of your site.
Test page speed – compare Core Web Vitals between old and new templates.

Test Redirects Before Launch

Upload your redirect rules to staging and test a significant sample – ideally all of them, but at minimum your top 200 pages by traffic and backlinks. Verify that each redirect returns a 301 status code and lands on the correct destination.

DNS and Hosting Considerations

If you are changing hosting providers or DNS configuration as part of the migration, plan for propagation time. DNS changes can take 24–72 hours to fully propagate worldwide, during which time different users may see different versions of your site.

Lower your TTL – reduce the Time To Live on your DNS records a few days before migration. This means changes propagate faster.
Prepare SSL certificates – ensure HTTPS is configured and tested on the new server before you switch DNS.
Check server capacity – your new hosting environment should handle at least the same traffic levels as the old one, ideally more.
Set up CDN – if you are using a CDN like Cloudflare, configure it before switching DNS.

Launch-Day Checks

When it is time to go live, work through this checklist methodically:

Remove all noindex tags and staging robots.txt rules
Verify the production robots.txt is correct and allows crawling
Submit the new XML sitemap to Google Search Console
If changing domains, use the Change of Address tool in Search Console
Test a sample of redirects on the live site – confirm 301 status codes
Check that canonical tags on the new site point to the correct URLs
Verify Google Analytics and any other tracking is firing correctly
Check that forms, checkout flows, and other critical user journeys work
Test on multiple devices and browsers
Request indexing for your most important pages in Search Console

Post-Migration Monitoring

Google Search Console

Search Console is your most important tool in the weeks following a migration. Monitor the following daily:

Index Coverage report – watch for spikes in errors, particularly 404s, soft 404s, and redirect errors
Performance report – compare clicks and impressions to your pre-migration baseline
URL Inspection tool – check individual pages to confirm Google is crawling and indexing the new URLs
Crawl Stats – verify that Googlebot is crawling the new site at a healthy rate
Sitemaps report – confirm your new sitemap has been processed and pages are being discovered

Analytics Monitoring

In Google Analytics (or your analytics platform of choice), set up daily monitoring for:

Total organic sessions – compare week-over-week and year-over-year
Landing page performance – are your top pages still receiving traffic?
Bounce rate changes – a sudden spike may indicate content or UX issues
Conversion rates – ensure the migration has not broken your conversion funnels

Crawl Error Monitoring

Run a fresh crawl of your site one week after launch using a tool like Screaming Frog. Compare the results against your pre-migration crawl. Look for:

Pages returning 404 or 500 errors
Redirect chains or loops
Pages with missing or incorrect canonical tags
Orphaned pages with no internal links
Broken internal links throughout the site

Common Mistakes That Cause Traffic Drops

After supporting hundreds of site migrations, we see the same mistakes repeatedly:

Redirecting everything to the homepage – this signals to Google that the original pages no longer exist. Always redirect to the most relevant equivalent page.
Forgetting to redirect non-www or HTTP versions – ensure all URL variants redirect correctly to the canonical version.
Leaving noindex tags on the live site – this is more common than you might think, especially when staging configurations are copied to production.
Changing content significantly alongside the migration – if Google sees a different URL and different content, it may treat the page as entirely new rather than a moved page. Migrate first, then make content changes gradually.
Not updating internal links – relying solely on redirects for internal navigation creates unnecessary redirect hops and dilutes link equity.
Ignoring backlinks – if your highest-authority pages do not have proper redirects, you lose the link equity those backlinks provided.
Removing pages without redirects – any page with traffic or backlinks needs a redirect, even if you are not carrying the content forward.

Recovery Timeline Expectations

Even with a flawless migration, expect some fluctuation in the first few weeks. Google needs time to recrawl, reprocess, and reconsolidate signals for your new URLs. A typical recovery timeline looks like this:

Week 1–2 – initial dip in traffic as Google discovers and processes changes. This is normal.
Week 3–4 – traffic begins to stabilise as Google indexes the new URLs and consolidates redirect signals.
Month 2–3 – full recovery for most sites, assuming no major issues. High-authority, well-established sites often recover faster.
Month 3–6 – for large sites (10,000+ pages) or domain changes, full recovery can take longer.

If you are still seeing significant traffic loss after 4–6 weeks, something is wrong – likely a redirect issue, a canonicalisation problem, or a content change that Google has not responded well to. At that point, a thorough migration SEO audit is essential.

Get Expert Support for Your Migration

Site migrations do not have to be stressful. With the right planning, execution, and monitoring, you can protect your organic traffic and even improve it. If you are planning a migration and want expert guidance from a team that has managed hundreds of successful transitions, get in touch with Dynamically today. We will help you move without losing ground.