Shopify SEO Migration Checklist: Keep Your Rankings When You Replatform (2026)

Rankings do not drop because you moved to Shopify. They drop because URLs changed without redirects, metadata was left behind, or the new store was slower and thinner than the old one. Every one of those is a checklist item, and this is the checklist we run on migrations, whichever platform the store is leaving. It is the SEO layer only; the data and cutover playbook is the zero-downtime migration guide, and the platform-specific steps are in the Magento, WooCommerce, BigCommerce and Wix guides. For international stores, Shopify Markets SEO covers hreflang in depth.

This guide covers the SEO side of a replatform. For the whole project — data, apps, payments, QA and launch — work through our free 74-task Shopify migration checklist alongside it.

Phase 1: before you build anything

1. Crawl the current site with a crawler and export every indexable URL with status code, title, description, H1, canonical and word count. This is the master list; every later step references it.
2. Export Search Console performance for 16 months: pages, queries, clicks, impressions, positions. Export the coverage report and the list of pages with backlinks (Links report).
3. Record baselines for organic sessions, revenue and conversion by landing page from analytics, and Core Web Vitals field data per template.
4. Mark the pages that matter: the top landing pages by clicks, every page with external links, and every page ranking in the top ten for a commercial query. These get manual review at every later step.
5. Decide the URL strategy. Shopify fixes the structure: /products/handle, /collections/handle, /pages/handle, /blogs/blog/handle. Map your current structure to it and decide handles now, matching old slugs where possible so redirects are one to one.

Phase 2: while the store is being built

1. Build the redirect map in a spreadsheet: every old URL to exactly one new URL, including filtered and paginated category URLs that carry traffic, old blog paths, image and PDF URLs with backlinks, and legacy redirects that already exist (chain them to the final destination, not to another redirect). Pages you are dropping redirect to the closest relevant page, not to the homepage.
2. Carry over metadata: titles, descriptions and image alt text imported with the products and pages, then reviewed on the pages that matter. Do not let a migration app generate new titles.
3. Preserve on-page content: category descriptions become collection descriptions, product descriptions keep their headings and internal links (rewritten to the new URLs), blog posts keep their publish dates and authors.
4. Rebuild structured data in the theme: Product with offers and availability, BreadcrumbList, Organization, Article for posts, FAQ where you had it. Test with the Rich Results tool on the staging store.
5. Set canonicals and indexing rules: collection pagination and filtered views canonicalized correctly, tag pages and search results noindexed, the staging store password-protected and blocked from indexing until launch.
6. International: Shopify Markets with subfolders or domains per market, hreflang generated per market, currency and language switching that search engines can crawl.
7. Speed: the new theme must be at least as fast as the old site on mobile; a slower migration is a ranking loss with no redirect to fix it. Measure the staging templates against the Phase 1 baseline (see the speed guide).
8. Internal links: navigation, footer, related products and in-content links point to new URLs directly, never through a redirect.

Phase 3: the week before launch

1. Load the redirect map into Shopify (Navigation, URL redirects, bulk import) and crawl the list of old URLs against the staging store to confirm each returns a 301 to a 200.
2. Crawl the staging store as a whole: no 404s in navigation, no redirect chains, one canonical per page, titles and descriptions present and unique on the pages that matter.
3. Validate structured data and hreflang on a sample of each template.
4. Confirm the XML sitemap is generated, contains only indexable URLs, and that robots.txt allows crawling after the password is removed.
5. Prepare the Search Console property for the new domain if the domain changes, and the change-of-address request; if the domain stays, no request is needed.
6. Lower DNS TTL and agree the launch window with the team.

Phase 4: launch day

1. Remove the password page; confirm the robots meta and robots.txt allow indexing.
2. Submit the sitemap in Search Console and Bing Webmaster Tools; if the domain changed, submit the change of address.
3. Request indexing for the top twenty pages from Phase 1.
4. Crawl the live store and the old URL list once more; fix any redirect that did not survive the DNS switch.
5. Keep the old platform reachable for a short period for redirects and images if any point there, but never indexable; noindex or block it so it does not compete with the new store.

Phase 5: the first ninety days

1. Daily for two weeks: Search Console coverage and 404 reports; add redirects for anything the map missed, which there always is.
2. Weekly: compare clicks and positions for the pages that matter against the Phase 1 export; investigate any page down more than a normal fluctuation, starting with its redirect and its metadata.
3. Check Core Web Vitals field data as it accumulates for the new templates.
4. Monitor backlinks: the pages with the most external links should be receiving them through redirects; contact the sites linking to pages you dropped if they matter.
5. After sixty to ninety days, if rankings have not recovered on a specific page, compare the old and new page side by side for content, headings, internal links and speed; the cause is nearly always visible.
6. Keep the redirects live for at least a year; longer if backlinks still point to old URLs.

What changes by platform you are leaving

• Magento and Adobe Commerce. Flat product URLs at the root and category paths with .html become /products/ and /collections/; layered navigation URLs with query parameters ranked for long-tail terms and need mapping to filtered collections or to the parent collection.
• WooCommerce. /product/ and /product-category/ paths map cleanly, but tag archives, author pages and attribute filters that were indexed need decisions: redirect to the closest collection or drop with a 410. Blog posts often keep dates in the URL; Shopify does not.
• BigCommerce. Product URLs at the root and category paths of your own design map to Shopify’s fixed structure; faceted URLs and multiple storefront domains need a per-market plan (see the BigCommerce guide).
• Wix and Squarespace. Product URLs under /product-page/ or /shop/ and page URLs that were generated from titles; the redirect map is short but the metadata is often thin, so this is the migration where you improve titles rather than copy them.
• Custom platforms. Expect ID-based URLs, duplicate paths for the same product, and no canonical logic; the crawl in Phase 1 is where you discover how many URLs one product really has.

The redirect map: columns that make it work

A redirect map that survives a migration has more than two columns. For each row: the old URL; its status in Phase 1 (indexable, redirected, 404); its clicks and impressions from Search Console; its external link count; the new URL; the redirect type (301, or 410 for deliberate removals); who approved the mapping; and a test result column filled by the crawl in Phase 3. Sort by clicks and links, review the top rows by hand, automate the rest with handle matching, and keep the file as the record of what was decided; it is the first thing you will need when a ranking drops in month two.

The mistakes that cause the drops

• Redirecting everything dropped to the homepage. Search engines treat that as a soft 404 and the equity is lost.
• Missing the filtered and paginated URLs that quietly ranked for long-tail queries.
• Letting an import tool rewrite titles and descriptions.
• Launching a slower theme and blaming the migration.
• Leaving the old site indexable “just in case”, creating a duplicate of your own store.
• Redirect chains through legacy redirects nobody documented.
• Forgetting image URLs with backlinks and blog feeds.

Timeline and who does what

On our migrations the SEO layer runs alongside the build: Phase 1 in the first week, Phase 2 through the build, Phase 3 in the final week, and Phase 5 as part of post-launch support. Smaller sites launch in 3–5 weeks and larger ones in 8–12, and the SEO work is what makes the difference between a launch that holds rankings and one that spends the next quarter recovering. The Shopify migration service includes every item above; if you are running the migration yourself, this page is the checklist to print.