Should you really return a 404 for products that are permanently unavailable?

Why does Google make this distinction between temporary and permanent unavailability?

Google's logic is based on crawl budget efficiency. An average e-commerce site has a limited crawl budget determined by its popularity and size. Googlebot must decide which pages to crawl first.

When a product is temporarily unavailable (temporary out of stock, restocking expected), maintaining a 200 status signals that this page remains relevant. Google will continue to crawl it regularly, allowing the page to retain its PageRank and ranking potential once the product is available again.

What technically happens with a 404 status for a product that has been permanently removed?

A 404 (Not Found) code explicitly informs Googlebot that this resource no longer exists. The crawler will gradually reduce its visit frequency to this URL and will eventually deindex it. This frees up crawl budget for active pages.

The term “soft 404” mentioned by Mueller refers to a page that returns a 200 status but its content clearly indicates that it is empty or nonexistent (message “product not found,” nearly absent content). Google detects these soft 404s and treats them similarly to real 404s, but with additional delay.

What is the difference in SEO impact between the two approaches?

Maintaining a 200 status for permanently removed products creates a dual problem: crawl budget dilution and the risk of soft 404s detected by Google. The bot wastes time on dead pages instead of exploring new products or updated content.

Switching to a 404 actively cleans up the site. The internal links pointing to these pages can be redirected to relevant categories or alternative products, thus preserving internal PageRank flow without creating dead ends.

• Temporarily Unavailable Product: 200 status, keep the page indexed, display a clear message of temporary out of stock with a return date if possible
• Permanently Removed Product: 404 status, remove the URL from the index, redirect external backlinks to a relevant alternative if it exists
• Optimized Crawl Budget: fewer dead pages crawled = more resources for active content
• Soft 404: to be avoided at all costs, they create confusion and delay deindexing
• Internal Linking: audit and clean links pointing to 404s to avoid crawl dead ends

Is this recommendation consistent with field observations of SEOs?

Yes, it's totally aligned with what we observe in practice. E-commerce sites that leave hundreds of product pages at 200 status with messages like “product not available” without a return date see their crawl budget wasted. Server logs show Googlebot spending time on these dead pages instead of quickly discovering new pages.

A classic case: a site with 50,000 references, 20,000 of which are obsolete at 200. Googlebot regularly crawls these 20,000 pages, while 5,000 new product pages struggle to be discovered quickly. Switching these 20,000 to 404 instantly frees up budget for active content. The indexing of new products speeds up measurably.

What nuances should be considered regarding this rule?

The notion of “permanently unavailable” is sometimes vague. A seasonal product that returns every year (swimwear, holiday decorations) is not permanently removed. In this case, keeping a 200 status with appropriate content (“Available soon in June”) is justified.

Another nuance: a product page with strong backlinks shouldn't simply return a 404. It's better to implement a 301 redirect to the parent category or an equivalent product. This preserves the SEO juice conveyed by these external links, unlike a 404 which cuts off this flow.

[To verify] Mueller talks about “soft 404” as acceptable, but in practice, Google sometimes takes weeks to detect that a 200 page is actually empty. Meanwhile, the crawl budget is wasted. A real 404 is more straightforward and effective immediately.

In what cases does this rule not strictly apply?

On sites with a very low product volume (fewer than 500 references), crawl budget is not a limiting factor. Google easily crawls the whole site several times a week. In this context, leaving a removed product at 200 with a clear message has little negative impact.

Another exception: collector or vintage products that are permanently out of stock but still generate organic traffic for informational queries. These pages can be transformed into editorial content (product history, current alternatives) and retain a 200 status. They become informational pages rather than dead transactional listings.

What concrete steps should be taken to manage removed products from the catalog?

First step: segment the catalog between temporarily unavailable products (out of stock with return date) and permanently removed products (discontinued, end of range). This distinction should be coded in the database to automate HTTP statuses.

For permanently removed products, set up a server rule (via .htaccess, nginx.conf, or the CMS) that automatically returns a 404 status. At the same time, analyze the backlinks of these pages via Search Console or a tool like Ahrefs to identify URLs that deserve a 301 redirect to a relevant alternative.

How to audit and clean the internal linking on these dead pages?

Internal links pointing to 404s create crawl dead ends and dilute PageRank. Use a crawler (Screaming Frog, Oncrawl, Botify) to identify all links pointing to removed products. Then, either remove these links, or redirect them to relevant categories or alternative products.

Navigation filters (facets) often generate links to combinations including removed products. Exclude these products from dynamic filters to avoid regenerating dead links as users navigate. A parameter “stock=0 AND status=removed” in filtering requests usually suffices.

What mistakes to avoid when implementing this strategy?

A common error: transitioning all out-of-stock products to 404 without distinction. A temporary out-of-stock situation (restocking in 15 days) does not justify a 404. The page would lose its indexing and ranking, while the product will soon return. Result: loss of organic traffic once back in stock.

Another trap: creating unintentional soft 404s by displaying a nearly empty page with just “Product not available” with a 200 status. Google eventually detects these pages as empty and treats them as 404s, but with a delay and confusion. It’s better to be explicit from the start with a real 404.

Failing to manage external backlinks before switching to 404 is a waste of PageRank. A page with 10 backlinks from authority sites should be redirected 301 to the parent category or a comparable product, not simply abandoned in 404.

• Segment in the database: temporarily unavailable products (200 status) vs permanently removed (404 status)
• Automate HTTP statuses via server rules or CMS based on product status
• Audit backlinks of removed products and implement 301 redirects to relevant alternatives
• Clean internal linking: remove or redirect links pointing to 404s
• Exclude removed products from dynamic navigation filters (facets, internal search)
• Monitor soft 404s in Search Console and correct pages detected as empty