I run <a href="https://next-episode.net" rel="nofollow">https://next-episode.net</a> and recently (a few months ago) - I noticed it started getting pages not indexed because of “Server error (5xx)” in Google Search Console (GSC):<p><a href="https://next-episode.net/img/upload/5xx.png" rel="nofollow">https://next-episode.net/img/upload/5xx.png</a><p>On the website everything looked good and all reported links worked fine.<p>I tried validating these errors at GSC as fixed, but it would always report back that the issue is still present and new links would keep popping up to have 5xx errors (as seen on the screenshot).<p>This was worrisome because it indicated there was some kind of an issue I wasn’t aware of that may be affecting not only Google’s crawlers, but my users as well.<p>I did what everyone would do - checked my server, Cloudflare and analytics logs for anything suspicious and placed some additional logging to try and catch what was happening.<p>This turned out nothing - as far as I could tell - no requests returned any 5xx errors, so I decided it’s just a weird Google quirk and ignored it for a while.<p>With time though, Google kept reporting these problems and the count of 5xx URLs only grew larger so once again (about 2 weeks ago) I started investigating what was happening.<p>This time around, I tried to match the URLs reported by GSC with the analytics provided by Cloudflare and bingo - I found that all these requests had the Edge Status Code (and Origin Status Code) of “429 Too Many Requests”.<p>Now that was progress.<p>There is only one thing on my service that would return this status code and is my custom rate limiting which would be triggered if you do more than 30 requests in less than 10 seconds.<p>What changed so that Google suddenly decided to crawl so aggressively and hit that limit (something that never happened before, and Next Episode is online for more than 19 years now!) and why it’s reporting them 5xx in GSC when my server clearly returns 429 - I don’t know.<p>What I do know for sure is that Google is misreporting 429 server status as 5xx.<p>To fix this (at least as a quick fix for now) - I whitelisted in my rate limiter all Google Crawlers’ IPs (which I found through here: <a href="https://www.infidigit.com/blog/google-update-googlebots-ip-addresses/" rel="nofollow">https://www.infidigit.com/blog/google-update-googlebots-ip-a...</a> ) - listed in this JSON provided by Google: <a href="https://developers.google.com/search/apis/ipranges/googlebot.json" rel="nofollow">https://developers.google.com/search/apis/ipranges/googlebot...</a><p>For just in case, I also passed on the ASN in the request header (through a Cloudflare transform rule) and whitelisted the whole Google ASN (15169) as well.<p>After - I monitored for new 5xx errors popping up in GSC and new 429 statuses logged in Cloudflare from Google’s ASN and so far (for more than 2 weeks) - so good.
Is there any possibility there is a problem with the 429 response? So something is converting to say a bad gateway error because it doesn’t like the 429?<p>Not trying to criticize if this was already checked. Just something I’d try to double check out of being overly cautious.
How do you rate limit unidentified users? If you are treating all unidentified users, or at least all Google bots as 1 user and they consider each Google bot instances with a unique ip and no credentials a unique user and are hitting a 429 with a single request they may be treating that as a 503 instead.
Sounds more like an issue on cloud flare or whatever server Google is hitting.<p>It should return 429 so Google can reduce the requests.<p>I'm not even sure why you would rate limit in the first place? IPS are not unique. One company gateway or university for example has plenty of users.<p>Rate limit requests from users you know and make sure every public API is properly cached.
I have gotten these emails as well for a Cloudflare-hosted site. I was surprised when I got them because they seemed to crop up out of the blue (a month or so ago?) and AFAIK I couldn't think of much that could actually cause a 500 status code on my end.<p>I'll take a look for 429s. Cheers.