Lorixen.
EN

Server errors (5xx) in Search Console: finding the cause

Short answer: "Server error (5xx)" in Search Console means Googlebot asked for a page and your server answered with an error instead of the page. A few transient errors are normal; repeated or widespread ones make Google slow its crawling and, if they persist, can lead to pages dropping out of the index. Work out whether the errors are constant or intermittent, then check hosting capacity, recent changes, plugins, firewalls and parameter-heavy URLs, in roughly that order.

A spike of 5xx errors in the Page indexing report tends to cause alarm. Sometimes it's a one-off outage that resolved itself; sometimes it's an overloaded server quietly turning Googlebot away every afternoon. Here's how to tell which, and what to fix.

What Google does with server errors

Google's documentation on HTTP status codes explains that 5xx and 429 responses prompt its crawlers to temporarily slow down. For Google Search, already-indexed URLs are kept in the index for a while but eventually dropped if the errors continue, and any content returned with a 5xx status is ignored. On 500 errors specifically, it says Google decreases the crawl rate in proportion to the number of URLs returning the error, and that URLs persistently returning a server error are removed from the index. Once the server returns 2xx responses again, Google gradually increases the crawl rate.

Search Console's Page indexing help lists "Server error (5xx)" as a reason pages weren't indexed: the server returned a 500-level error when the page was requested.

Symptom → cause → fix

Errors on a handful of URLs, and the pages load fine for you

Likely cause: transient errors, perhaps during a deployment, backup or traffic spike. Google's help notes that server errors can be transient, so a live test may succeed even though Google's crawl failed.

Fix: Use the URL Inspection tool's live test on a few affected URLs. If they load, note the dates of the errors and check whether they match maintenance or busy periods. If they don't recur, request validation in the report and move on.

Errors cluster at certain times of day

Likely cause: the server is running out of capacity during peaks: busy shop hours, scheduled jobs, backups or a burst of crawling.

Fix:

  • Check your host's resource graphs (CPU, memory, process limits) for those times.
  • Move backups and heavy scheduled tasks to quieter hours.
  • Enable or improve caching so pages don't hit the database on every request.
  • Consider a hosting plan with more headroom. Google's help advises making sure your hosting server isn't down, overloaded or misconfigured, and checking with your host about handling more traffic if problems persist.

Errors started after an update

Likely cause: a plugin, theme or code change throwing fatal errors on certain page types, or a PHP version change.

Fix: Check the server error log for the dates in question. Roll back or update the offending component, then test the affected page types (product pages, category pages, search).

Errors mainly on URLs with long query strings

Likely cause: parameter-heavy URLs (filters, sorting, tracking) that create many variants of the same page and are expensive to generate. Google's help gives the example of the same shoe page reachable with parameters in different orders, and warns that dynamic pages can take too long to respond, causing timeouts. It recommends keeping parameter lists short and using them sparingly.

Fix: Reduce crawlable parameter combinations (for example, don't link to every filter combination), make sure canonical tags point to the main version, and look at whether those pages can be cached.

Errors only for Googlebot, not for visitors

Likely cause: a firewall, security plugin, CDN rule or bot-protection service blocking or throttling Google's crawlers. Google's help suggests checking you aren't inadvertently blocking Google through system-level issues.

Fix: Check your security tools' logs for blocked requests from Googlebot, and allow verified Google crawlers. Don't simply allow anything claiming to be Googlebot by user agent; use your provider's verified-bot settings where available.

Errors on every page

Likely cause: the site is down or the server is misconfigured.

Fix: This is an outage, not an SEO issue. Contact your host immediately and set up uptime monitoring so you hear about the next one before Search Console does.

Where to look

  • Page indexing report: which URLs, and when they were last crawled.
  • Crawl Stats report: Google's help suggests looking at recent host availability there to judge whether there's a persistent or large-scale problem.
  • URL Inspection live test: whether the problem reproduces now.
  • Your host's logs and resource graphs: what the server was doing at the time.
  • Uptime monitoring: an independent record of downtime.

After fixing: validate

In the Page indexing report, open the server error issue and click Validate fix. Google's help asks you not to click it again until validation has succeeded or failed, and says validation typically takes up to about two weeks, sometimes longer.

Planned downtime is different

If you know the site will be unavailable for maintenance, a short period returning 503 (service unavailable) with a clear maintenance page is the conventional approach. Keep it brief; long stretches of errors carry the risks described above.

FAQ

Will a few 5xx errors hurt my rankings?

Occasional, short-lived errors are normal and Google retries. Persistent errors are the concern: Google slows crawling and can eventually drop affected URLs.

Why does the page load for me but Google reports an error?

The error may have been transient, may happen only under load, or may affect Google's crawlers specifically because of a firewall or bot rule.

What's the difference between a 500 and a 503?

Both are server errors. A 503 signals temporary unavailability, typically used for maintenance or overload; a 500 is a general internal error.

Should I worry about 429 errors?

Google treats 429 as a server-overload signal and slows crawling. If your server or CDN sends 429s to Google, review your rate limits.

Seeing a wall of server errors in Search Console and not sure whether it's your host or your site? Send us the dates and URLs and we'll help you narrow it down.

Sources

WhatsAppLet’s talk