Should you really return a 404 for expired pages, or is it SEO suicide?

Why does Google explicitly validate the 404 for expired pages?

Google reminds us that the 404 code is not a penalty but a legitimate technical piece of information: this URL no longer has content to index. Contrary to the belief that a 404 'loses juice', it merely signals the crawler not to waste time on this resource. The engine clearly understands that a permanently out-of-stock product, a past event, or an expired offer has no reason to remain online.

This clear stance contrasts with the vague practices observed in the field: some sites maintain empty pages with a 200, while others redirect massively to the homepage. Google legitimizes here the 'clean death' of a URL when it no longer has a reason to exist, without a natural equivalent.

When does a 301 redirect become relevant?

The essential nuance lies in the existence of a direct replacement product or content. Redirecting an out-of-stock iPhone 13 to the iPhone 14 makes sense: user intent remains satisfied, and the crawler receives a signal of thematic continuity. But redirecting a 2022 model to a generic category page dilutes the signal and frustrates the user.

Google does not specify the required degree of proximity necessary to justify a 301. An 'available' replacement can mean a successor model, a color variant, or a similar range. The interpretation remains vague, leaving a risky margin of appreciation on the SEO side.

What is the difference in treatment regarding crawl budget and indexing?

A correctly returned 404 allows Googlebot to quickly deindex the page and reallocate the crawl to active content. On a site with thousands of expired references, this gain becomes significant. Conversely, a 200 with empty content or a 301 to a generic page clogs the index and muddles thematic relevance signals.

301 redirects preserve some of the authority of the source page, but only if the target page is semantically coherent. A massive redirect to the homepage dissipates this signal without any real benefit. The 404, on the other hand, cuts short and frees up crawl resources.

• The 404 is not a penalizing error: it is a legitimate HTTP response for permanently absent content.
• The 301 redirect requires a direct equivalent: successor product, immediate variant, not a vague category page.
• Crawl budget and indexing: the 404 accelerates deindexing, while the 301 maintains a thematic signal if relevant.
• No consensus on the degree of proximity required to justify a 301: Google remains vague on this criterion.
• Avoid ghost 200s: keeping an empty page with a 200 status clutters the index without providing value.

Is this statement consistent with field observations?

Yes, but with a significant caveat: Google never quantitatively defines what constitutes an acceptable 'replacement product'. Practical tests show that overly distant 301 redirects (e.g., out-of-stock product → generic category) generate soft 404s after a few weeks. The engine detects semantic inconsistency and ultimately treats the URL as a disguised 404.

E-commerce sites that consistently redirect to the homepage or catch-all landing pages experience a gradual erosion of crawl budget. Googlebot eventually ignores these repeated redirects, indicating that the 'replacement product' must be genuinely equivalent, not just an active page chosen at random. [To be verified]: Google does not publish any metrics on the required degree of semantic similarity for a 301 to be considered 'clean'.

What nuances should be considered based on the type of site?

For a rapidly rotating e-commerce site, the distinction is critical. A product restocked later justifies a 503 (temporary), not a definitive 404. A product replaced by a new version calls for a 301. A product discontinued without a successor merits a clean 404, with an intelligent error page suggesting alternatives manually.

On an editorial or event-based site, expired pages (past conferences, limited offers) often have no direct equivalent. The 404 becomes the norm, but with a nuance: if the URL has accumulated backlinks or residual organic traffic, a 410 (Gone) can expedite deindexing while explicitly signaling that the content is intentionally removed, not just unavailable.

In what cases does this rule not strictly apply?

Pages with strong historical authority pose a problem. A product page with 50 quality backlinks and a high conversion history loses all signal if it goes to 404. Some SEOs keep these pages at 200 with minimal content ('product out of stock, see alternatives') to preserve PageRank, even risking a soft 404.

Google never comments on this borderline practice, but tests show that a well-built 'out of stock' page (relevant alternatives, editorial content around the product) can remain indexed and transmit its authority. [To be verified]: no official confirmation that this method is sustainable or tolerated in the long term.

What should be done concretely on a site with expired pages?

First, audit the inventory of expired pages: identify those with a direct equivalent (new model, variant) and those that do not. The first will be updated to 301, the second to 404. This segmentation avoids haphazard redirects that pollute the index.

Next, customize the 404 pages to propose relevant alternatives, ideally based on the category or attributes of the initial product. A smart 404 page limits user frustration and can recapture some residual organic traffic. Google does not index 404s, but user experience remains an indirect signal.

What mistakes should be absolutely avoided?

Never massively redirect to the homepage or a generic category page. Google detects these patterns and treats them as soft 404s, negating any potential benefit. The redirect must be individualized, based on a clear product logic (successor, color variant, equivalent range).

Avoid also keeping empty pages at 200 'to not lose PageRank'. If the page no longer has useful content, a clean 404 is preferable to a ghost 200 that clutters the index. Google will end up ignoring these pages anyway, so it's better to speed up the process.

How can I check if my site is managing expired pages correctly?

Use Google Search Console to detect soft 404s reported by Google: these pages return a 200 but are treated as 404s by the engine. This is a sign that redirects or residual content are not relevant enough. Crawl the site with Screaming Frog to identify redirect chains or unintentional 404s.

Also monitor the evolution of the crawl budget: an increase in the number of crawled 404s without a parallel decrease in total crawl can indicate that Googlebot is wasting time on dead URLs. Conversely, stabilization after implementing clean 404s confirms that the engine is efficiently reallocating its resources.

• Segment expired pages based on the existence of an identifiable direct equivalent.
• Apply a clean 404 for contents without successors, a 301 for equivalents for clear replacements.
• Customize 404 pages with relevant suggestions based on category or product attributes.
• Avoid any massive redirection to the homepage or generic category, sources of soft 404s.
• Monitor soft 404s in Search Console and redirect chains via crawler.
• Use a 410 (Gone) to explicitly signal a voluntary removal on highly visible historical pages.