Blog / Technical SEO /

Planning SEO for a site migration

The new site looks great. Everyone’s happy on launch day. Then, about a fortnight later, someone opens Search Console and the organic traffic line has fallen off a cliff.

It happens all the time, and almost never because the new site is worse. It happens because the move broke the connection between what Google knew about the old site and what exists now. Old URLs return 404s. Pages that ranked have been merged, renamed or left behind. Titles that took years to get right have been replaced with a template. The redirects were “going to be done after launch”.

A migration doesn’t have to cost you rankings. Most of the risk comes from things you can list, check and plan for before launch. This is the plan I’d follow.

Key takeaways

  • Treat a migration as an SEO project from the first meeting, not a checklist on launch day.
  • Build a full inventory of the old URLs, and know which ones earn traffic, links and sales.
  • Map every important old URL to its closest new equivalent with a 301 redirect.
  • Test the new site on staging before launch: redirects, titles, canonicals, indexing settings.
  • Expect some movement for a few weeks. Watch closely, and fix fast.

What counts as a migration

Any change that alters how Google finds or understands your pages:

  • Platform change: WordPress to Shopify, Wix to WordPress, one Shopify theme to a very different one.
  • Domain change: a rebrand, a new country domain, merging two sites.
  • URL structure change: new permalinks, new category paths, removing dates from URLs.
  • Protocol or subdomain change: HTTP to HTTPS, www to non-www, a blog moving from a subdomain to a folder.
  • Big redesign: new templates, new navigation, content cut or merged.

The more of these happen at once, the higher the risk. If you can, don’t change the domain, the platform and the content in the same week. Each one is easier to diagnose on its own.

Phase 1: before anything is built

Get SEO into the brief

The decisions that cause the worst migration problems are usually made early: “we’ll simplify the menu”, “we don’t need the old blog”, “the new platform does URLs differently”. Someone needs to ask “what happens to the traffic those pages bring?” before those decisions are final.

Benchmark the old site

Write down where you’re starting from, so you can tell what changed:

  • organic sessions, conversions and revenue by landing page (from Google Analytics)
  • clicks and impressions by page and by query (from Search Console, exported, because you’ll want the old data later)
  • a list of keywords you rank for that matter commercially
  • page speed for a few key templates
  • the number of indexed pages

Export it all. A spreadsheet you can’t lose beats a dashboard you no longer have access to.

Build the URL inventory

You need every URL on the old site that matters. Pull them from several places, because no single source has them all:

  • a full crawl of the site
  • the XML sitemaps
  • Search Console’s Performance report (pages with clicks or impressions)
  • Analytics landing pages with organic traffic
  • pages with backlinks (from Ahrefs or a similar tool; I covered the reports I start with in Ahrefs for beginners)
  • your platform’s export (products, collections, posts, pages)

Combine, remove duplicates, and you’ve got your master list. For each URL, note its traffic, links and conversions. That tells you how carefully it needs handling.

Phase 2: the redirect map

This is the heart of the whole thing.

For every old URL with any value, decide where it goes on the new site, and set up a 301 (permanent) redirect. A 301 tells Google the page has moved for good and passes its signals to the new address. (The difference between 301 and 302, and the common mistakes, are in redirects on WordPress.)

Rules I follow:

  1. One to one where possible. Old product page to new product page. Old guide to new guide.
  2. Closest equivalent, not the homepage. If a page is gone, redirect it to the most relevant page that exists: its category, a replacement product, a newer guide. Redirecting everything to the homepage tends to be treated like a 404 anyway, and it annoys visitors.
  3. No chains. Old URL → new URL, in one hop. If the old site already had redirects, update them to point at the final destination.
  4. Keep it in a spreadsheet with columns for old URL, new URL, status code, and a “tested” column. You will use it again after launch.
  5. Let worthless pages go. Old tag pages, test pages, thin archives with no traffic or links can return a 404 or 410. Not everything needs saving.

On Shopify, URL redirects live under Online Store → Navigation → URL redirects, and can be imported in bulk by CSV. Shopify’s fixed URL structure (/products/, /collections/, /pages/, /blogs/) means almost every URL changes when you move to it from another platform, so the map is essential. I wrote about those constraints in Shopify URL structure.

On WordPress, a redirect plugin or server-level rules both work. Large maps are usually better handled at the server.

Phase 3: carry the SEO across

Redirects move the address. You also need to move what’s on the page.

  • Titles and meta descriptions. Migrate them, don’t regenerate them. Templates on the new platform will happily overwrite years of careful work.
  • Headings and body content. If a page ranked, be careful about cutting its content in half for a cleaner design.
  • Internal links. Update links in content and menus to point at new URLs directly, not via redirects.
  • Structured data. Product, breadcrumb and article markup should exist on the new templates. Check with the Rich Results Test. I covered what to look for in product structured data.
  • Images. Alt text and file names, especially for stores where image search brings traffic.
  • Canonical tags pointing at the new URLs, not the old ones or the staging domain.
  • Hreflang, if you have language or country versions.
  • Analytics and tracking. GA4 and any e-commerce events installed and tested on the new site before launch, not after. Otherwise you’ll have a gap right when you most need data.

Phase 4: test on staging

Before launch, the new site should be live somewhere you can crawl but Google can’t index (password-protected, or blocked).

Check:

  • Redirects: run the old URL list against the staging redirects, if your setup allows, and confirm each one lands where the map says.
  • Crawl the staging site: broken links, missing titles, duplicate titles, accidental noindex tags, canonicals pointing at the wrong place.
  • Mobile: the new templates on a real phone.
  • Speed: test key templates. A redesign that’s beautiful and slow can cost more than it gains.

And make a launch-day note: remove the staging block. The single most common migration disaster I hear about is a site launched with “discourage search engines” still ticked or a noindex left on every page. It’s the first item in the WordPress SEO checks I run first for a reason.

Phase 5: launch day

  • Launch early in the week, at a quiet time, with people available to fix things. Not on a Friday afternoon.
  • Switch on the redirects at the same moment the new site goes live.
  • Check robots.txt, indexing settings and canonicals on the live site straight away.
  • Test a sample of old URLs by hand. Then test the full list with a crawler.
  • Submit the new XML sitemap in Search Console.
  • Changing domains? Verify the new domain in Search Console and use the Change of Address tool from the old property. Keep the old domain registered, and keep its redirects running for the long term. Years, not weeks.
  • Keep the old sitemap available for a short while too. It can help Google find the old URLs and discover the redirects faster.

Phase 6: the month after

Some movement in rankings is normal for a few weeks while Google recrawls and processes the redirects. What you’re watching for is a drop that doesn’t recover, or one that’s concentrated on certain pages.

Every few days at first:

  • Search Console → Pages: watch for rising “Not found (404)” and “Page with redirect” counts. The redirects should show up; unexpected 404s need fixing.
  • Crawl stats (Settings → Crawl stats): Google should be crawling actively.
  • Performance report: compare clicks for your top pages against the benchmark you exported. If a key page has dropped, check its redirect, title and content first.
  • Analytics: conversions and revenue from organic, not just traffic.
  • 404 log: anything getting hits that isn’t redirected yet goes into the map.

There’s a calmer version of this routine in after a traffic drop: a calm Search Console checklist.

FAQ

How long does it take to recover after a migration?

With good redirects and content carried over, many sites see things settle within a few weeks. Big changes (domain plus platform plus content) can take longer. A drop that’s still deepening after a month usually points to something specific: missing redirects, lost content, or an indexing setting.

Should I migrate and redesign at the same time?

If you can avoid it, yes. Separating them makes problems far easier to diagnose. If they have to happen together, keep the URLs and content of your best pages as close to the original as you can.

Do I need to redirect every single old URL?

Every URL with traffic, links or conversions, yes. Junk URLs with nothing behind them can be left to 404. When in doubt, redirect.

How long should redirects stay in place?

As long as you can. For a domain change, keep the old domain and its redirects for years. Links out on the web still point at the old addresses.

If a migration is on your calendar, start the URL inventory this week, before any design is signed off. It’s the one job that gets harder the longer you leave it.