Should you really avoid 301 redirects for expired pages to categories?

Why does Google reject this common practice?

Google's logic is based on HTTP semantics. A 301 redirect means "Moved Permanently" — in other words, the content has permanently moved elsewhere. If I sell red shoes in size 42 and the product no longer exists, redirecting to the "Red Shoes" page or "All Shoes" doesn't comply with this definition.

The content hasn't moved. It no longer exists. And this is where the confusion sets in: many SEOs believe that a 301 to a nearby category preserves some of the link equity (PageRank) and offers an alternative to the user. Google says no — or at least, not like that.

What should we do instead according to this logic?

The strict position would be to use a 404 code (Not Found) or, even better, a 410 code (Gone) if you know that the page will never return. The 410 is more explicit: it tells Google, "this resource existed, it no longer exists, no need to come back to crawl."

Some e-commerce sites combine: 404/410 on the server side, but with a custom page suggesting alternatives. This respects the technical guideline while providing an acceptable user experience. The problem is that this approach assumes losing all link signal that pointed to the expired page.

Is this Google position uniformly applied by search engines?

Let's be honest: field practice shows mixed results. Bing, for example, has long been more tolerant of "approximate" 301s. Google itself does not systematically penalize sites that massively redirect expired products to categories — as long as these redirects remain relevant.

The ambiguity remains on what "relevant" means. A blue jean size 32 to "Blue Jeans"? Probably acceptable. To "All Clothing"? Now that looks like a disguised soft 404, and Google can choose to ignore it or treat it as an error.

• A 301 redirect implies a permanent move, not a disappearance of content.
• Google instead recommends a 404 or 410 code for expired pages without an exact equivalent.
• Google's tolerance varies depending on the perceived relevance of the redirection — but there is no documented threshold.
• Large e-commerce sites often continue this practice without visible penalty — creating a gap between the official doctrine and the observed reality.

Is this statement consistent with observed practices on the ground?

No. And it's a classic problem with Google's communications: the theory is clear, reality is blurred. Large e-commerce players (Amazon, Cdiscount, Zalando) massively redirect their expired products to categories or similar replacement pages. They don't seem penalized for it.

Two hypotheses: either Google tolerates these practices on a large scale because the alternative (millions of 404s) would be worse for user experience, or the "penalty" is invisible — a simple loss of link signal without measurable ranking impact. In either case, the official statement does not suffice to guide a strategic decision.

What nuances should be applied to this rule?

It all depends on the semantic proximity between the expired page and the destination. If a product has a direct equivalent (new model, updated reference), a 301 is still justified — and Google generally accepts it. The problem arises when redirecting to a "vaguely related" page.

Some SEOs use a hybrid approach: 301 to a similar product if available, otherwise 410 with dynamic suggestions on the front end. This requires more business logic, but avoids the "soft" redirects that Google may interpret as soft 404s. [To be verified]: Google has never documented a numerical tolerance threshold for this type of redirection.

In what cases does this rule clearly not apply?

If you manage a site with event pages (concert tickets, limited-time bookings), the situation changes. Once the event is over, redirecting to the artist's page or the "Upcoming Concerts" category may make sense — even if technically, it's still debatable.

Similarly, for outdated editorial content (2018 guides replaced by 2023 versions), a 301 is legitimate if the new content deals exactly with the same topic. This is no longer an "expiration", it's an update. Here, Google should have no issue.

What should you do concretely with expired product pages?

The first step: segment expired pages according to their nature. A permanently discontinued product is not treated like a temporarily out-of-stock item. For products that are permanently removed without an equivalent, prioritize a 410 code rather than a 404 — it speeds up deindexing and frees up crawl budget.

If a product has a direct successor (new model, updated reference), then a 301 is still justified and Google shouldn't bat an eye. Document these choices in a decision matrix: it facilitates maintenance and avoids inconsistencies over time.

What mistakes should be avoided to prevent worsening the situation?

Never redirect in bulk to the homepage or a "catch-all" page. Google interprets this as a soft 404 and may purely ignore these redirects. Result: you lose link signal AND pollute your index with dead pages.

Avoid redirection chains (A → B → C). If an expired page was already pointing to a category that itself has been redirected, you create a chain that Google may refuse to follow entirely. Regularly audit to bypass these chains and point directly to the final destination.

How can you verify that your strategy is compliant and effective?

Use Search Console to monitor 404 errors and soft 404s. If Google classifies your redirects as soft 404s, it's a signal that they are deemed irrelevant. You will then need to either revise the destinations or accept to switch to 410.

On the analytics side, track the bounce rate of destination pages from the redirects. If users leave immediately, it indicates that the redirect is not relevant — and Google will eventually catch on through behavioral signals. A bounce rate higher than 70-80% on these pages should raise alarms.

• Segment your expired pages: temporary break, replaced product, permanent discontinuation.
• Use the 410 code for permanently removed pages without an equivalent.
• Reserve 301 for cases where a direct replacement product exists.
• Create custom 404/410 pages with relevant dynamic suggestions.
• Audit redirection chains quarterly to bypass them.
• Monitor Search Console for soft 404s and adjust strategy.