Shopify Migration Checklist That Protects SEO

A shopify migration checklist protects SEO when it covers redirects, canonicals, and Search Console checks in the right order. I've used this sequence on a move from a Nigeria-registered setup to a UK-registered setup, and it kept traffic steady through launch week. Here's what I do before and after I flip the switch.

I start with the URL map because that's where most traffic losses begin. Old category paths, product handles, and blog links all need a destination, and I keep the old store reachable until the new one is indexed. Nobody frames a redirect sheet, but I've learned to love one.

Shopify Migration Checklist: Map URLs Before You Move

I pull every live URL I can find from the sitemap, Search Console, and the old navigation. Then I match each one to its new home, and I note which ones should retire with a redirect to the closest parent collection. Shopify's redirect tool handles the mapping once you import the rows, and their Help page explains the limits and format in plain terms Shopify URL redirect guide.

I keep the mapping simple. One old path points to one new path. I avoid chains where A points to B which points to C, because those slow down shoppers and search engines. I also test a sample of redirects before launch day, including mobile, because that's how most shoppers will arrive.

Where destinations differ by market, I add per-locale rows so each audience lands in the right place. That extra step takes an hour and saves a week of confusion. I also keep a copy of the sheet after launch, since browsers and search engines cache 301s and you'll want the history.

Canonicals and Primary Domain Checks

After mapping, I check canonicals and the primary domain. The primary domain is what shoppers see, and every other domain should point to it cleanly. I set one primary, then I visit the alternates to confirm they forward without extra hops. Shopify covers connecting and primary setup in their domains Help, and I follow those steps in order.

For canonicals, I confirm each key page points to itself and that market variants don't compete with each other. I view source on the homepage, a collection, a product, and a blog post. If I see duplicates, I fix the source rather than hiding it. I've found this dull check catches more issues than any clever trick.

I also walk the storefront the way a shopper would. I search, I filter, I open the cart drawer, and I check that the address bar stays consistent. When the domain flips mid-visit, shoppers notice, and so do search engines.

I also click through navigation, footer links, and a few blog posts to confirm internal links point to new URLs rather than old ones. Menus often hold onto retired paths after a move, and those quiet links create 404s that Search Console finds before you do. I update each menu item by hand, then I re-crawl the key templates with a simple link checker and fix leftovers the same day.

Sitemaps and Search Console After Launch

Once the new store is live, I submit the sitemap and watch coverage. I check that product and collection counts look right, and I look for sudden 404 spikes. Shopify's own migration notes cover this order well Shopify SEO migration notes.

I don't promise stable rankings, because no checklist can do that. What I can do is remove the avoidable errors: missing redirects, mixed domains, and stale sitemap entries. I check Search Console daily for the first two weeks, then weekly for a month. If traffic dips on one template, I know where to look.

Related reading on this site helped me keep the order straight. My post migration bug checklist I run after launch covers the inventory and currency fixes that often surface next, and my GA4 setup for multi market stores shows how I confirm tracking still fires per market. You can also browse my selected Shopify work for context on these builds.

Takeaway: My Pre- and Post-Launch Checklist

Here's the condensed version I reuse each time. Copy it into your own sheet and tick items off with dates and owner names.

• Inventory URLs: export sitemap, Search Console links, nav links, and top blog posts into one sheet.
• Map redirects: assign one destination per old URL, avoid chains, add per-locale rows where markets differ.
• Import and test: load redirect rows, test 20 to 30 URLs on desktop and mobile, fix misses before launch.
• Primary domain: set one primary, confirm alternates forward cleanly, check address bar during a full shopper walk.
• Canonical pass: view source on home, collection, product, and post; confirm self-referencing canonicals.
• Sitemap and Console: submit sitemap, monitor coverage and 404s daily for two weeks, keep old redirects live.
• Keep history: save the map with dates so future edits don't break old links.

How long should I keep old redirects live?

I keep them live for at least a year, and often longer. Old links live on in bookmarks, emails, and other sites, and removing redirects too soon brings back 404s. If a redirect still gets hits, I leave it alone.

Will my rankings stay exactly the same?

Not always, and anyone who guarantees that is guessing. What you can control is the technical handoff: correct redirects, clean canonicals, one primary domain, and fast fixes when Console flags issues. That gives your content the best chance to hold its ground.

If you're working through a move, get in touch and we'll talk it through together.