Field guide · technical workflow
What happens when a catalogue product disappears?
When a product is retired, the old address can still receive traffic and links. A blank error page may waste a useful journey, but leaving an impossible purchase promise is worse. The correct response depends on whether a true successor exists and what visitors need next.
Who this is for: Help merchants choose a trustworthy retired-product response without automatically redirecting every missing page to a category home.
Editorial preview — facts, worked examples and publication approval are still being checked.
The practical problem
A practical what happens when a catalogue product disappears? exercise: Classify sampled products as temporarily unavailable, replaced or retired. The outcome is a documented decision backed by review genuine replacement relationships before issuing redirects. The final check is to recheck final status codes and visible availability information.
What you will be able to check
- Classify sampled products as temporarily unavailable, replaced or retired.
- Review genuine replacement relationships before issuing redirects.
- Recheck final status codes and visible availability information.
Reproducible scenario
Worked example: What happens when a catalogue product disappears?
A hypothetical lamp retailer has three old product URLs: one item will be restocked, one has a compatible replacement model, and one was discontinued without any comparable alternative. The content team is tempted to redirect all three to the lamp category because it removes 404 reports. That would collapse three different customer intentions into one convenience rule. The example explores the decisions required before changing these addresses.
Starting assumptions
- The retailer can confirm real inventory status and the existence of a genuinely comparable replacement product.
- Old product URLs may still attract visitors from saved links, search or external reviews, so they cannot be assessed by current menu visibility alone.
Decisions and checks
Separate temporary unavailability from permanent retirement
For the temporarily unavailable product, confirm whether a useful product detail page still helps visitors understand the item and return later. Preserve honest stock messaging rather than displaying an active offer that cannot be purchased.
What to verify: The product page displays truthful availability and a clear customer next step, with consistent merchant markup and no invented offer.
Review a replacement for actual product equivalence
For the replaced lamp, compare model specifications and what a buyer expected from the old address. A redirect is more defensible when the new product solves the same need; a superficially similar title is not enough.
What to verify: The replacement decision records matching specifications, a relevant permanent destination and a verified redirect response.
Close a genuinely retired URL with an appropriate response
When there is no useful successor or remaining content, decide whether a real not-found response is appropriate. Remove stale product navigation and sitemap entries; avoid a blanket redirect to a category that does not answer the old product's specific request.
What to verify: A documented final HTTP status, removed broken internal links and a coherent category navigation path remain after the release.
Expected output: The decision register now separates product lifecycle states from URL engineering actions. It should help customers reach honest information and permit the site to retire genuinely useless pages without turning all product removals into soft errors. A successful outcome is verified user relevance and technically consistent responses, not a low count of 404s.
This bigcommerce discontinued product response scenario is a fictional technical example, not a completed inspection or measured result for a merchant.
Separate temporary stock changes from retirement
Start with three conditions: expected back in stock, permanently discontinued with a meaningful replacement, and permanently removed with no equivalent. These are different editorial and merchandising decisions. Check the actual product history and traffic before declaring a permanent redirect target.
Reference: official · 2026-11-07
Match each old URL to its real outcome
A product with useful reference information may retain value even without an active offer if the page accurately states availability. A directly comparable successor can justify a deliberate redirect. Where the item and its useful content are genuinely gone, an appropriate 404 or 410 may be more truthful than sending everybody to the homepage.
Reference: official · 2026-11-07
Verify status codes and customer value
Audit old URLs, response codes, sitemap entries, internal links and product feed availability after the change. Treat a working 301 as only one technical test: the final page must help the buyer. Record examples with a named owner so temporary stock states are not confused with permanent retirements.
Reference: official · 2026-11-07
Decision aid
Decision table: Discontinued products: choose the right response
| Condition to investigate | Recommended decision | Proof to gather |
|---|---|---|
| Product expected to return to stock | Keep a useful page and show availability truthfully if it still serves the buyer. | Inspect real stock data and the page's displayed price, offer and alternative links. |
| Product replaced by a functionally equivalent version | Consider an intentional redirect to that verified successor after product-owner review. | Compare specifications, final HTTP chain and the actual content of the replacement page. |
| Product permanently removed without a suitable successor | Use an honest removal policy, which may include 404/410 instead of unrelated redirection. | Verify the true absence of a replacement and clean stale links from sitemap and navigation. |
What a passing test looks like
These checks describe the evidence that should exist after a real implementation. They are not reports of tests already completed on a customer website.
Separate temporary unavailability from permanent retirement
Expected result: The product page displays truthful availability and a clear customer next step, with consistent merchant markup and no invented offer.
Keep as evidence: Keep a dated sample of real URLs, final HTTP and HTML output, and the reviewer decision for the separate temporary unavailability from permanent retirement.
Review a replacement for actual product equivalence
Expected result: The replacement decision records matching specifications, a relevant permanent destination and a verified redirect response.
Keep as evidence: Keep a dated sample of real URLs, final HTTP and HTML output, and the reviewer decision for the review a replacement for actual product equivalence.
Close a genuinely retired URL with an appropriate response
Expected result: A documented final HTTP status, removed broken internal links and a coherent category navigation path remain after the release.
Keep as evidence: Keep a dated sample of real URLs, final HTTP and HTML output, and the reviewer decision for the close a genuinely retired url with an appropriate response.
Scope and limitations
This example does not inspect inventory or guarantee that a retained product page will remain indexed. Merchandising, availability feeds and actual linked references need current verification. The correct response depends on product history and the existence of valuable content; automated redirect-by-category rules should not replace that editorial decision.
Sources and verification
These references explain documented technical behaviour. The worked decisions are illustrative until checked on your own installation.
- official reference — Google documents how successful responses, redirects and HTTP error statuses affect crawling and indexing, which informs retired-URL decisions. Recorded: 2026-11-07