Podcast content link tag: external content fallback
Open a source-aware analysis with this article as the primary source.
Add us to your Preferred Sources.

The podcast content link tag is episode-level RSS metadata that gives supporting apps a labeled link to content outside the app. Written as <podcast:contentLink>, it can provide a fallback or additional destination for an episode or live event, such as a YouTube stream. The tag requires an href URI and includes listener-facing text.
How the podcast content link tag works
The official contentLink specification says the tag indicates that content delivered by its parent is available at an external location instead of, or in addition to, presentation inside an app.
Its parent sets the scope. It can appear under an RSS <item> or <podcast:liveItem>, and multiple copies allow one event to name more than one external destination.
<item>
<title>Episode 42</title>
<podcast:contentLink href="https://www.youtube.com/">
Watch this episode on YouTube!
</podcast:contentLink>
</item>The href attribute is required and contains the URI. The node value is free-form text. It should explain where the link points or what it is for, giving the listener more information than a bare phrase such as "Click here."
The podcast RSS feed glossary explains the item structure that can contain this element.
Using contentLink with a live event
The specification uses live streaming as its main example. A feed may describe a live event with <podcast:liveItem> while also providing links to external versions of the stream. Those links can help when an app cannot handle the live content directly or when the publisher wants to offer another destination.
<podcast:liveItem status="live">
<title>Live recording</title>
<podcast:contentLink href="https://www.youtube.com/">
Open the live video on YouTube!
</podcast:contentLink>
<podcast:contentLink href="https://x.com/">
Open the event chat!
</podcast:contentLink>
</podcast:liveItem>In this example, the first link points to a stream while the second points to chat. A supporting app can use the link text to explain what it presents to the listener. The specification allows external content instead of, or in addition to, in-app delivery.
contentLink versus an enclosure URL
Both elements contain URLs, but they serve different jobs. An RSS enclosure identifies the media resource attached to an episode item, including attributes used for media handling. Our enclosure URL glossary covers that delivery path.
A <podcast:contentLink> points to content outside the application and carries a human-readable label. It does not replace the enclosure requirements for an ordinary playable podcast episode.
| Element | Main job | Listener-facing text | Feed location |
|---|---|---|---|
| `<enclosure>` | Identify the episode media resource | No node label | RSS item |
| `<podcast:contentLink>` | Offer labeled external content | Yes | Item or liveItem |
For example, an episode can keep its audio enclosure and add a content link to a video version. A live item can provide its native stream data and add a link to an external viewing page.
The podcast: prefix depends on the Podcast Namespace declaration in the feed. The RSS namespace glossary explains that relationship.
What the tag does not guarantee
App support varies. The specification defines the element, but a valid content link does not prove that every podcast app displays it or uses the same presentation.
It also does not prove that the destination is available, safe, public, or usable in the listener's region. A successful HTTP response can still lead to a removed video, private room, sign-in screen, or page whose purpose no longer matches the label.
The tag itself does not record clicks, viewing time, chat participation, or playback at the external service. Those events belong to the destination's own reporting and should not be combined with podcast downloads without clear source labels.
How to write and verify a content link
Choose an external destination tied directly to the episode or live event. Use the canonical HTTPS URL when the service provides one, and write a short label that names the action and destination.
Good labels include "Watch this episode on YouTube" or "Join the live chat." Avoid promising access that the linked page does not provide. If the destination requires an account, ticket, or regional availability, explain that on the destination page or nearby listener-facing copy.
After publishing, inspect the raw feed, confirm that each content link sits under the intended item or live item, and check the destination itself. Open every href in a clean browser session, compare the label with the landing page, and test at least one app that documents support. Repeat the link check before a scheduled live event and remove stale destinations when they stop serving the stated purpose.
For the podcast side of your reporting, Podder Analytics can add episode delivery context. Keep external clicks and viewing metrics labeled by their own source.
FAQ
What is the podcast content link tag?
It is an item-level Podcast Namespace element that points listeners to related content outside the podcast app, often as a fallback when the app cannot present that content directly.
Where can podcast:contentLink appear?
It can appear under an RSS item or a podcast:liveItem. Multiple contentLink elements are allowed for the same episode or live event.
What does podcast:contentLink require?
It requires an href attribute containing a URI. The element's text is a free-form listener-facing label that explains the link's destination or purpose.
See who's actually listening.
Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.
Start free