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

Updated October 21, 2026 · Check Before Publish

“Server error (5xx)” means your server answered Googlebot with a 500-level error, or timed out, so the page could not be fetched. Google ignores the content of a 5xx response and slows its crawling, and URLs that keep failing drop out of the index. Check the host status in Crawl Stats, fix the cause, then validate.

The short version

• Google's wording: “A server error means that Googlebot couldn't access your URL, the request timed out, or your site was busy.”
• “Any content Google receives from URLs that return a 5xx status code is ignored.” Already indexed URLs “are preserved in the index, but eventually dropped”, and URLs that “persistently return a server error” are removed.
• Google gives no number of days for “eventually” or “persistently”. Its page on slowing crawling says that if Googlebot sees these codes on the same URL “for multiple days, the URL may be dropped”.
• A 429 counts too: Google treats it “as a signal that the server is overloaded, and it's considered a server error”.
• The live test can pass when the crawl failed: “server errors can be transient, so your live test might succeed when Google's crawl failed due to a server error.”

What the codes mean

Find the cause

1. Open the Crawl Stats report. Google says to check the host status verdict to see whether it is reporting availability problems, and to look at your recent host availability for a persistent or large-scale issue.
2. Look in your server and CDN logs for 5xx responses at the times Googlebot crawled. Google's list of fixes includes reducing excessive page loading for dynamic requests, because slow pages can time out, and making sure the host is “not down, overloaded, or misconfigured”.
3. If you use Cloudflare, read which of its error codes you have. Its docs say that for most 5xx errors the first step is to “contact your hosting provider or site administrator”, and describe 502 and 504 as Cloudflare being unable to establish contact with your origin server. They do not say whether Googlebot sees Cloudflare's error pages.
4. Check you are not blocking Google by accident (Google lists this too), then run URL Inspection to try to reproduce the error.

Planned downtime and emergencies

Google says to answer with a 503 and an informational page, and to add a Retry-After header with a date or duration. It warns against keeping this up: it does not recommend returning 500, 503 or 429 for longer than 1-2 days, because the URL may be dropped from the index. A different Google page says not to do it for more than “two or three days”, so treat 1-2 days as the safer limit. Do not return 403, 404 or 410 to hide a site: “This will remove the website's URLs from Google Search.” And don't put the 503 on your robots.txt file.

See what the server returns to us

Paste the URL. The checker reports the status the page answers to our server. It cannot see your logs or what Googlebot received.

What we tested

On 2026-10-19 we ran the live Website Pre-Publish Checker on a test page that always answers a chosen 5xx code. The test page is a preview that search engines are told not to index, not part of this site. The 503 test page also sent Retry-After: 120.

So the checker treats 500, 502 and 504 as something to fix and 503 and 429 as something to review, which fits their usual meaning of “temporary”. What it cannot do is tell an error that happens once an hour from one that happens every time: it asks the server once.

After the fix

Fix the cause, then use Validate fix on the issue. Google says validation “typically takes up to about two weeks, but in some cases can take much longer”, and that it reduces its crawl rate for a host with many errors and raises it again automatically once they stop.

What this can't tell you

A 200 from us now does not mean the failure Google saw is fixed: server errors can be intermittent, and Crawl Stats and your logs are where you see how often they happened.

Related: Blocked due to access forbidden (403), Not found (404) and why a page isn't showing up on Google.