/ Journal — Migration
Shopify SEO Migration Checklist: URLs, Redirects, Canonicals and Post-Launch Monitoring
A Shopify migration can keep its organic visibility, but only if search equity is treated as production data. The URLs that attract traffic and links, the redirects that connect old pages to new ones, and the canonical signals that identify preferred pages all need owners, acceptance criteria and testing.
( Short answer )
Treat search equity as production data.
This Shopify SEO migration checklist concentrates on the technical work most likely to protect organic revenue: building a defensible URL inventory, mapping one-hop redirects, aligning canonicals and internal links, and monitoring the move at page level after launch. It is designed for replatforms to Shopify or Shopify Plus, whether the domain stays the same or changes.
Short answer 8–12 weeks
Short answer
Crawl and export the legacy site before development ends; classify every valuable URL; lock the new Shopify handles; map old pages to the closest relevant live destinations; implement direct permanent redirects; make each indexable destination self-canonical; update internal links, hreflang and sitemaps; remove launch blocks; and monitor old URLs, new URLs, queries, templates and revenue for at least 8–12 weeks. Keep useful redirects for at least a year, and usually longer.
/ What this checklist is protecting ( 06 )
( What good looks like )
What this checklist is protecting.
A search migration is not successful because the new homepage loads or the number of indexed pages looks similar. It succeeds when customers and search engines can move from each valuable old resource to an equivalent new one, while the new site preserves the relevance, content and internal relationships that made the old page useful.
Organic performance can still fluctuate. Google processes site moves URL by URL, so old and new addresses coexist in its systems during the transition. The practical goal is not to promise zero movement. It is to remove preventable ambiguity and spot material problems before they compound.
01 · Legacy URL
Known, classified and tested
Failure to avoid: discovered only after traffic or backlinks break.
02 · Redirect
One permanent hop to the closest equivalent
Failure to avoid: chain, loop, homepage blanket rule or irrelevant destination.
03 · Canonical
New indexable page points to itself
Failure to avoid: new page canonicals to staging, an old URL or another variant.
04 · Internal links
Point directly to final URLs
Failure to avoid: depend on redirects throughout navigation and content.
05 · Sitemap
Contains canonical 200-status destinations
Failure to avoid: lists redirects, errors, blocked pages or non-canonicals.
06 · Monitoring
Page-, template- and query-level baselines
Failure to avoid: one total-traffic chart with no diagnostic detail.
/ Phase 1 — Baseline
Establish a migration baseline.
Capture the baseline before the old platform is hidden, DNS changes, or analytics implementations are replaced. Use consistent date ranges and annotate seasonality, campaigns, stock issues, brand activity and previous technical incidents.
Segment the baseline by page type and market. Products, collections, editorial content, stores, campaign pages and international routes behave differently. A 5% total decline can hide a severe loss on high-margin non-brand collections if brand demand rises at the same time.
01Export Google Search Console pages and queries, including clicks, impressions, CTR and position.
02Export organic landing-page sessions, revenue, transactions and conversion rate from analytics.
03List top pages by organic revenue, non-brand clicks and external links.
04Record indexed pages, submitted sitemap counts and existing indexing exclusions.
05Save current title tags, meta descriptions, headings, canonicals, robots directives and hreflang.
06Capture response codes and current redirect chains.
07Record Core Web Vitals and representative template performance.
08Validate existing product, breadcrumb, article, organization and review structured data.
09Document known measurement gaps so they are not misdiagnosed as migration losses.
( Escalation thresholds )
Define success and escalation thresholds.
Agree what the team will watch, who owns each signal and what triggers an incident. Thresholds should reflect normal volatility and business scale rather than a generic percentage.
Keep both technical and commercial measures. A crawl may be clean while an important collection has lost its useful copy, products or internal prominence. Equally, analytics may look weak because consent or purchase tracking broke even though search visibility is stable.
ClicksA sudden fall in clicks across an entire directory.
404sA spike in legacy 404 requests.
IndexingA collapse in indexed product pages.
RevenueRevenue landing on redirects instead of final URLs.
/ Phase 2 — Legacy URL inventory
Create a complete legacy URL inventory.
Do not build the redirect map from the old XML sitemap alone. Sitemaps normally omit redirected, orphaned, historical and parameterized URLs, while those addresses may still receive visits or backlinks. Combine and deduplicate URLs from:
01The current XML sitemap and a full site crawl
02CMS, product, category and blog exports
03Search Console landing pages and links reports
04Analytics landing pages over at least a full trading cycle
05Server, CDN or edge logs
06Backlink tools
07Paid media, email, affiliate, social and product-feed destinations
08International domains, language paths and previous migrations
09QR codes, support articles, PDF documents and offline material
10Images and downloadable assets with search or referral value
Normalize protocol, hostname, case, trailing slashes, parameters and encoded characters, but preserve the raw source URL for testing. One normalized row can represent several variants that require different infrastructure rules.
( Classify before redirecting )
Classify every row before you redirect it.
Every row should include the old URL, content type, current status, indexability, traffic, revenue, backlinks, intended new URL, migration action, rationale, owner and test result. Classification prevents the common mistake of redirecting everything merely to eliminate 404s.
Legacy page Preferred action
Product still sold301/308 to the same product. Preserves product intent and continuity.
Discontinued product with a true replacementPermanent redirect to replacement. Useful when customer need and specification are closely aligned.
Discontinued product without an equivalentKeep a useful archive page, or return 404/410. An unrelated redirect misleads users and can be treated as a soft 404.
Legacy category matching a Shopify collectionPermanent redirect to equivalent collection. Preserves browse and commercial intent.
Two overlapping articles consolidatedRedirect both to the stronger combined resource. Reasonable many-to-one mapping where intent is genuinely the same.
Expired campaign with no lasting value404/410 or a retained explanation page. No relevant destination exists.
Tracking parameter variantNormalize only where necessary. Avoid creating thousands of brittle rules for non-indexable variants.
Tradeoff: preserving every legacy page can carry obsolete or thin content into Shopify. Deleting too aggressively can remove long-tail demand, backlinks and support value. Use evidence: retain or consolidate pages with a clear audience; retire pages that have no meaningful replacement; never use the homepage as a universal disposal route.
/ Phase 3 — Shopify URL architecture
Lock the Shopify URL architecture.
Shopify routes products, collections, pages and blog content through platform conventions such as /products/, /collections/, /pages/ and /blogs/. Decide destination handles before finalizing redirect mapping. Repeated handle changes create duplicate work and make QA unreliable.
Preserve proven slugs when they remain accurate, but do not recreate an awkward legacy hierarchy at any cost. A stable Shopify destination with a precise redirect is better than a fragile custom architecture created only to mimic the old platform.
01Confirm primary domain, HTTPS and preferred hostname.
02Approve product, collection, page, blog and article handles.
03Decide how discontinued products will be handled.
04Define collection taxonomy and navigation independently from old platform limitations.
05Resolve international domain, subfolder and language strategy with Shopify Markets.
06Identify routes that need an app, edge rule or architecture change rather than a Shopify admin redirect.
07Freeze high-risk structural changes before redirect QA starts.
/ Redirect QA
Keep redirects relevant and direct.
Automated testing should request every source URL and record the first response, final response, final destination, hop count and unexpected changes. Then manually inspect the highest-value and most unusual routes.
( Avoid )
+Redirect chains and circular rules
+Redirecting all missing products or categories to the homepage
+Mapping informational pages to commercial pages with different intent
+Sending all regional URLs to one default market
+Redirecting to a URL that is noindexed, non-canonical, blocked or itself redirected
+Case-sensitive or query-string rules that work only for a sample URL
+JavaScript or meta-refresh redirects for primary migration paths
( Test the entire set, not a sample )
+Old URL returns the intended 301 or 308.
+Redirect reaches the approved destination in one hop.
+Destination returns 200 and is publicly accessible.
+Destination content satisfies the old page’s intent.
+No redirect loop, mixed protocol or hostname bounce occurs.
+Query strings and fragments behave as intended.
+International routes retain language and market intent.
+Redirects work on the production domain, not only a staging hostname.
/ In plain terms
Understand Shopify redirect constraints.
Shopify can import URL redirects in bulk and manage them in the admin, but not every source path is available for redirection.
Reserved platform routes and fixed resource paths can conflict with legacy structures. Audit these early rather than assuming the final spreadsheet can always be imported unchanged.
Some migrations need routing at the CDN, reverse-proxy or legacy edge layer, particularly when multiple domains, complex parameters or reserved paths are involved. That adds operational flexibility, but also another system that must be monitored and kept after launch. Prefer the simplest layer that can implement the rule correctly and survive decommissioning of the old platform.
/ Phase 5 — Canonicals
Align canonicals, internal links and indexation.
Redirects explain where old URLs moved. Canonicals explain which URL should represent materially similar new content. They support each other, but they are not interchangeable. Google recommends self-referencing canonicals on new URLs during a site move. For an indexable Shopify page, the canonical, internal links, XML sitemap, hreflang and redirect destination should all identify the same preferred URL.
Do not canonicalize genuinely different products or collections merely to reduce the index. A canonical is for duplicate or very similar pages, not a substitute for deciding which content should exist. Google may ignore a canonical when page content, linking and sitemap signals contradict it.
01Products use the intended product URL as canonical, including when reached through a collection route.
02Collections, pages, articles and the homepage are self-canonical where indexable.
03Canonicals use the production HTTPS hostname.
04No canonical references staging, a legacy domain, a redirect or a 404.
05Theme and apps do not output duplicate or conflicting canonical tags.
06Pagination, filtering, search and parameter routes follow an explicit indexation strategy.
07Localized pages have coherent canonicals and reciprocal hreflang where applicable.
/ Internal links and indexation
Update internal links to final URLs.
Navigation, breadcrumbs, product recommendations, editorial links, footer links and app-generated modules should link directly to the final Shopify URLs. Leaving old URLs in templates creates unnecessary redirect traffic, slows discovery and makes the architecture harder to understand.
Also update controllable external destinations: Google Merchant Center feeds, ads, email templates, affiliate systems, social profiles and major partner links. Redirects should remain a durable safety net, not become the permanent internal linking system.
Check indexation controls. Development stores often use password protection, robots rules or noindex directives. Those controls are useful before launch and damaging afterward. Add an explicit, owned launch task to remove temporary barriers and verify the rendered production response.
( Indexation checks )
+Important templates return 200 without authentication.
+Robots.txt does not block content that must be crawled.
+Meta robots and X-Robots-Tag headers allow intended indexing.
+Canonical pages are present in Shopify’s generated /sitemap.xml.
+Redirects, errors and non-canonical variants are absent from the sitemap.
+Structured data reflects visible content and has no conflicting app output.
/ Phase 6 — Launch day ( 12 )
Launch-day Shopify SEO checklist.
Step
01
Freeze structure.
Stop untracked changes to handles, collections, navigation, templates and redirect destinations.
Step
02
Take final exports.
Save the current redirects, URL inventory, crawl, analytics baseline and Search Console data.
Step
03
Complete the data delta.
Synchronize products, stock, customer-facing content, reviews and records changed since the main migration.
Step
04
Load redirect rules.
Confirm import errors and rule conflicts are resolved.
Step
05
Switch the domain.
Make the approved DNS and Shopify domain changes with rollback information available.
Step
06
Remove launch barriers.
Disable password protection or temporary noindex controls at the agreed moment.
Step
07
Run smoke tests.
Test checkout, account flows, forms, analytics, consent, feeds and representative URLs.
Step
08
Crawl from outside the build environment.
Verify status codes, canonicals, robots, internal links, hreflang, structured data and assets.
Step
09
Test all legacy URLs.
Compare observed redirects with the approved mapping.
Step
10
Submit the sitemap.
Add or resubmit the Shopify sitemap in Google Search Console.
Step
11
Use Change of Address only when appropriate.
If the domain or subdomain changes, follow Google’s Change of Address process; do not use it for path-only changes on the same domain.
Step
12
Annotate monitoring systems.
Record the precise launch time, DNS milestones and known issues.
( Choose a lower-risk trading window when SEO, engineering, ecommerce operations and a decision-maker are available. Avoid launching immediately before a major campaign, peak sales event or unstaffed weekend. A quieter launch does not change how Google processes the move, but it reduces customer impact and shortens incident response. )
/ Phase 7 — Post-launch monitoring
( Window · action · checks )
Post-launch monitoring.
Monitoring should answer two questions: is Google transferring signals as expected, and can customers still reach valuable content? Review daily during the first week, several times per week through the first month, and weekly until the pattern stabilizes. Larger or international sites may need longer.
01
First 24 hours
Fix broad blockers immediately
Availability, robots, canonicals, redirects, analytics, checkout, sitemap.
02
Days 2–7
Patch specific mapping and template defects
404s, redirect mismatches, Googlebot activity, indexability, top landing pages.
03
Weeks 2–4
Investigate clustered losses
Clicks, impressions, queries, page groups, canonical selection, coverage and revenue. Avoid uncontrolled site-wide changes.
04
Weeks 5–12
Prioritize persistent gaps
Recovery against baseline, long-tail pages, markets, rich results and Core Web Vitals. Begin measured improvements.
05
Quarterly
Maintain the redirect estate
Legacy redirect demand, chains introduced later, broken backlinks and retired content. Update controllable links.
/ What to watch
Search Console, crawls, logs and revenue.
Search Console is sampled and delayed, so combine it with regular crawls, server or CDN logs, analytics and revenue reporting. Logs show which old URLs search bots and users still request. Analytics shows whether the final pages convert. A crawler verifies the implemented site rather than Google’s current view of it.
( Google Search Console monitoring )
+Compare clicks, impressions, CTR and position by page type, query group, country and device.
+Inspect representative high-value URLs and Google-selected canonicals.
+Review Page indexing for spikes in not found, soft 404, blocked, duplicate and redirected URLs.
+Watch sitemap discovery and indexing, not merely submission status.
+Check rich-result reports for product, merchant listing, breadcrumb and review regressions.
+Review Core Web Vitals by URL group.
+Keep old-domain Search Console properties available when the domain changes.
( Crawls, logs and commercial monitoring )
+Track legacy 404s and unmatched high-value URLs.
+Detect chains, loops and redirects that terminate on errors.
+Compare the live canonical to the expected canonical.
+Monitor internal links to redirects and broken destinations.
+Check organic landing-page revenue and conversion, not traffic alone.
+Watch product feeds, paid destinations, email links and affiliate URLs.
+Record fixes and dates in an incident log for later comparison.
/ Diagnosing a drop
How to diagnose a post-migration drop.
Start by finding the shape of the decline. Is it sitewide, limited to a directory, isolated to mobile, concentrated in one country, or specific to non-brand product queries? Then compare the affected old and new pages.
Do not react to normal transition noise with simultaneous changes to titles, copy, navigation, apps and templates. That destroys the ability to identify cause and effect. When the loss clusters around one migration defect, correct that defect first.
01Request the old URL and confirm its complete redirect path.
02Verify the destination returns 200, is indexable and has the expected canonical.
03Compare content, products, metadata, structured data and internal prominence with the legacy page.
04Check whether Google has crawled the new page and which canonical it selected.
05Review sitemap inclusion, hreflang and internal links.
06Separate ranking loss from analytics, consent, stock or conversion problems.
07Fix the smallest proven cause, document it, and monitor the affected cohort.
( Redirect retention )
How long should redirects remain?
Google recommends keeping site-move redirects for as long as possible and generally at least one year. That gives Google time to revisit old URLs and transfer signals. For customers, backlinks, bookmarks, packaging and old campaigns, useful redirects often warrant indefinite retention.
Do not remove a redirect solely because traffic is low in a recent analytics window. Check search-engine crawling, backlinks and known offline uses. If an old page still has a relevant successor, maintaining the route is inexpensive insurance.
Minimum 1 year
At least one year
Keep relevant redirects for at least one year and usually longer.
/ Tradeoffs ( 04 )
Common migration tradeoffs senior teams should decide explicitly.
01 · Domain
Same domain versus a new domain
Keeping the established domain removes one major variable, but path changes still require complete redirects. A new domain can be commercially necessary for a rebrand or consolidation, yet it adds Change of Address, domain-level verification, external-link updates and a longer transition. If possible, avoid combining a domain change with a complete redesign and content rewrite.
02 · Content
Content parity versus improvement
Preserving all high-performing content makes the migration easier to diagnose. Improving weak pages may produce a better store, but also changes relevance at the same moment URLs and platform signals move. For high-value pages, default to parity at launch and schedule measured improvements afterward. Make exceptions only when the old content is legally risky, inaccurate or fundamentally incompatible with the new strategy.
03 · Catalogue
Retained product pages versus aggressive cleanup
Keeping discontinued products can preserve demand, reviews and support value if the page clearly states availability and guides customers to appropriate alternatives. Aggressive deletion reduces catalog clutter but can discard backlinks and long-tail visibility. Decide by product lifecycle, demand, replacement quality and customer usefulness rather than applying one rule to the whole catalog.
04 · Routing
Shopify-native redirects versus edge routing
Shopify-native redirects are easier for ecommerce teams to own. Edge routing can handle reserved paths, multiple legacy hosts and complex patterns, but creates another long-lived dependency. Choose the lowest-complexity solution that covers all valuable URLs, and document who maintains it after the migration project ends.
/ Final checklist
Final Shopify SEO migration checklist.
Before
build ends
Before development is complete
Baseline organic traffic, revenue, queries, pages and indexation.
Combine sitemap, crawl, analytics, Search Console, logs and backlink URLs.
Classify pages by value, intent and migration action.
Approve Shopify architecture, handles and international routing.
Assign owners for redirects, canonicals, content, measurement and launch.
Before
launch
Before launch
Map every valuable old URL to the closest relevant destination.
Resolve redirect chains, loops, conflicts and reserved-route limitations.
Validate self-referencing production canonicals by template.
Update internal links, hreflang, feeds and controllable campaign destinations.
Preserve high-value content, metadata and structured information.
Confirm Shopify’s sitemap contains canonical 200-status pages.
Test every redirect and crawl a production-like environment.
Prepare rollback criteria and launch-day escalation contacts.
At
launch
At launch
Remove password, noindex and temporary crawl restrictions.
Verify the preferred domain, HTTPS and public 200 responses.
Test the full legacy URL set on production.
Crawl canonicals, links, robots, hreflang, structured data and assets.
Verify analytics, consent, checkout and revenue events.
Submit the sitemap and use Change of Address only for a domain move.
After
launch
After launch
Monitor daily for broad technical and commercial failures.
Compare page types, queries, countries and devices against the baseline.
Review 404s, soft 404s, redirects, indexing and Google-selected canonicals.
Use crawls and logs to supplement delayed Search Console data.
Fix proven, clustered defects before making broad optimizations.
Keep relevant redirects for at least one year and usually longer.
( Keep relevant redirects for at least one year and usually longer. )
/ FAQ ( 08 )
Shopify SEO migration, answered.
What should a Shopify SEO migration checklist include?
It should include a pre-migration baseline, a complete legacy URL inventory, approved Shopify destinations, one-hop permanent redirects, content and metadata parity, canonical and internal-link QA, indexation checks, sitemap submission, launch-day testing and page-level post-launch monitoring. International routes, structured data, feeds and analytics also need explicit owners where relevant.
Will migrating to Shopify hurt SEO?
Not inherently. Rankings may fluctuate while Google recrawls and reindexes changed URLs, but serious losses usually come from preventable issues such as missing or irrelevant redirects, reduced content, incorrect canonicals, blocked crawling, broken internal links or poor measurement. A controlled migration can preserve and later improve organic performance.
Should every old URL redirect during a Shopify migration?
No. Every valuable old URL should have a deliberate outcome, but a permanent redirect is appropriate only when a relevant successor exists. An obsolete page with no equivalent can return 404 or 410. Redirecting unrelated pages to the homepage creates a poor experience and may be interpreted as a soft 404.
Should Shopify migration redirects use 301 or 302?
Use server-side permanent 301 or 308 redirects for completed URL moves. Use 302 or 307 only when the change is genuinely temporary. The destination should return 200, match the old page’s intent and be reached in one hop.
How should canonical tags work after a Shopify migration?
Each indexable new page should normally use a self-referencing canonical on the production HTTPS domain. Redirect destinations, internal links, XML sitemap entries and hreflang should agree with that preferred URL. Check themes and apps for duplicate canonicals, and never leave canonicals pointing to staging or the old domain.
How long should Shopify redirects stay in place?
Keep them for at least one year, in line with Google’s site-move guidance, and as long as possible. Relevant redirects often deserve to remain indefinitely because customers, backlinks, bookmarks, printed material and search crawlers may continue requesting old URLs long after launch.
How long does SEO recovery take after a Shopify migration?
There is no universal timeline. Smaller, well-mapped sites may stabilize within weeks, while large, international or heavily changed stores can take several months. Crawl demand, site size, content changes, domain changes and technical quality all matter. Monitor cohorts and templates rather than waiting for one sitewide number to recover.
What should be monitored after a Shopify migration?
Monitor organic clicks, impressions, queries, revenue and conversion by landing page and template; old and new URL status; 404s, soft 404s, chains and loops; sitemap indexing; Google-selected canonicals; internal links; structured data; Core Web Vitals; bot activity; product feeds and analytics integrity. Compare results with a dated pre-launch baseline.
Official technical references: Google Search Central: Site moves with URL changes · Google Search Central: Canonicalization · Google Search Console: Change of Address tool · Shopify Help Center: Creating and managing URL redirects · Shopify Help Center: Finding and submitting your sitemap
/ Next
Planning a high-stakes Shopify migration?
Signature Works helps established ecommerce brands plan, build and rescue Shopify and Shopify Plus migrations. We combine platform engineering with URL-level SEO QA, so redirects, canonicals, international routes, content and measurement are treated as launch requirements rather than post-launch cleanup.
Talk to Signature Works about your Shopify migration to review the architecture, migration risks and launch plan before valuable organic traffic is exposed.
Also worth a look: Migrations and rescues · Store audits · Shopify technical ownership
/ Next
Want this done on your store?
Tell us what’s going on. A first look costs nothing.