Should you return a 404 or a 200 on a product page that's out of stock?

Why does Google make a distinction between short and long-term shortages?

Googlebot has a limited crawl budget per site, even on large catalogs. If hundreds of product pages remain online with zero stock for weeks, the bot spends time visiting them regularly to check for a hypothetical restock. This time is not spent elsewhere: new listings, editorial content, enriched categories.

Google's goal is straightforward: reduce server load and optimize its own resources. By indicating that a page no longer exists (404), you inform the bot that it can drastically space out its visits, or even stop them. The crawl budget then focuses on what really matters.

What does 'temporary' versus 'long-term' actually mean?

Google provides no numerical threshold. 'Temporary' could mean few days to two weeks depending on the sector. 'Long' might start at a month or more. This gray area is problematic: an electronics site with monthly restocking doesn't have the same cycles as a fashion site with three-day shortages.

Without clear guidelines, you need to analyze your own data: average duration of stockouts, restock rates, crawl history in Search Console. If your products come back within 10 days, keeping the 200 is justified. Beyond 30 days, the 404 becomes relevant to avoid polluting the crawl.

Does the 'email alert' option have a direct SEO impact?

No, the email alert is a UX feature, not a ranking signal. Google mentions it to validate that a 200 page can still serve the user even without stock. It generates interest, maintains engagement, but changes nothing in the eyes of the algorithm.

What matters to Google is that the page displays useful content rather than just 'unavailable'. If your alert form is drowned in emptiness, the bot may consider the page as thin content and reduce its visit frequency anyway.

• 200 Code + Email Alert = acceptable for short shortages with predictable restocking
• 404 Code = recommended as soon as unavailability exceeds several weeks without a return date
• No official threshold: it's up to you to define 'temporary' according to your sector and stock cycles
• The email alert serves UX but does not directly boost SEO
• Main goal: avoid wasting crawl budget on pages with no added value

Is this statement consistent with what we observe in practice?

Yes, and it's even a welcome confirmation after years of debate. Many e-commerce merchants leave thousands of listings at 200 with 'out of stock' or 'coming soon' labels without ever deindexing them. Result: wasted crawl budget, polluted index, overall decreased visit frequency.

What we observe on the ground: sites that aggressively switch to 404 for products that are discontinued or unavailable for long durations see their crawl speed improve on active pages. Google redistributes the budget where there is stock, traffic, and conversions. [To be verified] It remains to define whether 'long-term' corresponds to the same timelines across all sectors — Google gives no figures.

What nuances should be added depending on the type of catalog?

A site with frequent and predictable restocking (fashion, food) can afford to keep the 200 longer. If your products return every week, deindexing would be counterproductive: you would lose acquired ranking, backlinks, and history.

Conversely, a catalog of industrial parts or seasonal products with unavailability lasting several months should quickly switch to 404. Otherwise, you're keeping alive pages that no one can buy, and Google continues to crawl emptiness. The rule of thumb: if your average stockout period exceeds 3 weeks without certainty of return, consider the 404.

What should you do if the product comes back after a switch to 404?

Switch back to 200 as soon as it's restocked. Google will recrawl the page, see the stock is back, and reindex it. The risk is that you may temporarily lose ranking if the stockout lasted long: the page drops out of the index and then must regain its position.

Let’s be honest: for products with low SEO value or low traffic, it's not dramatic. For best-sellers with backlinks and strong positions, one must weigh the pros and cons. An alternative option: 503 code with Retry-After header, but Google gives no guarantee that this signal is better interpreted than a 200 with alternative content.

How can you determine the 'temporary' versus 'long' threshold on your site?

Start by extracting the history of your stockouts over 6 to 12 months. Calculate the average duration between 'zero stock' and 'available again'. If 80% of your products return within 15 days, you can keep the 200 during this period. If 50% of stockouts exceed 30 days, automate switching to 404 beyond this threshold.

Cross-reference this data with Search Console: identify pages that have been crawled frequently but have been out of stock for weeks. These are your priority candidates for a 404. The crawl budget wasted on these pages could be redistributed to your new products or strategic categories.

What technical strategy should you implement to automate HTTP code management?

The ideal: a conditional rule in your CMS or ERP that automatically switches to 404 if the 'stockout_date' field exceeds X days without stock movement. On Shopify, WooCommerce, Magento, this can be configured via a plugin or custom script. This way you avoid manual management and forgetfulness.

Also plan for regular monitoring: alerts if more than Y products switch to 404 at once (sign of an import bug or massive stockout). And keep a list of products in 404 so you can revert to 200 as soon as they are restocked, ideally via a daily export from the ERP to the CMS.

What errors should you avoid in implementation?

Error #1: Switching to 404 on the very first day of stockout. You lose ranking unnecessarily if the product comes back the following week. Error #2: Keeping hundreds of pages at 200 for months without an email alert or alternative content — Google will eventually view them as thin content.

Error #3: Using a 301 to a category or similar product. This is acceptable only if the product is permanently discontinued and an equivalent replaces it. For a stockout, even long-lasting, the 404 remains cleaner than chain redirects that dilute PageRank.

• Extract the stockout history and calculate the average duration before restocking
• Define an internal threshold (e.g., 21 days) beyond which to switch to 404
• Automate the HTTP code switch via CMS/ERP based on stock and stockout date fields
• Monitor 404 switches to detect import bugs or massive stockouts
• Switch back to 200 as soon as restocked to quickly regain indexing
• Avoid 301s to category or similar product unless permanently discontinued