Shopify Migration: Preserve Rankings During Platform Switch & Relaunch

Every month, stores lose 60-80% of their organic traffic after a relaunch. Not because the new platform is bad. Not because Google has something against Shopify. But because nobody took care of the migration.

The pattern is always the same: a store grows organically over years. 10,000, 20,000, sometimes 50,000 monthly visitors from Google. Then comes the relaunch. New platform, new design, new structure. And four weeks later, traffic is at a fraction of what it was. The six-figure damage this causes isn't a worst-case scenario — it's the standard outcome when a migration is executed without an SEO plan.

Three Types of Shopify Migrations

Before we talk about solutions, let's clarify the terminology. Not every change to a store carries the same risk.

Platform switch — Moving from one shop platform to another. WooCommerce to Shopify. Magento to Shopify. Jimdo, Gambio, Shopware to Shopify. This is the riskiest variant because everything changes: URL structure, template system, data model, often even the domain structure. Every single URL must have a 301 redirect pointing to its new counterpart.

Relaunch — The existing store stays on Shopify but gets a new theme, a new navigation structure, or a completely new design. Often combined with a restructuring of collections and categories. The risk here lies in changed URL paths, deleted content, and missing internal links.

Redesign — A purely visual update. New theme, new colours, new layout — but the URL structure and content remain identical. The lowest SEO risk, but even here mistakes can happen: for instance if a new theme changes the heading structure or implements lazy-loading incorrectly.

Why Migrations Go Wrong

In our work with Shopify stores since 2020, we've identified a clear pattern: the migration itself is rarely the problem. The problem is the process that precedes it.

The most common mistakes in practice:

No redirects. The old URL /collections/summer-jackets no longer exists. The new one is /collections/summer-jackets-women. Google only knows the old URL, finds a 404 page, and removes it from the index. Multiplied across hundreds of URLs, this creates a massive ranking loss overnight.

URL structure changed without mapping. Shopify has a fixed URL structure: /products/, /collections/, /pages/, /blogs/. If the old store didn't use any of these prefixes — and that's the case with WooCommerce, Magento, and most other platforms — every single URL must be mapped. This is regularly forgotten or done half-heartedly.

Content deleted or consolidated. During a relaunch, old category texts are removed, blog posts aren't migrated, landing pages get merged. Sounds like tidying up. But from an SEO perspective it's a disaster if those pages had rankings and backlinks. Every deleted page with rankings means lost traffic.

noindex carried over from staging. A classic: the new store is built on a staging domain. The template contains <meta name="robots" content="noindex">. At go-live, someone forgets to remove it. Google de-indexes the entire store.

Meta data not migrated. Titles and descriptions were optimised over years in the old store. During the relaunch, default titles from the new theme are used: "Buy product — Your Store". All ranking signals tied to the old titles are lost.

Quantifying the SEO Risk

The damage from a botched relaunch can be calculated precisely. A store with 15,000 monthly organic visitors, a 2% conversion rate, and an average order value of €80 generates €24,000 per month from organic traffic alone. At a 70% traffic loss, that's €16,800 less — every month. Until rankings recover, you're looking at 3-6 months in the best case. In the worst case, they never recover because the authority was tied to the old URLs that now point to 404 pages.

These aren't theoretical numbers. These are values we've seen in practice with stores that relaunched without an SEO migration plan.

The Migration Plan: What Needs to Happen

A successful migration has three phases: before launch, the go-live itself, and the weeks after.

Phase 1: Pre-Migration (4-8 Weeks Before Go-Live)

The foundation for everything is a complete inventory of the current store. What exactly needs to be captured:

- URL inventory: Crawl all indexed URLs. Screaming Frog, sitemap export, Google Search Console — the sources complement each other. Goal: a complete list of all URLs that Google knows. - Ranking baseline: Which URLs rank for which keywords? Which URLs bring the most organic traffic? This information determines priorities for the redirect mapping. - Backlink audit: Which URLs have external links? These must be redirected correctly because incoming links pass authority. - Content inventory: Which pages have unique, valuable content? What can be migrated? What needs to be rewritten? What can go — and with what redirect strategy? - Meta data export: Export all titles, descriptions, alt texts and prepare them for the new store.

Based on this inventory, the redirect mapping is created: a table that assigns every old URL to its new URL. No exceptions. Every URL that had traffic or backlinks in the old store needs a 301 redirect to the semantically matching new URL.

Phase 2: Go-Live

The switch itself must be fast. DNS changeover, SSL certificate, activate redirects. But first: a complete test run on the staging environment. Check all redirects. Check all meta data. Check all canonical tags. Check robots.txt and sitemap. Remove the noindex tags — sounds obvious, but is still regularly forgotten.

Phase 3: Post-Launch Monitoring (1-12 Weeks After Go-Live)

The work doesn't end on go-live day. The critical phase begins after:

- First 48 hours: Check Google Search Console for crawl errors. Identify 404 pages and add missing redirects. Request indexing of the new sitemap. - First week: Monitor rankings of the top 30 keywords. Compare traffic with the previous week. Catch new 404 errors caused by Google's recrawl. - First month: Check indexing status of all important URLs. Are the new URLs indexed? Are the old URLs de-indexed or redirected? Are there unexpected ranking movements? - Months 2-3: Stabilisation. Rankings should settle at the level of the old store or improve — provided the migration was clean and the new content is at least equivalent.

Technical Migration: Data and Systems

Beyond the SEO aspect, there's the purely technical side: products, customers, orders, metafields. Shopify offers various paths for this — from CSV import via the Admin API to specialised migration apps.

The crux isn't the import itself but data integrity: are variants correctly migrated? Do the SKUs match? Is customer data migrated in compliance with GDPR? Are order histories correctly linked? These questions sound trivial but are regularly only discovered after go-live — when customer service is overwhelmed.

Timeline and Effort

A clean Shopify migration isn't a weekend project. Realistic timelines:

- Simple relaunch (same platform, new theme): 2-4 weeks, including 1 week of SEO preparation - Platform switch (small store, <500 products): 4-8 weeks, including 2 weeks of SEO migration - Platform switch (large store, >5,000 products): 8-16 weeks, including 4-6 weeks of SEO migration - International relaunch with multiple markets: 12-24 weeks, SEO migration running parallel to the entire process

The SEO effort is systematically underestimated. Redirect mapping alone takes several days for a store with 2,000 URLs — not hours. Content inventory, meta data migration, and post-launch monitoring come on top.

Why smplx. Approaches Migrations Differently

The core problem with most migrations is the separation of development and SEO. The agency builds the new store, the SEO consultant is supposed to clean up afterwards. This doesn't work because SEO decisions belong in the store's architecture — not as an afterthought.

At smplx., we do both. We develop the store and we own the SEO migration. This means: URL structure is defined before development begins. Redirects are implemented as part of the deployment. Content migration is a workstream in the project plan, not an afterthought. And post-launch monitoring starts on go-live day, not three weeks later when the client calls asking why there's no more traffic.

We've proven this with stores like J.Clay and Tramontina: multiple iterations, theme switches, and relaunches — without a single ranking loss. Because SEO has a seat at the table for every decision.

In the following articles, we dive deeper into the individual aspects of Shopify migration: from redirect mapping to content strategy to the post-launch checklist.