Ecommerce platform migration SEO is the work of moving a store between platforms without losing the organic revenue the old store earned. It differs from a general website migration mainly in scale and in what is at stake per URL.
A brochure site migration involves tens or hundreds of URLs. A store migration involves every product, every category, every filtered variant the old platform generated, and often years of review content. The general method still applies, but the volume changes which parts break.
The general migration sequence, inventory through redirect mapping to post-launch monitoring, is covered on SEO migration. This page covers what is specific to stores.
What makes store migrations different
- URL volume. Mapping thousands of product URLs cannot be done by hand, so it depends on reliable identifiers such as SKU or handle.
- Catalogue churn. Products go out of stock or get discontinued mid-migration, so the mapping target moves.
- Platform-imposed structure. Most platforms dictate their own URL patterns, so structure is rarely preserved exactly.
- Review and UGC content. Ratings and reviews frequently live in a third-party app and do not migrate with the catalogue.
- Structured data. Product markup regenerates from the new platform’s templates and often changes shape.
- Filter URLs. The old store may have indexed facet combinations that the new one generates differently or not at all.
Mapping a catalogue at volume
Manual mapping fails above a few hundred URLs. The approach is to match on a stable identifier and handle only the exceptions by hand.
- Export the full product list from both platforms with SKU, handle and title.
- Match on SKU first, then on normalised title, and treat anything unmatched as an exception queue.
- Map categories separately and deliberately, since they carry most commercial search demand.
- Decide a standing rule for discontinued products before starting, rather than case by case.
- Reconcile the result against Search Console indexed URLs, which will contain pages no export lists.
Categories deserve disproportionate attention. They are a small share of URLs and a large share of revenue, and their structure is where store architecture decisions get locked in.
Decisions to make before the build starts
- Whether the category hierarchy carries over unchanged or gets restructured. Doing both at once obscures cause and effect.
- Which filter URLs, if any, remain indexable on the new platform.
- How out-of-stock and discontinued products behave: kept live, redirected, or returned as 410.
- Whether reviews migrate, and if not, what replaces that content on product pages.
- Whether product descriptions are rewritten during the move, which again mixes two variables.
Where store migrations lose revenue
- Category URLs are treated as an afterthought behind product URLs, so the highest-value pages are mapped worst.
- Discontinued products are bulk-redirected to the homepage, producing soft 404s at scale.
- Reviews are lost, thinning every product page simultaneously.
- The new platform generates duplicate product URLs through multiple category paths without correct canonicals.
- Filter URLs that used to rank disappear with no redirect, or multiply into index bloat.
- Page speed regresses on templates, which matters most on category pages with many images.
Platform-specific guidance
The constraints differ substantially by destination. Detailed handling is covered separately for Shopify migrations and WooCommerce migrations, since each imposes different limits on URL structure and redirects.
Frequently asked questions
How long before traffic recovers after a store migration?
Expect several weeks for recrawling on a mid-sized catalogue, longer for large ones, because search engines will not recrawl thousands of URLs immediately. A shallow dip that recovers over four to eight weeks is typical. A deepening decline after recrawling is a fault, not a delay.
Should we migrate the catalogue and redesign at the same time?
It is common because it saves budget, but it costs diagnostic clarity. If URLs, templates and content all change together and revenue falls, isolating the cause is difficult. Where possible, migrate first and redesign afterwards.
What happens to products we no longer sell?
Give them a rule rather than a case-by-case decision. Redirect to the closest equivalent product or the parent category where the URL has links or traffic; return 410 where it does not. Blanket homepage redirects are the worst option.
Do we need to migrate reviews?
If reviews form a meaningful part of product page content, yes. Losing them thins every product page at once, which is a sitewide content change disguised as a technical migration. Confirm export and import paths before committing to a platform.
Consulting CTA
If you are replatforming a store, book an SEO consultation before the new URL structure is locked, and we can work through catalogue mapping, category structure and redirect rules while they are still changeable.