← All field notes

Website Migration SEO Checklist: Before, During and After Launch

Keep valuable URLs working through a redesign, replatform or domain move. Use the launch checklist and download a free redirect map template.

Nov 22, 2026 · 5 min read


Field Notes from Thunkle, a studio that takes AI-built apps from prototype to secure, production-ready software.

The most expensive page on a website migration is the one nobody remembered to move. It might be a service page that brings in enquiries, or a PDF that an industry publication has linked to for years. The new homepage can look great while both URLs quietly disappear.

This website migration SEO checklist is for a redesign, a move to another CMS or a new domain. The rule is simple: keep URLs that still make sense, redirect changed URLs to the closest replacement, and check the pages that bring in business before telling everyone the move is done.

Download the free redirect map template

Before launch: work out what is actually changing

If you are changing hosts but keeping the domain and paths, keep those URLs. You don't need to invent redirects for them. The important checks are that your new host returns the same public pages, the correct canonicals, working assets and the expected crawler access. Google has a separate guide for moves without URL changes.

For a redesign or replatform, ask whether each proposed URL change earns its keep. Changing /services/site-audit to /seo-audit is often optional. If there's no reason to move it, mark it Keep. If you also have to change the domain, try to avoid rewriting the entire site on the same day. When several things change together, it's harder to tell what went wrong.

Then make an inventory. Start with a crawl and the old sitemap, but don't stop there. Export top landing pages from Search Console and analytics, check the pages that receive backlinks, and add public PDFs, images and campaign pages you still use. Old content may never appear in the current navigation. Save the exports with a date so you have a baseline when someone asks what happened to traffic after launch.

Build the redirect map before touching redirects

Work through the inventory one URL at a time. Give every row an expected response, a responsible person and a test result. The downloadable worksheet includes these example decisions:

  • Keep: /contact stays /contact. Expect 200, with the published URL as its canonical.
  • Move: /services/site-audit moves to /services/seo-audit. Expect one permanent redirect to the new 200 page.
  • Consolidate: /resources/seo-audit-guide moves to the same service URL if the replacement genuinely covers what readers came for. Otherwise preserve the guide or give it a closer destination.
  • Retire: /events/2021-demo has no relevant replacement. Return a real 404 or 410. Don't send people to the homepage just to make the error disappear.

Use full URLs in the map when changing the host, scheme or domain. Decide separately what should happen to query strings. A campaign tracking parameter is different from a parameter that identifies a distinct page. Test a real example of each you depend on rather than assuming your new redirect rules handle them the same way.

For permanent moves use a server-side 301 or 308. Point old redirects straight to the final page too. If A already redirects to B and B is moving to C, update A to go to C in one hop. Google's URL migration guide covers relevant destinations, permanent redirects and old URL handling.

Use staging to catch the expensive mistakes

Keep staging private where possible, and verify that production will not inherit its access controls or indexing blocks. Check the pages that drive enquiries, sales or backlinks first. For those pages, compare the old and new content side by side. A redesign shouldn't accidentally remove the service details, pricing context or local coverage that made the page useful in search.

Before approving launch, confirm:

  • The test version produces the expected redirects, status codes and final destinations. Check the whole chain, not just the first response.
  • Internal links go directly to final URLs. Titles, headings and canonicals agree with the new page. Update hreflang references if you use them.
  • The new sitemap contains the intended indexable, canonical URLs, not redirect sources, staging URLs or retired pages.
  • The main contact or purchase journey works on mobile, and the analytics event you use to count enquiries or sales still fires.
  • Someone knows how to reverse the release and what would justify that decision. Broken checkout or critical pages returning 5xx can warrant an immediate stop; a daily ranking wobble by itself does not.

On launch day: check the public version

Re-run the highest-priority rows on the real domain. Test an old URL from a bookmark, a new URL from the sitemap and a URL you meant to retire. Open the final page in a browser and make sure it is the right page, not just a response with status 200.

Check production's robots.txt, page-level robots directives and canonical tags. Submit the new sitemap in Search Console. If this is an eligible domain move, use Google's Change of Address tool after the redirects are in place; don't use it for an ordinary redesign on the same domain. Keep control of the old domain and redirects. Google recommends leaving redirects in place for at least a year, and longer can be useful when old links still send visitors.

After launch: look for what changed, not just a traffic dip

Review the old and new URL groups over the following weeks. Compare Search Console clicks and impressions, organic landing pages, and your actual enquiry or sales records. Compare similar periods, not a Monday with a Saturday. If traffic looks fine but enquiries disappear, check the form and event tracking before blaming rankings. If one valuable page loses visibility and its replacement is not showing up, inspect that URL, its canonical, source links and redirect first.

Keep the redirect map until the move has settled. Record what actually happened beside what you expected, who owns the fix, and when it was verified again. Some fluctuation is normal as Google processes the move. That is not a reason to ignore broken URLs or promise rankings will stay unchanged.

If a redesign is already booked and you want someone to check what the new site could lose, see Thunkle's SEO services. We can review the baseline and redirect map before launch, test the staged site and recheck the important URLs once they're live. See how we measure SEO work for examples of the evidence we use.

Have the migration checked before you switch.

Share your current site, launch date and what is changing. Thunkle can scope the URL mapping, staging checks and post-launch verification.