FeedBurner is too broken for its biggest fan

Update: See this comment from Feedburner co-founder Dick Costolo for more on the progress the service is making.

Before Jason Shellen left Google and started Plinky (which launched earlier today), he helped develop products like Blogger and Reader — and he was the one who did the due diligence for Google before it bought FeedBurner for $100 million back in 2007. While I was talking to him about Plinky today, I asked him why he thinks FeedBurner has been having so many problems for so long. Problems like a new post on a blog not showing up in RSS readers and aggregators for hours, or problems like articles not even being picked up at all. Problems like not having a good way to get basic technical support from Google about the problems.

Feeds are vital to the web. The RSS (or Really Simple Syndication) standard allows sites to know when other sites have updated with new information, including blog posts, podcasts and videos. Many web sites and content aggregators have come to rely on FeedBurner to distribute the new data they publish. For VentureBeat, a large portion of our regular readers choose to read us using Google Reader, Bloglines, Netvibes and other personal feed aggregator services. Feeds are just as important for getting our stories picked up on news aggregator sites like Techmeme, that are trying to automatically crawl and sort the most interesting new content on the web. Indeed, Feedburner problems “are so bad” that unhappy Feedburner user and Techmeme founder Gabe Rivera has created his own software tool for finding new content. “I put in a workaround enabling Techmeme to find new post URLs for some blogs even when they’re not yet in the Feedburner-served feed,” he tells me.

See screenshot of VentureBeat’s raw Feedburner feed, below.

Shellen thinks that what “happened behind the scenes is that the sales team can sells ads [in FeedBurner feeds] if it wants to, but with so many other products, managing feeds is fairly low on the list.” So supporting FeedBurner isn’t getting the sort of resources — engineers, servers, etc. — that it needs because its not making enough money. It’s hard to think of what the other reasons might be; the original Feedburner team is comprised of talented entrepreneurs who, on their own, built a product that was becoming ubiquitous on the web before Google came along. But after all, ads in feeds don’t make much money — something VentureBeat itself experiences first-hand.

Feedburner problems aren’t new. Laughing Squid and a number of blogs had problems with FeedBurner’s feed-based email delivery service last month. This month, the problem seems to be that feed statistics counters on blogs like TechCrunch aren’t showing the correct number of readers. This is an issue that should be resolved shortly, we hear, but it’s something that’s happened several times over the past few months. Feed analytics is probably the reason most blogs are using FeedBurner in the first place, and if it isn’t reliable for that, what’s the point in using it? Speaking of, Shellen says that Googlers keep telling him they’re “working on” new analytics features, but improvements have been taking awhile.

Things are bad enough that Shellen himself got halfway into using FeedBurner for Plinky before he and his cofounders decided to ditch it and build a simple, “home-brewed” version, he tells me. Plinky is trying to make it easier for people to create and share content on other sites — functional feeds are certainly a requirement in doing that. They’d much rather use FeedBurner, but it’s just not working for them. “It’s the best thing around and we are chomping at the bit to use it,” he says.

Google is in the process of making all FeedBurner users migrate over to its servers. One can only hope that will end these recurring issues, but there’s little reason to believe that will be the case. After all, the migration process itself created an error the other day, one that had to be fixed by the FeedBurner team. To be fair, that team, made up of some of those who started the company, has been responsive in helping us through the issues we’ve encountered in the past few weeks. But the fact that there are multiple issues to begin with is the problem — for both the service and its users.

MG Siegler contributed to this article.

Next Story: TPI Composites raises $20M for wind turbine blades
Previous Story: Extreme Reach grabs $1.5M for video advertising

Bookmark and Share

Tags: ,

Photo of Eric Eldon

About the Author, Eric Eldon

Eric currently covers digital media technology and business news, especially what's happening on social networks and their platforms. He also writes and edits stories about venture capital, and lots of other stuff, too. He started at VentureBeat in the spring of 2007, half a year or so after Matt Marshall left his reporting job at the San Jose Mercury News to found the site. Eric previously cofounded a startup called Writewith, that was building editorial software for newspapers and other groups of writers. The startup didn't work out, but he learned a lot.

  • Sebastien
    I remember talking ppl out of using Feedburner in 2005 when I was pitching podcasts/RSS. "Why would you want to let someone put a toolbooth between you and your customer?" I would say.

    Sure, they had stats, and even if the feed ads never panned out as a viable business for publishers, at least the servers worked.

    The question is, if you were building a blog/podcast today, would you use Google/Feedburner?
  • Jon
    Feedburner has it's problems but VALID alternatives are few and far between.

    Jon
    http://WoodMarvels.com - Create Unique Memories
  • Dick Costolo
    We are in the process, as you’ve noted, of migrating publishers from the legacy FeedBurner environment to the new Google environment. We are focused right now on migrating publishers as efficiently as possible, so that we can begin to transition our focus to innovating on the new platform. In the process of migrating two million feeds from the legacy system to the new environment, in my opinion, it is inevitable that there will be challenges, simply because of the complexity involved. It is also the case, however, that the new systems are significant improvements over the legacy systems in many areas, once publishers are through the migration process. As an example, and without going into too many details, the legacy email service had several delivery constraints as it continued to grow dramatically, and the new system is vastly improved with a superior design for growth.

    Of course it is frustrating to experience an issue where there previously was none. A publisher doesn’t care if a feed runs on system X or system Y, just as long as it works. My personal perspective is that publishers are experiencing a single pain point as we jump from the old boat onto the new and better and faster boat, and once everybody’s on the new boat, it can accelerate. It’s not a particularly good metaphor, but I got a D in creative writing, so what are you gonna do.

    In the words of Inigo Montoya, let me sum up. We are excited about completing the migration of publishers to the new system because the team understands how well we will be able to innovate on the new system, and the team understands the superior design for growth behind the new system. I think it’s only a matter of time before this is clear to everybody.
  • In spite of your optimistic assessment of Google's new system, please explain why, after moving to Google, the # of my readers has dropped from 800 to 400, no one can subscribe to my feed via email, and those that do subscribe via email are no longer receiving new posts.

    Frankly, I can't wait until 2 million Feedburner users migrate to Google before improvements in the service magically appear. I am not alone: http://groups.google.com/group/feedburner-stati...
  • Dick Costolo
    hi peter,

    a) your email subscription html in your blog is setup wrong. You've got two double quotes after the href= instead of one, for example, so it will just reload the page instead of the subscription form. The form will work correctly once you fix your blog html.

    b) email went out correctly to your subscribers this morning. You might ask some of your subscribers to check to see if it is being incorrectly categorized as spam. I will follow-up with you directly with a specific detail that will make it easier for subscribers to find your email this morning, but I assure you that it went out.

    c) the subscriber number is a reporting issue with one of the aggregators, you have not lost any subscribers, and we are working with the aggregator to make sure the issue is fixed and to see what has to happen so that this kind of thing doesn't continue. We have seen this issue a couple times since we started migration - it could be for a few different reasons - and we'll sort these out as they arise and put in place mechanisms to mitigate any recurrences
  • Facebook User
    Glad to know that Google's FeedBurner team is working hard on it but it's a bit worrisome to notice that this sorry-but-we're-already-doing-everything-we-can corporate mindset has slowly grown within Google...
  • Dick -

    Thanks for LISTENING. It's a start. I will update the email code and I'm glad to learn that those who subscribe to The Flack via email are not left in the cold.

    Good weekend.
  • uhm, that's some pretty damn good customer service. Dick, would you mind migrating my various google hosted and non hosted accounts so I can use all the google services I want?

    Okay, that's not gonna happen. But it really is sweet to read the proaction. great job.