WhereGoes

429 Too Many Requests

4xx client error

The client exceeded the rate limit for this endpoint and should wait before retrying, using the number of seconds in Retry-After when present.

Common causes

  • A burst of requests from one IP or API key.
  • A crawler or bot ignoring crawl-delay.
  • A shared NAT or proxy concentrating many users on one address.

How to fix it

  • Return Retry-After with a realistic delay and reset information.
  • Exempt verified search engine bots from the tightest limits.
  • Add backoff and jitter on clients instead of immediate retries.

What it means for redirects and SEO

Rate limiting throttles crawlers and can look like an outage if too tight. The Retry-After header tells bots when to return. Search engines accept 429 if it is temporary and honest.

Related codes