Should you really keep out-of-stock product pages indexed?

Why does Google prefer you to keep pages for sold-out products?

When a product is no longer available, the temptation is strong to delete the page to avoid offering "useless" content. Except Google doesn't see it that way.

A product page that has existed accumulates SEO signals: external backlinks, organic traffic, engagement signals. Deleting it brutally destroys this capital and creates 404 errors that frustrate users arriving via search or external links.

How do you inform Google that a product is unavailable?

Google expects you to use Schema.org Product markup with the availability property. Relevant values: OutOfStock, Discontinued, PreOrder, BackOrder.

This approach allows Google to understand the product status without interpreting the page as dead content. The search engine can then display this information in rich results and adjust its crawl accordingly.

What's the difference from a complete deletion?

Deleting a page = immediate loss of rankings and backlinks. Google has to relearn everything if the product comes back in stock, which takes time — sometimes weeks.

Keeping the page with an "out of stock" status preserves indexation, maintains history, and allows an almost instant comeback when the product is available again. Backlinks remain active, PageRank flows through.

• Preserve SEO capital: inbound links, page authority, ranking history
• Avoid 404 errors that degrade experience and waste crawl budget unnecessarily
• Use Schema.org with availability properties to signal product status
• Facilitate restocking: the page remains indexed and can rank immediately again
• Improve UX: offer alternatives, availability alerts, similar products

Is this recommendation consistent with practices observed in the field?

Yes, and testing has confirmed it for years. E-commerce sites that delete out-of-stock product pages systematically see their rankings collapse — sometimes never returning to their original level, even after restocking.

What's less often mentioned: Google doesn't treat all out-of-stock situations the same way. A seasonal product that comes back each year? No problem. A product permanently discontinued with zero alternative? That's where it gets sticky. Alan Kent's statement lacks nuance on this point [To be verified].

What nuances should be applied depending on context?

Not all products deserve the same treatment. A high-ticket product with quality backlinks and recurring traffic justifies keeping it indexed indefinitely. A generic product with no inherent authority can sometimes be consolidated via a 301 redirect to a category or equivalent product.

The real problem is volume. A catalog of 50,000 items with 30% permanent stockouts becomes unmanageable — and Google will never crawl all of it effectively. Let's be honest: you need to balance SEO preservation with operational reality.

In what cases does this rule not apply?

When the product is permanently discontinued, with no equivalent, and the page has never generated significant organic traffic. There, a 301 redirect to a relevant category makes more sense than a ghost page.

Another edge case: ultra-fast-rotation products (fast-fashion, electronics). Keeping 10,000 out-of-stock product pages from 18 months ago dilutes crawl budget and sends a catastrophic freshness signal to Google. Sometimes you have to make the call.

What should you actually do to manage out-of-stock situations?

First, implement Schema.org Product markup with the availability property. That's the technical foundation for Google to understand the product status. Values to use: OutOfStock, Discontinued, PreOrder, BackOrder.

Then, enrich the user experience on these pages. Offer similar products, email availability alerts, additional content (comparisons, customer reviews). An out-of-stock page that converts through alternatives remains performant in Google's eyes.

What mistakes must you absolutely avoid?

Never return a 404 or 410 HTTP code on a product page with authority. That's SEO suicide, especially if the stockout is temporary. The code should remain 200, with Schema.org markup indicating unavailability.

Also avoid the "noindex" trap on out-of-stock pages. That's basically telling Google to forget the page — exactly the opposite of what you want. If you must deindex, at least redirect properly.

How do you verify your implementation is correct?

Use Google's Rich Results Testing Tool to validate your Schema.org markup. Verify that the availability property appears correctly and its value is recognized.

Monitor Search Console: out-of-stock pages should not generate indexing errors or soft 404s. If they do, your technical implementation is flawed and Google doesn't understand your signals.

• Keep out-of-stock product pages (HTTP 200 code)
• Add Schema.org Product markup with availability: OutOfStock
• Enrich the page: alternatives, availability alerts, additional content
• Never return 404 or 410 on a page with SEO authority
• Avoid noindex on temporary stockouts
• Redirect via 301 only if the product is permanently discontinued and has no equivalent
• Monitor Search Console to detect unintended soft 404s
• Balance volume considerations: a catalog with 30% permanent stockouts needs a consolidation strategy