An empty warehouse does not automatically mean a product URL should disappear. Keep a useful page when a product may return or still answers customer questions; redirect only to a genuine successor; return 404 or 410 when the product is gone and no useful page or relevant replacement remains. The visible stock message, structured availability and server response should describe the same product state.
| Product state | Possible response | Check first |
|---|---|---|
| Temporarily unavailable | Keep a useful product page available | Is a restock plausible, and does the page make the stock status clear? |
| A genuine successor exists | Permanent 301 to that product | Does it meet the same need, including important features and compatibility? |
| Permanently retired, no useful information or similar replacement | 404 or 410 | Have internal links and sitemap references been reviewed? |
| Still useful as a reference | Keep the page, clearly marked as discontinued | Does the page give accurate specifications or compatibility help? |
Temporary stock gaps
If an item may return, the product page is usually the clearest place to explain the gap. State that it is unavailable; give a return estimate only when the shop can support it. Offer a restock alert or alternative only if that function exists and the alternative meets a related need.
Google's guide for a temporarily paused business recommends keeping product pages available and marking items out of stock. That advice is for a temporary business pause, not a blanket rule for every retired product. Structured data should match the visible state: Google's product snippet documentation lists both OutOfStock and Discontinued as Offer.availability values. That markup describes the product state; it does not guarantee a rich result or search ranking. The structured data glossary covers the format.
Redirect only to a real replacement
A new model is a successor only if it serves substantially the same purpose. Compare the features people rely on, compatibility and the next step the page offers. If the new product meets that need and permanently replaces the old one, a 301 can send the old URL directly to it. Update shop links, navigation and sitemap entries to point to the destination. The redirect glossary explains the difference between permanent and temporary redirects.
A similar name or a shared parent category is not enough. A customer looking for a specific model may need its dimensions, compatible accessories or instructions. A broad category or home page does not answer those questions merely because the old item is no longer sold. Google's redirect guidance describes a permanent redirect as a strong signal for the target; it does not make an unrelated destination relevant.
Retire the URL when its page has no remaining job
If the item is permanently gone, no similar replacement exists and the page has no continuing informational value, return 404 or 410. Google treats both as unavailable responses for Search; 410 is not a promise of faster removal. A custom error page can still offer shop navigation, but its server response should remain a real not-found status. Remove obsolete sitemap entries and fix intentional internal links that still lead to the retired URL.
The Search Central Office Hours discussion of permanently out-of-stock products says deletion is fine from Search's perspective. For usability, a shop may keep a page available for a while or redirect it when external sites link to it or customers have bookmarked it. That is a visitor decision, not a requirement to preserve every old URL.
A page can also remain useful as a reference. Keep it available if people still need specifications, manuals or compatibility information, but label the product as discontinued and do not mark it InStock. The indexing glossary explains what it means for a page to be in Search; a 200 response alone does not guarantee indexing.
Example: one jacket, three different decisions
Imagine a shop with three jackets. The first is waiting for its next delivery. The second was replaced by a model with comparable weather protection and compatible accessories. The third will not return, has no close substitute and has no useful reference information.
The first page can remain available with a clear stock notice. The second can redirect directly to its genuine successor. The third can return 404 or 410. If one page lists several sizes or colours, check the variant data before applying a whole-product decision: one unavailable size does not mean every variant or the parent URL has been discontinued. This is a hypothetical review, not a report about a shop we inspected. The ecommerce SEO glossary explains why product and category URLs have different jobs.
Check the response, not just the product card
Fetch the URL anonymously and record the response, redirect chain, final URL and canonical. A destination that is unavailable or serves a different purpose is not a useful redirect target. A removed-product template that returns 200 while saying “not found” or showing no main content may be treated as a soft 404. Google's crawling error guidance explains that assessment.
Check the page content against the product feed or inventory source and its structured availability. If a product has variants, check each relevant variant rather than inferring the state of the whole page from one selection. Record the product ID, owner of the stock decision, chosen URL response, destination and review date. That record helps distinguish a temporary inventory gap from a final retirement. A review of internal links can also find shop pages that still send visitors to a retired URL.
For a repeatable check of response codes, redirects, canonicals and internal links across selected product URLs, use Crawl Foundry Site Audit. Its findings help verify the crawl state; they do not decide whether an out-of-stock product should be redirected.
Read the evidence after the change
Search Console can show whether a URL recently received search impressions or clicks. It cannot prove that a visitor still wanted the product or that a successor serves the same need. Inventory and order records help establish the product's actual status; support questions and compatibility requests can show whether the page still answers a separate information need. An inbound link is a reason to review a URL, not a reason to redirect it to an unrelated page.
After deployment, inspect representative URLs and compare the response and destination with the decision record. Search Console and server logs offer different evidence: a report does not show every request, and a log entry does not prove that Google indexed the URL. No fixed click threshold decides whether a product page should stay.
For cleanup, a broken link review can find stale internal references. If retirement is part of a larger URL move, the website migration guide covers redirect and destination checks.