Replatforming to Shopify without losing SEO: the technical checklist

The scariest part of a replatform is not the build. It is the week after launch, when you are waiting to see whether your organic traffic held. Done carelessly, a migration can wipe out rankings you spent years earning. Done properly, most stores see no meaningful traffic loss at all — and often a lift, once the new store is faster.

The difference is almost entirely in the boring, technical details. Here is the checklist we run on every store migration.

Map every URL before you touch anything

The single biggest source of migration traffic loss is broken URLs. Your old platform and Shopify structure URLs differently — product paths, collection paths, blog paths, pagination. Before launch you need a complete map of every indexed URL on the old site and where it lands on the new one.

Pull the list from three places and combine them: your XML sitemap, Google Search Console’s indexed pages, and a full crawl of the live site. Anything with traffic or backlinks gets a destination. Anything genuinely obsolete gets a deliberate decision, not an accidental 404.

301 redirects, one to one

Every old URL that had value gets a 301 (permanent) redirect to its closest equivalent. Not a 302, not a blanket redirect to the homepage — a specific, permanent, one-to-one redirect. Homepage-catch-all redirects are one of the fastest ways to tell Google “these pages are gone,” which is the opposite of what you want.

Shopify handles URL redirects natively, and for a large catalogue you will want to import them in bulk rather than by hand.

Preserve the on-page signals

Rankings live in the details Google reads on each page. Carry them across deliberately:

• Title tags and meta descriptions
• H1s and heading structure
• Image alt text
• Structured data (product, breadcrumb, review, FAQ markup)
• Canonical tags

It is tempting to “improve” all the copy during a migration. Resist doing it in the same release. Move like-for-like first, confirm rankings hold, then optimise. Changing the platform and the content at once means you cannot tell which change caused a ranking move.

Do not launch a slower store

One quiet upside of Shopify — especially on a well-built theme — is speed, and speed is a ranking and conversion factor. But a heavy theme stuffed with apps can easily be slower than the store you left. Budget time to check Core Web Vitals on the new store before launch, not after, and treat a regression as a launch blocker.

Sequence the launch so nothing indexes early

A staging store that Google crawls and indexes can create duplicate-content headaches. Keep the build password-protected or noindex until go-live, then flip it and submit the new sitemap in Search Console the same day. Keep the old domain’s redirects live indefinitely — they are cheap, and backlinks keep pointing at old URLs for years.

Watch the right things after launch

For the first few weeks, watch Search Console’s coverage report for a spike in 404s or “excluded” pages, and your top landing pages for traffic dips. A small wobble as Google re-crawls is normal. A cliff is a signal that a redirect is missing or a template lost its metadata — and it is fixable if you catch it early.

The takeaway

A replatform does not have to cost you traffic. It costs you traffic when URLs break, redirects are lazy, on-page signals get dropped, or the new store is slower. Handle those four things deliberately and the migration becomes what it should be: a faster, better store on the same organic footing.

If you are planning a move and want the redirect map and QA handled by people who have done it before, that is exactly the work we do.