Welcome to WebmasterWorld Guest from 126.96.36.199
Here is a good older thread that describes some ways to track feeds:
Our stats package is tagging based and doesn't have the facility to track RSS feeds unfortunately. We're in the market for a new stats package though, so I'll add that to the desirables list.
FeedBurner looks interesting so I've signed our feeds up. I'm not sure I understand where the stats come from though - is it just from popular sites which allow you to personalize and add feeds like Windows Live and Google? And does it get information from other places as well e.g. popular desktop feed readers?
Presumably FeedBurner wouldn't capture information from less popular websites using your feeds though e.g. a hobby site, you'd need to do that through your stats package?
My suggestion when using a service like this is to make your real RSS feed a 302 redirect so that if you ever decide to part company with the service your real RSS URI won't be pointing to the old service, and you won't inconvenience your subscribers.
Actually services like FeedBurner will capture all your feed traffic because they're serving up your feeds for you. All the traffic from the feed goes through their systems and their tracking. It's quite accurate.
Sorry if I'm being dense, but I don't understand this part. My feeds have not changed or moved, and are still served from our site, not FeedBurner's. Can you elaborate?
In a sense, the FeedBurner version of your feed becomes the public view of your syndicated content, and your original feed becomes a private feed that only you and FeedBurner know about.
Exactly. Just remove the link to the original feed so that future subscribers have to subscribe using FeedBurner. Don't kill the original feed unless you alert your subscribers and give them time to switch.
Here's the way I use it on my sites:
) and rename it (
) and point it toward FeedBurner
Redirect temp /feed.xml http://feeds.feedburner.com/YourNewFeedBurnerFeed
Feeds are consumed by aggregators, not browsers for the most-part. The aggregators pulling in your XML content don't look at the CSS and formatting that you're seeing at all. Generally the only thing you can do to customize the look of your feed is to add graphics to your entries.
The fact that FeedBurner makes a nice browsable page out of your RSS should not distract you from the purpose of your feed, which is to get information out in an XML format. It's not really meant to be read in a page format like FeedBurner presents. That's just a nice extra service on their part.
The BrowserFriendly service even has a disclaimer there that says:
This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site, subject to copyright and fair use.
Feeds are consumed by aggregators, not browsers for the most-part.
That's a good point, and one I'll try and keep in mind. I think a fair amount of users do simply click the link and stumble on the feed itself however.
We were just concerned that it might look more professional to have our own company stylesheet rather than that of a third party, and our own choice of buttons to add the feed to various feed readers.
A further bit of research however seems to suggest that IE7 jumps in with it's own stylesheet for RSS and ignores any which may have been created anyway, as does Firefox. If this is the way most new browsers are going, I guess this is a moot point.