Soft 404 Errors: What They Mean and How to Fix Them

You opened Search Console, clicked Page Indexing, and found a row that says Soft 404 next to a URL that loads perfectly in your browser. Nothing is broken. The page is right there. Google is still refusing to index it.

Almost every article about soft 404s explains the ecommerce version of this problem: a deleted product page that returns a 200 instead of a 404. That is not what is happening on your service site. On a plumbing, dental, or law-firm site, the soft 404s Google reports are usually live pages Google judged to be empty.

That distinction changes the fix completely. Here is how to tell which pattern you have and what to do about each one.

What is a soft 404, in plain English?

A soft 404 is a URL that returns an HTTP 200 (success) status code while Google's systems conclude the page has no real content. Google's Page Indexing report documentation describes it as a page that "returns a user-friendly 'not found' message but not a 404 HTTP response code."

The server says everything is fine. Google looks at what came back and disagrees. That disagreement is the whole issue.

Google's HTTP status codes documentation puts it directly: for a 2xx response, "if the content suggests an error for Google Search, an empty page or an error message, Search Console will show a soft 404 error." Note the phrasing — an empty page counts, not just an error message.

The original 2008 Google post Farewell to soft 404s framed the cost this way: "search engines may spend much of their time crawling and indexing non-existent, often duplicative URLs on your site. This can negatively impact your site's crawl coverage." On a 40-page service site crawl budget is rarely your bottleneck. Being judged empty is.

Why is Google calling a live page a soft 404?

Because a soft 404 is a content verdict wearing a technical costume. Google is not reporting a broken server response. It is reporting that after crawling and rendering the URL, there was not enough substance on it to be worth an index slot.

Three things make Google reach that conclusion on a page that renders fine for you:

• The visible text is tiny. A page whose entire unique body is a headline, a map embed, and a phone number reads as empty to a crawler, no matter how good it looks.
• The words look like an error. Copy such as 'Sorry, nothing here yet', 'Coming soon', or 'No results found' is a strong soft-404 trigger even when the page is intentional.
• Nothing painted for Googlebot. If your content only appears after client-side JavaScript runs, and it failed or timed out during rendering, Googlebot saw an empty shell.

Fix the wrong one of those and the error comes straight back after the next crawl. So identify the pattern before you touch anything — the same discipline a proper technical SEO audit applies to every indexing error.

Which five pages on a service site trigger it most often?

Five page types account for the large majority of soft 404s reported on small service-business sites. Each one has a different correct fix, and applying the wrong fix is how people end up chasing the same error for months.

Notice that only one of these five is a genuinely dead page. The rest are alive and reachable. That is why the ecommerce advice — "just return a 404" — is wrong for four out of five cases here.

If your thin location pages are the culprit, that is a strategy problem, not a status-code problem. A service-area page with a map and a paragraph is not a page; it is a placeholder. Our technical SEO service starts by separating those two categories before anyone edits a template.

Should you 410 the page, noindex it, or thicken it?

The decision comes down to one question: do you want a human to be able to reach this URL? If yes, the page must stay live and either get real content or get a noindex tag. If no, it should return a 4xx.

The honest verdict on thank-you pages: noindex. They are live, useful, and have nothing to offer a searcher. On empty tag archives: delete the tag. A noindexed archive that still exists is technical debt you will re-litigate next year.

The bulk-redirect-to-homepage move deserves its own warning. Google's docs on status codes confirm 301 is treated as a strong signal that the target should be processed — but a redirect from a deleted service page to your homepage is not a strong signal of anything. Google frequently treats those as soft 404s too. If there is no genuinely equivalent page, let it 404. Our guide to 301 vs 302 redirects covers where redirects actually earn their keep.

How do you fix a soft 404 caused by JavaScript rendering?

Server-render the content, or accept that Googlebot may never see it. Google's JavaScript SEO guidance states that single-page apps handling errors in client-side JavaScript "often report a 200 HTTP status code instead of the appropriate status code," which "can lead to error pages being indexed and possibly shown in search results."

The two workarounds Google names are blunt: "Redirect to a URL where the server responds with a 404 status code," or "Add or change the robots meta tag to noindex."

To confirm rendering is your problem, run the URL through the URL Inspection tool in Search Console, click Test live URL, then open View crawled page and read the rendered HTML. If your main body copy is not in there, Googlebot did not see it. Your browser is not the test — the rendered HTML is.

This bites service businesses in three specific places: booking widgets loaded from a third-party script, review carousels pulled at runtime, and any page whose text lives inside a tab or accordion component that only mounts on click. If a page's entire value is inside a widget you do not control, it is not a page you can rank.

What is the difference between a soft 404 and a real 404?

A real 404 returns the 404 status code in the HTTP header; a soft 404 returns 200 and only *looks* like an error to the reader. The status code is the entire difference, and you cannot see it in a browser window — it lives in the response header.

The 2008 Google post is still the clearest statement of what to do instead: "return a 404 response code and clearly explain to users that the file wasn't found." A helpful, branded, friendly not-found page is fine. It just has to send a 404 in the header while it does that.

Check yours in ten seconds. Open a terminal and run curl -I against a made-up URL on your domain — something like /this-page-does-not-exist — and read the first line of the response. If it says 200, every mistyped URL on your site is a candidate soft 404. That single server-config fix is often the highest-leverage item on the whole list.

Soft 404s rarely appear alone. They usually show up alongside crawled - currently not indexed, and both point at the same underlying judgment: not enough here to bother with. If your pages are not ranking, start with why before you start editing status codes.

How do you confirm the fix worked in Search Console?

Use the Validate Fix button in the Page Indexing report, then wait. Google's documentation is explicit: "Validation typically takes up to about two weeks, but in some cases can take much longer, so please be patient."

The sequence that actually works:

• Ship every fix for that error type first — Google recrawls the whole affected set, not just the URL you were staring at.
• Inspect one representative URL and click Test live URL to confirm the new status code or rendered content is live.
• Open the Soft 404 issue in Page Indexing and click Validate Fix. You cannot restart a validation run mid-cycle, so do not click it early.
• Expect status to move to Started, then Passing per URL, then Passed for the issue. Two weeks is normal. Longer is common on low-authority domains.

One warning: if you noindexed a page, Search Console will eventually move it out of Soft 404 and into 'Excluded by noindex tag'. That is not a failure. That is the error resolving exactly the way you asked it to. Read our breakdown of what to hide from Google if you are unsure which tool applies.

And track it in Search Console, not in a spreadsheet an agency emails you. If you are not sure how to read the Page Indexing report, our Search Console guide walks through it.

What should you do first, this week?

Sort your soft 404 URLs into the five buckets above, and you will usually find one template causing most of them — a thank-you page, a tag archive, or a location template. Fix the template, not the URLs.

If your soft 404 list is full of thin location or service pages, the status code was never the real issue and no amount of header tweaking will fix it. That is a content-depth problem, and it is the same problem that keeps those pages off page one. We fix both in the same pass on the technical SEO side — no lock-in, month to month. Get my free audit and we will tell you which bucket your errors are in before you pay us anything.