← All articles

Podcast remote item tag: point to another feed

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.

The podcast remote item tag points from one RSS context to another feed or to a specific episode inside that feed. Written as <podcast:remoteItem>, it tells a supporting app where to fetch the data requested by its parent element. The parent determines why the reference exists.

A remote item can identify only a feed, or it can add an item GUID to identify one item in that feed. It carries references, not a copied version of the remote feed's metadata.

How the podcast remote item tag works

The official Podcast Namespace remoteItem specification allows the element under <channel> and under three Podcast Namespace parents: <podcast:podroll>, <podcast:valueTimeSplit>, and <podcast:publisher>. Multiple remote items are allowed, though a specific parent can impose a narrower rule. A publisher element, for example, requires exactly one.

Inside a podroll, the remote feed's channel metadata is the target. A remote item inside another supported parent serves that parent's documented purpose. Check the enclosing element before interpreting the attributes.

Our guide to Podroll podcast metadata covers one common parent. For a wider view of extension elements and their prefixes, see RSS namespace podcast metadata.

Remote item attributes

Every remote item needs feedGuid. Four optional attributes narrow the reference or help an app decide how to handle it.

AttributeStatusMeaning
`feedGuid`RequiredThe `<podcast:guid>` of the remote feed
`feedUrl`OptionalThe URL of the remote feed
`itemGuid`OptionalThe standard `<guid>` value of a specific item in that feed
`medium`OptionalThe remote feed's Podcast Namespace medium when it is not `podcast`
`title`OptionalA title hint an app can display before doing a remote lookup

The specification prefers feedGuid because it identifies the remote feed through its Podcast GUID. Some apps may not have access to a resolvable GUID list, so feedUrl can provide a fallback. When both are present and the app can resolve the GUID, it should use feedGuid.

The optional medium gives the app advance notice when the target is not a standard podcast feed. That can affect how the app approaches fetching and display. The podcast medium tag explains the available content-type concept at feed level.

The title value is a hint. It lets an app show a name without first fetching the target, but it does not replace the remote feed or item's own metadata.

Feed references and item references

This example points to a remote feed:

<podcast:remoteItem
  feedGuid="917393e3-1b1e-5cef-ace4-edaa54e1f810"
  feedUrl="https://feeds.example.org/show/rss.xml"
/>

Add itemGuid when the reference should resolve to one item within that feed:

<podcast:remoteItem
  feedGuid="917393e3-1b1e-5cef-ace4-edaa54e1f810"
  feedUrl="https://feeds.example.org/show/rss.xml"
  itemGuid="episode-2026-11-03"
  medium="music"
  title="Live session"
/>

feedGuid and itemGuid identify different layers. The feed GUID comes from the remote channel's <podcast:guid>. The item GUID comes from the target episode's standard <guid>. Swapping them can leave an app looking for an episode where it expects a feed, or a feed where it expects an item.

A feed URL should lead to the remote RSS document. A show homepage is not a substitute. If the target feed changes location, update feedUrl while preserving feedGuid when the underlying feed identity has not changed.

What remoteItem does not guarantee

A correct reference tells an app where the remote data lives. It does not guarantee that the target URL is reachable, the GUID resolves in every app, or the app supports the parent element. It also does not copy or freeze the target metadata. An app that follows the reference retrieves whatever the remote feed currently exposes.

The element itself does not define a listening metric, referral count, or synchronization schedule. Keep any performance analysis separate. The podcast analytics guide explains how to label measurement sources rather than treating an RSS reference as listener activity.

How to verify a remote item

Open both source and target feeds as raw XML. In the source feed, check that the remote item sits under an allowed parent. In the target feed, copy the exact channel-level Podcast GUID into feedGuid. If you use itemGuid, copy the exact <guid> from the intended target item.

Then run a direct check:

  1. Open feedUrl and confirm that it returns the intended RSS feed.
  2. Match feedGuid against the target feed's <podcast:guid>.
  3. Match itemGuid, when present, against one item in that same feed.
  4. Confirm medium describes the target feed type.
  5. Keep title aligned with the target without relying on it as the identifier.
  6. Test the parent feature in apps that say they support it.

Once the references resolve cleanly, start with Podder Analytics for delivery reporting that stays separate from remote-item metadata.

FAQ

What is the podcast remote item tag?

It is a Podcast Namespace element that points to another feed or to a specific item in another feed so a supporting app knows where to fetch requested data.

Which podcast:remoteItem attribute is required?

The feedGuid attribute is required. It contains the podcast:guid of the remote feed.

What happens when feedGuid and feedUrl are both present?

A capable app should resolve and use feedGuid. FeedUrl is useful as a fallback when the app cannot resolve Podcast GUIDs.

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