What to do with a product page once the item is out of stock or permanently discontinued is one of the more commonly mishandled decisions on ecommerce sites, usually because the instinct is to either leave the page exactly as-is indefinitely or remove it immediately, when the right answer depends on whether the product is coming back and whether a genuine replacement exists.
The Two Different Scenarios
It matters a great deal whether a product is temporarily out of stock (expected back, or a normal seasonal gap) or permanently discontinued (never coming back, possibly with a direct replacement, possibly with none). Treating both the same way, whether that means leaving every page live forever or removing every out-of-stock page immediately, causes problems in one direction or the other.
Temporarily Out of Stock: Keep the Page Live
For a product that will return, the page should stay live and indexed. Removing it and rebuilding it later throws away any accumulated rankings, reviews, and backlinks the page had built up, and Google has been explicit in its own guidance that retailers shouldn't automatically remove out-of-stock product pages. The right approach:
- Update the schema availability property to
OutOfStockrather than leaving it asInStock, so the page accurately represents its current state to both users and search engines. - Show an estimated restock date if you have one, or offer a "notify me when back in stock" option, which also gives you a way to capture demand rather than losing the visitor entirely.
- Show genuinely similar in-stock alternatives on the same page where they exist, which helps the visitor and gives the page continued usefulness even while the specific item is unavailable.
- Avoid a soft 404, meaning a page that technically returns a normal 200 status but has effectively no useful content left on it. This confuses search engines about whether the page still has value and can lead to it being dropped from the index even though it wasn't intentionally removed.
Permanently Discontinued With a Direct Replacement
Where a product has been replaced by a clear successor (a new model, an updated version), a 301 redirect from the old product page to the new one is usually the right move, since it passes along the accumulated ranking signal from the old page to the one that can actually fulfil the same customer need going forward.
Permanently Discontinued With No Replacement
This is the genuinely difficult case. Options include:
- Redirecting to the closest relevant category page, which preserves some value and gives the visitor somewhere useful to go, though it's a weaker signal than a direct product-to-product redirect since the intent match is less precise.
- Leaving the page live with a clear "discontinued" message and links to similar products, which keeps any accumulated backlinks and content value intact and can still serve visitors arriving from external links or bookmarks, at the cost of the page no longer converting for that specific product.
- Returning a proper 404 (or 410 for a deliberate, permanent removal), which is honest about the page no longer existing, but sacrifices any accumulated SEO value entirely. This is generally the least preferable option unless the page has negligible existing traffic or backlinks and no reasonable redirect target exists.
For most ecommerce sites, keeping a clearly labelled discontinued page live with alternatives, or redirecting to a closely matching category, tends to preserve more value than an immediate 404, though the right call genuinely depends on how much accumulated SEO value the specific page has.
What Not to Do
The most damaging pattern is inconsistency: some discontinued products get redirected, some get 404'd, some get left live with no updates, applied without a clear rule, on the same site. This makes it impossible to reason about the site's overall handling of the issue and tends to produce worse outcomes across the board than any single consistent approach applied deliberately.
Update, 9 October 2026: Stock and price accuracy now matters beyond search results, because AI shopping features read the same data. See Merchant Center conversational attributes and Google's Universal Commerce Protocol.