Reclaiming What’s Yours: Getting your feed back from FeedBurner while still tracking subscribers

by Hamlet Batista | August 06, 2007 | 0 Comments

feed-icon.jpgAs you are probably aware, FeedBurner's way of tracking subscriptions is a little bit unreliable. You've probably seen your subscription numbers drop significantly during the weekends and during the days when you have no new posts or little activity. If you’re like me, you want to know your actual subscriber numbers.

There isn’t a straightforward solution, but I have a couple of ideas I'd like to test. One of the easiest involves using FeedBurner’s Awareness API to gain access to the raw data collected and interpreting the data myself in a more useful way. The other idea takes a little bit more time and involves parsing the RSS hits from the web server log file. I explained my idea for the log file in this comment.

The API idea has the disadvantage that depends on FeedBurner, and my hands would be tied later if I wanted to create a competing product. On the other hand, the log file idea is complicated by the fact that, once you’ve moved your feed to FeedBurner, your RSS hits no longer go to your website. You only get the RSS hits from FeedBurner. That is major obstacle.

My plan is to start with the API as it is easier and make sure I can really get better numbers. Next, I'd like to create code to gather subscription data from the sever logs or HTTP_REFERRER. In order to do that I need to move my feed back to my server while keeping FeedBurner's tracking.

Here is my current setup

1. My subscribers access the feed via http://feeds.hamletbatista.com/HamletBatista–InternetEntrepreneurDeveloperAndSearchMarketer
2. FeedBurner accesses my original feed at http://hamletbatista.com/feed/

My ideal setup

1. My subscribers access my original feed directly at http://hamletbatista.com/feed/
2. WordPress automatically redirects feed requests to http://feeds.hamletbatista.com/HamletBatista–InternetEntrepreneurDeveloperAndSearchMarketer
3. WordPress does not redirect feed requests from FeedBurner to avoid a loop

I use a very useful plug-in for WordPress that does exactly this: Feed Smith.

In case you don't use WordPress, here is how you can implement this very easy with mod_rewrite. Create a conditional rule that redirects all access to the feed if the USER_AGENT is not FeedBurner or FeedValidator. You also need to make sure the redirects are temporary (HTTP 302 or HTTP 307). The plug-in does 307s. Note that 307 is only supported by HTTP/1.1 clients. Check http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Example Rule:

RewriteCond %{HTTP_USER_AGENT} feedburner|feedvalidator [NC] RewriteRule ^/feed$
http://feeds.hamletbatista.com/HamletBatista–InternetEntrepreneurDeveloperAndSearchMarketer
[R=307,L] Note: This should be carefully tested in a non-production setting!

The hard part is getting your subscribers to switch links. I think that giving them a strong incentive should help. One idea I plan to implement to increase my RSS subscribers is to share some exclusive tips that are only available if they access the feed from the original URL instead of FeedBurner's. The plan is to release the tips on a given date. I turn off the redirect on that date and use a script that will strip the tips from the feed if it is requested from FeedBurner.

It sounds more complicated than it actually is.

Let me know what you think.

Hamlet Batista

Chief Executive Officer

Hamlet Batista is CEO and founder of RankSense, an agile SEO platform for online retailers and manufacturers. He holds US patents on innovative SEO technologies, started doing SEO as a successful affiliate marketer back in 2002, and believes great SEO results should not take 6 months

0

REPLIES

Comments are closed.

Try our SEO automation tool for free!

RankSense automatically creates search snippets using advanced natural language generation. Get your free trial today.

OUR BLOG

Latest news and tactics

What do you do when you’re losing organic traffic and you don’t know why?

Making it easier to implement SEO changes on your website

Changes to the RankSense SEO rules interface

As we continue to improve the RankSense app for Cloudflare, we are always working to make the app more intuitive and easy to use. I'm pleased to share that we have made significant changes to our SEO rules interface in the settings tab of our app. It is now easier to publish multiple rules sheets and to see which changes have not yet been published to production.

READ POST

How to Find Content Gaps at Scale: Atrapalo vs Skyscanner

For the following Ranksense Webinar, we were joined by Antoine Eripret, who works at Liligo as an SEO lead. Liligo.com is a travel search engine which instantly searches all available flight, bus and train prices on an exhaustive number of travel sites such as online travel agencies, major and low-cost airlines and tour-operators. In this...

READ POST

How to Build a Simple HTTP Code Checker in Python with Streamlit

In this RankSense Webinar, we were joined by Charly Wargnier who is a member of the Streamlit Creators Program. Streamlit is a Python open-source library used to make data apps quickly. Charly takes us on his Python journey from starting out in digital marketing with image editing software like Photoshop all the way to working...

READ POST

Exciting News!
seoClarity acquires RankSense

X