A Shopify migration SEO checklist that protects your rankings

Ask around and you will hear the same story from brand after brand: they replatformed to a site that looked better, loaded faster and converted the same shoppers perfectly well, and their organic traffic fell off a cliff anyway. A third of it, sometimes half, gone in a fortnight.

The reason is almost never the new platform. It is that the migration severed hundreds of quiet connections that search engines were relying on: URLs that changed shape, internal links that now point somewhere else, structured data that did not make the trip. None of it is visible to a shopper. All of it is visible to a crawler.

This is the checklist we work through on every migration. It is not exotic, it is just thorough, and thoroughness is the entire game.

Before you touch anything: inventory what you have

You cannot protect what you have not counted. Crawl the existing site and export every URL that exists, then cross-reference against the pages actually earning organic traffic and revenue in your analytics. The pages that earn get the most care; the pages that do not are candidates for pruning rather than migrating. A replatform is the one natural moment to fix catalogue architecture at the same time, because you are rebuilding the scaffolding anyway.

Map every URL, line by line

If URLs are changing shape, and on a move to Shopify they almost always are, every old URL needs a mapped destination and a 301 redirect. Not a redirect to the homepage, which Google treats as a soft 404, but to the equivalent page. Google’s own site move documentation is explicit that redirects should be one-to-one wherever possible.

Spreadsheet, two columns, every row checked by a human. It is tedious. It is also the single highest-leverage document in the entire project.

Carry the invisible passengers

Three things reliably get left behind because nobody can see them:

• Structured data. Product, review and organisation schema that took years to accumulate rich results. Rebuild it on the new templates before launch, not after.
• Meta titles and descriptions. Platforms love to regenerate these from defaults. Export the old ones, reimport them deliberately.
• Internal links inside content. Blog posts and guides full of links to old URL structures. Redirects will catch them, but updating the links themselves keeps authority flowing directly.

Crawl staging before launch day

Run a full crawl of the staging site behind its password and compare it to your inventory. You are looking for orphaned pages, accidental noindex tags left over from development, broken internal links and missing canonicals. Shopify’s own migration guidance covers the mechanics of moving data; the crawl is how you verify nothing structural got lost in translation.

Launching without a clean staging crawl is the migration equivalent of skipping the pre-flight checks because the plane looks fine from the outside.

Watch the right numbers after launch

For the first month, watch indexed pages, crawl errors and impressions in Search Console daily. Rankings wobble for a week or two after any migration; that is normal. What is not normal is impressions stepping down and staying down, which nearly always traces back to a redirect gap or an indexation problem you can still fix quickly if you catch it early.

Handled properly, a migration is not a traffic risk at all. Done with the inventory, the line-by-line map and the staging crawl, you can come out the other side with rankings intact and a faster site compounding on top of them. That is the standard our SEO work is built around, and if you have a replatform on the horizon and want it protected, start with a fit call.