Part of the Indexing Problems topic guide. Use the guide to move from this specific question to the full diagnostic workflow.
A soft 404 is a URL that returns a response such as HTTP 200, but Google interprets the page as missing, empty, error-like or otherwise not a useful representation of that URL. “Soft 404” is therefore Google’s indexing classification, not an HTTP status code. The correct fix depends on the page’s intended lifecycle: restore meaningful content, redirect to a genuinely equivalent replacement, or return a real 404/410 when the resource is gone.
For a URL in a verified property, use the Page Indexing report and URL Inspection to see the recorded state and test the current page. For a third-party backlink URL, an external checker cannot see the source property’s private Soft 404 reason. A backlink provider can report the response, rendered content, link presence and dated index observation, but should label a Soft 404 diagnosis as unconfirmed without property evidence.
Soft 404 is one branch of the IndexVero indexing-problem diagnostic library. If the URL’s broader failure state is still unclear, begin with the page-not-indexed diagnostic workflow. Use the URL Inspection guide to keep Google’s recorded crawl evidence separate from the current live response.
Soft 404 vs a real 404
| State | Server response | Page content | Defensible conclusion |
|---|---|---|---|
| Real 404 | HTTP 404 | A useful not-found page may still be shown to users | The server says the requested resource was not found |
| Real 410 | HTTP 410 | The resource is intentionally gone | The server says the resource is no longer available |
| Soft 404 | Often HTTP 200, or an irrelevant redirect | Missing, empty, error-like, extremely thin or unrelated to the requested URL | Google classified the response as not representing a useful page for that URL |
| Temporary unavailable page | Depends on the actual failure | Maintenance, login, rate-limit or application error | Diagnose the availability event before treating it as missing content |
Google’s 404 and Soft 404 guidance says that a non-existent page should return 404 or 410 rather than a normal success response or an irrelevant redirect such as the homepage. Google currently treats 404 and 410 similarly for this purpose.
Google documentation last checked: August 2, 2026.
Why a page can be classified as Soft 404
The label does not prove one cause. It tells you to compare the HTTP response with what the rendered page actually represents. Patterns worth investigating include:
- An error template, “not found” message or empty state returned with HTTP 200.
- A removed product, profile, listing or article that retains only navigation and boilerplate.
- Every missing URL redirecting to the homepage or another page that is not an equivalent replacement.
- JavaScript rendering that leaves the main content blank or replaces it with an error state.
- A gated, expired or unavailable page whose visible response does not match the successful status code.
- Large sets of generated URLs that contain nearly no URL-specific information.
These are diagnostic branches, not a claim that any one pattern automatically triggers the label.
The evidence worksheet
| Field | What to record | Why it matters |
|---|---|---|
| Requested URL | The exact URL being diagnosed | Prevents a canonical, redirect target or normalized form from silently replacing the subject |
| HTTP response | Status, headers and check time | Separates a protocol-level 404/410 from Google’s Soft 404 classification |
| Final URL | Redirect chain and terminal destination | Shows whether the replacement is equivalent or merely convenient |
| Rendered main content | URL-specific title, primary copy, media and meaningful data | Reveals blank, error-like or boilerplate-only output |
| Intended lifecycle | Exists, moved, permanently gone, temporarily unavailable or access-restricted | Determines the correct response rather than applying one fix to every case |
| Property evidence | Recorded Page Indexing reason, last crawl and live-test result | Keeps the older indexed evidence separate from the current page |
| Discovery declarations | Sitemap membership and internal links | Identifies URLs the site still presents as important despite a missing response |
Fix the page according to its intended lifecycle
The page should exist
Return a stable successful response and restore meaningful, URL-specific main content. Confirm that the rendered page—not only the raw HTML—contains the intended information. Align the title, canonical and internal links with the same URL representation.
The content moved to an equivalent replacement
Use a permanent redirect to the closest equivalent replacement. Do not redirect every deleted URL to the homepage, a category root or an unrelated commercial page merely to avoid a 404.
The resource is permanently gone
Return HTTP 404 or 410 and remove the URL from sitemaps and active internal links. A branded, helpful 404 template is fine for users as long as the server sends the correct status. Review the sitemap workflow before resubmission so removed URLs are not declared again.
The resource is temporarily unavailable
Fix the underlying availability problem and return the status that accurately represents the failure. Do not disguise an application error, maintenance response or access problem as a normal 200 page. Continue with the server and access error guide when the content cannot be retrieved reliably.
A provider/seller decision rule
| Evidence available | Allowed report | Do not claim |
|---|---|---|
| Private Search Console Soft 404 status | Record the status, inspected URL, last crawl and current live-test result | That one visible page feature caused the classification |
| Third-party source returns 200 with an error-like page | Report “reachable response, expected content/link not verified” | Confirmed Search Console Soft 404 |
| Source redirects to an unrelated destination | Report the redirect chain and failed delivery relationship | That the original URL is indexed or that link value was preserved |
| Check cannot render or reach the source | Report unavailable and recheck later | Not indexed, Soft 404 or link removed |
This protects both parties: the seller reports what can be verified, while the site owner keeps private Search Console classifications separate from public observations.
Validate the repair without promising a deadline
- Verify the intended HTTP response and rendered content.
- Remove contradictory sitemap, canonical, redirect and internal-link signals.
- For an owned URL, run a live test after the repair.
- Request indexing when appropriate, then preserve the request as a separate event.
- Recheck the recorded Page Indexing state after Google crawls again.
A successful live test proves that the current page passed the checks exposed by that test. It does not prove that Google has already replaced the older indexed record or selected the page for indexing.
The Soft 404 state graph
requested URL → HTTP response → redirect/final URL → rendered document → intended lifecycle → recorded Google classification → later observation
Preserve every node. If “HTTP 200” is collapsed into “healthy,” the missing-content problem disappears from the report. If “Soft 404” is collapsed into “the server returned 404,” the protocol evidence becomes false.
For backlink providers, route a source-page Soft 404 through the backlink indexing evidence workflow: availability and content mismatch must be resolved before placement or index-observation claims.
FAQ
Is a Soft 404 an HTTP status code?
No. It is Google’s classification of a response that does not behave like a useful page for the requested URL, even though the server may return 200 or redirect elsewhere.
Should every deleted page redirect to the homepage?
No. Redirect only when there is a genuinely equivalent replacement. Otherwise return 404 or 410 and remove active discovery signals.
Can a backlink checker confirm a Soft 404?
It can record the response, redirect, rendered content, link presence and public index observation. It cannot confirm a private Search Console Soft 404 classification without access to that property.
Does fixing a Soft 404 guarantee indexing?
No. The repair removes or clarifies one problem state. Google still makes later crawling, canonical and indexing decisions.
If the URLs you need indexed are backlinks on sites you don’t control, Search Console can’t submit them for you. Our backlink indexing service handles third-party URLs in bulk and verifies the outcome.
Leave a Reply