(3)
In case you didn't know, you can upgrade your Feedburner URL to feedproxy.google.com. However, some people noticed that feedproxy.google.com is actually disallowing robots.txt -- odd, huh? In fact, the problem has been breaking some feeds.
Fortunately, Google has been paying attention to the relevant discussion and will be adding the following code snippet to the robots.txt file for feedproxy.google.com:
User-agent: * Disallow: /~a/
Google has updated the issues page to confirm this update has been completed. Google said this will fix the issue: "This should permit all readers/crawlers that previously retrieved feed content, but now get a blocked response, to start working properly again. Our apologies for any inconvenience you may have encountered! "
Forum discussion continues at Google Groups.
Comments:
Elmer W. Cagape
09/19/2008 06:36 am
A bit out of topic but I wonder if FB would ever allow us to create custom subjects on feeds sent via e-mail.
Dale Peters
05/06/2009 04:47 pm
How does one submit songs, videos to feedproxy.google.com. Thanks Dale
Stephen Krish
01/17/2014 02:00 am
Sir my blog appinstall.blogspot.com is receiving traffic from http://feedproxy.google.com/~r/Appinstall/~3/1ahY0gHkaa4/best-google-chrome-extensions-to.html . Why feedproxy.google comes instead my blog's address? Is this a issue? I'm confused.