Your WordPress site loads fine, and every page you click opens without an error. Yet Google may have quietly decided some of those pages do not exist — and stopped showing them in search results.
That silent mismatch is what you learn when you work out how to fix soft 404 errors in WordPress. A soft 404 tells Google “nothing here” while the server insists “everything is fine.” Until you fix that mixed signal, Google keeps those URLs out of its index, and the traffic they should have earned never arrives.
Key takeaway: a soft 404 is a disagreement between your server and your content. Fix the disagreement, and Google can index the page again — or drop it cleanly.
What Is a Soft 404 Error in WordPress?
A soft 404 happens when a page returns a 200 OK status code but its content looks like an error, an empty page, or a “not found” message. Google’s own documentation on HTTP status codes puts it plainly: if the content suggests an error, an empty page, or an error message, Search Console will show a soft 404 error, even though the server returned a 2xx success code.
Unlike a normal 404, where the server honestly says the page does not exist, a soft 404 has the server claiming the page exists while the content says otherwise. Google trusts the content and excludes the URL.
WordPress sites are especially prone to this, because WordPress rarely produces a true 404 by accident. Instead, themes and plugins create pages that look empty:
- Empty tag and category archives with one thin post, or nothing worth showing
- Internal search result pages for queries nobody searched, which say “nothing found”
- Deleted products or posts whose URLs still render a template with empty fields
- “Redirect all 404s to the homepage” plugins that send every dead URL to your front page with a 200 status
- Thin pages from filters, pagination, or faceted navigation
Soft 404 vs 404: Why the Difference Matters
A normal 404 is not a penalty. A soft 404 is worse: it wastes crawl resources on pages that should never have been crawled and keeps pages you want indexed out of search.
| Feature | Hard 404 | Soft 404 |
|---|---|---|
| HTTP status code | 404 Not Found (or 410 Gone) | 200 OK, despite missing or empty content |
| What Google hears | “This page does not exist” | “Everything is fine” — contradicted by the content |
| Indexing outcome | Clean, gradual removal from the index | Excluded from search, but Google may keep re-crawling it |
| User experience | A clear error page | A blank page, “no results found,” or an irrelevant redirect |
| SEO risk | Low, when intentional | Higher when widespread — wasted crawl budget and lost visibility |
Key takeaway: a hard 404 is a clean “no.” A soft 404 is a shrug — and Google handles shrugs by ignoring the page.
A Real-World Example: The Bakery With 40 “Missing” Pages
Picture a small bakery in Austin, Texas. It published seasonal menu pages — pumpkin bread in the fall, king cake in January — then deleted each when the season ended. But the URLs still loaded: the theme rendered an empty product template at each old address. When the owner opened Search Console, the Page indexing report showed dozens of soft 404s: Googlebot was revisiting empty templates instead of the current menu and catering page. One afternoon’s fix — real 410s, redirects only to genuine replacements, and a cleaned-up sitemap — restored crawling of the pages that mattered.
How to Fix Soft 404 Errors in WordPress: Find Them First
Start with the full list in Search Console:
- Open Google Search Console, go to Indexing > Pages, and find Soft 404 in the “Why pages aren’t indexed” table.
- Click the Soft 404 row to see the affected URLs, then export the list.
- Inspect a few representative URLs with the URL Inspection tool, using “View tested page” to see the render exactly as Googlebot sees it.
- Confirm the status code yourself in your browser’s developer tools: open the Network tab and reload the URL. A “not found” page showing 200 confirms the problem.
- Sort the URLs into three buckets: pages that should not exist, pages that moved, and pages that should be indexed. This sorting step decides every fix that follows.
Key takeaway: fix the pattern, not just the URL — one template fix can clear dozens of URLs.
How to Fix Soft 404 Errors in WordPress by Cause
Pages that are gone for good: return a real 404 or 410
If a page has been deleted with no replacement, stop serving a 200 at that URL. WordPress returns a proper 404 for unknown URLs by default, so a deleted page returning 200 means a theme, plugin, or redirect rule is overriding it — find it and remove it. A 410 Gone signals deliberate removal, but a plain 404 works fine: Google treats all 4xx codes (except 429) the same for indexing.
Pages that moved: redirect to the closest match only
Set up a 301 redirect to the closest relevant replacement — never to your homepage. Mass homepage redirects are a classic soft 404 factory, since Google sees many URLs returning identical generic content. Use a redirect plugin such as Redirection for one-to-one mapping; with no close replacement, let the URL return a 404.
Empty tag and category pages: consolidate or noindex
Tag and category archives are the most common soft 404 source on blogs. For archives you want indexed, add a description and enough posts to be useful. Merge overlapping one-post tags into a single tag. For thin archives you do not need in search, apply noindex in your SEO plugin’s taxonomy settings.
Internal search pages and thin pages worth keeping
WordPress search result pages (“?s=random-keywords”) often show “nothing found” with a 200 status — a textbook soft 404. Keep them out of your sitemap, do not link to them, and make sure they carry a noindex directive. But a flagged page that deserves to exist needs content, not a status code: add paragraphs covering the problem, the approach, and the result.
If the mess is bigger than a few archives, professional help pays for itself — see TechCoff’s services or get in touch. Related upkeep: how to speed up a WordPress site and how to move a WordPress site to a new host without creating broken URLs.
Prove the Fix Worked, Then Prevent a Relapse
Fixing the URLs is only half the job. Confirm it, then keep soft 404s from creeping back:
- Re-test each fixed URL with URL Inspection: deleted pages should return 404 or 410, moved pages should 301 correctly, kept pages should show real content.
- Clean your sitemap — remove deleted and noindexed URLs so Google stops rediscovering them.
- Fix internal links pointing at removed pages, which keep sending visitors and Googlebot to dead ends.
- Click “Validate fix” in Search Console once, after every affected URL is corrected. Google says validation typically takes up to about two weeks, though it can take longer. Do not click again until validation has passed or failed. For a second walkthrough, see WP Rocket’s guide to Google soft 404 errors.
- Recheck monthly: soft 404s return when you delete products, merge categories, or install plugins that change missing-page behavior.
Going forward, one rule covers most cases: deleting a page means deciding in the same moment — 404, 410, or 301 to a real replacement — and never redirecting all 404s to the homepage.
Frequently Asked Questions
What is a soft 404 error in WordPress?
A soft 404 is a page that returns a 200 OK success code but shows error-like or nearly empty content, so Google treats it as missing. In WordPress it usually comes from empty archives, internal search pages, deleted posts that still render a template, or plugins that redirect all 404s to the homepage.
Does a soft 404 hurt my Google rankings?
No sitewide penalty applies. The damage is indirect: flagged pages leave search results, Google wastes crawl resources on empty pages, and many soft 404s signal poor maintenance.
Should I redirect all soft 404s to my homepage?
No. Redirecting everything to the homepage is one of the most common causes of soft 404s, because Google sees many URLs returning identical generic content. Redirect only to a close, relevant replacement; if none exists, return a 404 or 410.
Final Takeaway
Soft 404s are quiet, and quiet problems cost the most traffic. The fix is simple: find the flagged URLs in Search Console, sort them into gone, moved, or worth keeping, and give each group the honest response it deserves. A 404 for what is gone, a 301 for what moved, and real content for what stays. That is how to fix soft 404 errors in WordPress for good: validate the fix, and check back monthly.
