Server error (5xx) in Search Console: causes and fixes

Server error (5xx) means that when Googlebot requested the URL, your server answered with a 500-level error, such as 500, 502, 503 or 504, so Google could not read the page. This is a real problem to fix: repeated server errors make Google crawl your site less, and pages that keep failing are eventually dropped from the index.

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

Google’s documentation on HTTP errors says 5xx and 429 responses prompt Google’s crawlers to temporarily slow down, and that Google’s indexing pipeline removes URLs that persistently return a server error. Once the server responds normally again, Google gradually increases crawling.

Is it a problem?

Yes, though how urgent depends on the pattern. A handful of URLs from one bad afternoon will usually clear on their own once Google recrawls. A steady or growing list means Googlebot keeps hitting failures, which slows discovery of new pages across your whole site, not only the failing ones.

What causes it, most likely first?

1. Overloaded or underpowered hosting: shared hosting limits, too few workers, memory limits during traffic or crawl peaks.
2. Application errors on specific pages: a plugin or code bug that crashes certain templates or URL patterns.
3. Slow database queries that time out (often a 504 from a proxy or CDN).
4. Firewall or bot protection that returns 5xx to crawlers it doesn’t recognize.
5. Outages and deploys: downtime, a failed release, or maintenance without a proper 503.

How do I fix server errors?

1. 1. Check whether the error still happens

   Run Test live URL in URL Inspection on a few example URLs. If they load fine now, the error was temporary, such as an outage, a deploy or a traffic spike, and you mainly need to stop it recurring.

2. 2. Look at Crawl stats for the pattern

   Open Settings, then Crawl stats, and check the By response breakdown and host status. A spike on certain days points to outages; a steady share of 5xx points to a page or server problem.

3. 3. Find the error in your server logs

   Search your server or hosting logs for requests from Googlebot to the affected URLs at the times shown. The application error log usually names the cause: a crashed script, a database timeout, a memory limit.

4. 4. Check firewalls, CDNs and rate limits

   Make sure your firewall, bot protection or CDN is not answering verified Googlebot with 5xx errors or challenges. Verify Googlebot by reverse DNS or Google's published IP ranges before allowlisting.

5. 5. Fix capacity and slow pages

   Add caching for heavy pages, fix slow database queries, raise PHP or worker limits, or upgrade hosting if the server falls over under normal crawling plus visitor traffic.

6. 6. Validate the fix

   Once the URLs load reliably, click Validate fix on the Server error (5xx) reason in the Page indexing report.

How do I check that the fix worked?

Test live URL should return the page with no fetch error. Over the following days, the 5xx share in Crawl stats should fall back toward zero. Validation on the reason moves to Looking good and Passed as Google recrawls the examples successfully.

How long does it take?

Google rechecks failing URLs and ramps crawling back up gradually after errors stop, so recovery is usually a matter of days to a couple of weeks. Pages that had been dropped need to be crawled and indexed again; request indexing for the most important ones.

SEO Rank Fixer’s Site Audit also crawls your site and lists pages that return server errors, with the pages that get Search Console clicks first. Related: Discovered - currently not indexed, which slow servers often cause.