Out-of-stock and discontinued products

A store selling trail shoes stops carrying its most popular model. Someone deletes the product, the URL returns a 404, and weeks later the owner notices the page that brought in the steadiest search traffic has vanished, along with the links two running blogs had pointed at it. The product was gone; the page didn't have to be.

A product page that ranks is an asset separate from the product it sells. What you do with it when stock runs out, or for good, decides whether that asset survives.

Why a product page outlives its product

Ranking signals attach to a URL. Links from other sites, links from your own collections and Google's understanding of what the page is about all belong to the address, not to the item in your warehouse. When the URL returns a 404, Google's documentation on HTTP status codes describes what follows: once the error persists, the page is dropped from the index, and every link that pointed at it points at nothing.

A 301 redirect behaves differently. Google's documentation on redirects describes a permanent redirect as a strong signal that the target should be treated as the canonical, so what the old page earned moves to the new one, provided the new one is a genuine replacement. The question is never "should I delete this page" but "where should what this page earned go next".

Temporarily out of stock: keep the page and say so

If the product is coming back, the page stays live and returns a normal 200 status. Keep the description, images and reviews, because they are what ranks. Mark the product out of stock on the visible page and in its structured data: Google's Product structured data documentation supports an availability property with Schema.org values such as InStock, OutOfStock, BackOrder and PreOrder, and Google's structured data guidelines require the markup to match what the visitor sees. Then add a restock estimate, a back-in-stock email form and links to the closest alternatives.

Three mistakes turn a temporary gap into a permanent loss. Don't add noindex, because you'll have to earn its place in the index back when stock returns. Don't redirect it to a collection, even temporarily; that tells Google the page is gone. And don't strip the page down to a single "Sold out" line: Google's documentation on soft 404s describes pages that return a 200 while telling the visitor nothing is there, and a gutted product page can be classified that way.

Check what your platform's out-of-stock setting does to the page itself. Hiding a product from collection listings is fine; making its URL return a 404 is not.

Discontinued: redirect, replace or remove

When the product is gone for good, work down this ladder and stop at the first rung that fits.

1. Is there a direct successor, a new version that does the same job? Redirect the old URL to it with a 301, and say on the successor's page that it replaces the old model.
2. No successor, but the page has links from other sites or search traffic (Search Console's performance and links reports will tell you)? Redirect to the closest collection that holds genuinely similar products. Not the homepage: Google's documentation on redirects and soft 404s describes sending removed pages to an unrelated page, the homepage being the usual case, as something it may treat as a soft 404.
3. No successor, no links, no traffic? Let it go. Return a 404 or a 410; Google's documentation on HTTP status codes treats both as a page that no longer exists, with 410 the explicit "gone" version. Some SEOs report that a 410 clears the index faster, which Google's documentation doesn't promise. Remove it from your sitemap and from every internal link.
4. Seasonal product, back next year? Keep the URL, mark it out of stock or pre-order, and relist on the same URL next season. Google doesn't document this case, but the mechanism is the same: a URL that keeps its history starts next season ahead.

On Shopify, deleting or archiving a product takes its page down, so create the redirect under URL redirects in the admin first. On WooCommerce, trashing a product does the same; set the redirect with a redirect plugin or your host's rules. In both cases, one hop: a redirect that lands on another redirect is a chain, and every extra hop leaks signals.

Keep the rest of the store consistent

A removed product leaves traces everywhere it was linked. Collection pages, "related products" blocks, menus and blog posts keep pointing at the old URL until someone updates them. Search Console's Pages report lists the 404s it keeps finding; that's your clean-up queue.

Two more places must agree. The availability in your structured data has to match the visible state, as Google's structured data guidelines require. And if you list products in Google Merchant Center, the availability in your feed has to match the page too; Merchant Center's policies name a mismatch between feed and landing page as a reason for disapproval.

What to take away

• The ranking signals a product page earns belong to its URL, so deleting the page throws them away while a relevant 301 passes them on.
• A product that's coming back stays live with a 200 status, its content intact and its availability marked out of stock on the page and in structured data.
• A discontinued product is redirected to a successor or a closely related collection if it has links or traffic, and returns a 404 or 410 if it has neither; never redirect it to the homepage.
• Structured data, the Merchant Center feed and the visible page must agree about availability, and internal links to removed products need clearing.

Next

Product feeds and free listings shows what a clean Merchant Center feed needs to contain.