A FeedBurner account and its proudly displayed feed count chicklet has been primary promotional requirements for any blog for a few years now. Since Google’s take over of Feedburner last year, they have been working on integrating the FeedBurner services completely into Google and it seems they are ready with it now.
What does this mean to you? You are left with three to four weeks before you move your FeedBurner services to one of your Google accounts. Google plans to complete the migration process by the end of February 2009 and after that timeframe all FeedBurner accounts will expire. Fortunately the migration process involves only a few clicks and Google does the entire dirty job while you sleep. This post explains the steps involved in FeedBurner to Google migration, things to consider while migrating and some tips for advanced users who are using the awareness API.
How do I migrate my FeedBurner account to Google?
Very simple! Log on to your FeedBurner account, and click ‘Move my feeds to Google’ link on top of the screen. You will be asked which Google account you want to move it to. You just need to enter this Google Account ID and password (if you are already logged on, even better) and proceed to the next step and you are done!
Depending on the size of your content (number of posts), it may take from a few seconds to several hours. In my case it took hardly 5 minutes.
Things to remember while moving your feed account to Google
- If you intend to use AdSense for feeds, please make sure that you move your feeds to the same Google account that is used for AdSense publisher account. If not, you cannot put feed ads and I am telling from the first hand experience!
- If you are already using Google AdSense feed, it means that your feeds were moved (manually) to a Google account sometime last year. In this case you don’t need to do anything now!
- Once moved to Google, your blog feed may be changed from feeds.feedburner.com/myfeed to feeds2.feedburner.com/myfeed. You may need to change your Subscribe to RSS image links and URLs to reflect this
- Also, it is advisible to change your FeedSmith Plugin settings to reflect the above URL, though Google may take care of it automatically even post Feb 2009
- If you don’t migrate before the end of Feb 2009, your feed subscription hits may throw Page Not Found! errors and hence will have the risk of loosing your RSS subscribers. Also it may have impact on other plugins like CommentLuv (just an example) depending on their internal logic of obtaining post feeds
- Once the migration is completed you can access your feed account features (analyze, optimize, publicize, monetize etc) via http://feedburner.google.com/
Post migration, the following URLs will point to your feed though only time will tell which URL will be permanently provided by Google.
Awareness API usage for Advanced Users
A lot of people have been using the Feedburner Awareness API to build feed analysis tools or to show custom feed count. The awareness API has not been working very well during the past few months for feeds that were already migrated to Google Proxy (like the second URL above). Fortunately, Google has fixed this issue recently and all that you need to do is to change the Awareness API service access URL and no other change in your existing code!
I had helped Daniel with a scorecard logic for his last episode of the Blogging Idol competition and internally the scorecard had a piece of code something similar to the sample below (Sample code here). To make it work with the new Awareness API, I just had to change a single line of code. You may also use this piece of code to display your own FeedCount probably with different styles.
Thanks to Google who made this entire migration automated and peaceful. Google promises that many problems that FeedBurner had (like drastic drop in feed count once in a while) will go away with this migration. Google has also started working on some good feed analytics features as well. Feedcount chicklet still has some short term issues but it is a matter of a couple of weeks before Google fixes that (or you could use the code snippet above to get the actual count)