usdigitalmarketingindex.com SEO
How should a retailer manage SEO when several individual SKUs become one consolidated product?
Updated November 15, 2026
Map every old SKU’s page to its place in the new product before anything is switched off, choose one URL for the consolidated product, redirect each old URL to it only where the old item truly exists inside it as a variant, and update every internal reference. When five separate product pages for five sizes of the same item become one page with a size selector, five URLs have histories: links from other sites, positions in search results, reviews, and customers’ bookmarks. A mapping carried out with the catalog team’s knowledge of what each SKU is now keeps those. A bulk switch that deletes the old records and creates a new one discards them and leaves old addresses returning errors.
Inventory mapping and identity
Begin with what each old SKU has become.
| Old SKU's fate | Meaning | SEO treatment |
|---|---|---|
| Becomes a variant of the new product | The same item, now selected by option | Redirect to the new product, to the variant's URL where one exists |
| Merged with another SKU into one variant | Two records for the same item, de-duplicated | Redirect both to that variant |
| Not carried into the new product | Discontinued at consolidation | Handle as a discontinued product; no redirect to the new product unless it is a true successor |
| Stays separate | Different enough to remain its own product | No change |
An old-SKU-to-new-product mapping table, for a hypothetical consolidation:
| Old SKU | Old URL | New product | New variant | New URL | Action | Reviews | Rule check |
|---|---|---|---|---|---|---|---|
| RAD-600-W | /products/radiator-600-white/ | Northgate Panel Radiator | 600 mm, white | /products/panel-radiator/?size=600&color=white | 301 | Carry to product | Variant exists |
| RAD-900-W | /products/radiator-900-white/ | Northgate Panel Radiator | 900 mm, white | /products/panel-radiator/?size=900&color=white | 301 | Carry to product | Variant exists |
| RAD-900-A | /products/radiator-900-anthracite/ | Northgate Panel Radiator | 900 mm, anthracite | /products/panel-radiator/?size=900&color=anthracite | 301 | Carry to product | Variant exists |
| RAD-900-W2 | /products/radiator-900-white-v2/ | Northgate Panel Radiator | 900 mm, white (duplicate record) | Same as RAD-900-W | 301 | Merge | Confirmed same item |
| RAD-1200-C | /products/radiator-1200-chrome/ | None | Not carried forward | None | Discontinued process | Archive | Not in new product |
| RAD-VERT-W | /products/vertical-radiator-white/ | None; remains separate | Unchanged | None | Unchanged | Different product type |
The rule check column is the business validation. For each row, someone who knows the catalog confirms that the old item is the named variant: same dimensions, same specification, same thing in the box. An SEO mapping made from product titles alone will pair items that only sound alike.
Choosing the final product URL
One URL becomes the consolidated product’s canonical address.
| Option | For | Against |
|---|---|---|
| A new, clean URL for the product family | Describes the product without a variant in the path | Every old URL must redirect |
| Reuse the old URL with the strongest history | One fewer redirect; that URL's links stay direct | Its slug names a single variant, which misdescribes the page |
Evidence for “strongest history” comes from the site’s own data: external links in the Search Console Links report, organic clicks in the performance report, and referral visits.
Variants then get URLs that select them. Google’s ecommerce guidance recommends that each variant be identifiable by a separate URL, by path segment or query parameter, and that where optional parameters identify variants, the URL without the parameter be the canonical one (Google’s guidance on URL structure for ecommerce sites).
Structured data follows the new shape. Google’s documentation describes a ProductGroup with its variants for this arrangement (Google’s product variant structured data documentation). Each variant keeps its own SKU, price, and availability within the group.
Variant/order history implications
Consolidation touches more than pages.
| Area | Question to settle |
|---|---|
| Reviews | Are reviews pooled on the consolidated product? If so, does each show which variant it was written about? |
| Ratings | Is a pooled average fair to variants that were rated differently? |
| Order history | Do customers' past orders still link to a working page? |
| Reorder links and emails | Do old links in order confirmations resolve? |
| Wishlists and saved carts | Are saved items mapped to variants? |
| Product identifiers | Does each variant keep its own identifier, such as a GTIN, in the data and the feed? |
| Feeds | Are old items removed and variants submitted with a shared group identifier? |
| Analytics | Is there an annotation on the date, so before-and-after comparisons are read correctly? |
On reviews, be accurate. Pooling reviews of several sizes of one item is reasonable where the item is the same. Pooling reviews of things that differ in function presents feedback about one product as feedback about another. Label each review with its variant.
Redirect and internal link updates
Redirects:
- Use permanent redirects. Google’s documentation says to use them “when you’re sure that the redirect won’t be reverted” (Google’s documentation on redirects).
- One hop from each old URL to its final destination.
- Redirect to the variant-selecting URL, so a visitor who followed a link to the 900 mm white radiator lands with that option selected.
- Do not redirect SKUs that were not carried forward to the new product merely because it is nearby. Those follow the discontinued process.
- Keep the redirects in place indefinitely.
Internal references to update:
| Location | Change |
|---|---|
| Category listings | One tile for the product, not one per old SKU |
| Internal links in guides and articles | Point to the new product or the relevant variant URL |
| Related-product blocks | Reference the new product |
| XML sitemap | Old URLs out; new canonical URL in |
| Site search index | Old records removed; variants searchable by old SKU codes |
| Canonical tags | New product self-referencing; variant URLs per the chosen scheme |
| Breadcrumbs | For the new product |
Keeping old SKU codes searchable on the site matters for trade customers who order by code.
Validation after launch:
- Request every old URL from the mapping table. Each returns a single 301 to the intended destination, or the planned response for discontinued items.
- Load each variant URL. The right option is selected, and price and availability match that variant.
- Run the product page through the Rich Results Test.
- Crawl the site. No internal link points to an old URL.
- Check the feed: old items gone, variants present with a common group identifier.
- In Search Console, watch the page indexing report for the old URLs moving to redirected status, and the performance report for the new URL.
- Compare the mapping table with what was built, row by row.
Expect a transition. The old URLs’ search listings are replaced by the new one as Google recrawls, and performance figures are split across old and new addresses during that period. Compare totals for the product family, not individual URLs.
Keep the mapping table. It is the record that explains, a year later, why an old address leads where it does.
Whether a variant in the consolidated product should have an indexable page of its own, instead of pointing to the main product, is a separate decision with its own tests, set out in the guide to when ecommerce product variants should have separately indexable URLs.
The order of work: map each SKU to its true fate, choose the product URL, redirect only real equivalents, update every internal reference, and verify against the table.
Add your comment to this answer