E-commerce Site Migration: Platform-Specific Checklist

Executing an ecommerce site migration without a platform-specific plan is professional malpractice. This checklist covers the minefields of Shopify, WooCommerce, and BigCommerce to protect your traffic.

Stop Admiring the Problem. Start Your Migration with a Benchmark.

Every generic guide to an ecommerce site migration starts with ‘do an audit.’ This is correct but uselessly vague. What you need is a complete, immutable snapshot of the original site before a single developer touches the staging environment.

Your goal is to capture the entire digital footprint. This isn’t just a list of top pages; it’s a comprehensive architectural blueprint. You need every URL, every redirect chain, every canonical tag, and every piece of metadata.

Fire up ScreamingCAT and run a full crawl of the production site. Don’t just hit ‘Start’ and walk away. Configure the crawler to store HTML and render JavaScript to capture everything, especially on sites heavy with client-side content. Export this crawl. This file is now your source of truth.

• All Crawlable URLs: Products, categories, blog posts, filtered navigation pages (if they are indexable).
• Metadata: Title tags, meta descriptions, H1s, and H2s for every URL.
• Directives: Canonical tags, meta robots tags (index, noindex, follow, nofollow).
• Internal Linking: A full map of your internal link structure, including anchor text.
• Performance Data: Core Web Vitals and response times from the original site.

The Shopify Migration Minefield: Simplicity at a Price

Migrating to Shopify is popular because it’s ‘easy.’ For merchants, maybe. For SEOs, it’s a rigid system with baked-in limitations that can sabotage your migration if you aren’t prepared.

First, URL structures are non-negotiable. Products live at `/products/`, and collections are at `/collections/`. If your old site used a different structure, like `/shop/product-name/`, you are implementing redirects. There is no alternative.

Second, you cannot edit the `robots.txt` file. Shopify controls it, using it to block access to internal search pages, cart, and checkout URLs. This is generally fine, but if you had custom rules on your old site, they’re gone. You’ll have to rely on meta robots tags for page-level control.

Finally, be wary of apps. Many Shopify apps create pages, add structured data, or inject scripts. During a migration, audit every single app. Does it generate duplicate pages? Does its JavaScript bloat your load times? Assume every app is guilty until proven innocent. For more foundational knowledge, review our complete technical guide to e-commerce SEO.

Wrangling WooCommerce: The Wild West of Ecommerce Site Migration

If Shopify is a walled garden, WooCommerce is the open prairie. The flexibility is immense, but so is the potential to create an SEO disaster. An ecommerce site migration involving WooCommerce requires deep diligence on plugins and server configurations.

Your primary concern is the permalink structure. WordPress and WooCommerce offer several options. Your job is to match the new structure to the old as closely as possible to minimize the need for redirects. If you must change it, you’ll be living in your `.htaccess` file for a while.

Redirects are your next battle. While plugins like Redirection are useful, they can add database bloat. For sitewide pattern-based redirects, managing them at the server level via `.htaccess` is far more efficient. This is where you separate the pros from the amateurs.

For example, if your old category structure was `/category/` and the new one is `/product-category/`, a single RegEx rule is infinitely better than 1,000 individual redirects. For a deeper dive, read our guide on 301 redirect mapping for migrations.

RewriteEngine On
RewriteRule ^category/(.*)$ /product-category/$1 [R=301,L]

BigCommerce & Headless: The New Frontier of an Ecommerce Site Migration

Migrating to BigCommerce or a headless setup is often a move for scale. These platforms bring their own unique and sophisticated challenges to any ecommerce site migration.

BigCommerce’s faceted navigation is powerful but can generate a near-infinite number of parameter-based URLs. Get your canonicalization and `robots.txt` strategy straight from day one. Decide which facet combinations should be indexable and which should be blocked or canonicalized to the main category page. Fail here, and you’ll drown Googlebot in duplicate content.

Headless migrations are a different beast entirely. Your primary concern is ensuring Google can actually render your pages. Since the frontend is decoupled from the backend, you are likely dealing with a JavaScript-heavy framework like React or Vue.

You must have a robust server-side rendering (SSR) or dynamic rendering solution in place. Relying on client-side rendering is a gamble. Use ScreamingCAT’s JavaScript rendering feature to crawl the staging site and compare the rendered HTML to the raw HTML. If critical content and links are missing from the raw HTML, you have a problem that SSR needs to solve.

In a headless migration, the SEO is no longer just auditing a website; they’re auditing a JavaScript application. The required skill set is fundamentally different.

Anonymous & Stressed-Out Developer

Post-Launch Triage: Trust, but Verify Everything

The site is live. The champagne is premature. Your work has just begun. The goal of post-launch triage is to validate the execution of your migration plan and rapidly identify failures.

First, re-crawl the live site with ScreamingCAT. Compare this new crawl data directly against your pre-migration benchmark crawl. Are all old URLs accounted for? Do they 301 redirect to the correct new URL? Are any returning 404s or, worse, 200 OK status codes on a broken page?

Next, use the list mode in ScreamingCAT to audit your redirect map. Upload your list of old URLs and crawl them. Every single one should return a 301 status code and redirect to its intended destination. Any other result is a high-priority bug.

Monitor Google Search Console like a hawk. Watch the Indexing and Crawl Stats reports. An increase in ‘Not Found (404)’ errors is your earliest warning sign that your redirect map is incomplete. Address these immediately, starting with the pages that had the most traffic on the old site. For a complete overview, always refer back to our master site migration SEO checklist.