A 5xx error means your server failed when Googlebot asked for a page. If it keeps happening, Google slows crawling and can drop the pages. Here is how to find the cause and fix it.
This guide explains the Server error (5xx) status in the Page indexing report and how to fix it. It is part of my Search Console errors hub.
“Server error (5xx)” means Googlebot requested a URL and your server returned a 500-range error, timed out or was unavailable. Google temporarily slows crawling, ignores the content and, if the errors persist, removes those URLs from the index. Fix it by finding the error in your server logs, resolving the cause (crashes, overload, firewall blocks, timeouts), then clicking Validate fix in Search Console.
| Code | Meaning | Common cause |
|---|---|---|
| 500 | Internal server error | PHP fatal error, plugin or theme bug, broken .htaccess |
| 502 | Bad gateway | Upstream server or PHP process crashed |
| 503 | Service unavailable | Maintenance mode, overload, rate limiting |
| 504 | Gateway timeout | Slow database queries, heavy pages, low hosting resources |
For planned maintenance, a short 503 is fine and tells Google to come back later. Long or frequent outages are the problem.
A WordPress site shows 5xx errors every night at 2am. The hosting log shows the server hitting its process limit while a backup plugin runs. Moving the backup to off-peak hours on the host’s own system and adding page caching stops the errors.
I audit and fix speed, Core Web Vitals, indexing, redirects and schema, and send you a clear report of every change.
Googlebot asked for the page and your server returned a 500-range error, timed out or was unavailable.
Short, rare errors are usually fine. Persistent errors slow crawling and can get pages dropped from the index.
A short 503 during maintenance is the correct signal. Long or frequent 503s can lead to pages being dropped.
The error may be intermittent, happen under load, or only affect Googlebot because of a firewall or bot protection.
Crawling increases gradually once pages return 200. Validation in Search Console can take days to weeks.
Facts checked against these official pages on 10 October 2026. Read my editorial policy.
Not every 404 in Search Console is a problem. Some pages should be gone. Here is how to tell which 404s need a redirect, which need a fix, and which you can safely ignore.
Read article
What the Couldn't fetch status means, the causes Google lists, and nine checks that get your sitemap read, plus how to confirm it worked.
Read article
How to spot pages competing for the same search, decide what to do with each one, and fix it without losing traffic.
Read articleSend your website and I will reply with a free audit.