Server error (5xx): why Googlebot could not load your page

Last updated: 2026-10-30

In short

Server error (5xx) means your server returned a 500-level error when Googlebot requested the page. Google slows crawling when it sees these errors and eventually drops URLs that keep failing. Check host status in Crawl Stats, reproduce the error, then fix capacity, timeouts or rules that block Googlebot.

Exact label in Search Console: Server error (5xx)

What it means

Google's Page indexing help says your server returned a 500-level error when the page was requested. Its troubleshooting section adds that a server error means Googlebot could not access the URL, the request timed out or the site was busy, so Googlebot had to abandon the request. Server errors can be transient, so a live test may succeed even though Google's crawl failed.

Google's crawling documentation explains the effects: 5xx and 429 responses make Google's crawlers temporarily slow down, already indexed URLs are kept for a while but eventually dropped, and URLs that persistently return a server error are removed from the index. Once the server returns 2xx again, Google gradually increases the crawl rate.

Is it a problem?

Yes, if it affects pages you care about or keeps coming back. A few one-off errors during a deploy may clear on their own. A spike, a whole section affected or errors that persist across crawls point at capacity, configuration or a security layer blocking Googlebot, and they also reduce how much Google is willing to crawl.

Common causes

Overloaded or underpowered hosting

The server cannot keep up with visitors plus crawling and returns 500, 502 or 503 errors, or times out.

Slow dynamic pages

Google's help says dynamic pages, for example with long parameter lists, can take too long to respond and time out.

Firewalls and bot protection

Google says DoS protection and firewalls can block Googlebot because it makes more requests than a typical visitor.

Application errors

Bugs, failed deploys, database outages or exhausted memory on specific templates.

DNS or connectivity problems

Failed DNS lookups or dropped connections, which the Crawl Stats report shows as host availability issues.

A 503 or 429 left on too long

Google says returning these for more than about two days can lead it to drop those URLs from the index.

How to fix it

  1. Check host status in Crawl Stats. Open Settings, then Crawl stats, and look at host status for robots.txt fetching, DNS resolution and server connectivity, plus the breakdown by response code and average response time.
  2. Reproduce and read your logs. Run Test live URL on example URLs and check server logs for the same URLs and times. Look for errors returned only to Googlebot's requests.
  3. Fix capacity and slow pages. Add server resources or caching, speed up slow queries and keep parameter lists short. Google suggests increasing serving resources and checking whether crawl requests rise in the same period.
  4. Let verified Googlebot through. Make sure firewalls, WAFs and bot managers allow Googlebot. Verify requests by reverse DNS or Google's published IP ranges rather than trusting the user agent string.
  5. Use 503 or 429 only for short outages. During maintenance or overload, a temporary 503 or 429 tells Google to slow down. Stop returning them as soon as the problem is fixed.
  6. Validate after the fix. When the errors stop, click Validate fix so Google rechecks the affected URLs.

Check it with GSC Magic

gsc_inspect_urls_batch shows the page fetch state Google recorded for each URL, so your assistant can tell server errors apart from 404s or redirect problems across hundreds of URLs, and gsc_query_analytics by date shows whether clicks fell when the errors started. If you connect Bing Webmaster Tools too, bing_crawl_issues lists URLs where Bingbot hit 5xx errors, a second opinion on whether the problem is your server or specific to Googlebot. Pro plans can also alert you by e-mail when a page with clicks loses all impressions; see SEO alerts for traffic drops and indexing.

gsc_inspect_urls_batchgsc_query_analyticsbing_crawl_issuesgsc_inspect_url

Prompts to copy

Inspect these URLs and list every one whose page fetch state is a server error, with the last crawl time, grouped by directory.

Show daily clicks and impressions for the last 28 days and tell me whether they dropped around the dates when the server errors started.

Pull Bing crawl issues for my site and tell me whether Bing also sees 5xx errors on the URLs Google reports as server errors.

Guides on the blog

Redirect error

Redirect error means Google tried to follow a redirect from the URL and failed. Google lists four causes: a chain that was too long, a redirect loop, a URL that grew past the maximum length, and a bad or empty URL in the chain. Trace the redirect hop by hop and point the URL straight at a working final page.

 Discovered - currently not indexed

Discovered - currently not indexed means Google found the URL, through a link or a sitemap, but has not crawled it yet. Google says it typically postponed the crawl because crawling was expected to overload the site. Fix it by cutting low-value URLs, improving server response and linking to the pages that matter.

 Blocked due to access forbidden (403)

This status means your server returned 403 Forbidden to Googlebot. Google points out that Googlebot never sends credentials, so a 403 to Googlebot is usually returned incorrectly. If the page should be in Google, find the firewall, CDN or server rule that blocks it and allow verified Googlebot.

 Soft 404

A soft 404 is a URL that returns a 200 (success) status code but looks to Google like a not-found, empty or error page. Google excludes these pages from Search. Return a real 404 or 410 for missing pages, 301 redirect moved ones to a real replacement, and fix rendering for real pages that Google misread.

Frequently asked questions

Will 5xx errors remove my pages from Google?

Persistent ones can. Google says already indexed URLs are preserved for a while but eventually dropped, and URLs that persistently return a server error are removed from the index.

The live test works, but the report shows a 5xx. Why?

Google notes that server errors can be transient, so the live test may succeed when the earlier crawl failed. Check Crawl Stats and your server logs for the time of the failed crawl.

Does Google treat 429 as a server error?

Yes. Google's crawling documentation says its crawlers treat 429 as a signal that the server is overloaded and consider it a server error.

Should I return 503 during maintenance?

For short periods, yes. Google suggests returning 503 or 429 temporarily when the server is overloaded, but warns that doing so for more than about two days can cause it to drop those URLs.

Sources