How to migrate to Shopify without losing SEO (301 redirect map)

You do not lose SEO by moving to Shopify — you lose it by breaking URLs during the move. Map every old URL to its new Shopify address with a 301 redirect, preserve titles and on-page content, submit a clean sitemap, and monitor Search Console for four weeks. Do that and rankings survive the cutover. Skip the redirect map and traffic falls off a cliff.

I am a senior Shopify developer in Delhi, and the redirect map is the first thing I build on every migration — before a single theme file — because it is the one mistake that is expensive to fix after launch and cheap to prevent before it.

Why do migrations kill SEO in the first place?

A migration does not confuse Google because you changed platforms. Google does not care whether your store runs on WooCommerce, Magento, or Shopify. It cares about URLs. When a URL that used to rank returns a 404, that ranking is gone, and every backlink pointing at it now points at nothing.

Shopify makes this worse than most platforms because it forces its own URL structure and will not let you change the prefixes. Products live under /products/, categories under /collections/, static pages under /pages/, and articles under /blogs/{blog}/{article}. Almost no other platform uses that pattern. So the moment you go live, every product, collection, and blog URL you ever ranked for changes address.

Here is what that means in practice:

Every row in that table is a redirect you must create. Miss it, and that page 404s. The migration itself is safe. The unmapped URLs are what kill you.

What is a 301 redirect map, exactly?

A 301 redirect map is a spreadsheet with two columns: every old URL on the left, the exact new Shopify URL it should point to on the right. The "301" is the HTTP status code for a permanent redirect. It tells Google two things: this page has moved for good, and the ranking authority it earned should transfer to the new address.

That authority transfer is the whole game. A 301 passes the large majority of a page's ranking signals to its destination. A 302 (temporary) does not do this reliably, and a 404 passes nothing — the page and its rankings simply die.

The map is the single most important artifact in the entire project. It matters more than the theme, the apps, or the launch date, because it is the only thing standing between your current organic traffic and zero. I build it before design, review it with the client, and treat it as the definition of done for the SEO side of the migration.

How to build the map, in order:

1. Export every live URL from the old site. Crawl the current store with Screaming Frog or a similar tool and export every indexable URL — products, collections, pages, blog posts, and any ranking filtered or tag pages.
2. Pull your top pages from Search Console. Export the Performance report so you know which URLs actually earn clicks. These get checked by hand; nothing on this list is allowed to 404.
3. Match each old URL to its new Shopify handle. Shopify generates a URL "handle" from the product or page title. Where handles differ from the old slug, note the exact new path.
4. Fill gaps deliberately. Discontinued product? Redirect to the parent collection, not the homepage — a relevant destination preserves more value than a blanket homepage redirect.
5. Never redirect everything to the homepage. Google treats a mass homepage redirect as a soft 404 and ignores it. Every URL gets a specific, relevant destination or it is not on the map.

How do I actually create the redirects in Shopify?

Shopify has a built-in redirect tool, and for most stores it is enough. You will find it under Online Store → Navigation → URL Redirects. You can add redirects one at a time, or — the part that matters for a migration — bulk-import a CSV with Redirect from and Redirect to columns. Your redirect map becomes that CSV almost directly.

For a catalogue of a few hundred products this is straightforward. Where it gets harder:

• Large catalogues (thousands of SKUs). Entering these by hand is not viable. A developer scripts the map generation and the CSV import, or uses a redirect app that supports pattern-based rules.
• Pattern-based redirects. If the old platform used numeric IDs (/product/482) you often need rule-based logic rather than one-to-one rows. This is where I use apps or, on Plus, Shopify Functions to handle redirect logic at scale.
• Query strings and parameters. Old faceted URLs with ?color=blue&size=m need careful handling so you do not accidentally redirect thousands of thin parameter URLs into your indexable set.

One thing Shopify does automatically that helps: when you change a product or page handle inside Shopify after launch, it creates the redirect for you. That safety net does not exist for the migration itself — those redirects are entirely on you.

What else besides redirects preserves SEO?

Redirects get the most attention, and rightly, but they are one of four things that decide whether rankings survive. The other three are quieter and just as capable of sinking you.

Preserve on-page SEO. Titles, meta descriptions, H1s, body copy, and image alt text all carry ranking signals. Migrate them faithfully. The cardinal error is redesigning the content and changing the platform in the same move — when rankings shift you have no idea which change caused it. Port the content as-is, confirm rankings hold, then improve on-page SEO as a separate, measurable step. My approach to that second step is in Shopify SEO for D2C brands.

Get canonical tags right. A canonical tag tells Google which URL is the "real" one when several show the same content. Shopify has a known quirk: products that belong to a collection are reachable at both /products/x and /collections/y/products/x. Shopify's default theme sets the canonical to the clean /products/x version, which is what you want — but custom themes and some apps break this. Verify that every product's canonical points to the clean product URL, not the collection-nested one.

Submit clean sitemaps. Shopify auto-generates a sitemap at /sitemap.xml. The moment the domain points at Shopify, submit that sitemap in Google Search Console so Google discovers the new URLs and recrawls fast. Leaving the old sitemap live, or forgetting to submit the new one, slows recovery by weeks.

How do I run the cutover without downtime?

The safe pattern separates "build" from "go live" so there is never a window where old URLs 404.

The new store is built and tested on Shopify's own domain (your-store.myshopify.com) or a staging URL. The redirect map is loaded and verified there. You crawl the staging site, confirm every mapped redirect resolves, and fix breaks while nothing is live. Only then do you point the domain's DNS at Shopify. From the first second the new site is live, redirects are already in place. There is no gap.

This is also the moment your gateway, COD, and tax config have to be right, not just your URLs — the India-specific side of that is covered in Shopify Payments, COD and GST in India, and the full pre-launch sequence sits in the Shopify migration checklist for Indian D2C brands. The SEO work does not happen in isolation; it happens inside a launch that also has to take money correctly from minute one.

Done this way, "zero downtime, zero SEO loss" is not a marketing claim. It is just the correct order of operations.

What does an SEO-safe migration cost?

SEO-safe migration is not a premium add-on — it is what a migration is. The redirect map, canonical checks, and sitemap submission are inside the scope of a proper migration, not an upcharge. Here is where a migration sits against my published rates. As with all my pricing, USD is roughly INR divided by 83.

The range within each row is driven by catalogue size, the number of URLs to map, and how messy the old platform's URL structure is. A 200-SKU Woo store with clean slugs is at the bottom of the band; a 5,000-SKU Magento store with numeric-ID URLs and years of blog content is at the top. If someone quotes migration without mentioning redirects at all, that is the warning sign — the cheap quote usually skips the exact work that protects your traffic.

How do I monitor SEO after launch?

Launch day is not the finish line. The first four weeks are where you catch problems while they are still small. My monitoring routine:

• Crawl the live site immediately. Run Screaming Frog against the new domain the day it goes live. You are hunting for two things: 404s (a missing redirect) and redirect chains (a 301 pointing to another 301 — collapse these to a single hop).
• Submit the sitemap and watch Coverage. In Google Search Console, submit /sitemap.xml and check the Coverage report daily. Rising "Not found (404)" or "Redirect error" counts are your alarm.
• Watch the Performance report for a cliff. A small dip in impressions for two to four weeks is normal recrawl behaviour. A sudden vertical drop is a broken redirect leaking traffic — investigate the same day.
• Spot-check your top twenty URLs by hand. Paste each old top-earning URL into a browser and confirm it lands on the right new page. Automated crawls miss context; a human catches "this redirected, but to the wrong product."
• Give it six to eight weeks. With a clean map, expect a two-to-four-week dip, then recovery to previous levels within six to eight weeks. If you are still down after that, redirects are still broken somewhere.

If you never touch on-page SEO during the migration and only change the platform, this monitoring is clean — any ranking move is caused by the migration alone, so it is easy to diagnose. That is exactly why I keep content porting and content optimisation as two separate phases.

The one rule that prevents almost every SEO disaster

If you remember nothing else: build the redirect map before you build anything else, and let no ranked URL 404. Every migration horror story I have been called in to rescue traces back to the same root cause — the store was rebuilt beautifully, launched, and only then did someone ask about redirects, by which point Google had already started dropping the 404ing pages.

The map is cheap insurance bought at the right time. Bought late, it becomes an emergency recovery project that costs more and never fully undoes the damage.

What's next

If you are planning a move to Shopify and organic traffic is a meaningful part of your revenue, the redirect map is not the part to gamble on. The Shopify migration expert page lays out how I run SEO-safe migrations — full 301 mapping, canonical and sitemap verification, zero-downtime cutover, and 90 days of post-launch monitoring — with fixed pricing and no agency layer. Send me your current platform, your catalogue size, and your top-ranking URLs, and I will tell you exactly what the redirect map looks like for your store. Prefer to start with the shape of your project? Use /start and I will come back with an honest scope and number.

Related reads

• The Shopify migration checklist for Indian D2C brands — the full pre-launch sequence, in order.
• How long does a Shopify migration take? — realistic timelines by platform and catalogue size.
• Shopify SEO for D2C brands — the on-page work to do after rankings hold, not during.

Sources

• Shopify Help Center — URL redirects
• Google Search Central — site moves with URL changes
• Google Search Central — HTTP status codes and redirects