4xx Client Error
HTTP 429 Too Many Requests
The client sent too many requests in a given time and is being rate limited.
Check a URL's HTTP statusWhat 429 means
The Retry-After header often says how long to wait before trying again.
Common causes
- Exceeding an API rate limit.
- Aggressive crawling or automated scripts.
- Bot protection throttling.
How to fix it
- Wait for the Retry-After period and back off exponentially.
- Cache responses and batch requests.
SEO impact
Repeated 429s to search crawlers slow down crawling. Allow reasonable crawl rates for verified bots.
How to check a status code
Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.
FAQ
- What does HTTP 429 mean?
- 429 Too Many Requests is a 4xx client error status code. The client sent too many requests in a given time and is being rate limited.
- What causes a 429 error?
- Exceeding an API rate limit. Aggressive crawling or automated scripts. Bot protection throttling.
- How do I fix HTTP 429?
- Wait for the Retry-After period and back off exponentially. Cache responses and batch requests.
Defined in RFC 6585.
Other 4xx client error codes
400 Bad Request401 Unauthorized403 Forbidden404 Not Found405 Method Not Allowed406 Not Acceptable408 Request Timeout409 Conflict410 Gone413 Content Too Large414 URI Too Long415 Unsupported Media Type418 I'm a teapot422 Unprocessable Content425 Too Early431 Request Header Fields Too Large451 Unavailable For Legal Reasons