Troubleshooting · Explainer
What Causes the 429 Too Many Requests Error in WordPress
Short answer
A 429 Too Many Requests error means the client sent too many requests in a given time, and the server is asking it to slow down. In WordPress, the usual causes are a security plugin rate limit, a host or firewall limit, a login or API flood, or a misconfigured plugin making requests in a loop. Wait for the time in the Retry-After header before trying again.
Key takeaways
- A 429 means the server is throttling you on purpose, not that the server is down.
- The Retry-After header tells you how long to wait, in seconds or as a date.
- Rate limits can apply per IP address, per user, or per resource, depending on who set them.
- Google treats a 429 as a server-overload signal and slows its crawling, rather than dropping the page.
- A 429 must not be stored by a cache, so every retry gets a fresh answer from the server.
What does a 429 Too Many Requests error mean?
A 429 Too Many Requests error means you sent too many requests in a short time, and the server is asking you to slow down.
RFC 6585, the document that defines the code, says the 429 status means the user has sent too many requests in a given amount of time. MDN's 429 reference adds that this is commonly called rate limiting, and that the limit can be server-wide or per resource.
A 429 is a deliberate answer, not a crash. The server is up and working, and it is throttling traffic to protect itself from overload or abuse. Retrying harder makes it worse, because each new request counts against the same limit.
How is a 429 different from a 403 or a 503?
A 429 is a wait signal, a 403 is a refusal, and a 503 says the server cannot cope right now.
MDN's 403 reference says that for a 403, authenticating or re-authenticating makes no difference, and repeating the request fails the same way. A 429 is different: the same request works again once the limit window passes.
A 503 means the server is overloaded or down for maintenance, and it may come with a Retry-After header too.
| Code | Meaning | What to do |
|---|---|---|
| 403 Forbidden | Access refused | Fix the permission or rule |
| 404 Not Found | Resource missing | Fix the address or restore the page |
| 429 Too Many Requests | Rate limit hit | Wait, then slow down |
| 503 Service Unavailable | Server overloaded | Wait, then check the server |
Google's crawler documentation treats a 429 differently from other 4xx codes: it reads it as a server-overload signal, like a 5xx error, and slows its crawling. A 403 or 404, by contrast, tells Google the page is gone, and indexed URLs returning those codes are removed over time.
Our guide to fixing the 403 Forbidden error covers the refusal case.
For the server-overload case, see our guide to fixing the 503 Service Unavailable error.
What does the Retry-After header tell you?
The Retry-After header tells you how long to wait before making a new request, in seconds or as a date.
RFC 6585 says a 429 response may include a Retry-After header, and its example shows Retry-After: 3600, which means wait one hour. MDN's 429 reference shows the same value in its example, with requests allowed again after 3600 seconds.
Not every 429 carries the header. If there is no Retry-After value, wait a few minutes and try again, then double the wait each time you still get a 429.
RFC 6585 also says a 429 response must not be stored by a cache, so every retry gets a fresh answer from the server.
What causes a 429 on a WordPress site?
A 429 on a WordPress site usually comes from a rate limit set by a security plugin, a host, or a firewall.
Security plugins limit login attempts to block brute-force attacks, and a burst of wrong passwords can trip that limit. Hosts and firewalls set limits on requests per minute from one IP address, which a busy office or a shared network can hit together.
Cloudflare's rate limiting documentation says rate limiting rules can protect a login endpoint from brute-force attacks or cap how many API calls one client makes in a given time window.
A misconfigured plugin can cause a 429 from inside the site, by calling an API or an admin page in a loop. A backup, migration, or sync tool can do the same thing by sending hundreds of requests in a few minutes.
The site is not under attack in these cases; it is flooding itself.
How do you tell which limit you hit?
The pattern of the 429 tells you which limit you hit: one page, one user, or the whole site.
A 429 on one address, such as wp-login.php or an API endpoint, points to a limit on that address. A 429 on every page points to a limit on your IP address or on the whole server.
MDN's 429 reference says rate limits are typically based on a client IP, but can be specific to users or authorized applications when requests are authenticated or carry a cookie.
Check the response headers in your browser's developer tools, on the Network tab. Look for Retry-After and for headers that name the limit, such as X-RateLimit-Remaining. If the same page loads from mobile data but not from your office network, the limit is tied to the office IP address.
RFC 6585 notes that the standard does not define how a server identifies the user or counts requests, so the limit can be per resource, per server, or across a set of servers. That is why the same behavior can 429 on one host and work fine on another.
For the full repair steps, see our guide to fixing the 429 Too Many Requests error.
What if the 429 only appears on login or wp-admin?
A 429 on login or wp-admin usually means a brute-force limit has tripped, or a plugin is polling the admin area too fast.
Login limits count failed attempts, so a run of wrong passwords from your IP can lock the login page for everyone on that network. Wait out the block, then log in once with the right password.
Cloudflare's rate limiting documentation lists protecting a login endpoint from brute-force attacks as a core use for rate limiting rules.
In wp-admin, the cause is often a plugin that polls admin-ajax.php every few seconds, such as a live chat, a stats widget, or a backup monitor. Open the browser developer tools and watch the Network tab for repeated requests.
Disable the polling plugin and the 429 usually clears at once.
What if the 429 only appears to Googlebot?
A 429 that only Googlebot sees usually means a firewall or bot rule is treating the crawler as too aggressive.
Google's crawler documentation says 429 and 5xx errors prompt its crawlers to temporarily slow down, and indexed URLs are preserved at first but eventually dropped if the errors persist. A short 429 during a busy hour is normal, but days of 429s can shrink the pages Google crawls.
Check the firewall log for blocked requests from Googlebot, and check whether a rate limiting rule applies to verified bots. Cloudflare's rate limiting documentation warns that applying rate limiting rules to verified bots might affect search engine optimization. Raise the limit for verified bots, or exclude them from the rule.
If your host is under a traffic spike, the 429 may be the host protecting the server, not a rule aimed at Google. Ask the host whether the limit is site-wide and when it lifts.
Do not answer a crawler 429 with a 403 or a 404, since those tell Google the page is gone.
How do you stop a 429 from coming back?
Stop a 429 from coming back by finding the source of the requests and raising or fixing the limit that fired.
- Find the source: check the server access log for the IP address or user agent making the most requests.
- Fix a looping plugin or a polling widget before you raise any limit.
- Raise the limit for real traffic, or exclude verified bots from the rate limiting rule.
- Cache heavy pages so each visit costs the server fewer requests.
Cloudflare's rate limiting documentation describes the pieces of a rule: the characteristics that define how the rate is tracked, the period in seconds, the requests allowed per period, and the duration of the block once the limit is hit.
On the free plan, a rule counts by IP address over a 10-second period, so a small change there can clear a false block.
If the 429 comes from your host rather than Cloudflare, ask the host what the limit is and whether it can be raised. A host limit that trips on normal traffic is a sign the plan is too small for the site, or that a plugin is wasting requests.
What mistakes should you avoid?
The worst mistake is hammering the refresh button, since every retry counts against the same limit and extends the block.
- Do not retry a 429 at once, since the server is telling you to wait.
- Do not answer a 429 with a 403 or a 404, since those tell Google the page is gone.
- Do not raise the limit before fixing a looping plugin, since the loop will just hit the new limit.
- Do not block whole IP ranges to stop one flood, since shared networks put real visitors behind the same addresses.
Wait first, find the source second, and fix the cause third, and the 429 will usually clear on its own.
Frequently asked questions
How long does a 429 block last?
It depends on the limit that fired. The Retry-After header gives the exact wait when it is present, and common values run from a few seconds to an hour. If there is no header, wait a few minutes and try again, then double the wait each time the error returns.
Why do I get a 429 when I am the only visitor?
Your IP address may be shared with many other users, such as on an office network, a VPN, or mobile data. The limit counts requests from the address, not from you alone. A plugin on your own site can also flood the server with requests, so check the access log before you blame the network.
Can a 429 hurt my search rankings?
A short 429 rarely hurts, because Google treats it as a server-overload signal and slows its crawling instead of dropping pages. A 429 that lasts for days is different, since Google may crawl fewer pages and eventually drop indexed URLs that keep returning errors. Fix the cause quickly and let Google re-crawl.
Is a 429 the same as being banned?
No. A 429 is a temporary limit, and the same request works again once the window passes. A ban blocks you for good or until someone removes it. If the 429 clears after a wait, you were throttled, not banned. If it never clears, check whether a firewall rule is blocking your address.
Should I turn off rate limiting to stop 429 errors?
No. Rate limiting protects your login page and your server from floods and brute-force attacks, and removing it trades a short block for a real outage. Raise the limit for real traffic, exclude verified bots, and fix any plugin that loops. Keep the protection and tune it instead.
Sources
- 429 Too Many Requests MDN Web Docs
- 403 Forbidden MDN Web Docs
- RFC 6585: Additional HTTP Status Codes RFC Editor
- Rate limiting rules Cloudflare Docs
- How HTTP Status Codes Affect Google's Crawlers Google Search Central
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
