9 Must Update Google/FeedBurner Links

Ok, I’ve calmed down a little from the Google/FeedBurner fiasco. Not totally, but enough not to rant and to give you some pointers on what HAS to be Changed, either now or in the near future if you have a FeedBurner account.

This is a list of what I had to change on Three different blogs:

1. Links for RSS & e-mail subscriptions in the Header, Sidebar
2. RSS & e-mail for What Would Seth Godin Do plugin (offers subscriptions to new visitors)
3. Simple Pie plugin for sidebar updates of current posts (2 blogs)
4. FB Subscription count buttons
5. Feedflare code for links in posts and feeds
6. Headline animator (1 blog)
7. FeedBurner Feed Replacement plugin to make sure all subscriptions count in stats (it has since moved & redirects to Google Search)
8. RSS ads through FeedBurner for WAH business network
9. Waiting for response from Text Link Ads to see if an update is needed (my RSS ads on feeds)

Did I miss anything? 

At present Google/FeedBurner does have a redirect on all the old feed links, but they do advise to update to the new codes as soon as possible. I don’t know how long they plan on having redirects in effect, but why take a chance that you will forget to change them later when the new links become permanent?

So, my advice to you is find and change all your FeedBurner links and plugins and fancy doodle do hickeys NOW.

(See why I was so miffed the other day.)

UPDATE: Feed Flair from Google/FeedBurner DOES NOT WORK NOW. Codes have been updated etc, but it doesn’t work on the Site OR Feed. Not sure if it is actually FB or possibly the latest Upgrade to WP 2.6.5 because that was just done after the Feed change-over & I just noticed the problem today, but Other sites I have in my Feedreader that used to have FF don’t have it now either. Coincidence?

UPDATE 2: Per the Google FeedBurner known problems page…

29-DEC 2008: FeedFlare links are not currently showing for feeds hosted on feedburner.google.com. This is an issue the team is working on and hopes to have resolved as soon as possible.

At least I know it’s not a WP problem.