Shopify Migration SEO Checklist
Moving to Shopify without losing your rankings comes down to one job done completely: mapping and redirecting every old URL to its new equivalent, one to one.
Migrating to Shopify without losing rankings comes down to one job, done completely: map every old URL to its closest new equivalent and 301 redirect it, one to one, before the old site goes down. Everything else on this checklist supports that one job or verifies it worked.
This is one piece of the larger Shopify SEO strategy — the piece with the least room for error, because a mistake here is much harder to undo after launch than most other technical fixes.
On this page
What actually causes ranking loss during a migration?
Broken paths between the old URL and the new one. Every ranking, every bit of accumulated trust, and every external link is attached to a specific URL, not to your domain in general. When that URL stops resolving — a 404, or a redirect to the wrong page — everything attached to it is orphaned, and Google has no way to know the new equivalent exists unless you tell it directly.
Google's own guidance on site moves is explicit that a well-executed move preserves ranking, and the mechanism it names is a redirect that maps old to new one for one, not a blanket redirect to the homepage [1]. That last part is where most migrations quietly fail: a redirect map that sends every unmatched URL to the homepage looks complete in a spreadsheet and behaves, from Google's side, almost like no redirect at all.
There is a second, quieter cause worth naming separately: a new site that is genuinely worse than the old one on some dimension Google measures, independent of the redirects being correct. A slower theme, thinner category content, or a navigation structure that buries pages the old site surfaced prominently can all suppress rankings even when every URL resolves exactly where it should. A migration audit has to check both things — did the redirect land, and does the page it landed on actually hold up — because a technically perfect redirect to a weaker page still produces a real loss.
How do you build a complete redirect map?
Start from an export of every indexed URL on the old site, not from a guess at what matters. Pull this from your existing sitemap, your analytics' list of URLs that received traffic in the last twelve months, and Search Console's list of URLs Google currently has indexed — the union of those three, not any one alone.
Each source catches something the others miss. A sitemap only lists what the old platform chose to include, which can quietly exclude pages that still rank. Analytics only shows pages that received a visit, which misses pages with real ranking value but low click-through. Search Console shows what Google has actually indexed, which is the closest thing to ground truth but lags behind recent changes. Cross-referencing all three, rather than trusting whichever one is easiest to export, is what separates a redirect map that actually works from one that merely looks thorough.
Export every URL from all three sources
Sitemap, twelve months of analytics landing pages, and Search Console's indexed URL list. Deduplicate into one master list.
Match each one to its closest new-site equivalent
A product should map to the same product; a category should map to the closest matching collection. Do not default to the homepage.
Flag anything with no real match
A discontinued product with real traffic history still needs somewhere sensible to land — the closest live category, not a 404.
Build the redirects before cutover, test them in staging
Confirm every mapped URL actually resolves to the intended new page before the old site goes offline, not after.
| Do | Do not |
|---|---|
| Map old product → new product, one to one | Redirect every unmatched URL to the homepage |
| Preserve category structure where it still exists | Assume the old URL list is 'close enough' from memory |
| Test every redirect in staging before cutover | Launch and check redirects after the fact |
| Keep the map as a live document post-launch | Treat the map as done once the site is live |
What about content — should it change during the move?
Not in the first month, on purpose. Keep the page titles, headings and body copy as close to identical as the new platform allows for at least a few weeks after launch. This is not a permanent restriction — it is a diagnostic one: if rankings move after a migration where content stayed constant, the cause is almost certainly technical, and if content changed at the same time, you have lost the ability to tell which change caused what.
Once the dust has settled and Search Console confirms the new URLs are indexed and stable, content improvements can resume as their own separate, measurable project — with a clean baseline to measure them against.
Set a specific date for that resumption rather than leaving it open-ended, and write down what "stable" means before you get there: coverage errors back to their pre-migration baseline, rankings for your top twenty pages within a normal week-to-week range, and no unexplained spike in 404s for at least two consecutive weeks. Without that written threshold, it is easy to either resume changes too early, while the site is still settling, or to leave a genuinely stable site frozen out of caution long after it stopped being necessary.
When should the cutover actually happen?
During your quietest trading period, never your busiest. A migration that goes wrong during a peak sales window compounds a technical problem with a revenue problem at the worst possible time, and even a clean migration carries some risk of a short dip you do not want landing on your highest-traffic weeks.
Give yourself real time before and after the date you'd otherwise pick under pressure: staging environment testing beforehand, and at least two weeks of daily monitoring afterward, before you consider the migration itself finished. A launch treated as a single event rather than a two-week process is where redirect gaps get discovered by customers and competitors instead of by you.
Communicate the timing internally too, not just to whoever is executing the technical work. Customer support should know a migration is happening and roughly when, so a spike in "I can't find the page I bookmarked" tickets gets routed to the redirect map instead of treated as an unrelated support issue. Marketing should know as well, so a paid campaign or an email send is not scheduled to land in the middle of the riskiest week of the whole project.
How do you monitor the first few weeks?
Daily, using Search Console as the primary source of truth rather than rankings alone, which are noisier and slower to reflect what actually happened. Watch the coverage report for a sudden rise in 404s or "not found" errors — that is the direct signal a redirect gap exists somewhere in the map.
Google's own guidance on debugging a traffic drop after a change starts in the same place: confirm the pages are still indexed, still reachable, and still returning the content Google expects, before looking anywhere else [3]. Cross-reference the URLs generating errors against your redirect map, fix the gaps as they appear, and resubmit the affected paths rather than waiting for the next full crawl to find them on its own.
Every migration disaster I have diagnosed traces back to the same root cause: a redirect map that looked complete in a spreadsheet and was not complete on the live site. Test it before launch, not after.
Two pieces of the new site are worth locking down before the redirect map is even final, because they change how many URLs you actually need to map. Shopify URL structure explains the fixed prefixes Shopify applies to every path, and Shopify robots.txt covers what to block on the new site from day one rather than cleaning up later. Once the migration is stable, Shopify collection page SEO is the next project — category pages are usually the templates that lost the most in translation.
Questions people also ask
Will moving to Shopify hurt my rankings?
Some dip is normal even on a well-executed migration, because Google has to recrawl and reconfirm every URL. A poorly executed one — missing redirects, changed content, a slow new site — turns a temporary dip into a lasting loss.
How long should I expect the dip to last?
Weeks to a couple of months for most of the recovery, assuming redirects are complete and the new site is at least as fast and as complete as the old one. A migration missing redirects can take much longer to recover, if it fully does at all.
Do I need to redirect every single old URL?
Every one that has ever earned a link, a bookmark or search traffic — which in practice means all of them. A URL with no incoming links and no history is lower priority, but 'lower priority' is not the same as 'skip it.'
Should I redesign the site at the same time as the migration?
No. Combining a redesign with a platform migration means two simultaneous changes producing one result you cannot diagnose. If something breaks, you will not know whether it was the new platform or the new design.
Sources
- Site moves with URL changes — Google Search Central (checked 22 September 2026)
- 301 redirects — Google Search Central (checked 22 September 2026)
- Debugging search traffic drops — Google Search Central (checked 22 September 2026)
- Shopify migration — Shopify (checked 22 September 2026)
Get a redirect map built before you announce a launch date
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Shopify SEO strategy: the full planA Shopify SEO strategy in order: fix duplicate URLs and speed, build collection pages, add schema and content, then earn links and measure revenue.
- Shopify robots.txt: how to edit it safelyShopify lets you edit robots.txt.liquid directly. What the default file already blocks, how to add your own rules, and how to test a change safely.
- Shopify Collection Page SEOCollection pages carry most of a Shopify store's ranking potential and most of its thin-content risk. Here is how to write, structure and link them correctly.
- Shopify URL structure, explainedShopify fixes /products/, /collections/ and /blogs/ into every URL and will not let you remove them. Here is what that means and when it is worth a redirect.