Shopify Migration SEO Checklist (2026 Edition)

Most ecommerce migrations don't fail because of design.

They fail because of redirects, missing pages, inconsistent URL structures, and performance regressions that no one measured before launch.

If you're migrating to Shopify, this checklist will keep you from breaking what you've spent years building.

This guide is based on a real 339-URL migration from AmeriCommerce to Shopify that went live in April 2025 with zero traffic loss.

1. Inventory Every URL Before You Touch DNS

Before we migrated texasbeardcompany.com, we documented exactly 339 live URLs.

That included:

• Product URLs like
  /natural-beard-oils/clove-citrus-beard-oil

• Category pages like
  /beard-oil

• Legacy system URLs like
  /store/p/33-Beard-Trimming-Scissors.html

If you don't have a complete inventory, you cannot verify redirects later.

Export them. Crawl them. Normalize them. Then freeze that list.

This becomes your migration truth set.

2. Understand Your Legacy URL Structure (It's Messier Than You Think)

AmeriCommerce allowed two parallel realities:

• System-generated URLs like
  /store/p/49-Beard-Oil-4-pack.html

• Manually created “clean” URLs like
  /natural-beard-balms/clove-citrus-beard-balm

Over 10 years, those paths accumulated inconsistently. Some were nested. Some weren't. Some were indexed. Some weren't.

Shopify enforces structure:

• /products/
• /collections/
• /blogs/

That structural shift is where migrations get dangerous.

Before building redirects, map:

• What Shopify will generate
• What Google has indexed
• What customers have bookmarked

If you skip this step, you'll leak authority.

3. Build Redirects at Scale (Expect More Than You Think)

We ended up creating 648 redirects in Shopify.

Why more than 339 URLs?

Two main reasons:

1. Both /store/p/*.html system URLs and custom URLs were indexed.
2. Renaming the blog multiple times in Shopify automatically generated additional redirect layers for every post, including:
   • /blog/3-Tips-on-How-to-Grow-a-Fantastic-Fall-Beard
   • /blog/That-Uncomfortable-Itchy-Beard-Feeling

Redirect math compounds fast.

Flat collection URLs like /beard-oil also had to resolve cleanly to their new Shopify equivalents.

If you're not validating redirects at scale, read our guide on
setting up Shopify redirects correctly.

Manual spot checking is not enough.

4. Decide What Should 404 vs Redirect

Not every page deserves to live forever.

We intentionally allowed some URLs to 404, including:

• /texas-beard-co-affiliate-program
• /beard-care-subscription.html

These pages were obsolete and not strategically important.

Other pages, like /all-products, were redirected to a more appropriate destination after we retired the original structure.

This is a business decision, not just a technical one.

If the page has traffic, backlinks, or revenue history — redirect it.
If it's dead weight — let it go.

5. Test Status Codes (And Watch for 429s)

When scanning the old AmeriCommerce site, we hit rate limiting (429 responses). We had to slow our crawl speed to get clean data.

This matters.

If your validation tool is hammering the old site, you'll misinterpret rate limiting as broken pages.

Verify:

• 200 stays 200
• 301 goes exactly where it should
• No 302 mistakes
• No hidden redirect chains

If you're unsure how to detect chains, see
how to detect redirect chains during a Shopify migration.

6. Measure Performance Before and After

Here's the honest reality from this migration.

Backend performance improved dramatically.

Mean TTFB dropped from 327ms → 139ms (↓57%)

Core Web Vitals improved across the board:

• LCP: 772ms → 676ms
• CLS: 0.109 → 0.005
• TBT: 129ms → 66ms

However, frontend payload increased:

• Avg page size: 13.6 KB → 51.3 KB
• Total load time increased due to a modern Shopify theme

That's expected. Modern ecommerce themes ship more JavaScript and CSS.

The key takeaway: measure both backend response and frontend weight.
Don't assume “new platform” automatically means “better.”

For deeper validation workflows, see
How to measure TTFB before and after a migration.

7. Scan Multiple Times Before Launch

We scanned all 339 URLs multiple times before flipping DNS in April 2025.

Each scan caught issues we would have missed manually, including a handful of 404s.

DNS was flipped cleanly. No rollback. No panic.

If you can't compare old vs new at scale — you're guessing.

8. Flip DNS Confidently

When everything validated:

• Redirects correct
• Status codes verified
• Performance measured
• Critical URLs confirmed

We flipped DNS and didn't look back.

Traffic held steady. No ranking collapse. No emergency patches.

That's what preparation buys you.

The Real Difference Between a Safe Migration and a Risky One

Most Shopify migrations don't fail because of Shopify.

They fail because teams don't compare:

• Old vs new status codes
• Old vs new performance
• Missing pages
• Redirect accuracy

At scale.

That's exactly why Cutover exists — to scan both domains, validate redirects, measure performance deltas, capture screenshots, and surface problems before Google does.

If you're mid-migration, the next step isn't "hope."

It's validation.

Run a Shopify migration scan to verify redirects, status codes, and performance across your old and new domains.