{"id":253,"date":"2026-07-11T21:55:03","date_gmt":"2026-07-11T12:55:03","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/soft-404\/"},"modified":"2026-11-15T21:54:35","modified_gmt":"2026-11-15T12:54:35","slug":"soft-404","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/soft-404\/","title":{"rendered":"Soft 404"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">What is a Soft 404?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A Soft 404 is a label Google applies when a page that is actually empty or gone returns, instead of <code>404 Not Found<\/code> , a <code>200 OK<\/code>. Google decides on its own that &#8220;this page effectively doesn&#8217;t exist.&#8221; It shows up in Search Console&#8217;s <a href=\"\/en\/seo-glossary\/page-indexing-report\/\">Page indexing report<\/a> as a &#8216;Not indexed&#8217; reason. Google&#8217;s official Help Center defines this status as a case where the page &#8220;returns a user-friendly &#8216;not found&#8217; message but not a 404 HTTP response code.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The basic promise of the web is simple &#8211; if a page exists, the server returns <code>200 OK<\/code>, and if it doesn&#8217;t, it returns <code>404 Not Found<\/code>. A Soft 404 is when this promise breaks. The screen shows &#8220;No results&#8221; or empty content, but the server still sends <code>200<\/code>, so Google spots the contradiction (&#8220;the screen says nothing&#8217;s here, but the signal says it is&#8221;) and judges it a &#8216;soft (presumed) 404&#8217; on its own. The key point is that it isn&#8217;t a real <code>404<\/code>, but a label Google attaches based on its own inference.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Is it a problem or not?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">First, you need to understand what it is. A Soft 404 isn&#8217;t a server error; it&#8217;s a state where Google has decided to exclude the page from its index. So whether you need to act depends on whether you want that URL to appear in search.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>If the page shouldn&#8217;t be indexed (deleted posts, internal site search results, etc.)<\/strong> &#8211; It isn&#8217;t a big problem in itself that it falls into Soft 404. Still, it&#8217;s cleaner to switch it to an accurate signal (a real 404\/410), as shown below.<\/li>\n\n\n<li><strong>If you want the page indexed but it fell into Soft 404<\/strong> &#8211; This is a problem. It means a real product or content page has disappeared from search entirely, so you need to strengthen the content.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s also clear up a misconception about scale. A few Soft 404s won&#8217;t eat up your crawl budget and threaten your whole site. As of 2026, Google&#8217;s crawl budget guide narrows the sites that need budget management to large sites with &#8220;1 million+ unique pages with content that changes moderately often (once a week)&#8221; or &#8220;10,000+ unique pages with very rapidly changing content (daily),&#8221; and says other sites &#8220;don&#8217;t need to read this guide.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/large-site-managing-crawl-budget?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> So for most sites, the real issue isn&#8217;t wasted budget but &#8220;has a page that should be visible disappeared from search?&#8221; That said, for sites with many pages, Ahrefs points out that resources spent crawling and indexing such pages can affect the crawl efficiency of the whole site. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/what-is-soft-404\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why does this happen?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google&#8217;s official doc explains the cause like this: &#8220;If the content contains a Google Search error, an empty page, or an error message, Search Console will show a soft 404 error.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/http-network-errors?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> In other words, it happens when a screen that&#8217;s effectively &#8216;nothing&#8217; sits on top of a <code>200<\/code> response. Common types in practice include the following.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Empty search result and listing pages<\/strong> &#8211; Ahrefs explains that &#8220;if a search or category page shows &#8216;no results&#8217; while returning a 200 status, it can be interpreted as a soft 404.&#8221; <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/what-is-soft-404\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/li>\n\n\n<li><strong>Thin content with almost nothing on the page<\/strong> &#8211; Yoast says &#8220;if the page exists but you still get a soft 404, Google considers it thin content,&#8221; adding that this is a common cause in CMSs like WordPress that generate many pages automatically. <a class=\"jt-src jt-src--data\" href=\"https:\/\/yoast.com\/what-is-a-soft-404-error\/\" target=\"_blank\" rel=\"noopener\">Yoast<\/a><\/li>\n\n\n<li><strong>Redirecting missing pages to the home page<\/strong> &#8211; If you send a missing page to an unrelated home page, what was requested and the page that loads don&#8217;t match, so Google may treat the redirect as a soft 404.<\/li>\n\n\n<li><strong>Server configuration and rendering errors<\/strong> &#8211; Ahrefs points out that &#8220;the server may be misconfigured to return 200 OK for pages that don&#8217;t exist.&#8221; Pages drawn with JavaScript that fail to render and leave only a blank screen lead to the same result. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/what-is-soft-404\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">The right fix<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google&#8217;s official Help Center recommendation is clear: &#8220;If the page is truly not found, return a 404 response code, and add information to the page to let Google know it&#8217;s not a soft 404.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> This one sentence contains both solutions &#8211; if it really doesn&#8217;t exist, say so; if it&#8217;s a page that should exist, actually fill it with content.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Situation<\/th><th>Correct action<\/th><th>Basis<\/th><\/tr><\/thead><tbody><tr><td>The page is actually gone (permanently deleted)<\/td><td>Configure the server to return <code>404(Not found)<\/code> or <code>410(Gone)<\/code><\/td><td>Returning 404 is recommended for pages that truly can&#8217;t be found <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/td><\/tr><tr><td>The content should be there, but it&#8217;s thin<\/td><td>Fill it with rich, relevant content to show its value<\/td><td>Official recommendation to &#8220;add information to the page&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/td><\/tr><tr><td>The page has moved to another location<\/td><td>Set up a <a href=\"\/en\/seo-glossary\/301-redirect\/\">301 redirect<\/a> to the right new location (not the home page)<\/td><td>Handle moves with a 301 <a class=\"jt-src jt-src--data\" href=\"https:\/\/yoast.com\/what-is-a-soft-404-error\/\" target=\"_blank\" rel=\"noopener\">Yoast<\/a><\/td><\/tr><tr><td>Pages that don&#8217;t need indexing, such as search results and filters<\/td><td><code>noindex<\/code>to keep them out of the index<\/td><td>Use noindex for pages that shouldn&#8217;t be indexed <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/what-is-soft-404\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">You may wonder about the difference between <code>404<\/code>and <code>410<\/code>here. Google&#8217;s official doc says that, for crawling purposes, &#8220;all 4xx errors, except 429, are treated the same,&#8221; so both codes ultimately lead to the URL being removed from the index. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/http-network-errors?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> 410 has the stronger meaning of &#8220;gone permanently,&#8221; but Google&#8217;s handling is effectively the same as 404. Some sites use 410 for pages they&#8217;ve removed completely and some use 404, but either way, Google drops the URL from its index.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check and notify Google again<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After fixing it, you need to check what actually changed. Google&#8217;s official Help Center advises running a live URL inspection to see how Google renders the page. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> What helps here is Search Console&#8217;s <a href=\"\/en\/seo-glossary\/crawling-indexing\/\">crawling and indexing<\/a> flow &#8211; check the current status with the inspection tool, request indexing again if you&#8217;ve improved the content, and if you&#8217;ve truly removed the page, check the response code directly to confirm that <code>404\/410<\/code>is returned correctly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In short, a Soft 404 is a signal that &#8220;Google sees this page as effectively empty and has excluded it from search.&#8221; If that judgment is right (the page really doesn&#8217;t exist), confirm it with an accurate response code; if it&#8217;s wrong (the page should exist), fill in the content to clear up the misunderstanding. That&#8217;s the proper approach. Just remember that workaround redirects that only cover up the symptom can create new soft 404s.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">References<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">Page indexing report &#8211; Soft 404 status definition and recommended actions &#8211; Google Search Console Help<\/a><\/li>\n\n\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/http-network-errors?hl=ko\" target=\"_blank\" rel=\"noopener\">How HTTP status codes affect Google&#8217;s crawlers (4xx handling, soft 404) &#8211; Google Search Central<\/a><\/li>\n\n\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/large-site-managing-crawl-budget?hl=ko\" target=\"_blank\" rel=\"noopener\">Crawl budget management guide for large sites (size thresholds) &#8211; Google Search Central<\/a><\/li>\n\n\n<li><a href=\"https:\/\/yoast.com\/what-is-a-soft-404-error\/\" target=\"_blank\" rel=\"noopener\">What is a soft 404 error and what to do about it? &#8211; Yoast<\/a><\/li>\n\n\n<li><a href=\"https:\/\/ahrefs.com\/blog\/what-is-soft-404\/\" target=\"_blank\" rel=\"noopener\">What is a Soft 404 and what causes them? &#8211; Ahrefs<\/a><\/li>\n\n\n<li><a href=\"https:\/\/www.searchenginejournal.com\/technical-seo\/404-vs-soft-404-errors\/\" target=\"_blank\" rel=\"noopener\">404 vs. Soft 404 Errors: What&#8217;s The Difference &amp; How To Fix Both &#8211; Search Engine Journal<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>A &#8216;Soft 404&#8217; is a state where a page doesn&#8217;t actually exist (or has no content), but the server still returns a normal (200) response, so Google decides &#8220;this page effectively doesn&#8217;t exist.&#8221; Google&#8217;s official docs describe it as a case where the page &#8220;returns a user-friendly &#8216;not found&#8217; message but not a 404 HTTP response code.&#8221; It appears in the Search Console Page indexing report as a &#8216;Not indexed&#8217; reason.<\/p>\n","protected":false},"template":"","glossary_categories":[17],"class_list":["post-253","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-search-console"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/253","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":2,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/253\/revisions"}],"predecessor-version":[{"id":2384,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/253\/revisions\/2384"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=253"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=253"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}