← All articles

What is a podcast episode tag?

Explore this article with AI

Open a source-aware analysis with this article as the primary source.

ChatGPTClaudePerplexityGeminiGrokGoogle AI
Follow Podder on Google

Add us to your Preferred Sources.

A podcast episode tag is item-level RSS metadata that assigns a decimal episode number to one release. Written as <podcast:episode>, it requires a numeric value and can include a short display label that listening apps are encouraged, but not required, to show instead.

This tag belongs to the Podcast Namespace. It does not replace the episode title, publication date, or unique identifier. It provides a structured numbering field for apps that read the namespace and choose to use it.

How the podcast episode tag works

The Podcast Namespace episode specification defines <podcast:episode> as a single element under an RSS <item>. "Single" means an item should have no more than one of these tags.

The text inside the element is its node value. That value is required and must be a decimal number. A basic numbered episode looks like this:

<item>
  <title>How we plan a six-part season</title>
  <podcast:episode>3</podcast:episode>
</item>

Your feed also needs the Podcast Namespace declaration before prefixed tags can be used correctly. Our RSS namespace explainer covers where that declaration sits and why the namespace URI, rather than the prefix alone, identifies the vocabulary.

What the display attribute changes

The optional display attribute supplies a listener-facing label. The numeric node value remains in place for numbering and sorting, while a supporting app can show the label in its interface.

<item>
  <title>The overnight recording</title>
  <podcast:episode display="Day 5">9</podcast:episode>
</item>

Here, 9 is the decimal episode value and Day 5 is the alternate label. The specification encourages apps and aggregators to display Day 5 instead of the purely numeric value. It does not require them to do so, so the episode title still needs to make sense when the label is absent.

Keep the display value at 32 characters or fewer. The official documentation says not to exceed that limit. A compact label such as Ch.3, Bonus A, or Day 5 is a better fit than a second episode title.

When decimal episode numbers help

Decimal numbering is useful when a special release belongs between two numbered episodes. If you publish a mini-episode after episode 100 but before episode 101, the namespace allows this:

<item>
  <title>Listener questions from the break</title>
  <podcast:episode display="Mailbag">100.5</podcast:episode>
</item>

The value 100.5 preserves the episode's position between 100 and 101. A supporting app may show Mailbag to listeners while retaining the decimal value for chronological sorting.

Adding .5 to every bonus release can make the feed harder for your team to maintain, especially if your host already has its own episode-number field. Check the final RSS after publishing rather than assuming the value you entered reached the feed unchanged. The podcast RSS feed guide explains how show and episode metadata travel from a host to listening apps.

What the tag does not do

The tag provides structured episode numbering. It does not define whether a release is a trailer, bonus episode, or full episode, and it does not control where an app places that release. Those jobs use other metadata. For example, the podcast trailer explainer covers trailer classification and placement separately.

It also does not identify the episode uniquely. Titles and numbers can be edited or reused. An RSS item still needs its normal identity and delivery fields, including a stable GUID, publication information, and an enclosure for the media file.

Do not assume every listening app reads <podcast:episode> or honors display. The namespace document describes the tag's format and recommends UI behavior, but app support varies. Your title and core RSS fields should remain understandable without the tag.

How to check your implementation

Publish or update a test episode, then open the raw RSS feed and find that episode's <item>. Confirm these points:

  1. There is only one <podcast:episode> element in the item.
  2. The node value is present and decimal, such as 12 or 12.5.
  3. Any display value is a string no longer than 32 characters.
  4. The feed declares the Podcast Namespace used by the podcast prefix.
  5. The episode title still works if an app ignores the tag or label.

This check tells you what your feed publishes. It cannot prove how every app will render the metadata, so inspect the episode in the specific apps that matter to your audience.

If you also want a consistent view of episode delivery after the feed is live, start with Podder Analytics. Keep feed validation and audience measurement as separate checks.

FAQ

Is the podcast:episode value required?

Yes. When you add the tag, its node value must be a decimal number. The display attribute is optional.

Can a podcast episode number contain a decimal?

Yes. The Podcast Namespace specification allows decimals such as 100.5, which can place a special release between episodes 100 and 101.

Will every podcast app show the display attribute?

No universal support is promised. The specification encourages apps and aggregators to show the display value instead of the number when the attribute is present.

Put it into practice

See who's actually listening.

Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.

Start free