Question: What would cause Google to load one page ( over 700 times in 24 hours? Answer: I'll tell you when I find out.

Over the last few weeks, an ever increasing number of requests have been coming in from a few of Google's IP addresses loading the same page over and over and over... The page in question is updated at most once per hour. Every time they load it, the Referer header lists "", which is the old address of the page from before I changed my company name over a year ago. Today, the number of page loads skyrocketed from the level it had slowly risen to of about 300/day to over 700 in the last 24 hours!

I've contacted Google about the problem. The first time, they didn't quite seem to get the message and replied that they had slowed the crawling of my website. Thanks but that's not the problem I replied. I've gotten no response to that (not yet anyway, perhaps I will within a few days), so today (or was it yesterday?) I posted a brand new comment that was hopefully worded more clearly (not that the other one wasn't clear--just easier to gloss over if you handle too many messages like this in one day). At that time, I was up to about 400 requests in 24 hours. Now it's just getting ridiculous.

My first response before the latest burst was to add a little code to the page that sends a very small response when that page is loaded with the Referer header that Google is sending, and requires another click to see the real page (and no--I don't think that's what caused the new burst--otherwise I'd expect a different Referer header when they followed the link...but then who knows--if they're doing something screwy, maybe they're doing something even screwier too).

The next step, which I'm holding off on for just a bit in case leaving things as they are helps them fix the problem, will be to update robots.txt to block them from that page completely. Here's hoping the machines haven't already taken control in Mountain View.

Reader Comment:
Anonymous said:
ive the same problem. it even crashed my apache
(join the conversation below)