Ecommerce SEO Migration: How to Protect Organic Traffic During Replatforming

Protect ecommerce SEO during a migration by crawling and baselining the old site, mapping every valuable URL to its closest new equivalent, implementing permanent (301 or 308) redirects without chains, carrying over titles, descriptions, headings, content, canonicals and structured data, keeping internal links pointing at final URLs, generating new sitemaps and checking robots rules. Crawl staging before launch, then monitor Search Console, 404s and organic traffic by page type. Google advises keeping redirects for at least a year and expecting some temporary fluctuation.

Ecommerce sites have many URLs that earn search traffic: categories, products, variants, filtered pages, guides. A platform change often changes URL patterns (for example, Shopify uses fixed prefixes such as /products/ and /collections/), templates, internal linking and structured data all at once. Each change is manageable; together they create risk if not planned.

This article covers the SEO workstream. For redirect implementation in depth, see ecommerce URL migration. For general website moves, see website migration guide.

Crawl the current site to capture every URL, status code, title, meta description, canonical, heading, structured data and internal link. Export organic landing pages and queries from Search Console and analytics, and note top pages by traffic and revenue. Record backlinks to important URLs. These baselines let you check the new site against the old and measure changes after launch.

Map old URLs to new ones one to one where possible: each product to its new product URL, each category to its new collection, each content page to its new page. For discontinued products, redirect to the closest alternative or category; don't send everything to the homepage. Google recommends permanent server-side redirects such as 301 and 308, avoiding redirect chains, and keeping redirects for as long as possible, generally at least one year (Google Search Central).

Carry over titles, meta descriptions, H1s and body content for pages that perform well. New templates sometimes change heading structure, drop content blocks or truncate descriptions; compare templates with the old ones. If you're improving content, do it deliberately on pages where it's justified rather than as a side effect of the migration.

Check how the new platform handles canonicals for products reachable through several paths (for example products within collection URLs), variant URLs, pagination and filtered pages. Canonicals should point to the preferred URL for each product and category. Decide which facet combinations should be indexable and keep consistent rules. See faceted navigation SEO and category page SEO.

Product, breadcrumb and organization structured data help search engines understand pages and can support rich results. Check that the new templates output valid structured data with accurate price, availability and review data where genuine. Test with Google's Rich Results Test. See product structured data.

Update internal links in navigation, content, product descriptions and footers to point directly at new URLs rather than relying on redirects. Redirects protect external links; internal links should be clean. Crawl the staging site to find links that still point to old URLs.

Generate XML sitemaps for the new URLs and submit them in Search Console. Check robots rules: staging sites often block crawlers, and those blocks sometimes reach production. Make sure CSS, JavaScript and images needed for rendering aren't blocked.

Before launch, crawl the staging site (with access controlled, and without letting it be indexed) and compare with the old crawl: missing pages, changed titles, missing canonicals, broken internal links, missing structured data. Test a sample of redirects in a pre-launch environment or immediately at launch. See migration testing.

After launch, test redirects for the top URLs immediately, then monitor daily for the first weeks: Search Console crawl errors, page indexing, sitemaps and performance; server logs or analytics for 404s and redirect hits; organic traffic by page type against baselines. Google notes that ranking fluctuations are expected while it recrawls, and that medium-sized sites can take a few weeks or more to settle. Fix 404s and wrong redirects quickly. Use Search Console's Change of Address tool only if the domain changes.

Shopify's URL structure uses fixed prefixes such as /products/, /collections/, /pages/ and /blogs/, so most migrations to Shopify change URLs and need redirects, which can be added in the admin or imported in bulk. Plan how collection-based product paths and canonicals behave. See Shopify migration and Shopify SEO.

Report SEO recovery by page type rather than site-wide, so problems are visible: categories, products, content and landing pages. Compare with baselines using the same periods and adjust for seasonality.

An illustrative scenario, not a client case: a store moves platforms and sees category traffic fall while product traffic holds. Investigation shows new category templates dropped the introductory copy and changed H1s, and filtered URLs that used to rank now canonicalize to the base category. The team restores content and headings and adds indexable pages for the key filter combinations, then tracks recovery by page type.

SEO-safe migrations rest on a full crawl and baseline, careful URL mapping with permanent redirects, preserved content and metadata, correct canonicals and structured data, clean internal links, new sitemaps and weeks of monitoring. Related: ecommerce SEO and migration launch plan.