Migrate to Shopify Without Losing SEO: Redirects, Products and Launch Checks

To migrate to Shopify without avoidable SEO loss, build the new store around a complete inventory of the old one: export products and content, crawl every indexable URL, preserve valuable page intent, map each changed URL to its closest new destination, import permanent redirects, test canonicals and structured data, submit Shopify's sitemap and monitor pages, queries and sales after launch.

Do not leave the redirect sheet until the build is nearly finished. URL decisions begin when the new catalogue and navigation are designed.

Some ranking movement is normal while Google recrawls a migrated site. Missing product detail, irrelevant redirects and an accidentally blocked store are not normal. This checklist separates the two.

Checked: 14 July 2026 · Based on current Shopify and Google migration guidance

Shopify migration checklist at a glance

Assign an owner to every output. A migration shared between “the developer” and “the marketing team” without named boundaries develops gaps.

Step 1: decide what the migration is meant to improve

Moving platforms is not the objective. Name the constraint:

• difficult catalogue and order operations;
• unreliable plugins or hosting;
• slow product discovery;
• awkward mobile buying;
• weak international support;
• an expensive maintenance burden;
• content or merchandising the current system cannot express;
• poor integration between online and physical retail.

Then set baseline measures. Page speed, search use, product-view-to-cart rate, mobile conversion, support tickets, publishing time and operational errors may all matter.

Without this step, the project can preserve SEO and still fail commercially.

Step 2: inventory the current store before exporting data

Crawl every public URL

Capture:

• products and variants;
• categories or collections;
• brands, tags and filters;
• guides, blogs and landing pages;
• customer-service, shipping, returns and policy pages;
• images, PDFs and other linked files;
• titles, descriptions, canonicals, headings and structured data;
• status codes and indexability;
• internal links and pagination.

Keep this crawl untouched as the control copy.

Export search and commercial evidence

From Search Console, export page and query performance over a period long enough to capture seasonality. From analytics and the commerce platform, export landing-page sessions, transactions, revenue, conversion and assisted value where available.

Mark priority URLs using more than traffic:

• revenue landing pages;
• pages ranking for valuable non-brand queries;
• externally linked pages;
• products used in paid campaigns, email or partnerships;
• customer-service pages that prevent support work;
• seasonal pages that may be quiet today but valuable later.

A discontinued product may still earn links and help customers find its replacement. Do not judge it from current stock alone.

Step 3: clean the data before it enters Shopify

Shopify can import products, customers and historical orders through supported routes, apps or custom work, depending on the source platform and complexity. The difficult part is rarely the CSV upload. It is deciding which data remains useful and how fields map.

Products and variants

Check:

• stable SKU and barcode rules;
• product and variant titles;
• option names and ordering;
• prices, tax and compare-at prices;
• inventory locations;
• weights and shipping information;
• images, alt text and ownership;
• collections, product type, vendor, tags and metafields;
• subscription, bundle and personalisation requirements;
• product status and sales channels.

Do a representative test import early. Include the simplest product, the most complex product and one with awkward media or variants.

Customers and orders

Agree which history needs to be operational inside Shopify and which can remain in an accessible archive. Passwords generally cannot be moved as readable credentials between platforms; plan the customer activation or reset journey and explain it before launch.

Editorial content

Product data is not the whole site. Buying guides, comparison pages, FAQs, case studies and policy content may own valuable search intent. Give each one a keep, improve, merge or remove decision.

Step 4: design Shopify collections and URLs with the old evidence visible

Shopify has its own URL conventions for products, collections, pages and blogs. You may not be able to reproduce every old path exactly. That makes the redirect map more important, not less.

Keep commercially useful information architecture:

• collection pages that match how customers browse;
• product grouping that supports meaningful filters;
• editorial pages answering pre-purchase questions;
• navigation that reaches important pages in a few clear steps;
• contextual links between guides, collections and products.

Do not create dozens of indexable collection or tag combinations merely because the catalogue permits them. Decide which pages deserve unique search intent and content.

Step 5: create a one-to-one redirect map

Use at least these columns:

Rules:

1. Preserve the exact URL when the platform and architecture allow it.
2. When it changes, redirect to the closest equivalent product, collection or content page.
3. If several old pages are genuinely consolidated, redirect each directly to the new combined page.
4. If there is no useful replacement, return a real 404 or 410 instead of sending everyone to the homepage.
5. Point old URLs straight to the final destination; remove chains.
6. Include images and documents when they earn traffic or links.

Shopify supports creating redirects in the admin and importing them by CSV. Its official migration guide recommends redirecting important pages and checking the most visited old URLs after launch.

Google recommends server-side permanent redirects such as 301 and 308, a prepared URL map and direct destinations. It also says permanent redirects do not cause a loss of PageRank. The complete process is in Google's site-move documentation.

Redirects protect routes. They do not compensate for replacing a detailed page with a weak or unrelated one.

Step 6: rebuild the SEO elements people forget

For priority products, collections and pages, check:

• unique, useful title and meta description;
• one clear primary heading;
• product and category copy that supports the buying decision;
• descriptive image alt text where appropriate;
• self-referencing canonical on the final host;
• Product, Breadcrumb, Organisation and other relevant structured data;
• price, availability, variant and review markup matching visible content;
• indexable rendered HTML for important content;
• internal links using final URLs;
• Open Graph and social sharing data;
• merchant, shipping and return information where used.

Do not blindly carry every old title. Preserve the intent and proof, then improve weak presentation deliberately.

Step 7: test the complete buying system on staging

Storefront journeys

Test on real mobile and desktop devices:

• navigation, collection filtering and sorting;
• search, misspellings and zero-result states;
• product options, variants and stock;
• cart add, remove, quantity and discount behaviour;
• shipping estimates and policy links;
• checkout, payment and confirmation;
• customer activation and account access;
• order, dispatch and refund emails;
• returns or support routes.

Integrations

Test inventory, fulfilment, ERP, PIM, reviews, subscriptions, loyalty, email, analytics and advertising systems with realistic records. Confirm what happens when each is unavailable or receives bad data.

Technical and SEO checks

• crawl the staging store using authorised access;
• compare priority content against the old site;
• validate structured data;
• verify sitemap behaviour;
• inspect robots rules and noindex controls;
• test every priority redirect in a pre-launch environment or redirect test harness;
• confirm canonicals resolve to production URLs;
• check internal links for old hosts and redirecting paths;
• measure representative templates with the real apps and tags present.

Shopify password protection prevents public search crawling before launch. Record the exact steps for removing it when the domain switches.

Step 8: protect analytics and consent

Define the events before launch:

• collection view and filter use;
• search and zero results;
• product and variant view;
• add to cart and remove from cart;
• checkout stages;
• purchase, value, currency and transaction ID;
• account and subscription actions;
• phone, chat and form actions where relevant.

Run test orders through the consent states the store offers. Check Shopify reporting, analytics, ad platforms and email events without assuming one successful browser session proves the setup.

Annotate the migration date and preserve old reporting access. A platform move should not erase the baseline needed to judge it.

Step 9: launch with a cutover plan and rollback point

Before the switch

• freeze avoidable catalogue and content changes;
• take final exports and backups;
• lower DNS time-to-live where the infrastructure plan needs it;
• confirm staff, suppliers and support contacts;
• prepare the redirect import and test list;
• agree go/no-go and rollback authority;
• choose a lower-traffic window where possible.

At launch

1. Complete the final delta import.
2. Connect the production domain and HTTPS.
3. Remove storefront password or production index blocks.
4. Activate redirects.
5. Check robots, canonicals and the preferred host.
6. Complete test purchases and customer emails.
7. Confirm analytics and consent events.
8. Submit the Shopify sitemap in Search Console.
9. Inspect representative product, collection and content URLs.
10. Notify the team that post-launch monitoring has begun.

Shopify automatically generates sitemap.xml files for products, collections, blogs and pages and updates them as content changes. Submission helps discovery; it does not replace redirects.

Step 10: monitor queries, revenue and operations together

First 72 hours

Check uptime, checkout, payments, order flow, integrations, priority redirects, indexability, canonicals, analytics, emails and unexpected 404s several times.

First two weeks

Review:

• old URLs still receiving visits;
• redirect errors and chains;
• Search Console indexing and crawl problems;
• page-query changes for the protected URL set;
• organic revenue and conversion by device;
• internal search terms and zero results;
• customer-service issues caused by accounts, navigation or fulfilment.

Weeks three to eight

Compare groups: unchanged URLs, redirected products, redirected collections, editorial pages and new pages. Diagnose patterns by template and intent rather than reacting to one average position.

Google recommends keeping redirects for as long as possible and generally at least a year. Keep the old domain and redirect infrastructure under business control.

Platform-specific traps

WooCommerce to Shopify

WordPress pages, product categories, attributes, plugin-created subscription data and media paths need separate attention. Do not assume a product CSV captures the editorial site or plugin behaviour.

Magento or Adobe Commerce to Shopify

Large catalogues, layered navigation, customer groups, promotions, ERP and international rules usually make discovery and test migration substantial projects.

Wix or Squarespace to Shopify

The catalogue may be simpler, but pages, blogs, image URLs and old path patterns still need inventory and mapping.

Marketplace to Shopify

Moving from Etsy, Amazon or eBay means building an owned site, not recreating a marketplace listing. Customer relationship, content, navigation, trust and acquisition need a new plan alongside the data move.

Frequently asked questions

Will moving to Shopify hurt my SEO?

Some temporary fluctuation can happen while pages are recrawled. Lasting loss is not inevitable. Preserve useful content, map changed URLs directly, keep the store indexable and monitor priority page-query pairs after launch.

Can Shopify import all my old website data?

It depends on the source and data. Products and customers have supported migration routes, but apps, passwords, subscriptions, editorial content, order history and custom fields may need specialist handling or an archive. Test representative records early.

How do I redirect old URLs in Shopify?

Shopify provides URL redirects under Content > Menus and supports CSV import. Build the mapping from a complete crawl and performance evidence rather than creating rules ad hoc.

Does Shopify create a sitemap?

Yes. Shopify automatically generates a root sitemap linking to product, collection, blog and page sitemaps. Submit it through Google Search Console after launch and verify that it uses the preferred production domain.

Should I change the domain during the migration?

Only when there is a separate business reason. Changing platform, design and domain at once increases the number of variables. Google recommends changing major elements in stages where practical.

A safe migration is a data project with a storefront attached

The visual build receives attention because everyone can see it. The migration succeeds because the team inventories what cannot be lost, cleans what should move, maps what must change and watches the commercial system after the switch.

Related: Headless Shopify development · Choose a Shopify development agency · Redesign a website without losing SEO · Technical SEO audit checklist