Shopify migrations are among the most common — and highest-risk — SEO events an ecommerce store will go through. That includes moving to Shopify from another platform, moving away from Shopify entirely, or replatforming within Shopify itself by switching themes or apps that change how URLs are generated. The risk isn't hypothetical or occasional; it's structural, and it comes down to one fact that applies to nearly every Shopify migration.
Shopify enforces a fixed URL structure that almost never matches whatever structure existed on the platform you're moving from. Unlike a custom build or a WordPress site, you can't freely redesign Shopify's URL patterns to preserve your old paths. This isn't a detail to handle after the fact — it's the central constraint that every other part of your migration plan needs to be built around.
Plan your redirect map around Shopify's URL constraints, not your ideal structure. Shopify enforces /products/[handle] and /collections/[handle] patterns that cannot be fully customised — the redirect map has to work within that constraint, not fight it.
Shopify's URL Structure Constraints
Before mapping a single redirect, understand what you're working with. Shopify generates URLs in fixed patterns: products live at /products/[handle], collections at /collections/[handle], standalone pages at /pages/[handle], and blog articles at /blogs/[handle]/[article-handle]. These patterns are baked into the platform's architecture and, unlike WordPress or a custom-coded site, they can't be freely redesigned with a permalink setting or custom routing rules.
This means the most productive starting point is accepting the constraint early rather than trying to preserve an incompatible URL structure from your old platform. If your previous site used /shop/category/product-name or a deeply nested category path, that structure is not coming across intact. The goal shifts from "preserve the old URLs" to "map every old URL to the closest valid Shopify equivalent and redirect it correctly" — a subtly different but important reframing that shapes everything else in the checklist.
Pre-Migration Checklist
Crawl and export every URL from the current site. Before any migration work begins, run a full crawl of the existing store and export every indexed URL along with its current organic rankings and traffic. This becomes your baseline for measuring post-migration performance and your master source list for redirects.
Identify every page earning meaningful organic traffic. Not every URL deserves the same level of care, but any page currently driving real organic sessions — product pages, category pages, blog posts, landing pages — needs to be individually accounted for rather than lumped into a generic bulk redirect rule.
Map each page to its Shopify equivalent before any development starts. For every high-value URL identified, determine exactly which Shopify URL it will become under the new /products/, /collections/, /pages/, or /blogs/ pattern. This mapping should exist as a complete document before the store is built out, not something reverse-engineered the week of launch.
Redirect Mapping for Shopify
Shopify provides a built-in redirect tool under Online Store > Navigation > URL Redirects, which works well for stores with a manageable number of URLs. For larger catalogues, Shopify supports bulk redirect creation via CSV import, which is essential once you're dealing with hundreds or thousands of product and category URLs — manually entering redirects one at a time simply doesn't scale.
Pay particular attention to category and collection equivalents. Shopify's collection logic — whether manual or automated based on tags and conditions — often works quite differently from how categories were structured on your previous platform. A category that existed as a single page before might need to become two or three separate Shopify collections, or several old categories might consolidate into one collection. Map these deliberately rather than assuming a one-to-one match.
What Doesn't Carry Over Automatically
Custom schema markup from your previous platform almost never transfers automatically. Product, Review, and Breadcrumb schema typically need to be re-implemented through the Shopify theme's code or via a dedicated schema app, and this step is easy to overlook because the store can look and function correctly without it.
Certain metadata fields and structured data present on the old platform — custom meta fields, specialised attributes, or platform-specific markup — may need to be manually rebuilt in Shopify's metafields system, since there's rarely a direct import path for these.
Product reviews are one of the most commonly lost assets in a Shopify migration. Reviews frequently require a dedicated migration app to move from your old review system into a Shopify-compatible one, and skipping this step doesn't just lose the reviews themselves — it can also mean losing the review schema markup that generates star ratings in search results.
Post-Migration Technical Checklist
Once the new store is live, resubmit the new Shopify sitemap.xml in Google Search Console to accelerate recrawling of the new URL structure. Verify that canonical tags across the site point to the correct new Shopify URLs rather than leftover staging or old-platform URLs. Check the store's robots.txt settings to confirm nothing is accidentally blocking search engines from crawling key sections.
Just as important: confirm that GA4, Google Tag Manager, and conversion tracking still fire correctly on the new platform. Tracking setups frequently break silently during a platform change — a container that worked perfectly on the old site often needs to be reconfigured entirely for Shopify's checkout and theme structure, and a broken tracking setup can go unnoticed for weeks if nobody is checking dashboards daily right after launch.
| Element | Shopify Handling | Action Needed |
|---|---|---|
| Product URLs | Fixed /products/[handle] pattern | Redirect every old product URL individually |
| Collection/Category URLs | Fixed /collections/[handle] pattern | Map old categories to closest Shopify collection |
| Schema markup | Not automatic | Re-implement via theme code or app |
| Product reviews | Not automatic | Migrate via dedicated review app |
Common Mistakes
- Assuming Shopify's SEO-friendly reputation means migration risk doesn't apply. Shopify is a technically solid platform once configured correctly, but the migration itself carries the same URL-change and content-loss risks as any other platform move — the platform's reputation doesn't protect you from a missing redirect map.
- Leaving discontinued products with no redirect target, defaulting to the homepage. A mass redirect to the homepage is treated similarly to a soft 404 by Google and passes very little ranking value forward — redirect to the closest relevant collection instead.
- Forgetting to test redirects before DNS cutover. A redirect rule that works for most URLs but fails on edge cases like trailing slashes or old query parameters can silently break a meaningful share of your previously ranking pages.
- Not verifying reviews and schema survived the move. Because these elements don't affect whether the store visually looks correct, it's easy to launch without noticing they're missing until rankings or rich snippets quietly decline weeks later.