Page indexing report · Search Console
Server error (5xx)
When Google tried to crawl the URL, your server “returned a 500-level error”.1 A short blip does little harm, but errors that last make Google crawl less and eventually drop pages. Here’s how to tell which you have and fix it.
Check the URL first
The checker shows whether the URL returns an error right now, from outside your server. Many 5xx errors are intermittent or only hit Googlebot, so a pass here doesn’t rule them out.
In 30 seconds
- Many 5xx errors make Google slow crawling across the whole hostname, not just the failing URLs.4
- Indexed pages survive short outages but are “eventually dropped” if errors persist.2
- Use 503 for planned downtime, and no longer than 1–2 days.4
- If robots.txt itself returns 5xx, Google stops crawling the site for 12 hours.6
What it means
Google requested the URL and got a 500-level response: 500, 502, 503, 504 or similar. It ignores whatever content came with the error.2 The status is set at the crawl stage.
Discover
Google learns that a URL exists, mostly from links on pages it already knows and from XML sitemaps.
What goes wrong: Nothing links to the page and it isn’t in a sitemap, so Google never hears about it.
Report statuses at this stage
- URL is unknown to Google (shown in URL Inspection, not in the report)
Crawl
Googlebot checks robots.txt, then requests the URL. It spaces requests out so it doesn’t overload the server.
What goes wrong: The URL is blocked, returns an error, or the server is slow, so Google backs off and crawls less.
Report statuses at this stage
Render
Google runs the page’s JavaScript in a recent version of Chrome to see the finished page.
What goes wrong: Content only appears after a click or scroll, or the scripts fail, so the rendered page is nearly empty.
Report statuses at this stage
- No status of its own. Problems show up at the next stage as thin pages or soft 404s.
Index
Google decides which version of the page to keep and whether it is worth storing at all.
- Group duplicates. Pages with the same or very similar content go into one group.
- Pick a canonical. One URL represents each group. Canonical tags, redirects and sitemaps are hints, not commands.
- Select for the index. Google decides whether the canonical page is worth keeping. Google says this largely depends on quality.
What goes wrong: The page duplicates another, is marked noindex, or Google decides it adds too little to keep.
Report statuses at this stage
Serve
Indexed pages can appear in search results. Being indexed is not the same as ranking; an indexed page can still get no clicks.
What goes wrong: The page is indexed but doesn’t match what people search for, or other pages answer it better.
Report statuses at this stage
Google reads server errors as a sign it may be overloading your server. It slows crawling, in proportion to how many URLs fail. Already indexed URLs are kept at first but eventually dropped if the errors continue. When the server recovers, Google gradually increases the crawl rate again.2 Server errors also lower the crawl capacity Google allows your site.5
Is it a problem?
Usually fine
- A single blip that has already stopped
- A short planned outage that returned 503
- A handful of URLs, once, with a healthy Crawl Stats report
Worth fixing
- Errors that keep coming back
- Many URLs, or a rising count
- A Host status warning in Crawl Stats
- robots.txt returning errors or timing out
- Important pages: home, categories, products
John Mueller has said there’s no hard threshold, but an error rate above about one percent suggests something is broken, and Google would start slowing down.8
Find the cause
Answer a few questions to narrow it down. Each cause is explained below.
The server is down or overloaded
Google’s own checklist starts here: make sure the server “is not down, overloaded, or misconfigured”, and check host availability in the Crawl Stats report.1 Crawl Stats flags a problem when a category, such as server connectivity, fails on more than a small share of requests in a day.3
Pages are too slow to generate
Google lists reducing “excessive page loading for dynamic page requests”.1 Slow database queries and uncached pages time out at a proxy as 502 or 504, or hit the server’s own limits.
An application error
A bug, a broken plugin or a failed database connection returns 500 on the templates that use it. The error log for one failing URL usually names the cause.
A firewall, CDN or rate limiter
Google’s last item: check that you are “not inadvertently blocking Google”.1 Bot protection and rate limits can answer crawlers with 429 or 5xx while visitors see the page. Google counts 429 as a server error.2 Before allowing a crawler, confirm it’s really Google with a reverse DNS lookup that resolves back to the same IP address, or against Google’s published IP ranges.7
Planned maintenance that ran long
A 503 is the right signal for a short outage. Google warns that serving it for more than 1–2 days risks the URLs being dropped.4 In 2014, Mueller made the user’s view plain: after a couple of weeks down, most people assume a site is gone, 503 or not.10
The codes and how Google reacts
Pick a code to see what it usually means and what Google does with it.
500 Internal Server Error
The server hit an error it didn’t handle: usually a code, plugin or database failure.
Google lowers the crawl rate in proportion to the number of URLs returning errors, and removes URLs that keep returning a server error.2
502 Bad Gateway
A proxy, load balancer or CDN in front of your app got an invalid response from it. Often the app crashed or restarted.
Google treats it like any other 5xx: slower crawling, then removal if it persists.2
503 Service Unavailable
The right code for planned downtime. You can add a Retry-After header to say when crawlers can come back.4
HTTP/1.1 503 Service Unavailable
Retry-After: 3600It only works for short outages. Google says not to serve errors for longer than 1–2 days: after several days on the same URL, the page may be dropped from the index.4
504 Gateway Timeout
A proxy or CDN gave up waiting for your app. The page is too slow to generate, or the app is stuck. Google names “excessive page loading for dynamic page requests” as a cause to fix.1
429 Too Many Requests
Not a 500-level code, but Google treats it as a server error and a sign the server is overloaded.2 Rate limiters and bot protection often send it.
Like 503, it’s acceptable for slowing Googlebot for a few hours or a day or two, not longer.4
Cloudflare 520–526
Cloudflare returns its own 5xx codes when it can’t get a good response from your server: 520 unknown error, 521 server down, 522 connection timed out, 523 origin unreachable, 524 timeout, 525 SSL handshake failed, 526 invalid SSL certificate.11
To Google these are server errors like any other. The fix is at your origin server.
robots.txt returns 5xx
The most damaging case. If Google can’t fetch robots.txt because of a server error:6
- For the first 12 hours, Google stops crawling the site and keeps retrying.
- For the next 30 days, it uses the last good copy and keeps retrying.
- Timeouts, DNS failures and dropped connections count as server errors too.
Crawl Stats shows robots.txt fetch failures under Host status.3
How to fix it
- Check whether robots.txt loads. If it doesn’t, fix that first.
- Open Crawl Stats and look at Host status and the server error share over time.3
- Test a few affected URLs now, and match their errors in your server logs.
- Fix the cause: capacity, slow pages, the failing code, or firewall rules for verified Googlebot.
- For planned downtime, return 503 with a Retry-After header, and keep it short.4
- Click Validate fix once the URLs load reliably.
Myths
Some top-ranking guides say this. Google’s documentation describes something different.
| Often said | What’s actually true |
|---|---|
| Server errors directly lower your rankings | Google’s documented response is slower crawling and, if errors persist, removal from the index.2 |
How long it takes
- 1–2 daysis the longest Google says to serve 500, 503 or 429 before URLs risk being dropped.4
- 12 hoursof no crawling when robots.txt returns a server error, then up to 30 days on the cached copy.6
- No defined timefor crawl rate to recover; John Mueller says it returns to normal automatically.9
- Up to about 2 weeksfor Search Console to validate a fix, sometimes much longer.1
Questions
Do server errors hurt my rankings?
Not directly. Google’s documented reaction is to slow crawling and, if errors persist, drop the affected URLs from the index. A page that is dropped loses its rankings, so long-running errors do cost traffic. Short blips usually don’t.
How long can my site be down before Google drops pages?
Google says not to serve 500, 503 or 429 for longer than one to two days, because URLs that return errors for multiple days may be dropped. Google gives no exact cut-off.
Should I use 503 for maintenance?
Yes, for short maintenance. A 503 tells Google the outage is temporary, and a Retry-After header says when to come back. Don’t leave it in place for days.
The page loads fine for me. Why does Google see a 5xx?
The error may have been brief, may happen only under load, or may come from a firewall or bot protection that treats Googlebot differently. Check the Crawl Stats report and your server logs for Googlebot requests to that URL.
How do I fix Server error (5xx) on WordPress?
Check the PHP error log for the failing URL, then switch off plugins one at a time on a staging copy to find the one that fails. Also check your hosting plan’s limits, since many WordPress 5xx errors are the server running out of resources.
Why did validation fail?
Some of the URLs still returned a server error when Google rechecked them. Intermittent errors often cause this. Check that the URLs load reliably, including under load, before validating again.
Sources
- Google, “Page indexing report”, Search Console Help
- Google, “How HTTP status codes affect Google’s crawlers”, Search Central, updated February 2026
- Google, “Crawl Stats report”, Search Console Help
- Google, “Reduce the Google crawl rate”, Google Crawling Infrastructure, updated October 2026
- Google, “Crawl budget management for large sites”, Search Central, updated July 2026
- Google, “How Google interprets the robots.txt specification”, Search Central, updated August 2026
- Google, “Verifying Googlebot and other Google crawlers”, Google Crawling Infrastructure, updated March 2026
- John Mueller (Google), video Q&A, reported by Search Engine Journal, August 2021
- John Mueller (Google), Reddit r/TechSEO, August 2025, reported by Search Engine Journal
- John Mueller (Google), Twitter, September 2014, reported by Search Engine Roundtable
- Cloudflare, “Cloudflare 5xx errors”, Cloudflare Docs, updated June 2026