Constant 429 errors on website

Yesterday my Webflow website (http://sauron.gg/) is suddenly throwing 429 errors throughout the day. I don’t think I added or changed anything substantial yesterday, besides adding a fair amount of new CMS items (~200) so I can’t pinpoint why this is happening or how to prevent this in the future. Anyone else having the same problem found a solution?

I don’t know if this is related, but yesterday my website also lost all its SEO juice. I was consistently ranking on the first page (8-10) for various queries and pages and now I can’t rank higher than position 50…

Read-only link: Webflow - Sauron.gg
p.s. this is my first “real” website in Webflow so it’s likely very messily structured. Working on improving that!

Any help would be greatly appreciated :grinning:

The 429 “Too Many Requests” error suggests that your Webflow site is exceeding rate limits, likely due to excessive requests from bots, users, or your CMS updates. Since you recently added ~200 CMS items, Webflow may be rate-limiting your site due to increased indexing activity. To resolve this, check Webflow’s API rate limits, reduce automated requests (like API calls or frequent CMS updates), and consider using Cloudflare or another CDN to manage traffic. Also, check Google Search Console for crawl issues, as sudden SEO drops might indicate indexing problems. Temporarily blocking excessive bot traffic via robots.txt might help restore performance.

We also started getting them on our site unexpectedly. We’ve not changed anything or have abnormal traffic patterns. I think its something with Webflow.

I am having similar 429 issues with my site as well. Any thoughts on how to resolve? The issue seems to be sporadic today.

Multiple client websites on our account are also getting 429 errors. I noticed first when looking through the Webflow Showcase and several sites were also showing this error. Webflow just acknowledged it as I was writing this reply: https://status.webflow.com/

1 Like

Thank you for sharing this info!

Also getting it here.

Yeah, same thing here.

Also having visitors hit this error. Didn’t change anything.