Redesigning Your E-commerce Website Without Hurting SEO

Most e-commerce redesigns lose organic traffic, and most of that loss is avoidable. The pattern is always the same: URLs change without redirects, category pages get merged or dropped, product content gets “cleaned up” into thin templates, and nobody checks Search Console until sales dip six weeks later. This guide is the process we use for WooCommerce and other store redesigns so the new site launches with its rankings intact, plus what to watch in the first 90 days after launch.

Benchmark everything before a designer opens Figma

You cannot protect what you have not measured. Before the project starts, capture a baseline that you can compare against after launch.

1. Crawl the current site. Run Screaming Frog (free up to 500 URLs, paid above that) or Sitebulb over the whole store. Export every URL with its status code, title, meta description, H1, canonical, word count and inlinks. This becomes your redirect map later.
2. Export Search Console data. Performance report, last 16 months, by page and by query. Note the top 100 pages by clicks and the queries each one ranks for. These pages get special handling.
3. Export analytics. From GA4, landing pages by organic sessions and revenue for the last 12 months. A page that sends 3% of traffic but 15% of revenue is more important than its traffic suggests.
4. Pull backlinks. Ahrefs, Semrush or Search Console’s Links report. Any URL with external links must redirect one-to-one, no exceptions.
5. Record Core Web Vitals. PageSpeed Insights field data for the home page, a category page and a product page. The new site should beat these numbers, not just match them.
6. Screenshot rankings. A rank tracker for your top 50 commercial keywords, or at least a manual record, so you can separate a redesign problem from a normal fluctuation.

Put all of this in one shared spreadsheet. Every later decision (which pages to keep, merge, or drop) references it.

Decide what changes and what stays

A redesign can mean anything from a new theme on the same URLs to a replatform with a new domain. Risk rises with each layer you change at once. Be explicit about which of these are in scope:

Change	SEO risk	What protects you
New theme, same URLs and content	Low	Keep templates outputting the same headings, schema and internal links
New URL structure (permalinks, category paths)	High	One-to-one 301 map for every URL
Merging or removing categories and products	High	Redirect to the closest parent, never the home page
Rewriting product and category content	Medium	Keep the entities and terms that rank; do not shorten below current word count
New platform (Shopify to WooCommerce, Magento to WooCommerce)	High	All of the above plus schema and faceted navigation audit
New domain	Very high	All of the above plus Search Console Change of Address

Our position: unless there is a strong business reason, keep the URL structure. A redesign is a visual and UX project. Changing permalinks at the same time doubles the risk for almost no ranking upside. If you must change them (moving from /product-category/shoes/running/ to /running-shoes/, for example), treat it as a separate migration with its own testing.

On WooCommerce, category and product base slugs live under Settings → Permalinks → Optional. Changing them there rewrites every product and category URL at once, which is exactly why it should be a deliberate decision with a redirect map ready.

Build the redirect map, then test it on staging

The single most important deliverable in the project is a spreadsheet with two columns: old URL, new URL. Google’s site move documentation asks for permanent server-side redirects (301 or 308), no chains longer than three hops, and redirects kept in place for at least a year. In practice, keep them forever; there is no cost.

Rules for the map

• Every URL with organic traffic, backlinks or conversions gets a one-to-one redirect to its direct equivalent.
• Removed products redirect to their category or the closest replacement product, not the home page. Bulk redirects to the home page are treated as soft 404s.
• Discontinued products with backlinks can stay live as a “no longer available” page linking to alternatives, which often keeps more value than a redirect.
• Images matter too. If product image paths change, redirect them or you lose Google Images traffic, which can be 5 to 15% of an e-commerce site’s organic visits.
• Check the old site for existing redirects and collapse chains so old-old URL → new URL in one hop.
• Parameters: decide how faceted URLs (?filter_color=red&orderby=price) are handled. Most should be canonicalized to the clean category URL, not redirected.

Where to implement on WordPress

For up to a few hundred redirects, the Redirection plugin or the redirect managers in Rank Math and Yoast SEO Premium are fine. For thousands, put them at the server level (Nginx map or Apache RewriteMap) or in Cloudflare Bulk Redirects; plugin-level redirects on every request add database load at scale. Whatever you use, import the map to staging and crawl the old URL list with Screaming Frog in list mode. Every row should return 301 and land on a 200 page in one hop. Fix anything that returns 404, 302, or a chain.

Preserve the on-page signals that actually rank

Designers optimize for how a page looks. Search engines read the HTML. Several things routinely get lost between a design mock-up and a WooCommerce template.

Content on category pages

Category pages are where e-commerce rankings live. If the current category has 300 words of descriptive copy below the product grid and the new design has a hero image and nothing else, expect the rankings to go with it. Keep the copy, even if you collapse it behind a “read more” on mobile (it still counts as long as it is in the HTML and not loaded on click).

Headings, titles and meta

Carry titles and meta descriptions across using your SEO plugin’s export and import (Yoast and Rank Math both support CSV). Make sure the template’s H1 is the product or category name, not a logo or a tagline. Audit the new theme for duplicate H1s, which page builders produce constantly.

Structured data

WooCommerce outputs Product schema by default, but some themes and builders replace the single product template and lose it. Test a product page in Google’s Rich Results Test on staging. You want Product with offers, price, availability and aggregateRating (if you have reviews) passing. Losing rich results costs click-through rate even when rankings hold. The same applies to BreadcrumbList; keep breadcrumbs in the template.

Internal links and navigation

A simplified mega menu that drops 40 subcategories from the header removes 40 site-wide internal links. Those subcategories will lose crawl priority and authority. If the menu has to shrink for UX, replace the links elsewhere: footer, category hub pages, or “shop by” blocks on parent categories.

Faceted navigation

New filter plugins are a common source of index bloat. Check that filter URLs carry a canonical to the base category and that your robots.txt blocks crawl of obviously useless combinations (sort order, per-page counts). Do this on staging, because cleaning up 50,000 indexed filter URLs after launch takes months.

Launch day checklist

Pick a low-traffic window (for most stores, Tuesday or Wednesday morning in your main market, never Friday and never before a sale). Then run through this in order.

1. Take a full backup of the old site and database, and confirm you can restore it.
2. Remove any noindex from the new site. Check Settings → Reading (“Discourage search engines”) and the SEO plugin’s global settings. Staging sites get indexed and production sites get noindexed more often than anyone admits.
3. Confirm the redirects are active on production by testing 20 URLs from your map with curl or a redirect checker.
4. Regenerate and submit the new XML sitemap in Search Console. Keep the old sitemap submitted for a few weeks so Google recrawls the old URLs and sees the redirects faster.
5. If the domain changed, use Search Console’s Change of Address tool (Settings → Change of address). It only applies to domain or subdomain moves, not path changes.
6. Run a full crawl of the live site. Look for 404s, redirect chains, missing canonicals, missing titles, and pages blocked by robots.
7. Check GA4 and any conversion tracking fires on a real test order, and refund it.
8. Test checkout on mobile with a real payment method. A redesign that breaks Apple Pay loses more revenue than any ranking drop.

The first 90 days: what to monitor and when to worry

Some fluctuation is normal. Google has to recrawl, reprocess and reassign signals to the new URLs, and for a mid-size store that takes four to eight weeks. Larger sites and domain changes can take several months. Here is how to tell normal from broken.

• Daily for the first two weeks: Search Console Pages report for a spike in “Not found (404)” or “Page with redirect” that is not dropping; Crawl Stats for server errors; organic sessions and revenue in GA4 against the same weekday last month.
• Weekly through day 90: rankings for the top 50 keywords against your baseline, indexed page count, Core Web Vitals field data (it takes 28 days to refresh).
• Normal: a 5 to 15% dip in organic traffic in weeks one to three that recovers by week six to eight.
• Investigate now: a drop over 20% that is still falling at week three, a specific category that lost all its rankings, or indexed pages doubling (index bloat from filters).

When something is wrong it is almost always one of four things: a missed redirect set, a noindex left on a template, a template that dropped content or schema, or a crawl budget problem from new parameter URLs. Check those four before assuming an algorithm update.

A short real scenario

A WooCommerce store selling outdoor gear came to us after a redesign that cost them 38% of organic revenue in two months. The new theme was faster and looked better. Three things had gone wrong: the agency had changed the product category base from product-category to shop without redirects, the new category template had no room for the description text so it was deleted, and the mega menu was replaced by a four-item header. We rebuilt the redirect map from the old crawl (thankfully still in the agency’s files), restored category copy from a database backup, and added a “shop by activity” link block to every parent category. Traffic recovered to baseline in nine weeks and passed it by month four, mostly because the new theme’s Core Web Vitals were genuinely better. None of the loss had been necessary.

If you are planning a replatform rather than a reskin, our WordPress migration service handles the redirect mapping and testing, and for store-specific template work the WooCommerce development team can audit a staging build before it goes live.

Frequently asked questions

Should we launch the whole redesign at once or in phases?

Google’s guidance is to move small and medium sites all at once, which lets it detect the change faster. Large stores (tens of thousands of URLs) can move by section so problems are easier to isolate. For most WooCommerce stores, all at once with a thorough staging test is right.

How long do we keep the redirects?

Google says at least one year. We say indefinitely. Old URLs live on in bookmarks, emails, and backlinks long after you have forgotten them.

Will a faster site improve rankings enough to offset the risk?

Page experience is a minor ranking factor; a faster site helps conversion rate far more than it helps rankings. Do the redesign for users and revenue, and protect rankings as a separate workstream.

We already launched and traffic dropped. Is it too late?

No. Recover the old URL list from an old crawl, the Wayback Machine, or Search Console’s Performance export, build the redirect map now and deploy it. Rankings usually come back within weeks once Google can follow the redirects, though the longer the gap, the more you lose permanently.

What we’d do

Keep the URLs. Crawl before you start. Build and test the redirect map on staging before anyone sees the new design. Carry over category copy, schema and internal links deliberately rather than hoping the theme handles them. Launch midweek, watch Search Console daily for two weeks, and keep the redirects forever. A redesign done this way is boring from an SEO point of view, which is exactly what you want.