Wizard's Blog

Image via CrunchBase

I tried FeedBurner back in the days when this blog was running Blogger, but I never really saw the point and I didn’t have any subscribers anyway.  Since then I switched to WordPress and FeedBurner was bought by Google, so I gave it another shot.

I’ve been using it for a while now, with mixed results.  The stats are inaccurate to the point where they seem random (and weren’t stats the original point?), their whole website is dreadfully slow, and there was no easy way to switch everyone over from the direct feed to the burned one.

Then today I read about a WordPress plugin called FeedBurner FeedSmith, which (somehow) takes care of that exact problem.  Hooray!

And then I noticed that the FeedBurner feed wasn’t working at all.  I checked Google Reader and sure enough, it hadn’t had a blog post in two weeks!  And I’ve been posting every day!  And although I have FeedMedic alerts set up, I never got one.

The FeedBurner feed was showing this error:

Error getting URL: 502 - Source feed is too large … maximum size is 512K

Which is fairly self-explanatory I suppose, but it still took a while to fix.  First of all I lowered the number of posts that WordPress sends to the feed from 500 down to 10.  Although that should bring down the feed size drastically, I was still getting the error.  It turns out that the trick is to ping FeedBurner so it actually tries getting your feed again rather than just showing you the error from the last time it tried.

So in the end all is well with the world.

Related articles by Zemanta

• Fixing my Feed problem with Feedburner’s Feedsmith: Increase of 66% measurable readership
• What Is FeedBurner And Why It Is A Great Tool For Web Publishers
• FeedBurner May Not Be Hearing Your Pings (Marshall Kirkpatrick/ReadWriteWeb)
• Lies, damn lies, and RSS subscriber figures [Stats]
• FeedBurner to Google
• Google Reader Subcription Stats and FeedBurner