Mapping 301 redirects for an e-commerce site is the same discipline as any migration, scaled up by the sheer number of URLs a store hides. The method is to crawl every URL the store exposes, match each to its new address, and apply the redirects in bulk before launch. Products and categories are the obvious part. The pages that sink store migrations are the ones nobody lists by hand: filtered category pages, paginated archives, indexed search results, old promo URLs, and product variants. WPBuildAI crawls the whole store, builds the complete 301 map, and applies it, so none of those are left to 404.
Bulk work on a WooCommerce store is about to get cheaper: WooCommerce 11.0, scheduled for 28 July 2026, carries 28 changes tagged for performance, caching or scalability, including HPOS query optimisation for multi-status order lists, so it is worth exporting after the upgrade rather than before.
Why stores have more URLs than you think
A store generates URLs automatically, far beyond the products and categories you manage directly. Every filter combination can produce a URL, every page of a long category is its own address, every product variant may have one, and the platform’s internal search creates more. Many of these get crawled and indexed over the years and quietly accumulate traffic and links without anyone tracking them. Ahrefs found in its search traffic study that a small share of pages carries most organic traffic, and in a store that valuable share is often spread across exactly these auto-generated URL types. So the real count of URLs that matter is usually several times the product count, which is why a migration that only maps the obvious pages breaks the rest.
The URL types people forget
Diagnosing your own exposure means knowing what gets missed. Filtered and faceted category URLs, /category/?color=blue&size=large and the like, often rank for long-tail queries and rarely appear in a manual list. Paginated category pages, /category/page/2/ onward, are separate URLs that can hold rankings. Internal search result pages sometimes get indexed and linked. Old promotional and campaign landing pages linger long after the campaign ended, still earning the odd visit and backlink. And product variants modelled as their own pages each have a URL. None of these are front-of-mind when you picture “the store,” which is precisely why they fall through, and why building the list from a crawl rather than from memory is the difference between a complete map and a leaky one.
The bulk mapping method
- Crawl everything, products, categories, filters, pagination, blog, and policy pages, following links and the sitemap.
- Reconcile against analytics and Search Console so indexed-but-orphaned URLs are caught.
- Match each old URL to its final new URL, by slug, SKU, or title.
- Prioritize by traffic and revenue so the most valuable redirects get checked first.
- Apply in bulk as single hops, then verify a sample.
Google’s site move guidance frames the whole job as completing this old-to-new map, and the spreadsheet form of it is the URL mapping template. The product-specific matching is covered in mapping product URLs to Shopify.
A worked example: a 5,000-URL store
Picture a store that “has about 1,200 products,” which sounds manageable until a crawl returns 5,000 indexed URLs. The extra 3,800 are paginated category pages, filtered variants, a few hundred indexed search results, last year’s holiday landing pages, and product variants with their own addresses. If you had hand-listed the 1,200 products and the 40 categories, you would have redirected a quarter of the store and 404’d the rest, including filtered pages that ranked for valuable long-tail terms. With the crawl, all 5,000 are in the map: the products and categories matched precisely, the paginated and filtered URLs redirected by rule to their parent, the dead promos sent to relevant categories or retired with a 410. The crawl is what turned an invisible 3,800-URL gap into a handled one.
Matching at scale
You cannot hand-map 5,000 URLs, so matching runs in tiers. Clean one-to-one matches, product slug to product slug, SKU to SKU, resolve automatically and cover the bulk. Pattern groups, paginated and filtered category URLs, map by rule to their parent collection rather than recreating each variant. The remainder, merges, splits, discontinued lines, duplicate titles, get flagged for human review. Google’s redirects guidance confirms it is the 301 that passes ranking signals to the new URL, so the matching has to land each URL on a genuinely relevant destination, not a vaguely related one. The tiered approach is what makes a large map both fast, because most rows resolve mechanically, and accurate, because the judgement calls are surfaced rather than guessed.
Applying redirects in bulk safely
Bulk application is faster and less error-prone than hand-entering hundreds of rules, but it has to be done cleanly. Each old URL should point directly to its final new URL in a single hop, never through a chain, because chains slow the site and risk loops. Watch your platform’s redirect limits too: some hosts and CDNs cap the number of redirect rules or slow down past a threshold, so very large maps may need pattern rules rather than one line per URL. Apply the map, then immediately spot-check that the rules took effect and resolve as intended. Done this way, bulk application is the safe option; the danger is not bulk itself but bulk without single-hop discipline and without a verification pass afterward.
Verify the pages that matter most
You cannot individually verify thousands of redirects, so verify by value. Sort the map by traffic and revenue and check the top pages by hand, your best-selling products and best-ranking categories, because that is where a wrong redirect costs real sales. Confirm each returns a single clean 301 to the correct destination. Then sample the rule-mapped tiers to catch systematic errors. Backlinko’s analysis of 11.8 million search results is a reminder to preserve internal links into those top pages too, so the redirected equity has somewhere to flow. The long tail still needs its redirects, but your verification effort belongs where an error would actually be felt, which is the small set of pages driving most of the revenue.
When bulk redirects go wrong
A few failure modes recur at store scale. Redirect chains form when an old URL points to another redirected URL instead of the final one, slowing every redirected visit and risking the too-many-redirects loop. Hitting a platform’s redirect-rule limit silently drops the rules past the cap, so the tail of your map never applies. Mapping filtered URLs to the homepage instead of their parent category manufactures soft 404s at scale. And applying the map without a verification pass means a systematic matching error, say, every variant pointing at the wrong product, goes live unnoticed. Each is avoided by single-hop discipline, awareness of platform limits, relevant destinations, and a post-launch sample check, which together keep a bulk apply from turning into a bulk break.
Common mistakes in store redirects
The recurring errors all reduce to incompleteness or carelessness. Building the list from your product feed instead of a crawl omits out-of-stock, variant, filtered, and paginated URLs. Redirecting products but forgetting categories, or vice versa, breaks half the store. Sending everything uncertain to the homepage creates soft 404s. Skipping the priority step spreads verification evenly and under-checks the pages that matter. And ignoring redirect chains and platform limits lets a technically-complete map fail in practice. The broader store move, cart, checkout, payment, and inventory, is scoped in migrating a WooCommerce store without losing sales, and whether product pages hold their rankings through it is covered in do product pages lose rankings when migrating.
Key points to remember
A store hides far more URLs than it shows, so completeness from a full crawl is what protects sales: crawl products, categories, filters, pagination, search, promos, and content, then reconcile against the sitemap and analytics so nothing indexed is missed. Match in tiers, clean one-to-ones automatically, pattern groups by rule, judgement calls by hand, and apply single-hop 301s in bulk while respecting platform limits. Verify the highest-value pages individually and sample the rest, and preserve internal links so equity flows. WPBuildAI crawls the whole store and builds and applies the complete redirect map, so the launch leaves nothing to 404; send your store URL for a fixed quote.
Not affiliated with WooCommerce, Shopify, WordPress, or Lovable.