Site Migration SEO Checklist: Don’t Lose Traffic During Your Move

A botched site migration can vaporize your organic traffic overnight. This comprehensive site migration SEO checklist provides a step-by-step framework for technical SEOs to execute a flawless move.

What Is a Site Migration and Why Does It Terrify SEOs?

Site migrations are the digital equivalent of open-heart surgery, performed by a marketing team, with the lights off. They are high-stakes, high-risk projects that can—and often do—go catastrophically wrong, erasing years of SEO equity in a single afternoon.

A ‘site migration’ is a broad term for any event where a website undergoes substantial changes to its location, platform, structure, content, or design. This could be a move from HTTP to HTTPS, a domain name change, a CMS replatforming, or a major content and URL restructuring.

The risk is simple: if Google can’t understand the ‘move,’ it will treat the new site as a brand-new entity, devoid of the authority and history you’ve painstakingly built. A solid site migration SEO strategy isn’t a ‘nice-to-have’; it’s the only thing standing between you and a traffic nosedive.

This checklist is your framework. It’s a battle-tested process for technical SEOs who prefer data over panic. Follow it, and you might just get through this with your traffic—and your job—intact.

The Pre-Migration Phase: Your Comprehensive Site Migration SEO Blueprint

If you get this phase right, you’ve done 80% of the work. The pre-migration phase is all about meticulous data collection and planning. Do not skip a single step.

First, you must establish a benchmark. This is your ‘before’ picture, the source of truth against which you will measure the success or failure of the entire project. You cannot prove you didn’t break something if you don’t have proof of how it worked before.

Start by crawling your entire existing site. Use a robust crawler like ScreamingCAT to get a complete inventory of every URL. Export everything: status codes, page titles, meta descriptions, H1 tags, canonicals, directives, and word counts. This data is your safety net.

Simultaneously, record your key performance metrics. Document organic traffic levels (site-wide and for top pages), keyword rankings for your most valuable terms, conversion rates, and core web vital scores. These are your success metrics.

Finally, get a complete list of all external sites linking to you and the specific URLs they link to. These inbound links are SEO gold. Failing to redirect the URLs they point to is like throwing away your most valuable assets. Your backlink tool’s bulk export feature is your friend here.

• URL Inventory: A full list of every crawlable URL on the old site.
• SEO Metadata: Titles, descriptions, H1s, and canonical tags for every URL.
• Performance Data: Organic traffic, keyword rankings, and conversion data.
• Backlink Profile: A list of all URLs with inbound links.

The Art and Science of Redirect Mapping

Redirects are the connective tissue of a site migration. This is where most migrations fail, usually due to laziness or a fundamental misunderstanding of how search engines pass value.

The Golden Rule is non-negotiable: implement server-side 301 (permanent) redirects on a 1:1 basis. Every important old URL must map directly to its new, most relevant equivalent. There are no exceptions for your top pages.

The Cardinal Sin of any migration is the blanket redirect. Redirecting thousands of old pages to the new homepage is the fastest way to tell Google you’ve deleted your content. You will lose all page-level equity, and your rankings will vanish.

Your process should be simple, yet exhaustive. Create a two-column spreadsheet: Column A for the ‘Old URL’ and Column B for the ‘New URL’. Use your pre-migration crawl data to populate Column A, then work with your team to map each one to its new destination. This is tedious, but it is the most critical task in the entire migration process.

For pages that are truly being retired with no equivalent, a 410 ‘Gone’ status code is often better than a 404 ‘Not Found’ or a soft redirect to an irrelevant page. It sends a clearer signal to Google to de-index the page. For a deeper dive, read our guide to 301 redirect mapping for migrations.

Auditing the Staging Site: Your Final Site Migration SEO Check

Your staging (or development) environment is your final chance to catch errors before they impact your live site. Treat the staging audit with the same seriousness as a live site audit. Your future self will thank you.

First, ensure the staging site is blocked from indexing. A staging site appearing in search results is unprofessional and can cause duplicate content issues. The most common method is a `robots.txt` file, but it’s not foolproof.

A better solution is IP whitelisting or server-side password protection (HTTP authentication). These methods prevent all unauthorized users and bots—including Googlebot—from ever accessing the site. Just remember to remove the block on launch day.

Once access is secured, run a full crawl of the staging site. You’ll need to configure your crawler to ignore `robots.txt` and, if necessary, enter credentials. The goal is to audit the new site in its pre-launch state.

This is where you compare apples to apples. Use ScreamingCAT’s Crawl Comparison feature. Load your pre-migration crawl and your new staging crawl to instantly see what’s changed. Have titles been altered? Have internal links been updated to the new structure? Have canonicals been correctly implemented? This feature turns weeks of VLOOKUPs into a few clicks.

# A restrictive robots.txt for staging.yourdomain.com
# This is a basic safeguard, but password protection is better.
User-agent: *
Disallow: /

Launch Day: The Go-Live Checklist

Launch day should be controlled and procedural, not chaotic. If you’ve done the prep work, this is just the execution phase. Have your checklist ready and your team on standby.

This is not the time for last-minute changes. Enforce a strict code and content freeze. The only thing that should be happening is the deployment of the new site and the implementation of your redirect map.

• Implement Redirects: The main event. Push the redirect map live.
• Remove Crawl Blocks: This is the one everyone forgets. Remove the `robots.txt` disallow, password protection, or `noindex` tags used on staging.
• Verify Key Pages: Manually check that the homepage, top landing pages, and a sample of deep pages load correctly and that their old versions redirect properly.
• Run a ‘Smoke Test’ Crawl: Use ScreamingCAT’s list mode to crawl your top 100-200 URLs. Check for 200 status codes on the new URLs and 301s on the old ones. This is your first sign of any systemic issues.
• Update XML Sitemaps: Submit your new sitemap(s) in Google Search Console. Keep the old sitemap live for a few weeks; GSC will use it to discover the old URLs and process the redirects more quickly.
• Use Change of Address Tool: If changing domains, officially inform Google via the Change of Address tool in Search Console.
• Update Analytics & Ads: Ensure your tracking code is correct and update the default URL property in Google Analytics. Don’t forget to update all destination URLs in your paid ad campaigns.

Post-Migration Monitoring: You’re Not Done Yet

The launch is not the finish line. The first few weeks post-migration are critical for identifying and fixing the issues that inevitably slip through the cracks. Your job now is to monitor, analyze, and react.

Live in Google Search Console for a while. Watch the Index Coverage report for spikes in 404s, redirect errors, or ‘Crawled – currently not indexed’ warnings. These are leading indicators that something is wrong with your redirects or internal linking.

Keep a close eye on your analytics. Some traffic fluctuation is normal as Google processes the changes, but a sustained drop of 20% or more is a clear signal of a problem. Segment your data to see if the drop is isolated to specific sections, like the blog or product pages, to help pinpoint the cause.

About a week after launch, run a new, full crawl of the live site. Compare this crawl against your original pre-migration benchmark. Are there unexpected 404s from broken internal links? Are all redirects resolving correctly? This full-circle analysis validates the success of the migration.

Don’t panic at the first sign of a dip, but don’t get complacent either. A structured approach to post-migration monitoring allows you to quickly identify and resolve regressions before they cause long-term damage.