Field guide · technical workflow
What should the store show when a product is discontinued?
A discontinued product may still attract visitors months after its last sale. Sending everybody to the homepage is not a meaningful replacement. The decision depends on whether it will return, has a true successor or is permanently gone with no valuable remaining explanation.
Who this is for: Help merchants protect customer journeys to retired product URLs while maintaining honest stock and replacement information.
Editorial preview — facts, worked examples and publication approval are still being checked.
The practical problem
A practical what should the store show when a product is discontinued? exercise: Distinguish out-of-stock products from permanently retired inventory. The outcome is a documented decision backed by require a real successor decision before issuing any 301 redirect. The final check is to check sitemap, feed, internal-link and HTTP response consistency.
What you will be able to check
- Distinguish out-of-stock products from permanently retired inventory.
- Require a real successor decision before issuing any 301 redirect.
- Check sitemap, feed, internal-link and HTTP response consistency.
Reproducible scenario
Worked example: What should the store show when a product is discontinued?
A hypothetical shoe shop removes last year's trainer collection. One model will return next quarter, another has a true replacement with similar specifications, and a third is permanently discontinued without a comparable successor. The operator proposes redirecting all old product URLs to the general trainers category. That approach would treat three distinct visitor expectations as one and may lead to irrelevant destinations.
Starting assumptions
- The merchandising owner can verify real restock plans and replacement equivalence for each model.
- Product feeds, XML sitemaps and category links can be compared against the page's displayed availability.
Decisions and checks
Verify which discontinued products are temporarily unavailable
Inspect real stock lifecycle and customer needs. A genuinely useful product detail page can remain truthful while out of stock, but an InStock offer or available checkout would mislead visitors. Record whether buyers can be notified of a return without inventing a restock guarantee.
What to verify: A status record distinguishes temporarily unavailable products from permanently retired ones and matches actual visible offer information.
Review any proposed replacement against the original product
Compare sizing, technical specifications and buying purpose, not merely similar words in the titles. If a replacement genuinely satisfies the old task, map the old URL deliberately and inspect the new product's content and offer.
What to verify: An approved relevant successor decision with observed old-to-new response and corresponding product details.
Retire unmapped pages honestly while maintaining store navigation
For content with no lasting value or successor, choose an appropriate removal response and remove stale links from feeds, sitemaps and category paths. Do not use a blanket redirect to disguise every deleted product as a live category.
What to verify: The final HTTP response and store navigation reflect the real product lifecycle without sending customers to unrelated pages.
Expected output: A useful retirement programme finishes with a product-level decision register, not simply fewer errors in a crawl report. It respects the visitor's original intent and supports accurate buying choices. The release review can verify whether each old URL leads to truthfully described content or an appropriate removal response.
This woocommerce discontinued product plan scenario is illustrative; no real WooCommerce customer result or tested store is implied.
Group product retirements by user need
Create a small list including temporary stock-outs, replaced models and genuinely retired products. Check which URLs still receive visitors and whether a specific successor answers the same need. The merchandise owner should verify replacement relevance rather than mapping products by matching words in their titles.
Reference: official · 2026-11-07
Choose a truthful URL response
If the page remains useful, state unavailable stock truthfully and offer appropriate alternatives. Redirect only to a genuinely matching successor. If there is no useful content or successor, a proper not-found response can be more helpful than a misleading soft 404 home redirect.
Reference: official · 2026-11-07
Keep feeds and internal links aligned
Update product listings, XML sitemaps, shopping feeds and related product links to match the chosen state. Record each sample's final HTTP status and the destination's visible content. Test again after an inventory update so an automation does not quietly undo the chosen policy.
Reference: official · 2026-11-07
Decision aid
Decision table: WooCommerce discontinued product response planner
| Observed page behaviour | Decision to consider | Verification evidence |
|---|---|---|
| Restock planned and page remains useful | Retain informative page with accurate availability and alternatives. | Check real inventory, offer markup and customer next action. |
| True replacement with equivalent buying purpose | Consider a deliberate relevant redirect with owner signoff. | Compare product specifications, redirect and final purchase behaviour. |
| Permanent retirement with no meaningful alternative | Record honest removal and update product feeds and links. | Verify final status, sitemap removal and absence of misleading stock offers. |
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.
Verify which discontinued products are temporarily unavailable
Expected result: A status record distinguishes temporarily unavailable products from permanently retired ones and matches actual visible offer information.
Keep as evidence: Save a dated, source-specific HTTP and rendered-product record with an assigned reviewer for verify which discontinued products are temporarily unavailable.
Review any proposed replacement against the original product
Expected result: An approved relevant successor decision with observed old-to-new response and corresponding product details.
Keep as evidence: Save a dated, source-specific HTTP and rendered-product record with an assigned reviewer for review any proposed replacement against the original product.
Retire unmapped pages honestly while maintaining store navigation
Expected result: The final HTTP response and store navigation reflect the real product lifecycle without sending customers to unrelated pages.
Keep as evidence: Save a dated, source-specific HTTP and rendered-product record with an assigned reviewer for retire unmapped pages honestly while maintaining store navigation.
Scope and limitations
The products, restock dates and conversion effects are hypothetical; no inventory has been inspected here. Commerce themes and feeds can emit different availability signals. The right response requires merchandising evidence and actual URL-level status checks, and retaining a page is not a guarantee that it will remain indexed.
Sources and verification
These references explain documented technical behaviour. The worked decisions are illustrative until checked on your own installation.
- official reference — Google's HTTP-status guidance distinguishes working URLs, redirects and error responses that influence indexing of removed content. Recorded: 2026-11-07