Consolidate and Localize Your WordPress Feeds

Published Monday, May 26, 2008 @ 3:30 pm • 0 Responses

[ ~{*}~ ] 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:

  • Inconsistent presentation of the site’s main feed as either the Feedburner URL or the WordPress URL
  • Offering feed links for every different type of feed format (e.g., RSS 2.0, RSS 0.92, Atom)
  • Each of the many different site themes featured an inconsistent mix of different feed URLs
  • Inconsistent placement of feed links throughout the site
  • Inconsistent placement of feed links throughout several older themes
  • Inconsistent reference to feed URLs within posts, pages, and other database-driven content

Eventually, as I began to realize the importance of providing consistent feed linkage, I began to consolidate the myriad feed formats into a single, canonical feed. I ended up choosing RSS-2.0 formatted feed simply because it is the one redirected to my Feedburner feed. In addition to this, I also went through each one of my different theme’s and optimized the presentation of feed links. These steps alone greatly improved the consistency of my site’s feed delivery. Then, during the design of the site’s current default theme, I finally got serious about feed canonicalization: only two feeds are provided (one for content and another for comments), and they are presented in the same location throughout the site. At this point, I felt that more work needed to be done, however overall feed uniformity had been much improved, so I moved on to other, more pertinent business.

Several months since then, I finally took the time to follow-up and finish the job. After all, the project remained on my ever-expanding “to-do” list, and would certainly improve site usability and overall sharpness. Essentially, the process of consolidating and localizing your site’s feeds involves the following process:

  • Determine the main (canonical) feed URL(s) that you wish to serve (e.g., one for comments, one for content).
  • If using Feedburner, the main feed URL(s) that you choose should be the locally generated WordPress URLs. These should then be redirected to the corresponding Feedburner address.
  • Once you have decided on which feed URL(s) to use, all references to any other feed link, format, URLwhatever — should be replaced with your canonical feed URL or else removed entirely.
  • Using a comprehensive guide, make a list of every non-canonical feed URL (e.g., different formats, redundant resources) to facilitate the search process.
  • Using your “rejected URL” list and a decent file-search program (e.g., Dreamweaver), execute a comprehensive search for each of the listed URLs. Replace or remove each discovered item according to your predefined strategy.
  • Now repeat the search process with your database. Using phpMyAdmin (or whatever you prefer), search your database for all instances of the listed URLs. As before, replace or remove each discovered item according to your predefined strategy.
  • Once this localization and consolidation process is complete, make it a point to refer only to your preferred, canonical URL(s).

Granted, cleaning up convoluted feed linkage is a tedious, time-consuming process. If possible, know what you are doing before diving into the whole blogging game and serve only canonical feed URLs from the outset. Doing so will save time and make it easier for readers to subscribe to your site. Otherwise, for dinosaurs like myself that just “make it up as we go along,” there is no time like the present to streamline syndication and improve consistency.



Share your thoughts..

TopRead official comment policy

Contact Perishable Press

  • Contact Jeff via form

Search Perishable Press

About Perishable Press

Perishable Press is the virtual playground of Jeff Starr — visionary, founder and lead developer of Monzilla Media, a small web and graphic design company in the lush desert oasis of Moses Lake, Washington. Perishable Press features articles and tutorials on many aspects of digital design..

Read more..

Perishable on Twitter

automation is great: i've got photoshop batch processing 300+ images while FTP is simultaneously uploading them to the server..

Perishable on Tumblr

Tons of Firewalls

Tuesday, 7 October 2008, 1:45 am

Recently overheard on conservative talk radio (instructing listeners how to obtain a free promotional video from their new website):

“This website has tons and tons of firewalls, so you have to use your real email address to download the video..”

The Quiet Search Revolution

Monday, 6 October 2008, 12:15 pm

Just a thought.. As awesome as Google is these days, it would suck if they ended up owning the entire search-engine business. When they get to the point where all competition is impossible (due to their sheer size, financial resources, media influence, etc.), how many alternate search engines will have the resources for continuous improvement and top-quality search results? When this happens, we will have no choice but to do exactly what Google tells us to do.

As deeply ingrained as it is for everyone to instinctively and unthinkingly turn to Google for their search activity, it is time to leave a few alternate search tabs open for as much use as possible. Instead of using Google just because that’s what you always do, try your search on MSN, Yahoo, Ask, or any of the other independent search engines instead. Sharing traffic with other search engines is a nice, quiet way to keep the competitive spirit alive and well in the search-engine business.

Disappearing WordPress Posts

Wednesday, 1 October 2008, 7:50 pm

Today I experienced difficulties while trying to publish or even save new posts in WordPress. I would compose the post as usual, add all of the keywords, tags, meta tags, and so on, but as soon as I clicked the “Publish” or “Save” button, the post would just disappear from existence.

The weird thing is that during the drafting process, WordPress’ default auto-save feature showed that the post had been saved at expected intervals. Unfortunately, after trying to publish several different posts, WordPress showed absolutely no record of the posts ever being created. They simply vanished into thin air.

Fortunately, a little investigation revealed the culprit. If you should find yourself dealing with this same issue, here are some different things that you should try. First, re-upload fresh copies of your entire WordPress installation. I don’t know why exactly, but apparently various files can either go stale or completely disappear from the server. Overwriting or writing fresh files may do the trick.

If that doesn’t work, check your WordPress database for errors. In my case, a little investigation revealed that something had caused a couple of fatal errors in the wp_posts table. Fortunately, checking and repairing the table solved the issue.

Tumblr Battles

Wednesday, 1 October 2008, 5:30 pm

Please excuse the duplicate Tumbr posts.. seems there is no way to ping Tumblr to refresh/rebuild the RSS feed according to changes in post content. So, to resolve the issue I have discussed now like two or three times regarding paragraph elements and proper feed formatting, I have no choice but to repost a majority of my text posts.

This is necessary for the proper import and display of my Tumblr feed into WordPress. Currently, there are five items displayed at once, each styled according to proper inclusion of paragraph tags. Thus, whenever the Tumblr feed “forgets” to enclose single-paragraph posts with the proper tags, the result is an unstyled post entry displayed on my site.

Assuming that makes sense, you will please excuse my dust while I repost a few older entries in an attempt to reconstruct (the hard way) a properly formatted Tumblr feed.

More Optimization Measures

Wednesday, 1 October 2008, 5:27 pm

Another important step in improving the performance of my recent redesign involves the optimization of both CSS and JavaScript content. During development there were around 15 server requests for these two types of files, 10 JavaScript files and 5 CSS files. This was okay for my own use, but would not work for production purposes.

Optimizing these file types involves consolidation, compression, and caching. Consolidation of 10 JavaScript files into three is huge improvement. Now I deliver one JS file for the functionality of the site, one for Mint, and another for Analytics. Likewise for the stylesheets; after consolidation, a single stylesheet is delivered to all modern browsers. There are two additional stylesheets as well, but they are targeted at IE6 and mobile browsers and will not load elsewhere.

Once the files were consolidated as much as possible, it was time to optimize or “crunch” them. Using the sexy Flumpcakes CSS optimizer, I was able to reduce my stylesheets by around 25%. Likewise for JavaScript, I used xtreeme.com’s optimizer to shave an additional 20% off the size of my JS content.

Finally, once I had consolidated and compressed my JS and CSS files as much as possible, I wanted to further my optimization efforts by ensuring that these files were cached by the browser. By setting far-future Expires headers for everything but the statistical files, my site gains an additional performance boost by eliminating the need to reload preexisting content.

Read more on Tumblr..

Subscribe to Comments Recent Dialogue

  • Adam Singer: Thanks for this. You're right, if it isn't broken, don't fix it. I was about to update my permalinks and install a plugin to redire...
  • Marilyn: It looks great on my browser! I wish I had that much creativity in my head! It's gorgeous!...
  • Randy: "Too girly?" It looks like a great design. Define "too girly!"...
  • Christopher Ross: .htaccess based redirects are wonderful. I'm always baffled by web professionals who don't take the time to learn more about them....
  • federico: Hi Jeff... tnx so much...it worked perfectly... c u Federico...
  • Cooltad: The skin seems (mostly) fine in my expert opinion. Your one of the few people able to make a design with a transparent table and a b...
  • Neal: The free Intro to Linux book is a great place to start http://www.ischool.utexas.edu/mirrors/LDP/LDP/intro-linux/html/index.html ...
  • Louis: @Jeff: Your “Archives” page is slick, although I would expect a cleaner implementation from such a vehement advoc...
  • Jeremy: Well I think that you may be over-critical, I don't see a darn thing wrong with it - I like it a lot!...
  • Jeff Starr: Alright, this is exactly the kind of information I was hoping to get. Lots of great ideas and recommendations here. I will be reading...

Read more recent comments..