Over a million developers have joined DZone.

Parsing RSS Feeds in JavaScript — Options

· Web Dev Zone

Start coding today to experience the powerful engine that drives data application’s development, brought to you in partnership with Qlik.

For a while now I’ve used the Google Feed API to parse RSS feeds in JavaScript. It did a good job of converting various RSS flavors into a simple array of entries you could easily work with. Unfortunately, Google has deprecated the API and while it still worked the last time I used it, I would strongly recommend folks migrate their apps away from it as soon as possible. While this makes me sad, you have to move on.


So what kind of options do you have?

Parsing Manually

So, remember that RSS is just XML, and XML is just a string, and string parsing is easy, right? Of course, there are 2 major flavors of RSS, and multiple versions of both flavors, but if you’re just parsing one known RSS feed then you can write to that particular flavor and version. (More about the different versions can be found on Wikipedia.) Unfortunately, if you try to simply XHR to an RSS feed you’ll run into the lovely cross-origin browser doohicky that prevents you from making requests to another server. Of course, if the RSS is on the same domain, that isn’t a problem. And of course, if you are building something in Apache Cordova, then it isn’t a problem either. (Just don’t forget to update the CSP!) And finally, if you control the RSS, you can add a CORS header to it so modern browsers can use it. Unfortunately, if none of those apply, you’re out of luck trying to do it completely client-side. (Well, until we get to the next options!) Let’s pretend that none of the roadblocks apply to you and look at a simple example. (As a quick note, none of my sample code will actually render anything. It will just get crap, parse it, and log data. I’m assuming folks know how to manipulate the DOM. I’ve heard there’s a good library for that.)

$(document).ready(function() {
//feed to parse
var feed = "http://feeds.feedburner.com/raymondcamdensblog?format=xml";

$.ajax(feed, {
success:function(data) {
//Credit: http://stackoverflow.com/questions/10943544/how-to-parse-an-rss-feed-using-javascript

$(data).find("item").each(function () { // or "item" or whatever suits your feed
var el = $(this);
console.log("title      : " + el.find("title").text());
console.log("link       : " + el.find("link").text());
console.log("description: " + el.find("description").text());



So, all I’m doing here is using jQuery to request my RSS feed. I then use jQuery’s built-in XML parsing to iterate over the <item> blocks in my RSS feed. As you can see, I’m using sample code from a StackOverflow answer that I modified a tiny bit. Specifically, the answer iterated over <entry> blocks, not <item>. Remember when I said there were different flavors of RSS? That’s an example of the issue right there. If you must write code to handle both cases, you would need to look for <item> first and then <entry>. But that’s basically it. If your curious, I tested this in Canary with –disable-web-security as a command line flag.



Remember YQL (Yahoo Query Language)? The last time I blogged about it was way back in 2010 (Proof of Concept 911 Viewer). As a gross simplification, YQL acts like a “query language” for the web. You can literally run SQL like content against URLs and get formatted data out of it. They provide a powerful testing console and wouldn’t you know it, one of the examples is a RSS parser:


Just in case that screenshot is a bit too small, here is what the YQL statement looks like:

select title from rss where url="http://rss.news.yahoo.com/rss/topstories"

I’ve got one word for that. Bad ass! Like, kitten in armor bad ass!


I tested with two different RSS flavors and YQL had no issue handling either. Note the REST query URL at the bottom. I copied that into a new file:

$(document).ready(function() {

var yql = "https://query.yahooapis.com/v1/public/yql?q=select%20title%2Clink%2Cdescription%20from%20rss%20where%20url%3D%22http%3A%2F%2Ffeeds.feedburner.com%2Fraymondcamdensblog%3Fformat%3Dxml%22&format=json&diagnostics=true&callback=";

$.getJSON(yql, function(res) {
}, "jsonp");


And, it worked like a charm. Note the use of JSON/P to sidestep needing CORS. And here is the result:


A big thank you to Addy Osmani from Google for reminding me that YQL was still around. Google, I forgive you for killing the Feed API now.


Last but not least is a brand new service, Feednami, created just in time for the death of the Google Feeds API. To use it you simply add a new script to your code and then use feednami.load() to get your feed. Here is an example:

$(document).ready(function() {

var url = 'http://feeds.feedburner.com/raymondcamdensblog?format=xml';

if(result.error) {
} else {
var entries = result.feed.entries;
for(var i = 0; i < entries.length; i++){
var entry = entries[i];


That's also pretty darn easy to use. Here is the result:



So, you've got options. Which one is best? Honestly, I don't know. YQL requires the least amount of code from what I can see, but I kind of dig Feednami's look a bit more. If you've used any of these in production, drop me a comment below with your thoughts!

Create data driven applications in Qlik’s free and easy to use coding environment, brought to you in partnership with Qlik.

javascript ,rss ,xml ,web dev

Published at DZone with permission of Raymond Camden, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}