Should you really use 404 errors instead of redirecting expired content to a category?

What is a soft 404 and why does Google detect them?

A soft 404 occurs when a page returns an HTTP 200 (success) code or a 301/302 redirect, but its content clearly indicates that it no longer exists. Google has developed algorithms capable of identifying these situations: generic category page unrelated to the requested URL, empty search page, disguised unavailability message.

The engine considers these responses to be deceptive. Instead of receiving straightforward information (404 = this resource no longer exists), Googlebot gets an ambiguous signal that requires additional content analysis to confirm that the page is indeed dead.

Why does redirecting to a category seem logical to SEOs?

The logic behind this practice seems defensible: preserving link juice by redirecting to a relevant category page instead of completely losing traffic and accumulated authority. For an e-commerce site removing a sold-out product, redirecting to the parent category avoids frustrating users with a 404 error.

However, Google does not see it this way. The engine distinguishes between a valid redirect (URL change, content merging) and a convenience redirect to a generic page. In the latter case, it simply cancels the redirect in its index.

What is the real impact on crawl budget and indexing?

The concrete effect is twofold. First point: Google must periodically revalidate these redirects to check if the destination content has changed or if the redirect has been corrected. Each revalidation consumes crawl budget without providing new information.

Second point: the category page does not regain the authority of the expired page. Google treats the situation as if the source page no longer exists but continues to crawl it as a precaution. As a result: you waste server resources and crawl time for zero SEO benefit.

• Soft 404s create algorithmic ambiguity that forces Google to unnecessarily recrawl
• Redirecting to a generic category provides no measurable transfer of authority
• A 404 or 410 code allows Google to definitively handle the page and free up crawl budget
• The 410 (Gone) specifically signals that the content will never return, unlike the 404
• For high-volume sites, the accumulation of soft 404s degrades the site's health metrics in Search Console

Does this recommendation contradict established practices?

Yes, directly. For years, the SEO doctrine has preached the preservation of PageRank at all costs: never let a page return a 404 if it can be redirected somewhere. This approach has led to systematic redirect strategies, often to pages of low relevance.

Google's stance here is clear: it is better to accept a real 404 error than a false redirect. This aligns with what has been observed on the ground for several years: sites that aggressively clean up their 404 errors by redirecting everything to home or categories see no ranking improvement. Worse, some experience a degradation of their overall indexing.

In which cases is a redirect still relevant?

Let's be precise: Google does not say that any redirect of expired content is bad. If a product is replaced by a similar model, a 301 redirect to the new product makes sense. If a blog post is updated and changes URL, the same applies.

The decision criterion is simple: does the destination page directly address the search intent of the source URL? If yes, redirect. If no (generic category, search page, home), let go and use a 404. [To be verified]: Google has never provided a clear metric on the acceptable relevance threshold to validate a redirect, resulting in an uncomfortable grey area.

Should you really prioritize the 410 over the 404?

The 410 (Gone) code explicitly indicates that the resource is permanently deleted and will not return. Theoretically, this should speed up the de-indexing process and avoid future crawls. Google has repeatedly confirmed that it treats 410s slightly faster than 404s.

In practice, the difference is marginal. A well-configured 404 (without disguised soft 404) works perfectly. The 410 primarily provides a semantic signal: useful for an e-commerce site that permanently removes entire lines, less critical for a blog removing an outdated article. In practice, if your CMS natively handles 404s, don't complicate your life by implementing 410 everywhere.

How to identify soft 404s on my site?

Go to Google Search Console, in the “Coverage” or “Pages” section. Google explicitly signals URLs treated as soft 404s. You will see pages that you thought were properly redirected but that Google has blacklisted as irrelevant.

Complement this with a Screaming Frog or Oncrawl crawl: identify all 301/302 redirects pointing to category pages, search pages, or home. Cross-check with your server logs to measure the crawl frequency of these URLs. If Google is regularly returning to expired pages for months, you have a massive soft 404 problem.

What strategy should be adopted to clean up existing content?

First step: segment your expired content. E-commerce products definitively removed from the catalog go to 404 or 410. Outdated blog posts without a recent equivalent: the same. Pages with genuinely relevant replacement content: a 301 redirect to that specific content only.

Second step: remove redirects to generic categories. Modify your server configuration (htaccess, nginx.conf) or your CMS to return a true 404 with a branded and useful error page. A good 404 page includes an internal search engine, category suggestion links, and a clear link to home.

How to avoid creating new soft 404s in the future?

Train your content and product teams on the doctrine of acknowledged 404s. When a product is removed without a direct equivalent, no automatic redirect. When a piece of content is unpublished, the same applies. Configure your CMS so that the default behavior is a 404, not a redirect to a parent page.

Establish a validation workflow: every 301 redirect must be justified by a true content equivalent, validated by someone who understands search intent. Automate monitoring of soft 404s via the Search Console API to quickly detect deviations.

• Audit Search Console and identify all URLs marked as soft 404
• Crawl the site to list suspect redirects to categories/home
• Replace these redirects with 404 or 410 codes depending on the nature of the content
• Create a personalized, useful, and well-internally linked 404 page
• Document a clear policy for managing expired content for the teams
• Monthly monitor new occurrences of soft 404s via GSC