{"id":255,"date":"2026-07-11T21:55:03","date_gmt":"2026-07-11T12:55:03","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/server-error-5xx\/"},"modified":"2026-11-15T18:46:51","modified_gmt":"2026-11-15T09:46:51","slug":"server-error-5xx","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/server-error-5xx\/","title":{"rendered":"Server error (5xx)"},"content":{"rendered":"<h2 class=\"wp-block-heading\">What does &#8220;Server error (5xx)&#8221; mean?<\/h2>\n<p class=\"wp-block-paragraph\">&#8220;Server error (5xx)&#8221; is a status shown in Search Console&#8217;s <a href=\"\/en\/seo-glossary\/page-indexing-report\/\">Page Indexing report<\/a> as a &#8220;Why pages aren&#8217;t indexed&#8221; reason. Google&#8217;s official help defines it as &#8220;Your server returned a 500-level error when the page was 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> Googlebot went to fetch the page but couldn&#8217;t get the content, not because the address was wrong but because of something on the server&#8217;s side.<\/p>\n<p class=\"wp-block-paragraph\">Think of a courier who goes all the way to the warehouse to pick up a package, only to find the shutters down. The address (URL) wasn&#8217;t wrong and the package (content) didn&#8217;t disappear; the warehouse just couldn&#8217;t open its doors at that moment. All 500-level responses, such as 500, 502, 503 and 504, fall into this category.<\/p>\n<h2 class=\"wp-block-heading\">Is it a problem or not?<\/h2>\n<p class=\"wp-block-paragraph\">The deciding question is &#8220;Is it still an error now?&#8221; If it happened briefly because of a server restart or a momentary overload and has already recovered, it may actually be resolved even if traces remain in the report. The first step is to use the live test in the <a href=\"\/en\/seo-glossary\/url-inspection-tool\/\">URL Inspection tool<\/a> to check whether the page responds normally right now.<\/p>\n<p class=\"wp-block-paragraph\">That said, Google doesn&#8217;t take this error lightly. The Crawl Stats report help says of server errors, &#8220;These errors trigger availability warnings, so you should fix them if possible.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9679690?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> If it keeps showing up repeatedly rather than as a one-off blip, it needs fixing.<\/p>\n<h2 class=\"wp-block-heading\">What happens if you ignore it? The answer from Google&#8217;s official documentation<\/h2>\n<p class=\"wp-block-paragraph\">Google Search Central&#8217;s &#8220;How HTTP status codes affect Google&#8217;s crawlers&#8221; document summarizes Googlebot&#8217;s response to 5xx errors in three ways. <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><\/p>\n<ul class=\"wp-block-list\"><li>Crawl rate &#8211; &#8220;Google decreases the crawl rate for the site. The decrease in crawl rate is proportionate to the number of individual URLs that are returning a server error.&#8221;<\/li><li>Content processing &#8211; &#8220;Any content Google receives from URLs that return a 5xx status code is ignored.&#8221;<\/li><li>Indexing &#8211; &#8220;URLs that were already indexed are preserved in the index, but eventually dropped.&#8221;<\/li><\/ul>\n<p class=\"wp-block-paragraph\">The &#8220;Reduce the Google crawl rate&#8221; document is more specific. It warns that when 500, 503 or 429 errors persist, the crawl rate drop affects not just the erroring URLs but &#8220;your site&#8217;s entire hostname,&#8221; and that &#8220;if Googlebot finds these status codes on the same URL for multiple days, the URL may be dropped from Google&#8217;s index.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/reduce-crawl-rate?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> When the crawl rate drops, the site&#8217;s overall <a href=\"\/en\/seo-glossary\/crawl-budget\/\">crawl budget<\/a> shrinks, so it&#8217;s not a problem that stays limited to a few erroring pages.<\/p>\n<h2 class=\"wp-block-heading\">A few days is the tipping point: John Mueller&#8217;s explanation<\/h2>\n<p class=\"wp-block-paragraph\">The point that the official documentation describes only as &#8220;eventually dropped&#8221; was explained more clearly by Google Search Advocate John Mueller in office hours. To summarize, for a temporary outage of about a day, a 503 response code is a good signal to come back soon, but if it lasts several days, Google treats it as permanent and removes the page from the index <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.searchenginejournal.com\/google-will-deindex-pages-if-site-is-down-for-several-days\/429903\/\" target=\"_blank\" rel=\"noopener\">John Mueller&#8217;s remarks<\/a> (2021). In practice, the official documentation&#8217;s vague &#8220;eventually&#8221; translates into a timeline: &#8220;one day is fine; a few days or more is risky.&#8221;<\/p>\n<h2 class=\"wp-block-heading\">Diagnosing the cause and fixing it<\/h2>\n<p class=\"wp-block-paragraph\">The Page Indexing report help recommends checking the following in response to server errors. <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<ul class=\"wp-block-list\"><li>Review the site&#8217;s host status assessment in the Crawl Stats report.<\/li><li>Reduce excessive server load from dynamic page requests.<\/li><li>Make sure your hosting server isn&#8217;t going down or getting overloaded.<\/li><li>Check that firewall or security settings aren&#8217;t accidentally blocking Googlebot.<\/li><\/ul>\n<p class=\"wp-block-paragraph\">Host status in the Crawl Stats report is shown in three levels, like a traffic light. According to the help, green means &#8220;Google hasn&#8217;t encountered any significant crawl availability issues on your site in the past 90 days,&#8221; and red means &#8220;Your site had at least one significant availability issue in the last week.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9679690?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> If it&#8217;s red, server errors are likely ongoing, so check the server logs together with your hosting company or developer.<\/p>\n<h2 class=\"wp-block-heading\">For planned maintenance: 503 and Retry-After<\/h2>\n<p class=\"wp-block-paragraph\">If you need to take your site down briefly for server maintenance or a deployment, Google officially recommends returning a 503 status code. Its &#8220;Pause or disable a website temporarily&#8221; document says, &#8220;If you need to urgently disable the site for 1-2 days, then return an informational error page with a 503 HTTP response status code instead of all of the content,&#8221; and adds, &#8220;Use the retry-after HTTP header to specify your best estimate of a date or duration.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/pause-online-business?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<pre class=\"wp-block-code\"><code>HTTP\/1.1 503 Service Unavailable\nRetry-After: 3600<\/code><\/pre>\n<p class=\"wp-block-paragraph\">A 503 is a sign telling Googlebot, &#8220;I can&#8217;t give it to you right now, but I&#8217;ll be open again soon.&#8221; However, the same document warns that disabling the entire site is &#8220;an extreme measure that should only be taken for a very short period of time (a few days at most),&#8221; and that going longer &#8220;can have significant effects on your website in Google Search, even if implemented properly.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/pause-online-business?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> This lines up with John Mueller&#8217;s &#8220;a few days&#8221; explanation above: a 503 is a stopgap measured in days, not a solution for long-term maintenance.<\/p>\n<h2 class=\"wp-block-heading\">References<\/h2>\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 Center<\/a><\/li><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 &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/reduce-crawl-rate?hl=ko\" target=\"_blank\" rel=\"noopener\">Reduce the Google crawl rate &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/pause-online-business?hl=ko\" target=\"_blank\" rel=\"noopener\">Pause or disable a website temporarily &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/9679690?hl=ko\" target=\"_blank\" rel=\"noopener\">Crawl Stats report &#8211; Google Search Console Help Center<\/a><\/li><li><a href=\"https:\/\/www.searchenginejournal.com\/google-will-deindex-pages-if-site-is-down-for-several-days\/429903\/\" target=\"_blank\" rel=\"noopener\">Summary of John Mueller&#8217;s remarks on 503s and deindexing &#8211; Search Engine Journal (2021)<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>&#8220;Server error (5xx)&#8221; means the page couldn&#8217;t be indexed because the server returned a 500-level error when Googlebot requested it. A temporary outage may resolve itself on recrawl, but Google&#8217;s official documentation says that if errors persist for several days, the crawl rate drops and even URLs already indexed may eventually be removed. For planned maintenance, Google officially recommends using a 503 status code and a Retry-After header.<\/p>\n","protected":false},"template":"","glossary_categories":[17],"class_list":["post-255","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\/255","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\/255\/revisions"}],"predecessor-version":[{"id":2340,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/255\/revisions\/2340"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=255"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}