Rankings rarely die from the platform switch
The biggest reason stores stay on an outdated platform is fear of losing organic traffic. It is a reasonable fear: a bad migration can cost months of search performance. But the platform switch itself is rarely what hurts. What hurts is everything happening around it — nearly every URL changes, some redirects get missed, and metadata that took years to tune quietly disappears during the import.
Google treats a platform move as a site move. A permanent redirect tells the index that the target is the new home, but processing takes time — weeks for small sites, longer for big catalogs. The objective is not to avoid any dip; it is to keep the dip shallow and short. That is a planning problem, not a platform problem.
Build the redirect map before you touch anything
Every ranking you own is tied to a specific URL, and Shopify's URL structure is fixed: products live under /products/, collections under /collections/, pages under /pages/. Coming from WooCommerce, Magento, or a custom build, almost every indexed URL changes. That is why the redirect map is the spine of the whole project. Before launch, crawl the old site with Screaming Frog or Sitebulb and export every indexable URL along with its title, H1, meta description, and structured data. Then pull your top pages from Google Search Console and analytics — crawlers miss orphan pages that still earn traffic.
Map each old URL to its closest Shopify equivalent, one to one. A 301 to a genuinely equivalent page transfers ranking signals; a redirect to an unrelated page, or a mass redirect to the homepage, is treated like a soft 404 and passes nothing. Keep every redirect a single hop — chains waste crawl budget and can weaken the signal transfer. Load the map as CSV into Shopify's URL redirects, and keep it live for at least a year. Old backlinks keep pointing at old URLs for years after you move.
Carry the signals over, not just the products
Product importers move inventory; they do not move rankings. Titles, meta descriptions, image alt text, and structured data such as Product and Breadcrumb schema need to be exported and re-applied on the new pages. Many importers default to generic auto-generated titles — they look fine in the backend and quietly drag down click-through rates in search results. If your old store ran an SEO plugin, that data lives in plugin fields, so export it before the old site comes down.
Use the move as a reason to drop dead weight, not to redesign. Remove or consolidate pages that already rank poorly, but do not merge dozens of live product pages into a collection — aggregate rankings dilute when you consolidate. And resist treating the migration as a full redesign: the fewer things that change at once, the easier it is to know what actually moved the numbers.
Launch clean, verify, then measure
Before you point the domain at the new store, test the redirect map end to end. Crawl the list of old URLs: each should return a 301 and land on a new URL serving a 200, with no chains and no loops. Check for stray noindex tags left over from staging, self-referencing canonicals, and internal links that still aim at old URLs. Confirm analytics is firing and page speed is no worse than the old store — a migration that makes the site slower undoes the whole point.
On launch day, submit the new sitemap in Search Console. If you are changing domains, run the Change of Address tool as well. Then check Search Console's page indexing report and your analytics daily for the first couple of weeks. Every 404 is a redirect you missed; add it, and move on.
Let the migration settle before judging it
A clean migration still produces a temporary dip. Google takes weeks to fully process a move, and longer for large catalogs, so judge the migration on the 90-day trend rather than the first Monday's numbers. Benchmark clicks, impressions, and revenue by landing page before launch. If the dip is shallow and traffic recovers on the pages that mattered before, the move worked.
Plan the calendar too: do not migrate right before your busy season. Give the new store time to settle before the traffic you depend on arrives. Shopify's managed infrastructure — CDN, SSL, uptime — often outperforms the self-hosted setup you left, which is why a well-run migration regularly ends with search performance as good as or better than it started. The rankings survive when you treat every old URL as an asset that needs a new home.