{"id":256,"date":"2026-07-11T21:55:03","date_gmt":"2026-07-11T12:55:03","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/not-found-404\/"},"modified":"2026-11-15T18:46:51","modified_gmt":"2026-11-15T09:46:51","slug":"not-found-404","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/not-found-404\/","title":{"rendered":"Not found (404)"},"content":{"rendered":"<h2 class=\"wp-block-heading\">What It Means<\/h2>\n\n<p class=\"wp-block-paragraph\">&#8220;Not found (404)&#8221; is the status where Googlebot requested a specific URL and the server returned an HTTP 404 response, in other words &#8220;no such page,&#8221; so Google did not add the page to its index or removed it from the existing index. In Google Search Console&#8217;s <strong>Page indexing report<\/strong>, it appears as one of the reasons under &#8220;Not indexed,&#8221; and the official documentation describes it as &#8220;This page returned a 404 error when requested.&#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<p class=\"wp-block-paragraph\">404 is not a concept invented by a particular search engine; it is a standard web response code. MDN defines 404 as &#8220;a response status code that indicates that the server cannot find the requested resource.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Reference\/Status\/404\" target=\"_blank\" rel=\"noopener\">MDN (standard)<\/a> This Search Console report doesn&#8217;t create new errors; it simply gathers and shows the 404 responses your server was already sending.<\/p>\n\n<h2 class=\"wp-block-heading\">Does It Hurt Rankings?<\/h2>\n\n<p class=\"wp-block-paragraph\">The short answer: most 404s are not a problem. Google Search Central says &#8220;404 errors are a perfectly normal part of the web,&#8221; and that as new content appears and old content disappears, returning a 404 is the preferred approach. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/blog\/2011\/05\/do-404s-hurt-my-site\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> On rankings, it also states explicitly that the fact some URLs return 404 &#8220;does not impact how other URLs that return 200 (successful) perform in search results.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/blog\/2011\/05\/do-404s-hurt-my-site\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n<p class=\"wp-block-paragraph\">The data backs up this principle. When Ahrefs analyzed backlinks to about 2.06 million sites, at least 66.5% of links created since 2013 had already died (link rot). <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/link-rot-study\/\" target=\"_blank\" rel=\"noopener\">Ahrefs data<\/a> Pages disappearing and leaving a 404 behind is not the exception; it is how the web normally works.<\/p>\n\n<p class=\"wp-block-paragraph\">So Google&#8217;s official position boils down to two points. First, a 404 by itself doesn&#8217;t lower rankings. Second, a deleted page returning a 404 is normal and actually the recommended behavior. Google says that when you remove a page, it prefers you honestly return a 404 or 410 rather than a &#8220;soft 404&#8221; that sends visitors to the home page. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/http-network-errors\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n<h2 class=\"wp-block-heading\">Why 404s Show Up: Common Causes<\/h2>\n\n<ul class=\"wp-block-list\"><li><strong>Pages you deleted on purpose<\/strong> &#8211; old events, sold-out products, removed posts. This is normal and fine to leave as is.<\/li><li><strong>Old or mistyped URLs<\/strong> left in internal links or sitemaps &#8211; Google follows those links and requests addresses that don&#8217;t exist.<\/li><li><strong>Broken links from external sites<\/strong> &#8211; when another site links to a mistyped address, Google tries that address.<\/li><li><strong>Important pages that vanished by mistake<\/strong> &#8211; deployment accidents, slug changes, CMS errors. Only these actually need fixing.<\/li><\/ul>\n\n<h2 class=\"wp-block-heading\">When to Act<\/h2>\n\n<p class=\"wp-block-paragraph\">Google&#8217;s documentation distinguishes between &#8220;deleted&#8221; and &#8220;moved.&#8221; The Page indexing report says, &#8220;If the page was removed without a replacement, a 404 response isn&#8217;t necessarily a problem,&#8221; and if the content has moved, it recommends you &#8220;use a 301 redirect to the new location.&#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> The test is simple: is it okay for this URL to disappear?<\/p>\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Situation<\/th><th>Action<\/th><th>Basis<\/th><\/tr><\/thead><tbody><tr><td>Page removed on purpose, no replacement<\/td><td>Keep the 404 (no action needed)<\/td><td>404 is a normal response<\/td><\/tr><tr><td>Content moved to a different URL<\/td><td>301 redirect to the new location<\/td><td>Google: &#8220;use a 301 redirect to the new location&#8221;<\/td><\/tr><tr><td>An important URL with backlinks or traffic disappeared<\/td><td>Restore the page or 301 to the most relevant page<\/td><td>Preserves link value and user experience<\/td><\/tr><tr><td>You want to signal permanent removal clearly<\/td><td>Consider returning 410 (Gone)<\/td><td>See &#8220;404 vs 410&#8221; below<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">The key point is <strong>don&#8217;t cover every 404 with a redirect<\/strong>. If you send hundreds of missing pages to the home page no matter what, Google may classify them as soft 404s. Mass redirects to unrelated pages don&#8217;t solve the problem; they create a new one.<\/p>\n\n<h2 class=\"wp-block-heading\">404 vs 410: How Fast Pages Leave the Index<\/h2>\n\n<p class=\"wp-block-paragraph\">Site owners often confuse these. A 404 means &#8220;can&#8217;t find it right now,&#8221; while a 410 (Gone) means &#8220;permanently gone.&#8221; Yet the &#8220;same treatment&#8221; described in the official documentation and the &#8220;difference in crawl frequency&#8221; seen in experiments don&#8217;t quite line up. The table below sums up why, and how to decide in practice.<\/p>\n\n<figure class=\"wp-block-table jt-verdict\"><table><tbody><tr><th>Google&#8217;s official position<\/th><td>The indexing pipeline treats all 4xx errors except 429 the same way: whether 404 or 410, previously indexed URLs are removed from the index. The end result is the same. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/http-network-errors\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/td><\/tr><tr><th>Expert measurements<\/th><td>Reboot Online tracked 119 pages for more than three months and found Google <strong>recrawled 404 URLs 49.6% more often<\/strong> than 410 URLs (95% confidence level). This suggests Google trusts a 410 as &#8220;permanently removed&#8221; sooner. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.rebootonline.com\/blog\/404-vs-410-the-technical-seo-experiment\/\" target=\"_blank\" rel=\"noopener\">Reboot data<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">The difference comes from Google&#8217;s habit of double-checking. Even after getting a 404, Google tends to come back to confirm the page is &#8220;really gone,&#8221; whereas it takes a 410 as a permanent removal signal right away. Google&#8217;s John Mueller has also explained that a 410 tends to drop out of the index a little faster than a 404, but usually only by a few days. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/google-404-status\/254429\/\" target=\"_blank\" rel=\"noopener\">SEJ report<\/a> The practical conclusion is simple: if a page already returns a 404, Google will remove it from the index on its own, so there is little benefit in switching to 410. It&#8217;s enough to pin down with a 410 only the pages that &#8220;must never be indexed again,&#8221; such as spam URLs created by a hack.<\/p>\n\n<h2 class=\"wp-block-heading\">Tips for Checking and Fixing<\/h2>\n\n<ul class=\"wp-block-list\"><li>Click the example URLs in the report and first check <strong>whether it&#8217;s actually fine for those addresses to be gone<\/strong>. Most can simply be left alone.<\/li><li>If an important page shows up as a 404, restore it or 301 it to a relevant page, then recheck its status with the URL Inspection tool.<\/li><li>Check that <strong>no dead URLs remain<\/strong> in your sitemap or internal links. It&#8217;s best not to include 404 URLs in your sitemap.<\/li><li>If the number of 404s suddenly spikes, it may signal a deployment accident or mass deletion, so look into the cause.<\/li><li>Prepare a <strong>custom 404 page<\/strong> that gently guides users who hit a broken link to the home page or search, and you can reduce drop-offs. You can see well-made examples in <a href=\"\/en\/studio-jt-404-error-page-collection\/\">STUDIO-JT&#8217;s collection of 404 error page designs<\/a>.<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">For related concepts, see <a href=\"\/en\/seo-glossary\/soft-404\/\">soft 404<\/a>, which looks like a 404 but returns 200 so Google classifies it separately; <a href=\"\/en\/seo-glossary\/301-redirect\/\">301 redirect<\/a>, the right way to handle moved pages; and the <a href=\"\/en\/seo-glossary\/page-indexing-report\/\">Page indexing report<\/a>, where this status appears.<\/p>\n\n<h2 class=\"wp-block-heading\">References<\/h2>\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">Page indexing report &#8211; Google Search Console Help<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/blog\/2011\/05\/do-404s-hurt-my-site\" target=\"_blank\" rel=\"noopener\">Do 404 errors hurt my site? &#8211; Google Search Central Blog<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/http-network-errors\" target=\"_blank\" rel=\"noopener\">HTTP status codes and network errors &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Reference\/Status\/404\" target=\"_blank\" rel=\"noopener\">404 Not Found &#8211; MDN Web Docs<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/link-rot-study\/\" target=\"_blank\" rel=\"noopener\">At Least 66.5% of Links to Sites in the Last 9 Years Are Dead &#8211; Ahrefs (2022)<\/a><\/li><li><a href=\"https:\/\/www.rebootonline.com\/blog\/404-vs-410-the-technical-seo-experiment\/\" target=\"_blank\" rel=\"noopener\">404 vs 410: The Technical SEO Experiment &#8211; Reboot Online<\/a><\/li><li><a href=\"https:\/\/www.searchenginejournal.com\/google-404-status\/254429\/\" target=\"_blank\" rel=\"noopener\">Google Offers Advice on 404 and 410 Status Codes &#8211; Search Engine Journal<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>&#8220;Not found (404)&#8221; is the status where Googlebot requested a URL, the server returned a 404 (page not found) response, and the page was left out of the index. Google&#8217;s official documentation describes 404s as &#8220;a perfectly normal part of the web&#8221; and says you don&#8217;t need to fix every one. However, if an important page disappeared by mistake or its content moved elsewhere, you need to act, for example with a 301 redirect.<\/p>\n","protected":false},"template":"","glossary_categories":[17],"class_list":["post-256","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\/256","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":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/256\/revisions"}],"predecessor-version":[{"id":2341,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/256\/revisions\/2341"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=256"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=256"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}