Guide

SEO Migration Checklist: Before, During and After Launch

Most migration traffic loss is avoidable. It comes from URLs, redirects and tags that nobody checked before launch day.

An SEO migration checklist protects the rankings you already have while the site changes underneath them. Record everything before launch, test the redirects and tags before anything goes live, then monitor crawling, indexing and clicks closely for weeks afterwards. Most migration losses come from skipped steps, not from the move itself.

What counts as a migration

A migration is any change that alters URLs, templates, content or hosting at scale. That includes a redesign, a move to a new platform, a switch from http to https, a domain change, a merge of two sites and a change in URL structure. Each one can break the link between what Google has indexed and what your site now serves.

Before launch: record and plan

Before anything changes, capture the evidence. You cannot repair what you never recorded.

Before launch

Pre launch checklist

This record is your comparison set. After launch, every question starts with: what did this URL look like before?

Keep it somewhere the whole team can open, with the date it was taken.

Record before you change

  • Crawl the live site and save every URL, title, H1, canonical and status code
  • Export top pages and queries from the Search Console Performance report
  • Save your backlink list and note the pages that earn the most links
  • Back up the current robots.txt, sitemaps and redirect rules
  • Note your current Core Web Vitals and page speed baseline
  • Set up the new property in Search Console if the domain is changing

Then plan the changes. Keep URLs the same wherever you can. Where a URL must change, build a one to one redirect map from every old URL to its closest new equivalent. Our redirect mapping guide covers how to build and test one. Plan to keep the content, titles and internal links of your best pages as close to the old version as possible.

Pre launch testing on staging

Test the new site before real users and Googlebot see it.

The most common launch day disaster is a staging noindex tag or a blocking robots.txt rule that goes live with the site. Make removing it a named task with a named owner.

During launch: day one checks

On launch day, work through a short list in order.

  1. Remove staging blocks and check robots.txt in a browser.
  2. Spot check key pages: status 200, indexable, correct canonical.
  3. Test the redirects on a sample of old URLs, including top backlinked pages.
  4. Submit the new XML sitemap in Search Console.
  5. Check that analytics and conversion tracking fire.
  6. Use the URL Inspection tool on the home page and a few key pages to see what Google sees.

If you are changing domains, use the Change of Address tool in Search Console once the redirects are live. Our guide to changing your domain without losing rankings explains the steps.

After launch: watch and repair

The weeks after launch are when problems surface. Check these reports often.

Where to lookWhat it tells youWhat to act on
Pages report in Search ConsoleWhich URLs are indexed and which are notSudden rises in Not found, Excluded by noindex or Crawled, currently not indexed
Crawl stats reportHow Googlebot is crawling the siteSpikes in server errors or a fall in crawl requests
Performance reportClicks and impressions by page and queryPages that lost clicks compared with the old version
Sitemaps reportWhether the new sitemap was readErrors or a low count of discovered URLs
Your own crawlRedirect chains, broken links, missing tagsAnything that differs from the pre launch record
Post launch monitoring reports

Fix what you find the same day. Keep the redirects in place for at least a year, and longer where old URLs still earn links. Our answer on how long redirects should stay in place explains why.

Some movement in the first days is normal while Google reprocesses the site. A sharp, sustained fall is not, and it needs evidence, not waiting. Our guide on what to check after a redesign traffic drop lists the faults in order of how often we see them. If you are asking whether a redesign can do this, see our short answer on whether a redesign can hurt SEO.

Common migration mistakes

When to call for help

Get help when traffic has dropped since launch and the cause is not obvious, when the site has thousands of URLs, or when the redirect map was never built. We compare the old and new site URL by URL, find what broke and fix it. Ask for a free SEO triage, or see how our website migration SEO recovery work runs.

FAQ

Questions owners ask us

How early should SEO be involved in a migration?

Before design and development are signed off. URL structure, templates, navigation and redirects are all set early, and they are expensive to change late. Bringing SEO in after the build means checking work that is already done instead of shaping it.

Should I launch on a weekend or a quiet period?

A quiet traffic period gives you room to fix problems, and you should launch when your team can respond the same day. Pick a time when developers are available for fast fixes. The launch day matters less than having a tested redirect map and a rollback plan.

What do I do if traffic drops right after launch?

Do not roll back at once. Check what changed: redirects, robots rules, noindex tags, canonicals and internal links. Compare old and new URLs. Most post launch drops come from a handful of fixable faults. If you need help, ask for a free SEO triage.

Get started

Tell us where it hurts.

Your site, what changed and when. We reply with a first read on the cause.