How long should I wait before retrying?

Check the Retry-After header in the response. If not present, wait 30-60 seconds before retrying with exponential backoff.

If temporary, 503 tells search engines the downtime is temporary and to come back later. It will not cause deindexing if it resolves quickly.

HTTP 503 Service Unavailable — What It Means & How to Fix It

Critical5xx server error

Overview

The HTTP 503 Service Unavailable status code indicates the server is temporarily unable to handle the request, usually due to maintenance or overload.

Key Details

This is a temporary condition and the server should recover.
The response should include a Retry-After header indicating when to try again.
Common during planned maintenance, deployments, or traffic spikes.
It tells search engines and clients to come back later, not to deindex the page.
Load balancers may return 503 when no healthy backend servers are available.

Common Causes

The server is undergoing planned maintenance or deployment.
The server is overloaded with too many requests.
All backend servers behind a load balancer are unhealthy.
The application crashed and is restarting.

Steps

1Wait and retry the request after the time specified in the Retry-After header.
2Check server status pages for maintenance announcements.
3If you control the server, check application health and restart services if needed.
4Scale up server resources or add more instances if the cause is overload.
5Review load balancer health checks to ensure backend servers are detected correctly.