What it means
429 is the rate limiting code. The server can use the Retry-After header to say how many seconds to wait. It's common with APIs (OpenAI, GitHub, Google), logins and bot protection.
Most common causes
- Too many API calls per minute, or the quota is used up.
- Automated scripts or a page refreshing in a loop.
- Many users behind the same public IP (CGNAT, office network, VPN).
- Protection against login attacks.
What you can do as a visitor
- Wait a few minutes and try again; don't keep refreshing.
- Turn off your VPN if you share an IP with lots of other people.
- For subscription services, check whether you've used up your quota.
What the site owner or developer should do
- Always return a Retry-After header.
- On the client, use exponential backoff with random jitter.
- Set limits per user or key, not just per IP.
- Don't rate-limit Googlebot with 429 unless you're seriously overloaded.
Impact on SEO and Google
Google treats 429 much like 503: it temporarily slows down crawling. Prolonged 429s can lead to URLs being dropped from the index.
Frequently asked questions
How long should I wait after a 429?
As long as the Retry-After header says. If there isn't one, start with a few seconds and double the wait each time.
Why do I get a 429 when I've sent only a few requests?
You may be sharing a public IP with other users (CGNAT, VPN, office network).