Here's a scenario that plays out more often than most marketing ops teams realize: a site migration finishes on schedule, the CMS looks clean, and every URL returns a 200 OK status. Six weeks later, organic traffic is down 40%. Three months in, it's down 90%. Nobody changed the content strategy or faced a manual action. The pages are "there"; they just aren't in the index anymore.
The culprit, in many cases, is soft 404s at scale.
What a Soft 404 Actually Does
A soft 404 is a page that returns a 200 OK HTTP status but appears as a missing, empty, or placeholder page to Google. This includes thin content, empty category pages, removed products still returning 200, or templates lacking meaningful content. The server says "everything's fine," but the page itself says otherwise.
Google's response is predictable: it excludes those URLs from the index. The page exists on your server but not in search.
This distinction matters because soft 404s are considered more harmful than honest 404s. An honest 404 is a clear signal: this page is gone, stop crawling it. A soft 404 is contradictory. The status code and the content don't match, confusing crawlers. Google doesn't penalize sites for honest 404s, but soft 404s waste crawl budget, distort crawl allocation, and can prevent important revenue-driving pages from being discovered or recrawled.
The Compounding Effect Most Teams Miss
If you have 50 soft 404s on a 10,000-page site, the damage is localized. Those specific URLs drop out of the index—annoying but survivable.
The problem compounds when soft 404s are widespread. During migrations, CMS platform changes, or large-scale content operations, removed or empty pages that still return 200 can multiply. Hundreds become thousands. Google starts spending crawl resources on low-value pages while your actual content waits in line. Useful pages get crawled less often, new content takes longer to index, and older content that should be refreshed sits stale.
At that point, you don't have a soft 404 problem; you have a crawl allocation problem masquerading as a traffic collapse.
Here's the part that complicates diagnosis: the traffic drop may not be entirely about indexing. Google removed FAQ rich results from live search results. Sites relying on those expandable FAQ boxes for extra SERP real estate lost clicks. That's a CTR loss from a SERP feature change, not a ranking penalty. But if it coincides with a soft 404 issue, the two signals blur together in your analytics, leading teams to chase the wrong fix.
The Diagnostic Workflow
Separating these failure modes requires discipline. The operational sequence looks like this:
- Search Console soft 404 report. Pull every URL flagged as a soft 404. Sort by template type (category pages, product pages, blog posts) to identify patterns.
- URL Inspection rendering check. For a sample of flagged URLs, use URL Inspection to see how Google renders the page. If the output is thin, empty, or placeholder content, that's your confirmation.
- Segment your traffic loss. Separate pages that lost clicks due to FAQ rich result removal from those that dropped out of the index entirely. Different causes require different fixes.
The fix is straightforward in principle but painful in execution: align HTTP status with reality. If a page is gone, return a real 404 or 410. If there's a true replacement, use a 301 redirect (only to a genuinely relevant destination, not a homepage dump). If the page should exist, add substantive unique content to avoid soft 404 classification.
The Governance Problem Behind the Technical One
Most teams treat soft 404s as a one-time cleanup: fix the flagged URLs and move on. That's treating the symptom.
The systemic issue is that nobody owns the contract between content operations and technical SEO. Products get removed, and the CMS keeps returning 200. Categories go empty after a taxonomy restructure. Landing pages from last quarter's campaign remain as shells. Without operational guardrails (removed content returns 404/410 automatically, redirects require relevance checks, and pages intended to rank get a minimum content threshold), soft 404s reappear every quarter.
For B2B SaaS teams running large content operations, this is a governance gap, not a technical one. The fix is a process, not a patch.
A 90% traffic collapse rarely has a single cause. But when the server keeps telling Google "everything's fine" while the pages tell a different story, the index quietly disagrees. By the time someone notices the gap between the 200 OK and the empty page, the crawl budget has already been spent on nothing.
