August 14th, 2024

Tell HN: Server error (5xx) in Google Search Console may not be 5xx at all

The website next-episode.net faced indexing issues as Google misreported "429 Too Many Requests" as "5xx" errors. Whitelisting Google Crawlers' IPs resolved the issue, with no new errors reported since.

Tell HN: Server error (5xx) in Google Search Console may not be 5xx at all

The website next-episode.net experienced issues with Google Search Console reporting "Server error (5xx)" for several pages, despite the site functioning normally. The owner investigated the server, Cloudflare, and analytics logs but found no evidence of 5xx errors. Over time, the number of reported 5xx URLs increased, prompting further investigation. The owner discovered that the requests were returning a "429 Too Many Requests" status due to a custom rate limiting feature that restricts excessive requests. This unexpected increase in Google's crawling activity led to the misreporting of the 429 status as a 5xx error in GSC. To address the issue, the owner whitelisted Google Crawlers' IPs and the entire Google ASN (15169) in the rate limiter. After implementing these changes, there have been no new 5xx errors reported in GSC for over two weeks.

- The website faced indexing issues due to Google misreporting "429 Too Many Requests" as "5xx" errors.

- The owner discovered the problem stemmed from a custom rate limiting feature.

- Whitelisting Google Crawlers' IPs and ASN helped resolve the issue.

- Monitoring showed no new 5xx errors for over two weeks after the fix.

- The incident highlights the importance of understanding server response codes and their implications for SEO.

Link Icon 4 comments
By @kevin_nisbet - 3 months
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?

Not trying to criticize if this was already checked. Just something I’d try to double check out of being overly cautious.

By @theginger - 3 months
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.
By @agpl3141592 - 3 months
Sounds more like an issue on cloud flare or whatever server Google is hitting.

It should return 429 so Google can reduce the requests.

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.

Rate limit requests from users you know and make sure every public API is properly cached.

By @mattgreenrocks - 3 months
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.

I'll take a look for 429s. Cheers.