(Search Console)

Server error (5xx)

What does “Server error (5xx)” mean?

“Server error (5xx)” is a status shown in Search Console’s Page Indexing report as a “Why pages aren’t indexed” reason. Google’s official help defines it as “Your server returned a 500-level error when the page was requested.” GSC Help Center Googlebot went to fetch the page but couldn’t get the content, not because the address was wrong but because of something on the server’s side.

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’t wrong and the package (content) didn’t disappear; the warehouse just couldn’t open its doors at that moment. All 500-level responses, such as 500, 502, 503 and 504, fall into this category.

Is it a problem or not?

The deciding question is “Is it still an error now?” 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 URL Inspection tool to check whether the page responds normally right now.

That said, Google doesn’t take this error lightly. The Crawl Stats report help says of server errors, “These errors trigger availability warnings, so you should fix them if possible.” GSC Help Center If it keeps showing up repeatedly rather than as a one-off blip, it needs fixing.

What happens if you ignore it? The answer from Google’s official documentation

Google Search Central’s “How HTTP status codes affect Google’s crawlers” document summarizes Googlebot’s response to 5xx errors in three ways. Google (official)

  • Crawl rate – “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.”
  • Content processing – “Any content Google receives from URLs that return a 5xx status code is ignored.”
  • Indexing – “URLs that were already indexed are preserved in the index, but eventually dropped.”

The “Reduce the Google crawl rate” 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 “your site’s entire hostname,” and that “if Googlebot finds these status codes on the same URL for multiple days, the URL may be dropped from Google’s index.” Google (official) When the crawl rate drops, the site’s overall crawl budget shrinks, so it’s not a problem that stays limited to a few erroring pages.

A few days is the tipping point: John Mueller’s explanation

The point that the official documentation describes only as “eventually dropped” 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 John Mueller’s remarks (2021). In practice, the official documentation’s vague “eventually” translates into a timeline: “one day is fine; a few days or more is risky.”

Diagnosing the cause and fixing it

The Page Indexing report help recommends checking the following in response to server errors. GSC Help Center

  • Review the site’s host status assessment in the Crawl Stats report.
  • Reduce excessive server load from dynamic page requests.
  • Make sure your hosting server isn’t going down or getting overloaded.
  • Check that firewall or security settings aren’t accidentally blocking Googlebot.

Host status in the Crawl Stats report is shown in three levels, like a traffic light. According to the help, green means “Google hasn’t encountered any significant crawl availability issues on your site in the past 90 days,” and red means “Your site had at least one significant availability issue in the last week.” GSC Help Center If it’s red, server errors are likely ongoing, so check the server logs together with your hosting company or developer.

For planned maintenance: 503 and Retry-After

If you need to take your site down briefly for server maintenance or a deployment, Google officially recommends returning a 503 status code. Its “Pause or disable a website temporarily” document says, “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,” and adds, “Use the retry-after HTTP header to specify your best estimate of a date or duration.” Google (official)

HTTP/1.1 503 Service Unavailable
Retry-After: 3600

A 503 is a sign telling Googlebot, “I can’t give it to you right now, but I’ll be open again soon.” However, the same document warns that disabling the entire site is “an extreme measure that should only be taken for a very short period of time (a few days at most),” and that going longer “can have significant effects on your website in Google Search, even if implemented properly.” Google (official) This lines up with John Mueller’s “a few days” explanation above: a 503 is a stopgap measured in days, not a solution for long-term maintenance.

References

Jul.2026By Studio JT

More from Search Console

Like this term?
Give it a like!

(103)