Most ranking losses on a migration aren't caused by the migration itself. They're caused by the SEO work that didn't happen during the migration. The platform doesn't determine whether you keep rankings. The redirect map, the schema migration, the canonical strategy, and the post-launch monitoring do. Get those right and traffic stays flat through cutover. Get them wrong and you lose 12 to 18 months of compound progress in a week.
What actually causes ranking drops on migrations
Migrations don't cause ranking drops. Specific things on migrations cause ranking drops. Knowing which ones lets you plan against them.
Missed redirects. The single biggest cause. Every URL on the old store needs a destination on the new one. Most migrations build a 301 redirect map from the current sitemap and stop there. The current sitemap doesn't include long-tail blog posts from 5 years ago that still rank, archived collections that have indexed URLs, or product variant URLs that earned organic traffic. Missing these costs rankings on long-tail terms.
Slow redirect implementation. Some migrations launch with a partial redirect map and add the rest over weeks. Googlebot doesn't wait. URLs that 404 for more than a few days drop from the index. Rankings on those terms are lost immediately and recover slowly.
URL structure changes that weren't planned for. Shopify's URL structure is fixed. Product URLs are /products/handle. Collection URLs are /collections/handle. Some source platforms have completely different patterns. Brands that don't redirect comprehensively lose rankings on every URL whose structure changed.
Schema markup not migrated. Schema doesn't migrate automatically. The new store has its own template-driven schema. If product schema, breadcrumb schema, or FAQ schema disappears from key pages, rich results disappear with them.
Content changes during migration. Brands sometimes use the migration to rewrite product descriptions, reorganise category structures, or change page titles. Each change is a ranking risk. Combining content changes with platform changes makes diagnosis harder if rankings drop.
Robots.txt or noindex misconfigurations. Staging environments are usually noindexed. Production launches should not be. Migrations that ship with the staging robots.txt or noindex tags lose all rankings within a week.
Slow page speed post-launch. Shopify Plus is fast by default, but custom themes with bloated apps or unoptimised images can ship slower than the source store. Page speed is a ranking factor. Slower pages mean slower recovery on competitive terms.
Each one of these is preventable. The migration playbook addresses each one explicitly.
The redirect map: the most under-resourced part of every migration
The 301 redirect map is a spreadsheet that pairs every URL on the old store with its destination on the new one. The size of the map is determined by the size of the URL surface, not the size of the catalogue.
A complete map for a mid-market store covers:
For a typical mid-market migration, this is 5,000 to 100,000 URLs depending on platform and catalogue size. Magento and Salesforce Commerce Cloud stores tend to be at the higher end because faceted navigation generates large URL surfaces.
The map gets built in three passes:
Pass 1: Live site crawl. A full crawl of the live site with Screaming Frog, Sitebulb, or similar. Captures every URL the site links to internally.
Pass 2: External data merge. Pull Google Search Console URLs for the last 12 months. Pull backlink data. Merge into the spreadsheet to find URLs that rank or are linked to but aren't in the live crawl.
Pass 3: Existing redirect import. Pull the current redirect rules out of the source platform admin or .htaccess. Map them either to the new direct destination or as a chain through the new structure.
Once the source URL list is complete, each URL gets a destination on the new site. Direct mappings (/products/old-handle → /products/new-handle) cover the bulk. Pattern mappings cover faceted navigation. Manual mappings cover anything that doesn't fit a pattern. Every row gets validated against the new sitemap before launch.
URL structure decisions before catalog mapping
Some URL structure decisions need to be made before the catalogue migration starts because they affect handles, slugs, and collection structures.
Product handles. Shopify generates product handles from titles by default. For migration, handles need to either match the old URLs (so redirects are simpler) or be deliberately new (which means redirects from the old URL to the new one). Decide which approach before products move.
Collection handles. Same decision for collections. For brands with strong rankings on category pages, preserving the handle path is usually the right call.
Blog URL structure. Shopify uses /blogs/blog-name/article-handle. Source platforms vary. The blog URL structure on Shopify can't be flattened to /article-handle directly without a custom domain or proxy. The migration needs to either accept the new structure (and redirect everything) or set up a custom blog routing solution.
Multi-locale URL structure. Markets on Shopify support subfolder URLs (/en-au/), subdomain URLs (au.example.com), or top-level domains (example.com.au). Each has SEO implications. Subfolder is usually the right call for SEO consolidation but requires planning.
Trailing slashes. Shopify URLs don't have trailing slashes. Source platforms may. The redirect map needs to handle both forms.
The decisions made here drive the rest of the SEO migration work. Making them late causes rework.
Multi-locale and hreflang
For brands with multi-locale or multi-region sites, the SEO work doubles.
Hreflang annotations. Tell Google which version of a page belongs to which language and region. Shopify Markets handles hreflang automatically when set up correctly, but the configuration needs to mirror the existing setup. Mistakes here cause Google to treat localised pages as duplicate content, which loses rankings.
Canonical strategy. When the same product is sold in multiple regions, canonical tags decide which version Google indexes. Markets handles this, but custom domains or non-standard configurations need explicit canonical rules.
Translation strategy. Shopify Translate & Adapt handles translations, but content that was machine-translated on the old platform may need re-translation. Quality matters for both rankings and conversion.
Region-specific URLs. If /au/products/x was the URL pattern on the old site, the new pattern depends on the Markets configuration. The redirect map needs to handle every locale.
For brands with 5+ markets, the multi-locale SEO conversation deserves its own scoping pass before catalogue mapping starts.
Schema migration
Schema markup tells Google what kind of content each page contains. Rich results in search depend on it. Schema doesn't migrate automatically. It gets re-implemented on the new platform.
For Shopify Plus, schema usually lives in the theme as Liquid snippets or in a JSON-LD block injected via the theme's <head> element. The implementation patterns:
Product schema. Generated per product page from product fields and metafields. Most themes generate this automatically but the output should be validated post-migration with Google's Rich Results Test.
Breadcrumb schema. Generated per page based on the navigation path. Either built into the theme or added via apps like Schema App.
FAQ schema. Per-product or per-page FAQs marked up with FAQPage schema. Usually built via metafields or apps.
Organisation and website schema. Site-wide schema describing the brand. Lives in the theme <head> once.
Article schema. For blog posts. Generated from blog post fields and author metafields.
Local business schema. For brands with physical locations. Lives in the relevant page templates.
The schema validation step happens twice: once on the migration sandbox before launch, once on the live site within 24 hours of cutover.
Content migration versus content rewrite
The temptation during migration is to rewrite product descriptions, restructure categories, and improve content. Each change carries ranking risk.
The principle: separate content changes from platform changes. Migrate the existing content as-is, then iterate on content after the platform is stable. Two reasons.
Diagnosis. If rankings drop post-launch, you need to know whether the cause is the migration or the content changes. Combining the two makes that impossible.
Bandwidth. Migrations are already big projects. Adding a content rewrite multiplies scope and risk.
The exception is content that was actively hurting rankings before migration: thin product descriptions, duplicate category text, missing meta descriptions. These can be fixed during migration if there's bandwidth, but they're a separate workstream.
Sitemap and robots.txt
Two technical artifacts decide whether Google can find and crawl the new site.
XML sitemap. Shopify generates an XML sitemap automatically at /sitemap.xml. For multi-store, multi-Market, or headless setups, the sitemap configuration may need attention. The sitemap should be submitted to Google Search Console immediately after cutover.
Robots.txt. Shopify generates a default robots.txt that allows Google to crawl product, collection, blog, and page URLs while blocking admin, search, and cart URLs. Custom rules can be added via the robots.txt.liquid template if needed. The most important check post-launch: the production robots.txt should not include Disallow: / from the staging environment.
Both should be verified within an hour of cutover.
Post-launch monitoring
The first 30 to 90 days post-launch are where SEO outcomes get decided.
Day 1 to 7. Confirm robots.txt allows crawling, sitemap is submitted, GSC reports successful crawls. Watch for crawl errors. Check that 301 redirects fire correctly across a sample of 50 to 100 URLs. Verify schema renders on key pages.
Day 7 to 30. Monitor GSC daily for coverage issues, mobile usability errors, and Core Web Vitals. Watch for spikes in 404s. Some ranking volatility is normal in this window. Brands typically see 5 to 20% temporary traffic dip while Google re-crawls.
Day 30 to 90. Rankings should have stabilised. If specific pages or terms are still down by Day 30, investigate: redirect chain too long, content materially different, schema missing, internal linking weakened.
Day 90+. New rankings on the new platform. By this point any migration-caused drops should have recovered. Drops that persist past 90 days are usually content or technical issues, not migration issues.
The monitoring runbook should be set up before launch. GSC, Ahrefs or SEMrush, and Shopify Analytics dashboards all configured to flag drops.
What we won't do
A few principles that keep SEO work clean.
We don't sign off on a redirect map we haven't tested. Every URL in the map gets verified against the new sitemap before launch. A sample of 100 to 500 URLs gets crawled post-launch to verify redirects fire correctly.
We don't combine content rewrites with platform migration. Each is a separate project. Combining them makes diagnosis impossible if rankings drop.
We don't trust auto-generated redirect rules without manual review. Pattern-based rules are fast but miss edge cases. Every pattern rule gets sampled for accuracy.
We don't launch without sitemap submission and GSC monitoring set up. Day 1 visibility into crawl errors is non-negotiable.
We don't migrate without external SEO data. Backlink data and GSC export are required inputs to the redirect map. Building the map from the live site alone misses URLs that still matter.
Where to start
If you're planning a Shopify Plus migration and want to keep your rankings, the SEO work starts in the audit phase. We document your URL surface, schema implementation, hreflang setup, content depth, and current ranking profile before any data moves.
For broader context on Shopify Plus migrations across all source platforms, see the complete migration guide. For the cost breakdown of including SEO work in a migration scope, the hidden costs of platform migration covers the line items in detail. For platform-specific SEO considerations, the Magento and WooCommerce playbooks have detail on URL structure differences per platform.
Or browse the rest of our Platform Migration insights for deeper coverage on cost, conversion impact, and the operational decisions that come with a re-platform.
Frequently asked questions
How do I build a complete redirect map for migration?
A complete map gets built in three passes. Pass 1: full site crawl with Screaming Frog or Sitebulb to capture all internal URLs. Pass 2: merge Google Search Console URLs from the last 12 months and backlink data to find URLs that rank or are linked but missing from the crawl. Pass 3: import existing redirect rules from the source platform admin or .htaccess. Every URL gets a destination and every row gets validated against the new sitemap before launch.
How long does it take rankings to recover after a Shopify Plus migration?
Most mid-market brands see a 5 to 20% temporary traffic dip in the first 30 days while Google re-crawls and re-evaluates the site. Rankings typically stabilise by day 90. If specific pages or terms are still down past day 90, the cause is usually a missed redirect, schema gap, or content change that wasn't planned for. Recovery on those issues is slower because the URLs may need to be re-indexed from scratch.
Does schema markup migrate automatically when I change platforms?
No. Schema markup is theme-specific and never migrates automatically. Product schema, breadcrumb schema, FAQ schema, organisation schema, and article schema all need to be re-implemented in the new theme. The validation step happens twice: once on the migration sandbox before launch, once on the live site within 24 hours of cutover.
Will my URL structure change when I move to Shopify Plus?
Yes, in most cases. Shopify uses fixed URL patterns: products at /products/handle, collections at /collections/handle, and blogs at /blogs/blog-name/article-handle. If your source platform uses different patterns, every old URL needs a 301 redirect to its new destination. Decide URL structure before the catalogue migration starts because it affects handles, slugs, and collection structures.
Can I rewrite content during a migration to improve SEO?
You can, but it's risky. The principle is to separate content changes from platform changes, because if rankings drop post-launch, you need to know whether the cause is the migration or the content rewrite. Migrate the existing content as-is, then iterate on content after the platform is stable.
What's the difference between subfolder, subdomain, and TLD URL structures for international SEO?
Subfolders (/en-au/) consolidate SEO authority on the main domain and are usually the right call for new international expansion. Subdomains (au.example.com) are treated as separate sites by Google and split authority. Top-level domains (example.com.au) are best for established country-specific brands but don't share authority. Shopify Markets supports all three.
How do I monitor SEO performance after a Shopify Plus migration?
Set up the monitoring runbook before launch, not after. Day 1-7: confirm robots.txt allows crawling, sitemap is submitted to GSC, redirects fire correctly across a 50-100 URL sample. Day 7-30: monitor GSC daily for coverage issues, mobile usability errors, and 404 spikes. Day 30-90: rankings should stabilise. Drops past day 90 indicate content or technical issues, not migration issues.
What's the most under-resourced part of an SEO migration?
The 301 redirect map. Most agency-built maps cover only the URLs in the current sitemap, which misses long-tail blog posts that still rank, archived collections with indexed URLs, and product variant URLs that earned organic traffic. A complete map for a mid-market store is usually 5,000 to 100,000 URLs. Skip this work and rankings on long-tail terms drop within 7 to 14 days post-launch.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- Migrations don't cause ranking drops. Specific things on migrations cause them: missed redirects, slow redirect implementation, URL structure changes that weren't planned for, schema not migrated, content rewrites layered on top of platform changes, and robots.txt or noindex misconfigurations that ship with the launch.
- The 301 redirect map is the single biggest determinant of whether you keep rankings. A complete map for a mid-market store is 5,000 to 100,000 URLs covering crawl, GSC data from the last 12 months, backlinks, and existing redirect rules. Built in three passes, not one.
- Schema markup does not migrate automatically. Product schema, breadcrumb schema, FAQ schema, and organisation schema all need to be re-implemented in the new theme and validated against Google's Rich Results Test before launch and within 24 hours of cutover.
- Don't combine content rewrites with platform migration. Each is a separate project. Combining them makes diagnosis impossible if rankings drop, and migrations are already big projects without adding scope.
- The 30 to 90 days post-launch decide the SEO outcome. Day 1-7: confirm crawl, sitemap, redirects, schema. Day 7-30: monitor GSC daily for coverage and 404s. Day 30-90: rankings should stabilise. Drops past day 90 are usually content or technical issues, not migration issues.
- Some traffic dip is normal in the first 30 days while Google re-crawls. A 5 to 20% temporary drop is expected. Recovery to baseline by day 90 is the target. Drops larger than 20% or persisting past 60 days indicate something missed in the redirect map or schema work.
