I checked my Feedburner subscriber count on April 2nd and was surprised to see that the number of RSS subscribers had dropped from around 1800 to around 1100. The next day, my subscriber count decreased again, this time to around 700. Today, my Feedburner statistics increased slightly to around 1000 subscribers. So, in the course of three days I lost around 40% of my loyal readers, according to Google Feedburner. Will I get these subscribers back? Will my Google subscriber count return to normal? Why did my Feedburner count drop in the first place? Let’s explore the issue and try to answer these critical questions.

Continue Reading

With the recent Feedburner service outage, many sites across the Web experienced severe drops in their Feedburner subscriber counts. Apparently, Google is requiring all Feedburner accounts to be transferred over to Google by the end of February. In the midst of this mass migration, chaotic subscriber data has been reported to include everything from dramatic count drops and fluctuating reach statistics to zero-count values and dreaded “N/A” subscriber-count errors. Obviously, displaying erroneous subscriber-count data on your site is not a good thing. Fortunately, there are several ways to ensure that this doesn’t happen.

Over at CSS Newbie, author Rob Glazebrook weighs in with an excellent point about covering your bases when displaying your Feedburner subscriber count. As explained in the article, Feedburner’s handy API makes it easy to tap your data and display your subscriber count on your blog. Despite its best intentions, however, Feedburner occasionally returns inaccurate data or even no data at all for the subscriber count. For those of us who care about the accuracy of our publicly displayed feed statistics, displaying information like this on your site is simply unacceptable:

Continue Reading

If, for whatever reason, you don’t want to use Feedburner to track your feed statistics, this article describes a relatively simple, “roll-your-own” alternative. Instead of redirecting your feed traffic through Feedburner, keep your original feed URLs and place the following code into a file named “feed_stats.php” (or whatever) and upload to your server:

Continue Reading

Time for another Feedburner redirect tutorial! In our previous FeedBurner-redirect post, I provide an improved HTAccess method for redirecting your site’s main feed and comment feed to their respective Feedburner URLs. In this tutorial, we are redirecting individual WordPress category feeds to their respective FeedBurner URLs. We will also look at the complete code required to redirect all of the above: the main feed, comments feed, and of course any number of individual category feeds. Let’s jump into it..

Continue Reading

Recently, a client wanted to deliver her blog feed through Feedburner to take advantage of its excellent statistical features. Establishing a Feedburner-delivered feed requires three things: a valid feed URL, a Feedburner account, and a redirect method. For permalink-enabled WordPress feed URLs, configuring the required redirect is straightforward: either install the Feedburner Feedsmith plugin or use an optimized HTAccess technique. Unfortunately, for sites without permalinks enabled, the Feedsmith plugin is effectively useless, and virtually all of the HTAccess methods currently available on the Web are designed for permalink-enabled configurations. In this article, we will modify our existing HTAccess technique to work with default WordPress feed URLs.

Continue Reading

Recently, I received a bizarre email accusing me of calling someone out on their fake Feedburner subscriber count. Apparently, some desperate blogger had been claiming to have something like 30,000 Feedburner subscribers when in reality they only had around 700. From what I could tell, the fraudulent site was displaying a counterfeit Feedburner subscriber-count badge using some fancy CSS image-replacement or something. Whatever. I really could care less, but the information contained in the email got me thinking:

Providing an easy way for visitors to verify your subscriber count is a good idea..

Enabling visitors to quickly and easily verify your claimed subscriber count fosters a sense of credibility and legitimacy concerning you and your site. Especially for larger feed counts, validating your claim removes doubt, improves perception, and solidifies reputation. Without some sort of verification, new visitors to your site have no practical way of determining the validity of your claim. Reassuring your guests with an official “verification” link is an excellent way to demonstrate your authenticity and sincerity. Users may or may not actually click on the link, but its mere presence provides a clear signal of your site’s integrity. You know, like saying “look, this is the real McCoy — I’m not faking popularity for personal gain.”

Continue Reading

This may surprise you, but I post quite a bit of content that never appears in the site’s main feed. It is my impression that a vast majority of subscribers are interested in web/graphic-design and development-related topics, and are really much less interested (if at all) in the miscellaneous odds and ends that wind up in the ever-expanding Perishable Press database.

In the past, the process of excluding content from the main feed typically involved changing the post-date to something at least a year or so in the past. The thinking was that I could always return to these posts at some point in the future and put them back into sequential order. Although effective, this process quickly became far too tedious and time-consuming to prove practical. Keeping my eyes open for possible solutions, I have accumulated several excellent techniques for excluding content from WordPress feeds.

Continue Reading

Recently, I found occasion to consolidate and localize my WordPress feeds. A couple of years ago, shortly after I first began using Feedburner to deliver and monitor my site’s feeds, I began listing my Feedburner-assigned feed URL in addition to my localized WordPress feed URL. As time went on, inconsistent feed linkage here at Perishable Press had greatly convoluted the feed-subscription process. Confounding factors include:

Continue Reading

In a previous article, I explain how to redirect your WordPress feeds to Feedburner. Redirecting your WordPress feeds to Feedburner enables you to take advantage of their many freely provided, highly useful tracking and statistical services. Although there are a few important things to consider before optimizing your feeds and switching to Feedburner, many WordPress users redirect their blog’s two main feeds — “main content” and “all comments” — using either a plugin or directly via htaccess. Here is the htaccess code as previously provided here at Perishable Press:

Continue Reading

Just a quick tip on how to create error-free links to feed validation services for feeds that are redirected through Feedburner. For example, let’s say our site’s main feed is originally located at:

http://domain.tld/feed/

If we wanted to provide our visitors with a link that would enable them to automatically validate our feed using a free service such as feedvalidator.org ¹, we would create the link as follows:

Continue Reading

My current adventure into the fascinating realms of site redesign and optimization has yielded several chunks of fruit related to managing and delivering feed content. One of my primary concerns regarding the overhaul of Perishable Press is streamlined content delivery and rights management. An important area of convergence for these two factors involves the management and delivery of a site’s syndicated content. In this article, I explain the shortcomings of many default feed configurations and present an effective overall strategy for better feed management.

When it comes to managing syndicated content, most blogging platforms enable bloggers to provide a multitude of feeds to their readers. For example, WordPress (as well as many other blogging platforms) automatically generates feeds for each of the following channels:

• Main content feed (includes all posts)
• Main comments feed (includes all comments)
• Unlimited number of individual category feeds
• Any combination of individual category feeds as a single feed
• A feed for each the comments given for any particular post
• A feed for each blog author or contributor
• A feed comprised of virtually any combination of the above feeds

Then, as you consider this astronomical number of feeds, multiply each possibility by a factor of at least three: feeds generated via RSS 2.0, RSS 0.92, and Atom formats. Then, as if that were not enough, some bloggers throw third party services such as Feedburner into the mix and link directly to those feeds as well. Now add a zillion non-canonical URL variations into the mix. Eventually, your eyes begin to bug out and you go a little bonkers trying to keep track of them all.

Continue Reading

If you are using Feedburner to deliver your feeds, chances are high that most — if not all — of your loyal readers have subscribed to the Feedburner-specific version of your feed’s URL. This is not a good idea for a couple of important reasons:

• Complete content-delivery failure if/when the Feedburner service goes down
• Cohesive branding strategy impossible because visitors see Feedburner’s name in feed URL instead of your own

At this point, millions of feed subscribers have Feedburner-branded feed URLs listed in their feed readers. If/when the venerable Feedburner service should ever fail, the results would be disastrous. Feedburner needs to provide a comprehensive way for content producers to deliver their feeds through user-specified channels. Currently, Feedburner demonstrates that this is possible by enabling a partial method of redirecting feed traffic to custom URLs.

Continue Reading

Recently, we installed and configured the excellent WordPress Feedburner plugin by the venerable Steve Smith ¹. The plugin basically redirects our various WordPress-powered content feeds to Feedburner, which then delivers them to subscribers. This method enables us to take advantage of Feedburner’s excellent statistical tools. Further, all of the action happens silently, beneath the surface, and without the subscriber even realizing it.

After a few weeks running the plugin with great success, we began hearing reports of broken and missing images messing up our feeds. After some investigating, we realized that our tried-and-true anti-hotlinking htaccess rules were doing their job a little too well — blocking everyone outside our domain from accessing our image content — including Feedburner.

Continue Reading