Samuel Tardieu @

Braindead Google feed fetcher


It looks like Google feed fetcher has a memory span much shorter than the one of a goldfish (which is more than three months, and not five seconds as commonly believed). For weeks, my web site has been answering Google feed fetcher that has permanently moved (301 redirection) to Each and every time, Google feed fetcher reads the feed from its new location… then forgets about it; it will ask for the old location the next time it runs. - - [07/Dec/2010:06:00:18 +0100] "GET /blog/feed/atom HTTP/1.1" 301 306
  "-" "Feedfetcher-Google; (+
  [...] feed-id=2355462125646541597)" - - [07/Dec/2010:06:00:19 +0100] "GET /blog/feed/ HTTP/1.1" 304 -
  "-" "Feedfetcher-Google; (+;
  [...]; feed-id=2355462125646541597)"

But this is not the end of it: some Google Reader users did indeed indicate the right feed, and Google feed fetcher also asks for it with a different feed-id: - - [07/Dec/2010:06:49:47 +0100] "GET /blog/feed/ HTTP/1.1" 304 -
  "-" "Feedfetcher-Google; (+
  [...] feed-id=15198288757280251505)"

Google, why not remember this permanent redirection and unify those feeds by grouping them under the same feed-id? This would cut down the traffic and the work both for you and for me.

blog comments powered by Disqus