SEO migration checklist: how to move a website without losing search traffic

What counts as a website migration?

Any change that alters how search engines reach or understand your existing pages is a migration. That includes a new domain, a new platform, a new URL structure, a merge of two sites, or a redesign that rewrites most of the content. The risk is not the change itself. Search engines rank URLs and the content on them, not the CMS behind them, so rankings drop when URLs disappear without redirects or when the content and metadata on them quietly change.

The level of risk depends on how much moves at once:

Type of change	What moves	Risk
Redesign, same platform and URLs	Templates and maybe copy	Low, if content and metadata carry over
Platform change, same URLs	Templates, metadata, structured data	Medium
Platform change with new URLs	Everything above, plus every address	High
Domain change or site merge	Every address and the site's identity	Highest

I use the same seo migration checklist for all of them and skip the steps that do not apply. The full list is at the end of this post.

What should you capture before you build anything?

A migration plan starts with an inventory, not a design. You cannot protect pages you do not know about, and the menu rarely shows everything that is indexed.

1. Crawl the current site. I use Screaming Frog to export every URL with its status code, title, meta description, H1, canonical tag, and indexability. That export becomes the baseline you compare against after launch.
2. Pull Search Console data. Export pages and queries for the full 16 months Search Console keeps. Pages with impressions and clicks are the ones to protect most carefully.
3. Pull GA4 landing pages. Some pages earn few search clicks but bring in leads from other channels. They still need a home on the new site.
4. Check backlinks. Export the pages other sites link to. A linked page that returns a 404 after launch wastes the most valuable signal you have.

With that list, every old URL gets one decision: keep it at the same address, move it to a new address, merge it into a stronger page, or retire it on purpose.

How do you build a redirect map that works?

The redirect map is the heart of the migration. It is a simple spreadsheet with two columns, old URL and new URL, but every row is a decision.

• Use permanent 301 redirects. They tell search engines the move is permanent and pass the old page's signals to the new one.
• Redirect one to one. Send each old page to its closest equivalent. Sending everything to the homepage is treated much like a missing page, and it frustrates the people who clicked an old link.
• Avoid chains. If a page was already redirected once, point the oldest URL straight at the final destination instead of stacking hops.
• Keep the old hostname alive. If you are retiring a domain or subdomain, it still has to answer requests so it can send them on.

That last point came up during the Bonefoam migration, where a Webflow website and a separate Shopify storefront on a shopping subdomain were brought into one Shopify site. The retired subdomain and the old Webflow paths were two different redirect problems, and the plan treated them separately.

What has to carry over to the new site?

Most ranking losses I see after a migration come from details that were never copied across, not from the new platform. Check each of these on your highest-value pages before launch:

• Title tags and meta descriptions, which many platforms regenerate automatically if you leave them blank
• H1s and heading structure
• Body copy, including FAQs and sections that a new design might trim
• Canonical tags pointing at the new URLs, not the old ones or the staging site
• Structured data, which almost never moves on its own and has to be rebuilt
• Internal links, updated to final URLs so they do not depend on redirects
• Image alt text and file names on pages that earn image search traffic

I covered the platform-specific version of this in the Framer to WordPress migration guide, and the same checks apply to any move.

How do you keep tracking intact?

If measurement breaks at launch, you cannot tell whether the migration worked. Install GA4 on the new templates before launch, rebuild your key events, and submit a test form to confirm each one fires. Keep the same GA4 property and Search Console property so the before and after sit in one report, and note the launch date so nobody mistakes a tracking gap for a traffic drop. A website tracking audit before launch is cheap insurance.

What should you check on launch day?

Launch day is mostly verification.

1. Remove any staging blocks. A leftover noindex tag or a Disallow: / line in robots.txt is the single most damaging launch mistake, and it is easy to miss.
2. Run your old URL list through a crawler against the live site. Every old URL should return one 301 to a page that returns 200.
3. Submit the new XML sitemap in Search Console.
4. If the domain changed, use Search Console's Change of Address tool after the redirects are live.
5. Spot check a few key pages for titles, canonicals, and structured data.

What should you watch in the weeks after launch?

Expect some movement. Google's own guidance on site moves says it can take a few weeks for most pages of a medium-sized site to be processed, and longer for large sites. What you are watching for is a drop that does not recover, and those are almost always traceable to a specific URL.

Check the Search Console Pages report weekly for not-found and redirect errors. Compare clicks and impressions by page against your baseline export. When a page drops, crawl it, check where it redirects, and compare its title and content to the old version. Keep the redirects in place for at least a year, and longer if old URLs still get links.

The full SEO migration checklist

Copy this into a spreadsheet and add an owner and date column. "Done when" is the test that the step actually worked, not just that someone did it.

Phase	Check	Done when
Before	Crawl the current site and export every live URL	You have a complete list, including pages missing from the menu
Before	Export 16 months of Search Console pages and queries	You know which URLs earn impressions and clicks
Before	Export GA4 landing pages and key events	You know which pages bring visits and leads
Before	Export top linked pages from Semrush or another backlink tool	Pages with external links are flagged for careful redirects
Before	Decide which pages move, merge, or retire	Every old URL has a decision
Before	Build a one-to-one 301 redirect map	Every old URL points to its closest equivalent, not the homepage
Build	Keep URLs the same wherever the new platform allows	Redirects are only used where a URL truly changes
Build	Carry over titles, meta descriptions, H1s, and body copy	Spot checks match the old pages, or improve on them on purpose
Build	Rebuild structured data	Schema validates in Google's Rich Results Test
Build	Rebuild internal links to final URLs	No internal link relies on a redirect
Build	Block the staging site from indexing	Staging is password protected or noindexed
Build	Install GA4 and key events on the new templates	Test submissions register in GA4 DebugView
Launch	Remove staging blocks from the live site	robots.txt and meta robots allow indexing
Launch	Crawl the old URL list against the live site	Every old URL returns one 301 hop to a 200 page
Launch	Submit the new XML sitemap in Search Console	Sitemap status shows Success
Launch	Use the Change of Address tool if the domain changed	Search Console confirms the move
After	Check the Search Console Pages report weekly	Not-found and redirect errors trend toward zero
After	Compare clicks and impressions by page against the baseline	Drops are traced to a specific URL and fixed
After	Keep redirects in place long term	Redirects stay live for at least a year

If you are planning a move and want a second set of eyes on the redirect map, this is work I do as part of website audits and CMS strategy.

SEO migration FAQ

Will changing platforms hurt my SEO?

Not by itself. Search engines rank URLs and content, not the CMS. Rankings drop when URLs change without redirects or when titles, copy, and structured data are lost in the rebuild.

How long does it take rankings to recover after a migration?

For a well-planned move, most pages settle within a few weeks. Google says a medium-sized site can take a few weeks for most pages to be processed, and larger sites longer. A drop that lasts beyond that usually points to a specific URL problem.

Can I redirect old pages to the homepage?

Avoid it. Redirect each old page to its closest equivalent. A blanket redirect to the homepage is treated much like a missing page and loses the value the old page had built.

How long should redirects stay in place?

At least a year, and longer if old URLs still receive links or traffic. There is little cost to keeping them.

What is the most common migration mistake?

Launching with the staging site's indexing block still in place, either a noindex tag or a robots.txt rule that blocks crawling. Check it first on launch day.