A soft 404 is a page that tells the server everything is fine (status code 200) while showing users and Googlebot nothing useful. It is one of the most common technical SEO problems I encounter on audits, and it is consistently underweighted because your monitoring tools do not flag it as a server error. The server is happy. The page is broken. Google knows it, even if your dashboards do not.

What Causes Soft 404s

The most common causes fall into a few predictable categories:

  • Deleted content without a redirect: The CMS removes the content but the URL remains, now serving an empty template or a generic ‘no results found’ message that returns 200.
  • Zero-result search pages: A site search URL that returns no results still renders the page template with a 200 response. Every unique search query creates a new URL that Google may crawl.
  • Filter pages with no matching results: Faceted navigation URLs that produce empty product grids or category pages with no matching inventory.
  • Thin auto-generated pages: Programmatically generated pages with minimal or boilerplate content — common in directory sites, location pages, and large e-commerce catalogs built with templating.
  • Expired content that was not removed: Event pages, promotional landing pages, and time-limited campaigns whose URLs persist after the content is no longer relevant, now serving a sparse or placeholder page.
  • WordPress ‘page not found’ templates returning 200: Some WordPress configurations serve the 404.php template but return a 200 HTTP status code due to a misconfigured theme or plugin.

How Google Detects Soft 404s

Google uses a combination of signals to classify a page as a soft 404: very low word count relative to the site average, content that is nearly identical to another URL, explicit ‘not found’ or ‘no results’ text present on a 200-response page, or page content that is essentially just a site template with no body content. Google has confirmed it uses machine learning to identify these patterns across its crawl data.

Google Search Console surfaces soft 404s in the Pages report under the ‘Not indexed’ section. When a URL appears as a soft 404 in Search Console, Google is explicitly telling you it crawled the page, evaluated the content, concluded it had no standalone value, and refused to index it. This is useful diagnostic information — it is not a penalty, but it is a signal you should act on.

Why Soft 404s Hurt

Three direct effects compound over time:

  • Crawl budget drain: Google continues crawling soft 404 URLs because they return 200. Every crawl of a valueless page is crawl capacity not spent on your real content. On large sites with thousands of soft 404s, this materially delays how quickly new pages get indexed.
  • Index quality dilution: If soft 404s slip into the index before Google classifies them correctly, they contribute to a lower overall quality signal for your site. Google’s quality assessment operates at the domain level, not just the page level — a large volume of low-value indexed pages can affect how Google evaluates your site’s authority overall.
  • Internal link waste: If your site navigates to or links from soft 404 pages, you are routing users and crawlers into dead ends. Any link equity passing into a soft 404 URL is not flowing to pages that can use it.

How to Find Soft 404s Across Your Site

Start with Search Console. The Pages report shows soft 404s Google has already identified. Export the complete list. Next, run a crawl with Screaming Frog or Sitebulb and filter for pages with very low word counts — under 100 or 150 words of body text is a practical threshold for initial review. Cross-reference those low-word-count 200 pages against your intentional thin pages (contact pages, simple landing pages, paginated archives) to isolate genuine soft 404 candidates.

Also audit your site search results pages explicitly. Most CMS platforms generate unique URLs for each search query. If those pages are crawlable — not blocked in robots.txt — they are generating soft 404s at scale every time someone searches for something on your site. Related: CDN and SEO.

How to Fix Them

The fix depends entirely on the cause:

  • Deleted content with no replacement available: Return a proper 404 or 410 HTTP status code. A 410 is preferable for content you are permanently removing — Google processes 410s faster and stops recrawling sooner.
  • Deleted content with a relevant replacement: 301 redirect to the closest equivalent live page. Do not redirect to the homepage unless there is genuinely no better destination.
  • Search results and filter pages: Add a noindex directive to search result page templates. Block high-volume parameter patterns in robots.txt. For filter-based facets, use canonical tags pointing to the base category page.
  • Thin auto-generated pages: Either invest in real, distinct content for each page (location pages, product variants) or noindex them and consolidate into paginated parent pages with proper navigation.
  • Expired content: Set a 410 for permanently removed content. For recurring content like annual events, keep the URL live and update it each cycle rather than deleting and recreating.

Building Prevention Into Your Workflow

Soft 404s accumulate through content churn with no governance process. The best prevention is making URL lifecycle management part of your content workflow: when content is removed, the person removing it is responsible for the redirect or the correct error response. In my SEO University cohorts, this is a module I dedicate time to because most soft 404 problems I see on audit engagements were entirely preventable — they built up over years because no one was watching the URL inventory. Related: technical SEO checklist.

Soft 404s vs. Thin Content — The Distinction Matters

A soft 404 and a thin content page are related but not the same thing. A soft 404 is Google’s classification: it has evaluated the page and determined it has no standalone value, declining to index it. A thin content page may be indexed but performs poorly in rankings because the content is shallow or near-duplicate. Both are problems, but the fix is different. A true soft 404 needs a status code correction, redirect, or noindex. A thin content page that is indexed needs substantive content improvement — adding noindex without improving it just removes a page from the index without addressing the underlying quality issue.

The practical test: if Search Console explicitly labels a URL as a soft 404 under ‘Not indexed,’ treat it as a soft 404. If a page appears in your index but ranks poorly on all queries and has thin word count, that is a thin content problem requiring content work, not just a technical directive. Distinguishing between the two prevents misapplying noindex as a shortcut to clean up content that could otherwise be improved and ranked.

Soft 404s are a symptom of URL inventory management failure. A technical website audit maps the full scope of the problem — including soft 404s that have not yet appeared in Search Console. Pair the fix with a review of your indexation issues to ensure your clean, valuable pages are getting the crawl and indexation attention they deserve.