Skip to the content
searchboar.

Crawling and indexing

HTTP 503: Meaning, examples and limitations

HTTP 503 Service Unavailable indicates that a server is temporarily unable to handle a request, for example during overload or maintenance. It distinguishes temporary unavailability from a resource that is missing or permanently gone.

At a glance

  • 503 describes temporary inability to serve a request.
  • A maintenance screen should not accidentally look like a successful replacement page.
  • Persistent failures still prevent reliable access and need investigation.
On this page
A workshop temporarily pauses service while keeping its address.
HTTP 503 Service Unavailable indicates that a server is temporarily unable to handle a request, for example during overload or maintenance.

What makes this a temporary failure?

The requested resource may still exist, but the service cannot currently provide it. The response can carry Retry-After to suggest when to try again. That suggestion is not proof that the service will recover at the stated time. HTTP reference

A 404 says something different about the requested address, while 410 communicates a likely permanent removal. Choose a status that reflects the actual condition rather than using one generic error response for everything.

Example: scheduled maintenance

Suppose a membership site pauses public page delivery during a database upgrade. A maintenance message with 503 can explain the interruption. Returning that message with 200 risks presenting it as the page's ordinary content. Returning 404 inaccurately suggests that existing addresses cannot be found.

This example does not mean every upgrade needs downtime. Static public pages may remain available while account functions are unavailable, depending on the architecture. Evaluate the response for each affected route, including important landing pages.

What should an operator inspect?

Check whether the response comes from the application, an upstream service or a delivery layer. Compare public pages, authenticated routes and static assets. Record the duration and recoverability of the incident. The text displayed in a browser is only one part of the evidence; inspect the status and headers too.

After recovery, confirm that normal content and successful responses have returned. A cached maintenance response can outlive the original outage, so the cache policy also matters.

Does temporary mean harmless?

No. A long or recurring outage stops visitors and crawlers from retrieving useful pages. A correct 503 explains the failure but does not solve its cause or guarantee stable search visibility. Keep monitoring access after the incident and distinguish recovery of the website from later changes in search reporting.

Google describes crawler-specific responses to these status codes in its HTTP status reference.

Sources

  1. MDN: HTTP 503
  2. Google: HTTP status codes and crawler behavior