What does a 500 error mean?

A server returned a failure response, not the requested page. The status does not identify the broken component. RFC 9110 defines the response. Diagnose the request before changing application settings.

A valid URL can return 500. A missing resource is a different problem, so redirecting every failure to the homepage hides useful evidence.

How server errors affect Google

Google slows crawling when it encounters server errors, ignores their response content, and can eventually remove persistently failing URLs from Search. It can retain previously indexed URLs initially. Google documents this handling.

A recovered page does not come with a ranking-restoration deadline. Check delivery first, then the search evidence for the affected URLs. A single aggregate error percentage cannot describe which customer tasks or pages failed.

Read the response, not just the error page

This illustrative HTTP response carries the failure in its status line:

HTTP/1.1 500 Internal Server Error
Content-Type: text/html

The request could not be completed.

Check the status for the actual page request in browser developer tools. Record the URL, method, timestamp and request identifier before looking through application, proxy and server logs. A friendly error message does not prove that the status is correct.

Distinguish nearby HTTP failures

HTTP failure meanings
StatusMeaningWhat to investigate
500Unexpected server condition.The failed request and application/server logs.
502A gateway received an invalid upstream response.Gateway and upstream communication.
503Temporary overload or scheduled maintenance.Availability and maintenance configuration.
504A gateway did not receive an upstream response in time.Upstream latency and timeout configuration.

These meanings come from the HTTP standard. A status names a response condition, not a complete root-cause diagnosis.

Illustrative diagnosis: a failed deployment

Suppose a deployment changes the application configuration and a product page begins returning 500. Compare a failing request with a working route, inspect the matching exception, and check whether the new configuration is available to the process serving that route.

If rollback is appropriate, preserve the error evidence and verify the page after rollback. Do not assume that a successful deployment job proves the public request works. This is a hypothetical troubleshooting scenario, not a customer incident or ranking result.

For temporary overload or scheduled maintenance, 503 communicates the unavailable service. A server may send Retry-After to suggest a waiting period. RFC 9110 explains this header.

Use the response that describes the actual condition. A maintenance response still needs monitoring; changing the code does not make extended downtime harmless to search visibility.

A practical investigation sequence

  1. Confirm which public requests fail and which still work.
  2. Match their timestamps or request IDs to the relevant logs.
  3. Compare recent code, configuration and dependency changes.
  4. Fix the evidenced cause or use a recoverable rollback.
  5. Test the same failing request again, including the returned status and useful page content.
  6. Check any intermediary serving stale failures before clearing an affected cache.

Avoid masking the failure

Returning an error page with 200 can create a soft 404 rather than delivering the intended content. Google distinguishes success responses from error-like content.

Do not repeatedly submit a payment or form merely to test recovery. Use an appropriate test environment for actions with side effects. Keep stack traces and secrets out of the public error message while retaining useful diagnostic logs.

Questions readers ask

Why does one route fail while another loads?

Investigate the code and dependencies used by the failing route, then compare its logs with a working request. The generic status alone cannot identify that difference.

How should I compare error counts across days?

Compare equivalent time windows, total requests and affected routes. Keep the failed customer tasks in view; a raw count alone cannot explain the severity of the problem.

404 errors, soft 404s, crawl rate, crawl errors.

Primary references

Source guidance checked on October 12, 2026. Examples are illustrative; no customer outcome or human expert review is claimed.