How to Migrate to Shopify Without Losing Rankings
Rankings are rarely lost because a store moved to Shopify. They are lost because URLs changed without redirects, content was quietly trimmed, or nobody checked the new site was crawlable.
Key takeaways
- Map every URL before the build starts, not the week of launch.
- Redirect to the closest equivalent page, never to the homepage.
- A redirect keeps the address alive, not the value — carry the content across too.
- Deploy all 301s before the DNS change, not after.
- A two to four week dip is normal; a decline past six weeks is a fault.
The fear that stops most replatforming projects is not the build. It is the possibility of waking up a month after launch with traffic halved, the rankings gone, and no obvious way back.
That outcome is common, and it is almost always avoidable. Rankings are rarely lost because a store moved to Shopify. They are lost because URLs changed without redirects, because content was quietly trimmed during the rebuild, or because nobody checked the new site was crawlable before the old one was switched off.
This is a practical sequence for migrating to Shopify while keeping the search visibility you have already paid for — written from doing it, including the parts that are tedious and get skipped.
Why migrations to Shopify lose rankings
Search engines rank URLs, not businesses. That is the whole reason a move to Shopify can cost you visibility. Every ranking URL on your current site represents accumulated authority — links, history, engagement. Move that URL without telling anyone where it went, and the authority does not transfer. It simply stops existing.
Platform migrations change URLs by default. Shopify has its own structure — products live under a products path, collections under a collections path — and this rarely matches what WooCommerce, Magento or a custom build produced. A category page that ranked for years becomes a 404 the moment the DNS changes.
The second cause is quieter and more common: content loss. Category descriptions, buying guides, FAQ sections and internal links often get dropped in a rebuild because nobody explicitly owned them. The URL still resolves, but the page that ranked has been replaced by a thinner one.
The third is technical. A staging site left with noindex directives, a robots file blocking crawlers, canonical tags pointing at the old domain — small mistakes that are easy to make and costly to leave in place for a fortnight.
Before you touch anything: measure
You cannot tell whether a migration went well without a picture of how things were. Capture this before any work starts, because reconstructing it afterwards is impossible.
- A full crawl of the existing site, exporting every URL that returns 200
- Your top pages by organic traffic over the last twelve months, from analytics
- Your top ranking keywords and the URLs that rank for them, from Search Console
- Every page with backlinks pointing at it — these are the ones that hurt most if lost
- Current indexed page count in Search Console
- Core Web Vitals as they stand, so you can show the improvement afterwards
Twelve months of data matters because seasonal stores rank differently in November than in June, and you will want to compare like with like.
Map every URL before you migrate to Shopify
This is the step that determines whether the migration succeeds, and it is the one most often left until the week of launch.
Build a spreadsheet with every old URL in one column and its new Shopify equivalent in the next. Every URL. Products, collections, blog posts, static pages, filtered category pages that happen to rank, and anything with a backlink.
Three rules make the mapping defensible. Map to the closest equivalent page, not to the homepage — a homepage redirect passes almost nothing and tells the visitor nothing. Where no equivalent exists, choose the nearest parent category rather than deleting. And where a page ranked well and genuinely has no successor, consider recreating it rather than redirecting it away.
Shopify's URL structure is fixed for products and collections, so plan around it rather than fighting it. You control handles, which is usually enough to keep URLs recognisable.
A migration is also the moment to improve rather than merely copy. If Search Console shows pages ranking on the second or third page, this is the point to consolidate thin auto-generated tag URLs into proper collections that target real demand. Rebuilding the same weak structure on a new platform wastes the opportunity.
Preserve the content, not just the pages
A redirect keeps the address alive. It does not keep the page valuable. If the destination has less content than the original, rankings will drift even with perfect redirects in place.
- Category descriptions and long-form copy, which Shopify collections can carry but new themes often hide
- Product descriptions in full, including specification detail — not truncated to fit a template
- Structured data for products, breadcrumbs, articles and FAQs
- Title tags and meta descriptions, which should be exported and reapplied rather than regenerated
- Image alt text, which is frequently lost in bulk imports
- Internal links between related products and guides
- Reviews, which carry both trust and indexable content
This is where theme choice quietly matters. A theme that supports collection-level content, metafield-driven specifications and structured data lets you carry everything across. A theme without those features forces you to drop content that was ranking, and no redirect compensates for that.
Test the new site before it goes live
Launch day is not the time to discover the staging site was blocking crawlers. Work through this on the development store first, and check the result with Google's Rich Results Test.
- Crawl the new site and compare the URL list against your mapping spreadsheet
- Confirm every title tag and meta description transferred, and that none are duplicated
- Check canonical tags point at the new domain, not the old one or the development URL
- Validate structured data on a product, a collection and an article
- Confirm no noindex directives remain anywhere
- Test on a real phone, since mobile is what is indexed
- Check page speed against your pre-migration baseline
Remove the password protection from the development store only when you are switching over. Leaving it open early can get the development URL indexed, which creates duplicate content against your own site.
Launch, then watch closely
Put every redirect in place before the switch, not after. Google's own site move documentation makes the same point. A gap of even a few hours means real visitors hitting 404s and crawlers recording them.
- Deploy all 301 redirects — permanent, not temporary — ahead of the DNS change
- Submit the new sitemap in Search Console immediately
- Use the URL Inspection tool on your most important pages to request indexing
- Watch the coverage report daily for the first fortnight, weekly after that
- Monitor 404s in Search Console and add redirects for anything missed
- Keep the old site's analytics accessible for comparison
- Update backlinks you control — social profiles, directories, partners
Expect a dip. A fluctuation of ten to twenty per cent for two to four weeks is normal while search engines recrawl and reassign authority. What is not normal is a decline that continues past six weeks, or an immediate fall of more than half — either means something in the mapping or the crawlability is wrong, and it is fixable if you catch it early.
Two details that catch people out. Keep the redirects live indefinitely rather than removing them after a few months — Shopify's own SEO migration guidance recommends a year at minimum. And if the domain is changing as well as the platform, use Google Search Console's Change of Address tool, which is a separate step from submitting a sitemap.
Watch for redirect chains, where an old URL passes through an intermediate page before reaching its destination, and redirect loops, where two URLs point at each other. Both waste crawl budget and dilute what the redirect was meant to preserve. Map each old URL directly to its final Shopify address.
What a good Shopify migration looks like afterwards
Traffic returns to its previous level within four to eight weeks, then typically exceeds it — not because Shopify ranks better inherently, but because migrations force a content audit and the new build is usually faster — a gain worth measuring with speed and technical SEO work.
Shopify's own SEO team gives a similar range: some impact whenever URLs change, with recovery in weeks for a small store and months for a large one. Page count and the share of traffic coming from non-branded search are what decide which end you land on.
Indexed page count should land close to where it started. A large drop means pages were lost; a large rise often means duplicates or filtered URLs are being indexed and need canonical attention.
The Yuui migration moved a ten-year-old Magento store to Shopify with catalogue, customers and order history preserved. The brief specified configuration over custom code — free theme, free apps, anything paid raised as a decision — which kept the running cost down and left the owner able to maintain the store without a developer on retainer.
Common mistakes to avoid
Redirecting everything to the homepage
It is quick and it passes almost no authority. Visitors land somewhere irrelevant and leave. Map each URL to its closest equivalent instead.
Building the redirect map after launch
Every hour without redirects is real traffic hitting 404s and crawlers recording them. The map should be finished before the build is.
Assuming redirects preserve rankings on their own
A redirect keeps the address alive, not the value. If the destination has thinner content than the original, rankings drift regardless.
Leaving noindex on after go-live
It is the single most common catastrophic migration error, and it can go unnoticed for weeks because the site looks perfectly normal to visitors.
Panicking at the two-week dip
A short-term fluctuation is expected while search engines recrawl. Changing things reactively during that window makes diagnosis harder, not easier.
Choosing a theme that cannot hold the content
If the theme has nowhere to put category copy, specifications or FAQs, that content gets dropped — and it was part of why those pages ranked.
Shopify theme selection checklist
Before switching your DNS to Shopify, confirm:
- Every old URL is mapped to a new one, with no gaps
- All redirects are 301 and deployed, not queued
- Title tags and meta descriptions have transferred
- Category and product content is complete, not truncated
- Structured data validates on product, collection and article pages
- No noindex directives remain anywhere on the store
- Canonical tags point at the live domain
- The new sitemap is ready to submit
- You have a pre-migration baseline to measure against
- Someone is watching Search Console daily for the first two weeks
Final thoughts
Migrating to Shopify without losing rankings is not a matter of luck or of any single technical trick. It is a mapping exercise done carefully, content carried across in full, and a fortnight of paying attention afterwards.
The stores that lose visibility are almost always the ones where the redirect map was rushed at the end. The stores that come out ahead are the ones that treated the migration as a content audit as well as a rebuild.
If you are planning a move to Shopify and want the mapping checked before anything goes live, send us your current URL list and we will look at it.
Frequently asked questions
Will migrating to Shopify hurt my SEO?
Not if the migration is done properly. Rankings are lost when URLs change without 301 redirects, when content is dropped during the rebuild, or when the new site is left uncrawlable. Each of those is preventable with a complete URL map and pre-launch testing.
How long do rankings take to recover after a migration?
Expect a fluctuation of ten to twenty per cent for two to four weeks while search engines recrawl and reassign authority. Traffic usually returns to its previous level within four to eight weeks. A decline continuing past six weeks indicates a problem worth investigating.
Do I need 301 redirects for every page?
Yes, for every URL that returns a 200 status on the old site — products, collections, blog posts, static pages and anything with backlinks. Redirect each to its closest equivalent rather than to the homepage, which passes almost no authority.
What is the most common Shopify migration mistake?
Leaving a noindex directive in place after go-live. It is easy to miss because the store looks completely normal to visitors, and it can go unnoticed for weeks while pages drop out of the index.
Should I keep my old URLs when moving to Shopify?
Where possible, yes. Shopify uses a fixed structure for product and collection paths, but you control the handles, which usually keeps URLs recognisable. Anything that cannot be preserved exactly must be redirected.
How long should Shopify redirects stay in place?
Indefinitely. Shopify recommends a minimum of one year, but there is no benefit to removing them afterwards. Old links on other sites keep sending traffic for years, and a redirect that is deleted turns each of those into a 404.
Does migrating from WooCommerce or Magento to Shopify hurt SEO?
The platform you leave matters less than how the URLs are handled. Both WooCommerce and Magento use structures Shopify cannot reproduce exactly, so both need a complete redirect map. Done properly, either migration preserves rankings.