Ecommerce Product and Category Redirects: A Catalog Maintenance Workflow
ecommerce SEOproduct URLscategory pages301 redirectscatalog managementsite maintenance

Ecommerce Product and Category Redirects: A Catalog Maintenance Workflow

RRedirect Portal Editorial Team
2026-11-19
7 min read

A practical ecommerce workflow for deciding which product, category, variant, seasonal, and faceted URLs to redirect and how to audit them.

Ecommerce catalogs change constantly: products are renamed, variants disappear, categories are reorganized, and seasonal landing pages go offline. This workflow explains what to redirect, what to leave accessible, and how to maintain a practical URL map that protects useful backlinks, supports shoppers, and reduces avoidable SEO loss after every catalog release.

Overview

A product URL redirect should lead visitors and search crawlers to the most relevant surviving destination. The correct destination is not always the homepage, a broad category, or the newest item in the catalog. Relevance, inventory status, internal links, backlinks, conversion intent, and canonical signals should all inform the decision.

Use a permanent redirect, generally a 301 redirect, when a URL has been replaced or removed for good and a substantially relevant destination exists. A temporary redirect, such as a 302 or 307, may be appropriate when a page is unavailable for a limited period and its original URL is expected to return. Redirect status codes and platform behavior should be tested rather than assumed; see the 301 vs 302 vs 307 guide for implementation context.

Do not redirect every discontinued product to an unrelated page. If no useful replacement exists, a carefully managed unavailable or retired page may provide a better experience than sending visitors to a generic category. The decision should reflect the shopper’s likely intent and the value of the old URL.

Redirect decision table

Catalog changeRecommended actionDestination guidance
Renamed product301 redirect the old product URL if the product remains substantially the same.Use the product’s current URL and update internal links, title, structured content, and canonical signals.
Merged categories301 redirect the retired category when the new category covers the same intent.Choose the closest surviving category, not automatically the top-level category.
Temporarily out of stockUsually keep the product URL live when the item is expected to return.Show availability, alternatives, back-in-stock options, and clear purchase guidance. Avoid a permanent redirect for a temporary inventory state.
Permanently discontinued product301 redirect only when a close replacement or useful equivalent exists.Otherwise serve a helpful retirement or unavailable response with related products and navigation.
Variant removedKeep the parent product page when other variants remain.Remove or disable the unavailable option without redirecting every variant URL to an unrelated item.
Faceted or filtered URLControl crawlable combinations according to their search and user value.Consolidate duplicates with canonical signals, links, or redirect rules where appropriate; do not mass-redirect useful landing pages without review.
Seasonal collectionRetain and refresh the URL if the collection returns regularly.For a retired one-time campaign, redirect to the closest active collection or seasonal hub only when the intent remains relevant.
Replacement item launched301 the old URL when the replacement fulfills the same primary need.Confirm that stock, specifications, price presentation, images, and product claims support the replacement.

What to track

Maintain one catalog redirect spreadsheet or database rather than making isolated edits in several systems. A reusable row structure helps merchandising, SEO, development, and analytics teams work from the same source.

Reusable catalog redirect spreadsheet template

Use one row per old URL. These columns are sufficient for a regular review and can be expanded for platform-specific fields:

  • Old URL: The complete legacy product, category, variant, filter, or collection URL.
  • New URL: The proposed destination, or leave blank when no redirect is approved.
  • Change type: Renamed, merged, discontinued, out of stock, variant removed, seasonal, faceted, or replacement.
  • Status code: Expected 301, 302, 307, 404, 410, or live-page outcome.
  • Product or category ID: The stable catalog identifier used by the commerce platform.
  • Inventory state: In stock, temporarily unavailable, discontinued, preorder, or unknown.
  • Replacement match: Exact, close, category-level, or none.
  • Backlink value: A review label based on referring domains, links, traffic, and business importance.
  • Organic and referral visits: The selected comparison period and source data.
  • Canonical target: The canonical URL returned by the destination page.
  • Owner and approval: The person or team responsible for the decision.
  • Last tested and notes: Response result, redirect hops, cache behavior, and follow-up actions.

Export changed URLs from the commerce platform, product information system, XML sitemaps, analytics reports, server logs, and backlink tools where available. Compare the export with the previous catalog version to find deleted slugs, changed handles, category moves, and new parameter patterns. Keep the original URL exactly as requested, including meaningful path details and query parameters, before normalizing them for analysis.

Prioritize URLs that receive visits, appear in internal navigation, have valuable backlinks, or represent important products and categories. A redirect audit is more useful when it separates high-impact URLs from automatically generated filter combinations that have no clear user or search value.

Cadence and checkpoints

Run this workflow at three points: before a catalog release, immediately after deployment, and during a recurring maintenance review.

Before a release

  1. Export current and proposed product, variant, category, and collection URLs.
  2. Compare both lists and classify every changed or removed URL.
  3. Review the strongest backlinks, landing-page visits, internal links, and revenue-related paths.
  4. Choose a destination based on relevance, inventory, and customer intent.
  5. Remove duplicate rules, resolve conflicting patterns, and confirm that redirects will not expose user-controlled destinations.
  6. Load the rules into a staging environment or a safe test set before publishing them.

For larger imports, use a controlled bulk process with a backup and rollback plan. The bulk redirect management guide covers organization, deduplication, and safe retirement of rules.

After deployment

Test representative URLs from every change type. Confirm the response status, final URL, page relevance, canonical tag, indexability signals, internal links, and availability message. Check for redirect chains, loops, mixed HTTP and HTTPS destinations, and redirects that point to another retired URL. A staging checklist can help structure this QA before the changes reach production; use the redirect testing checklist as a companion.

Monthly or quarterly review

Run a redirect audit against the live catalog. Identify rules that now point to unavailable, out-of-stock, irrelevant, or redirected destinations. Review newly discovered 404 responses, repeated requests for old URLs, and traffic changes around important product and category paths. A monthly review may suit frequently changing catalogs; a quarterly review may be sufficient for a smaller, stable assortment.

How to interpret changes

A redirect report is a diagnostic tool, not a list of rules to optimize blindly. A rising number of old product requests can indicate external links, saved bookmarks, email campaigns, QR codes, or internal links that still use retired URLs. Fix the source link when possible, then retain the redirect when the old address continues to receive legitimate requests.

Several patterns deserve immediate attention:

  • Many redirects ending on unavailable pages: Recheck replacement logic and inventory data. A redirect that technically works may still frustrate shoppers if the destination cannot satisfy the original need.
  • Redirect chains: Update the old rule to point directly to the final canonical URL. Chains add maintenance risk and can obscure the intended destination.
  • Redirect loops: Compare platform rules, server rules, CDN settings, and canonical host redirects. Test HTTP, HTTPS, www, non-www, trailing-slash, and case variants where relevant.
  • Category traffic falling after a restructure: Check whether the new category matches the former intent, remains indexable, has useful inventory, and is linked from navigation.
  • Faceted URL growth: Inspect which combinations are being crawled or linked. Consolidate duplicate paths carefully rather than applying a broad rule that removes useful landing pages.
  • Old URLs receiving valuable referrals: Preserve a direct, relevant destination and update high-value referring links when you control them.

Use server logs and redirect analytics alongside search and commerce data. A request count alone does not prove that a redirect should remain, but it can reveal forgotten campaign links, product feeds, or navigation components. The redirect analytics and server logs guide provides a useful framework for separating lost clicks, bot activity, and attribution gaps.

When to revisit

Revisit the redirect map whenever a product import, slug change, category restructure, seasonal assortment, platform migration, or inventory policy changes the URL set. In addition, schedule a monthly or quarterly audit based on catalog volatility. Review sooner when analytics show an unusual increase in 404 responses, redirect requests, referral traffic to retired pages, or visits to destinations that no longer match the old intent.

At each review, export the current catalog, compare it with the previous snapshot, and filter for three questions: Which old URLs are still requested? Where do current redirects end? Does each destination remain useful and technically clean? Record the answer in the spreadsheet, test the highest-impact changes in batches, and update internal links before retiring any rule.

Finally, document exceptions. A seasonal page that should return, a discontinued product with strong editorial links, and a faceted page used in a campaign may each require a different treatment. Clear notes prevent the next catalog release from undoing a deliberate SEO decision. For broader migrations, combine this process with a complete website migration redirect map and review canonical URL consistency across the store.

Related Topics

#ecommerce SEO#product URLs#category pages#301 redirects#catalog management#site maintenance
R

Redirect Portal Editorial Team

Technical SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.