Migrating from FeedBurner to Google

20 Feb 2009

When I logged into FeedBurner today, I was presented with the following message:

Your FeedBurner account "shiflett" and all of your feeds should move to Google.

I've actually been seeing this message for a few weeks, but today I didn't have the option to skip it. If you use FeedBurner, you're being forced to migrate your account to Google today.

There are a couple of concerns worth noting as you make this move:

I'm sure this was not planned haphazardly, but it does seem like the second issue would have been easy to solve. If Google wanted to be clever, they could simply preserve the old URLs indefinitely, so old posts could still use the same (feeds.feedburner.com) URLs, and all new posts could use the new (feedproxy.google.com) URLs.

Via Twitter, I learned that Ben Ramsey ran into this problem and accidentally spammed Planet PHP along with all of his other subscribers. With his help, we were able to determine how to disable proxying entirely, so that the real URLs to his blog posts showed up in his feed. Here are Ben's instructions:

Click your feed -> click Configure Stats under the Services heading in the left-hand column of the "Analyze" tab -> uncheck "Item link clicks" and click the Save button.

Figure 1 illustrates this. Leaving the middle checkbox ("Item link clicks") unchecked will restore your URLs. You can inspect Ben's feed to see the results.

Figure 1:

Uncheck the the item link clicks option.

With Google running the show, a Ma.gnolia meltdown seems unlikely, but it does seem like there are a few details that weren't addressed very well.

Because I've just made this switch myself, I decided to go ahead and change my feed URL while I'm at it. Although I plan to maintain the old feed URL indefinitely, please be sure you are subscribed to the following:

http://shiflett.org/feeds/blog

I have 4,088 subscribers according to FeedBurner. I'll add a comment or post a followup to let you know how this migration affects that number.

Sean doesn't want to use FeedBurner, because people can subscribe to your feed using a URL that's not under your control. These migration issues justify his concern, and we have been discussing ways to preserve statistics without giving up control. I might experiment to see if I can make a request to my FeedBurner URL that includes an X-Forwarded-For header for every request to my feed URL (http://shiflett.org/feeds/blog). If it works, this would be an alternative to redirecting that is transparent to subscribers.

Good luck to everyone migrating their feed(s) today!