Every store owner has the same fear: “we redesign, we lose the traffic we spent years earning.” That outcome is real — but it’s caused by specific, avoidable mistakes. A redesign that protects SEO is a planning problem, not a hope problem. Here’s the plan.
Before you redesign anything
1. Get a baseline
In Google Search Console, record: indexed pages, top organic queries, pages earning the most clicks, and organic transactions. You can’t defend what you didn’t measure. This baseline is your contract with the project — everything after launch gets compared against it.
2. Crawl the current store completely
Every product, collection, blog post, policy page, search page — with its URL, title, meta description, status code and internal links. This crawl is the source document for the entire migration.
The redesign decisions that protect SEO
3. Map every old URL to a new one
Build a spreadsheet: old URL → new URL → action (same, 301, or deprecate). The rules that matter:
- Product pages keep equivalent URLs wherever possible (URLs containing product handles are worth preserving)
- Every old URL that changes gets a 301 to the most relevant new URL — never to home
- Old collection URLs redirect to the closest surviving collection, or to a replacement page that earns the same queries
4. Carry metadata over deliberately
Titles and descriptions that already rank should be updated with intent, not replaced with boilerplate. If a new page replaces an old one, the old page’s metadata is the starting draft, not a suggestion to ignore.
5. Protect structured data
Product schema (name, price, availability, reviews) and breadcrumb schema should exist on the new store in at least the same coverage as the old one. Missing schema is an invisible regression most people only notice months later.
6. Preserve the internal linking that earned equity
If the old store’s navigation and collection cross-links built your architecture, redesign the structure to keep that logic — the new IA should route to the same money pages, not orphan them.
7. Keep images honest and optimized
Alt text migrates with the images, filenames stay descriptive, and compression applies. (This is also where most redesigns quietly win: the new store is usually faster than the old one, which is an SEO benefit in itself.)
Launch day and the weeks after
8. Redirects deploy before the new store goes live
The 301 map must be in place before cutover, not after. Every old URL should resolve to its new home on the first request.
9. Submit the new sitemap and watch indexing
New sitemap to Search Console, crawl stats tracked daily for the first two weeks. If indexed pages drop without a corresponding product removal, investigate immediately — early in a redesign, drops are usually fixable within days.
10. Compare against the baseline, weekly, for 30 days
Organic clicks, queries, indexed products, transactions. Expect some volatility — that’s normal. What’s not normal is a sustained decline in your money queries, and if it happens, the redirect map and crawl are where the answer lives.
When to roll out in phases
For large catalogs (thousands of products, heavy SEO history), a phased cutover — redesigning and switching one section at a time, measuring between phases — is often the safer play. It trades a few extra weeks of project time for a lot less risk to live traffic.
The short version: baseline → full crawl → URL map with 301s → metadata and schema carried over → redirects before cutover → 30-day monitored comparison. That’s the entire game. If you’d rather hand it off, this is exactly the process behind our Shopify redesign service — a live example is the Rachel’s Texas Kitchen rebuild.