What SEO information should you save before a Shopify migration?
A website SEO migration plan starts with the established store, rather than a product import file alone. Identify which pages bring organic visits, orders, enquiries or valuable external links. Combine sitemap exports, crawl results, Search Console data and analytics into one URL inventory. Record the export dates and deduplicate addresses so the team works from a shared list.
Include collections, editorial pages, brand information, useful downloads and language versions. An out-of-stock item may still have a valuable fitting guide or support document. Product status and content usefulness require different decisions. Add columns for commercial priority, content owner and intended Shopify destination. The inventory should explain why a page matters without copying customer records or account credentials into the working sheet.
Commercially important pages
Flag pages that support an actual buying decision. A collection may assist research even when it is not the final purchase landing page. Avoid deciding which content to remove from a single last-click report.
Template families
Group product, collection, article, information and language URLs separately. Select examples from every family; one faulty template can affect many addresses even when the homepage appears correct.
Measurement baseline
Save the comparison period, channel definitions and conversion events. Note seasonality and campaign changes. This gives the team a context for investigation instead of attributing every later fluctuation to the platform move.
How do you map old URLs to Shopify destinations?
Use the ecommerce migration and launch checklist to assign a clear outcome to each old address: keep it, move it to an equivalent page, consolidate it or remove it. Choosing a destination from a similar title is insufficient. Open the proposed page and ask whether it meets the need behind the original link.
A replacement colour of the same product and a broad collection containing unrelated products are different choices. Where no useful equivalent exists, agree the removal decision with the content owner. Sending every retired URL to the homepage creates a convenient spreadsheet, not a useful customer journey. Record a reason and an approver. Aim for a direct final destination, then test for chains, loops and an unintended change of language.
FROM READING TO A NEXT STEP
Map your existing store before the move
Share the current platform, destination store, language scope and priority URL examples. We can turn product transfer, redirect decisions and live validation into a clearly owned migration plan.
Which Shopify redirect behaviours need their own tests?
A technical SEO review should test the output of the migration, not just the imported redirect list. Shopify’s built-in redirect system has conditions and reserved paths. Check its current documentation when a source still serves an active page or uses a platform-controlled route. A saved row in the admin interface is not evidence that a visitor reaches the intended destination.
Select separate examples for old filter links, query parameters and market subfolders. When a language or country version needs a different destination, test that specific version. Avoid assuming one market rule covers every case. Save the requested address, response chain, final page and expected language in the acceptance record. Escalate unclear platform behaviour before cutover rather than leaving it as an unexplained launch-day exception.
| URL family | Representative check | Acceptance record |
|---|---|---|
| Old product link | A valuable external reference | Equivalent product and intended final response |
| Filters and parameters | An old campaign or listing URL | A useful outcome for the visitor |
| Language and market | Primary store plus another locale | Intended language without an accidental switch |
| No equivalent content | A permanently removed page | A reasoned decision from its owner |
How should you compare content and metadata in the new theme?
Work through the business technical SEO checklist with representative old and new pages side by side. Compare the title, H1, descriptions, important images and contextual internal links. A redesigned product card may look cleaner while silently dropping a size table or usage instructions. Treat those differences as decisions to review, rather than harmless consequences of the new layout.
Inspect canonical references, robots metadata, language relationships and structured data in the page output. Installing a theme or app does not establish that these signals are correct. Include difficult examples such as variants, unavailable products, long collections and mobile layouts. Separate optional redesign and content work from the platform move where practical; changing the domain, presentation and information at once makes later diagnosis harder.
Choose meaningful examples
For each important template, include a normal page and a case likely to expose a problem. Write down the reason for the selection. Homepage approval is not a substitute for product and collection acceptance.
Classify each difference
Distinguish an intended design choice from missing information or a technical defect. Give each item an owner and a specific acceptance condition. A vague note such as “theme issue” leaves the delivery unresolved.
Repeat the same check
After a fix, test the same address under comparable conditions. Visual approval, technical acceptance and payment-flow validation serve different purposes. Record them separately so responsibility remains clear.
Who should run the live Shopify launch checks?
Operational dependencies such as CRM and ecommerce integration belong in the cutover plan alongside SEO tasks. Assign owners for domain and HTTPS behaviour, priority redirects, product access, basket, payment, notifications and measurement events. The developer and store manager may be checking different parts of the journey; do not assume that a general “tested” message covers them all.
Confirm that development noindex settings, incorrect canonicals or a restrictive robots rule have not reached production. The live sitemap should describe the intended accessible destinations. Agree who can stop or reverse the cutover if a critical issue appears, and which communication channel the team will use. Save the launch time, theme version, redirect file and unresolved items. These records provide a useful starting point for any later investigation.
How do you investigate traffic changes after the migration?
Post-migration SEO monitoring needs more detail than a total traffic chart. Compare old and new URL families, queries and commercial events using consistent definitions. Separate crawl or indexing problems in Search Console from changes to analytics collection. A missing tag can change a report without changing visits; a wrong redirect can prevent a real customer from reaching the intended page.
Fix concrete defects on priority pages first. Then examine demand, campaigns, seasonality and deliberate content changes. No checklist can promise zero fluctuation or an exact date for previous traffic to return. Evidence of a sound delivery includes implemented mapping decisions, recorded template checks and tracked unresolved issues. Set the observation period and reporting cadence according to the store’s size, change scope and available evidence.
BEFORE YOU DECIDE
Frequently asked questions
Must every URL change when we move to Shopify?
No. Compare the existing paths with the destination platform before deciding. Preserve useful addresses where feasible, and document the equivalents for paths that must change. Keeping the domain does not automatically preserve every product, collection or article path.
Can we redirect every old product to the homepage?
That can lose the need behind the original link. Consider a genuinely equivalent product, a useful information page or another appropriate destination. If none exists, review a removal response with the content owner. Each choice should have a reason rather than a universal fallback.
Is a redirect saved in Shopify admin sufficient proof?
No. Request the old link and inspect its response chain and final destination. Active source pages, reserved paths and special address formats can affect behaviour. Test language and market cases independently of what the admin row appears to describe.
Should we rewrite all product descriptions during migration?
Necessary corrections can be made, but a large content rewrite adds another source of change. Preserve useful information first. Record planned edits explicitly and consider a separate delivery where practical, so technical migration problems and content effects can be investigated separately.
Can we remove redirects shortly after launch?
Consider old external links, saved customer addresses and the processing of changed paths. An arbitrary short deadline is not a maintenance policy. Retain the redirect inventory and review removal against actual use and technical requirements with the people responsible for the store.
Does completing this checklist guarantee no organic traffic loss?
No. The purpose is to reduce preventable technical errors and make diagnosis clearer. Demand, competition and search-system processing also affect outcomes. Expect implementation and acceptance evidence rather than a guaranteed ranking or a fixed recovery timetable.
LET’S DEFINE THE SCOPE
Map your existing store before the move
Share the current platform, destination store, language scope and priority URL examples. We can turn product transfer, redirect decisions and live validation into a clearly owned migration plan.
Discuss your Shopify migration