A workflow for retired product URLs that preserves useful customer paths while choosing whether a page should remain, redirect, or return a removal response.
A product-retirement workflow that preserves useful customer paths while deciding whether a discontinued URL should remain, redirect, or return a clear removal response.
The decision and its boundary
A discontinued item is a business-state change, not automatically a redirect request. The decision depends on whether a close replacement exists, whether the old page still answers a support or compatibility need, and whether the URL has meaningful links or demand. The useful outcome is a truthful page or response for a person and a crawler; sending every retired item to a category or home page can become a soft-404-like dead end.
What to inspect
Inventory retired URLs with their last known purpose, incoming links, traffic evidence, available replacement, and stock or support status. Open a sample of rendered pages and responses. Verify that a proposed replacement is genuinely substitutable, that any retained page says the item is unavailable, and that sitemap and internal links do not contradict the chosen state.
A practical implementation path
Choose one of three explicit paths. Keep a useful archive if it contains durable specifications or compatible alternatives; use a direct permanent redirect only for a close successor; otherwise return an honest removal response with helpful navigation. Update product feeds, internal links, canonicals, and sitemap entries to match the decision. Test the old URL and its final destination, then keep a reversible map of the change.
Mistakes and measurement limits
The frequent mistake is a blanket redirect rule. A category page is not a replacement for a specific product, and a redirect chain conceals the actual retirement policy. Do not promise that a redirect preserves rankings or sales. Measure whether the URL state, links, sitemap, and user message agree; missing measurement is a follow-up item, not a pass.
Worked decision example. Suppose a discontinued model has no stock but its specification page still receives links from installation guides. First ask whether a current item is a genuine replacement: it must satisfy the same core use, not merely share a category. If it does, a single 301 to that successor can be appropriate. If no successor exists but the specifications, manuals, compatible parts, or safety information remain useful, retain the URL as an archive and state that availability has ended. If the page offers neither a replacement nor durable information, return 404 or 410 according to the documented removal policy. A generic category redirect is not a neutral fallback; it can mislead a visitor and obscure the original URL’s status.
Acceptance checks. Test the old URL without following redirects and record its status and Location. Follow it once and verify that the final page is live, relevant, and not another redirect. Inspect the rendered archive message or removal page on desktop and mobile. Search internal navigation, comparison widgets, feeds, sitemaps, and canonical tags for references to the retired address. The proposed state is only ready when these surfaces agree. Keep an export of the old-to-new map so a later product-data correction can be reversed without guessing.
Common errors. Do not redirect a discontinued product to a search result, homepage, or different product simply to avoid a 404. Do not leave an ‘in stock’ offer, price, structured availability, or sitemap entry behind on an archived page. Avoid deleting a URL before checking whether it carries support value or high-quality incoming links. A 301 is not a substitute for product-data maintenance, and a 404 is not proof that search engines have already updated their index. Treat crawl, sitemap, and search observations as separate checks.