When Search Console Flags Soft 404s: Return 404, Redirect, or Repair the Page?

If Search Console lists soft 404s in Page Indexing, do not treat every URL the same way. Google detected a success status code with content that looks like an error, empty page, or missing-result state. The right next step is usually one of three actions: return a true 404 or 410, send a permanent redirect to a clear replacement, or repair a page that should still exist. This article shows how to triage those URLs in order so you fix the highest-risk patterns first.

Bottom line: Soft 404s are excluded from Search once Google recognizes them as error-like pages, and Google notes they can keep being crawled. Start with confirmation in URL Inspection, then choose the disposition that matches the content’s real fate—gone, moved, or still needed.

What a soft 404 actually means

According to Google’s crawling troubleshooting guidance, a soft 404 occurs when a URL returns a 200 success status while showing users that the page does not exist—or when the page is empty / nearly empty of main content. Common triggers include missing server-side includes, broken database connections, empty internal search results, or critical JavaScript that never loads.

Google’s HTTP status documentation makes the same point from the protocol side: a 2xx response does not guarantee indexing. If the received content looks like an error or empty page, Search Console can report a soft 404.

That is different from intentionally keeping healthy pages out of Google with robots.txt, noindex, or a true 404. Soft 404s are usually an accidental mismatch between the HTTP status and the page experience. For intentional exclusion choices, see our guide on robots.txt, noindex, or 404.

Why soft 404s matter for business sites

Three practical consequences usually matter more than the label itself:

• Search eligibility: Google says soft 404 pages are excluded from Search once detected as error pages.

• Crawl waste: In Google’s crawl budget guidance, soft 404 pages continue to be crawled and can waste budget. That guidance is written primarily for large or rapidly changing sites, but the inventory principle still helps smaller sites keep Google focused on useful URLs.

• User trust: Serving “page not found” messaging with a success status confuses people and makes broken journeys look like live pages.

Google has also been clear that ordinary true 404 responses are normal and do not, by themselves, hurt rankings for the rest of the site. Soft 404s are the less helpful pattern because they disguise missing content as successful pages. See Google’s older but still useful explanation in Do 404 errors hurt my site?

The Soft 404 Response Ladder

Use this ladder when Page Indexing shows a soft 404 cluster. Move down only after the previous level is clear.

1. L0 — Inventory and group. Export or review the soft 404 examples. Group by pattern: deleted product URLs, empty site-search results, filter/sort combinations, homepage catch-all redirects that look like soft 404s, and pages that should still exist but render blank.

2. L1 — Confirm with URL Inspection. For representatives of each group, check the live HTTP code and rendered HTML. Confirm whether Google sees a 200 with empty or error-like content, a resource-loading failure, or a true replacement URL elsewhere.

3. L2 — Score the disposition. Use the Soft 404 Disposition Scorecard below. Decide whether the URL is gone, moved, or still needed.

4. L3 — Apply the narrowest correct fix. Return 404/410 for permanently removed content with no replacement. Use a permanent redirect when a clear replacement exists. Repair rendering, blocked resources, or thin templates when the page should remain.

5. L4 — Verify and watch re-crawl timing. Re-test a sample in URL Inspection. Remember Google may not recrawl immediately, so Search Console can continue showing older detections until the next crawl. Request indexing only for high-value repaired URLs.

Soft 404 Disposition Scorecard

Score each URL group from 0–2 on the factors below. Higher totals favor keeping and repairing the URL. Lower totals favor a true 404/410 or a redirect.

How to read the total (0–12):

• 0–3: Prefer a true 404 or 410. Customize the HTML for users if helpful, but keep the error status code.

• 4–7: Prefer a permanent redirect only when a replacement is clearly relevant. Do not dump every unknown URL to the homepage.

• 8–12: Repair the page. Fix rendering, unblock critical resources, remove false error messaging, and restore substantive content before asking Google to recrawl.

Worked example: an ecommerce soft 404 cluster

Hypothetical: a mid-size Shopify brand sees 180 soft 404 URLs. Inspection shows three groups.

• Group A — discontinued products (110 URLs): Template says “This product is unavailable,” status is 200, no successor SKU. Score about 2. Return a true 404/410, keep a helpful custom error page, and remove those URLs from sitemaps.

• Group B — renamed collections (40 URLs): Old winter collection now lives under a new path with the same intent. Score about 6–7. Issue permanent redirects to the replacement collection, not the homepage.

• Group C — category pages blank to Googlebot (30 URLs): Users see products after client-side scripts load; Google’s rendered view is nearly empty because a key script is blocked or fails. Score about 10. Unblock or fix the critical resource, confirm rendered HTML includes product content, then request indexing for the most important categories.

Treating all 180 URLs as “add more content” would miss Groups A and B. Treating all of them as “just return 404” would delete discoverable category pages in Group C.

Common failure patterns

• Pretty 404 with HTTP 200. You can serve a branded not-found page while still returning a 404 or 410 status. Google explicitly recommends this over a soft 404.

• Catch-all redirects to the homepage. Google warns that sending many unrelated old URLs to one irrelevant destination, such as the homepage, can confuse users and may be treated like a soft 404 pattern during site moves.

• Empty search or filter result pages on 200. Zero-result internal search pages are a classic soft 404 trigger. Decide whether those URLs should remain crawlable at all.

• Assuming Soft 404 equals “Google hates 404s.” True 404s are expected. Soft 404s are the problem state because the status code and content disagree.

• Fixing once and expecting instant report clearance. Search Console can keep listing detections until Google crawls the corrected responses again.

Limitations and when this advice does not apply

This framework is for URLs Google already classifies as soft 404s, or for pages that clearly present error/empty states with a success status. It is not a substitute for broader crawl-budget engineering on million-page sites, and it does not replace a full site-migration plan when domains or URL structures change.

It also does not mean every low-traffic page should become a 404. If Google selected a different canonical, start with canonical diagnosis rather than soft 404 triage. Soft 404 scoring is about matching status codes and rendered content to the page’s real business fate.

Recommended next steps

1. Open Page Indexing, isolate the soft 404 reason, and sample URLs by template.

2. Run URL Inspection on live examples and note status code plus rendered content.

3. Score each group with the Disposition Scorecard and assign 404/410, redirect, or repair.

4. Remove retired URLs from sitemaps, stop homepage dump redirects, and re-test after deploy.

5. Track whether soft 404 volume falls after Google recrawls—not only whether your server now returns the intended code.

If soft 404 clusters sit beside indexing, canonical, or crawl-efficiency problems, a structured search engine optimization engagement can help prioritize technical fixes against content and conversion work.

If you want a second set of eyes on a soft 404 backlog before you change templates sitewide, book a growth strategy session and bring a Search Console export of the affected URL groups.

Sources

• Google Search Central — Troubleshoot Google Search crawling errors (soft 404 section)

• Google Crawling Infrastructure — How HTTP status codes affect Google’s crawlers

• Google Crawling Infrastructure — Crawl budget management

• Google Search Central Blog — Do 404 errors hurt my site?

• Google Search Central — Site moves and migrations