Putting The Simple Back In Podcast RSS Feeds

Subscribing to a podcast should lead to frictionless listening. That’s true for present and future episodes, but what about those from the past? It may be time for us to move past our one-size-fits-all approach to feed management.

May 6, 2020

Article

This is not about getting rid of RSS feeds. This is about better ways to utilize RSS feeds to keep the friction low for podcast listeners. I know I've raised the specter of podcasting moving beyond RSS feeds t some point. But that's not today’s topic.

It’s not an overstatement to say podcasting would not exist without RSS feeds. The magic power of an RSS feed is enabling the process by which people get new content and then listen to that new content. The magic of an RSS feed is manifested on the listeners’ end via a podcast listening app. They subscribe to a feed in their app of choice. That app then checks the feed to pull down new content. And the app makes it so the listener simply has to press play to listen to that new content.

I wrote the word “new” four times in the preceding paragraph on purpose. Because RSS feeds are great at connecting listeners to current and future episodes. So great, in fact, that listening to current and future episodes is nearly frictionless

But they’re less great when it comes to back-catalog content.

Many would argue against my supposition. After all, there’s no theoretical limit on the number of items that can be added to an RSS feed. Even for shows with more than a thousand episodes, they can still have a single RSS feed that contains all episodes.

But, as I discussed on Monday’s episode, trying to listen to extensive back catalog episodes inside of a podcast listening app is a horrid experience.

But we can make it better if we think about RSS feeds from a slightly different perspective.

Real-world Examples Where Choice-limitation Is A Good Thing

At some point in your life, you have walked into a library. When you did that, you did not find books organized by recency. Sure, you probably saw a promotional “new arrivals” shelf. But you did not find books on shelves organized by the month in which they arrived at the library, going on for row after row of books sorted by arrival date, all the way back in time to the very first book procured by the library.

Because that would be a terrible way to manage library content for library patrons.

Think about the menu of your favorite restaurant. You know it’s not a complete list of everything the chef knows how to make. In many cases, it’s not indicative of only what you can order. I order off-menu all the time.

When you go shopping for new clothes, you know that what’s on the showroom floor is backed up by a stockroom with more sizes and sometimes even more styles. And, of course, the store is connected to a distribution center filled with even more choices for you.

Those examples make the case for segregating content into two buckets:

What We Want People To See Right Now
Other Options We’ve Moved Out Of The Way As To Not Overload People With Too Many Choices

Yeah, I should come up with shorter names for those buckets. But here we are.

We podcasters can do this too. The solutions is multiple RSS feeds:

The List Of Episodes We Want To Display To New And Current Listeners
Well-organized Archived Or Back-catalog Content For Listeners Who Want To Dig
Another Batch Of Well-organized Back-catalog Content For Listeners Who Want To Dig Even More

Again, I’m not crazy with those names. But you get the idea. I hope?

Conventional Podcasting Wisdom Says This Is Stupid

Right now, conventional wisdom says that a podcast’s RSS feed should be complete with all available episodes.

Conventional wisdom also probably thinks that having multiple RSS feeds for the same podcast would lead to confusion among new would-be-subscribers.

But bear with me, as I think there’s a simple solution that eliminates confusion.

I’m A Much Bigger Fan Of Advancing Podcasting Wisdom

It starts with the main RSS feed for a show. That main RSS feed must always be current. Every new episode -- full, trailer, or bonus -- is published to this feed. This main feed, as well as the directories and listings the feed powers, is the one that is promoted by the podcaster. It’s the one that’s linked to from the podcast’s website. It’s the one that is sent when someone asks “how can I subscribe”.

Anyone brand new to the podcast should be subscribed to this, the main RSS feed.

This re-imagined main feed does not contain every episode your show has ever produced. It only contains enough episodes to satisfy the needs of a new subscriber. No, I don’t think you should only have the most current episode in this feed. We still have to consider how the feed causes the show to appear in podcast listings and directories. Take out too many episodes, and suddenly a show looks less impressive.

But this only works if the main feed is accompanied by another archive feed and the subsequent listing of that archive feed on all podcast directories and apps. Perhaps even multiple archive feeds and their listings.

This requires some strategic thinking on the part of podcasters. How “full” should your main RSS feed be? How do you decide where to break content? Do you need more than one archive feed?

We Have To Get The Naming Conventions Correct Or This Fails Miserably

If the episodes of your show are already aggregated by seasons, your decisions get a lot easier. Imagine a directory listing of the following feeds:

Podcast Pontifications: Season 3
Podcast Pontifications: Season 2 (July 2019 - May 2020)
Podcast Pontifications: Season 1 (July 2017 - June 2019)

That doesn’t seem all that confusing to me. Yes, I know we’re at the whim of Apple or other directory owners who have clear guidelines that I’m ostensibly breaking. But those guidelines exist to weed out bad actors and spammers. The changes I’m suggesting here increase the clarity and usability of podcasts in their catalogs. So I’m betting they’ll be OK with it.

If you don’t do seasons, then what about years? Apple Podcasts already segregates episodes for un-seasoned podcasts by years. But here, I’m suggesting you do it by year of your release, much in the way that Chris Christensen was doing for the Amateur Traveler Podcast (here’s his 2012 archive listing on Apple Podcasts).

Again using my show as an example, breaking out feeds by years would look like this in directories or apps:

Podcast Pontifications
Podcast Pontifications Archive: 2019
Podcast Pontifications Archive: 2018
Podcast Pontifications Archive: 2017

Both of these systems work and are fairly simple to implement. Sure, it takes a little maintenance on the part of the podcaster. But nothing too arduous, I hope.

The Huge Misstep That’s Easy To Make That You’ll Want To Avoid, Podcasters!

This is really important: Never make a new RSS feed for your next season or the next year. Never do that. If you make a new feed for new content, people will have to subscribe to that new feed. You do not want to ask people to subscribe to a new feed. Because most -- the vast majority -- will not. That’s the opposite of “frictionless”.

Instead, you’ll simply rename the main feed, if warranted. In my example, I’m still in Season 2. So if I implement this new way of approaching RSS feeds, I’d call my current feed “Podcast Pontifications: Season 2”, without the date range. And, obviously, I’d make a new feed for Season 1 content, naming it appropriately and removing all S2 content from this new archive feed.

Before I launch Season 3, I’ll create a “new” archive feed with only episodes from season 2. I’d name the new archive field appropriately and submit the new feed to all the directories. Only then would I go in and rename my main feed “Podcast Pontifications: Season 3”, removing all the S2 episodes so it only contained the trailer episode for Season Three.

Confused? Don’t be. It’s just following a good procedure so that listeners aren’t confused. That’s what’s important. Oh, and this needs to be said one more time:

Never make a new feed for brand new content. Not if you want to keep subscribers.

Other Considerations To Help Make Podcast Listeners Love Your Big Catalog Even More

There are other aspects which might help. Like adding a season-ending trailer to the archived feeds where you tell people that there’s more archived content on another listing and that there’s still a current listing in the same app if they haven’t already discovered it.

There might be different naming conventions. Like the show my wife and I created when were traveling around the world. Maybe we create a feed with subsequent directory listings called “The Opportunistic Travelers Archive: The Thailand Years (2016 to 2018)”? That's descriptive enough so that people would know what they're getting.

Best of all? We can do all this with the current architectural infrastructure podcasting relies on. We don't need to change the way RSS feeds work or how podcast clients ingest those feeds to make this happen.

This seems like a good idea to me. So much, that I'm going to implement it by the end of the week. Let me know if you’ll join me!

Also: please tell someone you know about Podcast Pontifications. Your word-of-mouth and personal recommendation goes a long way to bringing more listeners into the fold. So thank you in advance

If you’ve done that and want to help further, go to BuyMeACoffee.com/EvoTerra and slide a couple of bucks my way each month to support the show.

I shall be back tomorrow with yet another Podcast Pontifications.

Cheers!

Transcript

PP307 - Putting The Simple Back In Podcasts RSS Feeds

Evo Terra: [00:00:00] Subscribing to a podcast should lead to frictionless listening. That's true for present and future episodes, but what about those from the past? It may be time for us to move past our one size fits all approach to feed management.

[00:00:23] Hello and welcome to another podcast. Pontifications with me, Evo Tara. This is not about getting rid of RSS feeds. This is about better ways to utilize RSS feeds to keep the friction low for podcast listeners. I know I've. Been one of the voices saying maybe it's time for us to move past RSS feeds, but we're not there yet.

[00:00:51] That's not the conversation today. Today I want to talk about what we have, how we do it, and that's with RSS feeds and RSS feeds are wonderful. I really, really liked them. If it wasn't for RSS feeds, podcasting wouldn't be podcasting. We'd just be putting audio files upon the internet and hoping people would listen.

[00:01:10] But as we all know, the magic of an RSS feed is, as I said previously, it lowers the friction. It enables a very simple way for people to, number one, get content, and then number two, listen to that content. Now, of course, the feed in and of itself doesn't do that. You have to connect the feed to something, most likely a podcast listening app.

[00:01:35] Once someone is subscribed to the app, as we know they're going to get the content. And then within that app, it is very simple for them to press play. Great. Very great for current episodes, and also great for future episodes is frictionless. The content will show up on their device and with a single click they can listen.

[00:01:57] Great. But what about the archive? What about the back catalog? You could argue that it's all there in the feed and that with just a little bit more friction they can pay. The listeners can get and consume that content, and that's true to a point, but take this show for example. I have 300 I think there's 307 307 different episodes.

[00:02:34] That's more than the feed can handle. Maximum feed size inside of Apple podcast at least is 300 a feed can be as long as a feed needs to be, but the act of going back and listening to those old episodes is anything but frictionless. We had, it happens. From time to time. So I'm thinking about this and I'm thinking lots of weird thoughts on Monday.

[00:02:59] I talked to you about ways maybe we should recategorize things and why doesn't, why don't the podcast apps make it easier for us to categorize? And that's the kind of a high minded thing. But today is more of a real thing, a real way we can fix this. But I want you to think about it from a couple of different perspectives.

[00:03:17] Let's think about a library. Whenever the last time you walk into a library was, but at some point in time in your life, you have walked into a library and at no point did you walk into a library and discovered their books were shelved by release date with the most recent books up front, and then row after row of bookshelf going back through the stacks all the way to the beginning book they put in the library.

[00:03:42] Of course not. That's a terrible way to manage library content. Think for a moment about the last time you were at a restaurant and you looked at the menu, and that menu, as many of you know, is not a complete list of everything the chef knows how to make, nor is it in many cases, all that indicative of only what you can order.

[00:04:10] I like to order off menu all the time. Think about the last time we were in a clothing store and you saw the racks and racks of clothes they had out for you to look at. You know that there's a warehouse in the back, right? More sizes, sometimes even more styles, and of course that's connected to a distribution center with all sorts of things which are not available in that store.

[00:04:41] So what I'm talking about is utilizing an RSS feed to differentiate between content you want to display right now to someone and content for other purposes, content for the archives, content for the back stuff. Right now we have this mind that RSS feeds should be complete. It should have the entire show in it, but I'm wondering.

[00:05:09] If that's right, maybe the solution is to do something different. Maybe it's multiple RSS feeds for a show. I know you're thinking about the confusion that might ensue, but, but bear with me, I think I have a solution for the confusion. Maybe the main RSS feed that you have is current. And it's where you're always going to publish new episodes.

[00:05:40] It's certainly the one that you promote. It's the one you link to from your website. It's the one that you mail to people. It's the feed that powers the show. Anybody brand new should be listening to this feed. Do you need to have 300 episodes in that feed? I don't think you do. I think you can have other feeds.

[00:06:06] Yeah. Multiple feeds for your show. For people who want to get other content. Again, the primary feed, the primary feed. What do you want people to listen to right now? What is the important stuff that's out there? Not just the most recent episode, but you know a catalog of stuff people can listen to because you want it easy for them to go back and listen to some, but remember, once you get past some a dozen.

[00:06:34] It becomes very arduous to scroll back and scroll back and scroll back. It's just, sorry. Podcasts. Apps aren't designed for going back and looking at older content. They're just not. So what if you do this? What if you make your main feed, which has, and I think the easy way to do it is your current season.

[00:06:54] If in fact you're using seasons, and if you're not using seasons, then make it the current year 2020. As of this recording, we are just started our fifth month into 2020 so if you release weekly shows, you should have a dozen or so episodes. You got several, you got a lot, you got enough to make a feed worthwhile.

[00:07:16] Maybe that's what goes in your main RSS feed, and then maybe you make another RSS feed that is your archive. Or actually, what if there are lots of different RSS feeds that are your archives. I mean take this show for a moment. Podcast pontifications what if the main show was still called podcast pontifications but then I had a secondary feed listed in all the podcast directories and maybe linked on my website, but probably hidden somewhere in an archive section.

[00:07:48] Maybe that feed is podcast pontifications archive season one and the 120 or so shows I did in season one. Are there. And just the shows from season two are in podcast pontifications see, in my case, because I do my show by seasons, I don't think I'd use the year long tag. I think I just at the beginning of a year, continue on my current feed.

[00:08:16] I'm not making a new feed. I don't want to lose people. So my main feed is always my most current stuff, but then the other stuff gets moved to one of the archive feeds and I produce a new archive feed and publish it to all the different directories. Maybe if it's not by seasons or years, maybe it's by what you did.

[00:08:33] Like when my wife and I were traveling around the world, maybe we have a feed that's called the opportunistic travelers archive. The Thailand years 2016 to 2018 that's descriptive enough. People would know what they're getting and the best thing we can do all this with current. Existing architectural infrastructure.

[00:09:00] We don't need to change the way RSS feeds or podcast clients or anything really work in order to make this happen. I'm thinking about this. In fact, I'm thinking about doing it. Want to join me? Let's see how this can work out. Hey, one thing real quick, tell someone you know about this. Show your word of mouth.

[00:09:21] Your personal recommendation goes a long way. And if you really want to help me go to buy me a coffee.com/evo Tara and slide a couple of bucks for support to the show on a regular basis. I shall be back tomorrow with yet another podcast. Pontifications cheers.

‍

More Episodes About

Listener Experience

Taking The Creepy Out Of Personalized Podcasts

Personalization of podcasts is filled with pitfalls, including a well-deserved reputation of being creepy. But the true benefits of personalized podcasting have nothing to do with making ads better.

Tweaking Your Serialized Podcast For More Listener Love

Every rational podcaster with a story to tell wants to create a good listening experience. Sadly, misconceptions or lack of attention often block listeners from engaging further. But we can fix that.

The Gateway Drug To Podcasting Is You

Podcasting may look hot, but it’s still one of the slowest growing mediums ever. As podcasters, we’re partly to blame. Here’s how we can fix that without changing how we make our own shows.

View All