How to Retire a Product Page While Preserving Useful Paths

When a retailer stops selling a product, its old page may still help people who need specifications, manuals, compatibility details, or information about a replacement. For each discontinued product page, decide what its URL should do: stay available with accurate information, redirect to a close replacement, or return an error when no useful content or successor remains.

A redirect sends visitors and the automated programs search engines use to find pages from one URL to another. A 404 or 410 response tells them the page is gone. Choosing the response that matches the page’s actual purpose preserves useful routes without sending people to an unrelated destination.

Choose an outcome for each retired URL

Keep a page live when it still answers questions. A discontinued product page can retain specifications, support details, reviews, or compatibility information even after sales end. State clearly that the product is discontinued, remove purchase buttons and delivery promises that no longer apply, and link to current alternatives when they genuinely help.

Distinguish permanent discontinuation from temporary unavailability. Google’s product data, machine-readable details that describe a product to search engines, supports separate availability values for Discontinued and OutOfStock; use the value that accurately describes the product. Keep any structured product data consistent with the information people see on the page. Correct markup does not guarantee a search feature, but inaccurate markup can misrepresent the offer. Google explains these requirements in its product snippet documentation.

Redirect when another page is a close replacement or contains substantially the same information. For example, a newer model may serve as the next purchase option, but it may not preserve the old model’s compatibility details. If those details remain useful, keep the old page and link to the newer one rather than redirecting visitors away from the information they came for.

When the product information is gone and no similar page exists, return a 404 (“not found”) or 410 (“gone”) response. Google recommends these responses for removed pages without a suitable replacement. Neither status has a documented ranking advantage over the other in this situation. Its crawling error guidance also warns that sending visitors to an irrelevant page can confuse them and result in a soft 404, where a page appears to exist but effectively says its content is gone.

Check the page’s value before removing it

Review each URL on its own instead of applying the same rule to every discontinued product. Check whether the page still attracts search visits or referrals, has links from other sites, or supports customer service through manuals, parts information, or compatibility guidance. Analytics, Search Console, server logs, and reports of links from other sites provide useful evidence. None of them alone tells you whether a page should stay.

Then assess the proposed replacement from the visitor’s point of view. Does it answer the same need, or does it simply belong to the same category? A category page may help someone browse current products, but it does not necessarily replace a discontinued model’s specifications or support history.

If the page stays live, keep it easy to find through relevant internal links from categories, support pages, or related products. Google describes internal links as a way to discover pages and understand their relationships. Removing a page from the sitemap or its internal links does not remove it from the web; those changes should match the decision you made about the URL.

Test redirects, error pages, and product data

A permanent redirect, usually sent with HTTP status code 301 or 308, tells a browser and search engine that a URL has moved. Point it directly to the closest relevant destination, then update internal links so they lead to that destination without passing through the old URL. Avoid redirect chains and broad rules that send every retired product to the homepage or a general category.

For a page you remove, request the old URL directly and confirm that it returns 404 or 410. A custom error page can offer links to useful categories or support resources, but the server must still return the error status. If the server returns the 200 success status code, Google may treat the page as a soft 404.

For a retained page, confirm that the URL returns a normal success response and that its visible content, purchase options, and structured product data agree. Remove outdated prices, stock claims, and delivery promises. To let people reach a page while keeping it out of Google Search, you can use a noindex directive, which tells Google not to show the page in search results. Google must be able to crawl the page to read the directive. Blocking it in robots.txt prevents that check. Google explains the distinction in its guidance on blocking search indexing.

After publishing the changes, inspect sample URLs. For each one, check the status code the server returns and view the page in a browser; follow any redirect to its destination. Search Console’s URL Inspection tool can help check what Google receives. Remove retired URLs from XML sitemaps, which list URLs for search engines. Include the preferred destination when it should be indexed. A sitemap can help Google discover URLs, but it does not guarantee crawling or indexing, as Google notes in its sitemap guidance.

Understand what the evidence supports

Google’s guidance supports matching the URL’s response to the page’s real status: retain useful content, redirect to a genuinely similar replacement, or return 404 or 410 when no successor exists. It does not show that keeping every discontinued product page preserves rankings, that every redirect produces a particular ranking benefit, or that deleting low-traffic product pages improves other pages. Google’s advice about redirects during a site move applies to site migrations; it does not establish a universal ranking outcome for retired product URLs.

For Google AI Overviews and AI Mode, a page can serve as a supporting link only if Google has indexed it and it can appear with a snippet, the short text shown in a Google Search result. Google says there are no additional AI-specific technical requirements, and it does not guarantee indexing or display. A retained page with accessible, accurate product facts therefore remains eligible under those conditions, but eligibility does not ensure that Google will cite it. See Google’s explanation of AI features and website eligibility.

Key Takeaways

• Choose the URL’s outcome first: Keep useful information live, redirect to a close replacement, or return 404 or 410 when no suitable successor exists.
• Separate discontinued from out of stock: Show the product’s true availability in both visible content and structured product data.
• Judge replacements by the visitor’s need: A newer model or category page is suitable only when it answers the purpose of the old URL.
• Test what the server returns: Check status codes, redirect destinations, internal links, sitemap entries, and product data after deployment.
• Treat search visibility as uncertain: Google’s guidance describes correct handling but makes no promise of ranking gains or indexing.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com