Is a Podroll the same as a feed drop?

No. A Podroll is recommendation metadata in RSS. A feed drop publishes promotional audio or an episode into a feed.

What identifier does a Podroll use?

Each remoteItem requires the recommended show's channel-level podcast:guid. A feed URL and title may also be included as optional discovery and display hints.

What is a Podroll in podcasting?

Q: What is a Podroll in podcasting?

A Podroll is a list of podcasts that a creator recommends in the channel section of an RSS feed. Supporting apps can use it for creator recommendations or similar discovery features.

What is a Podroll in podcasting? A Podroll is a creator-selected list of recommended podcasts declared in a show's RSS feed. Supporting apps can display those entries as creator recommendations or shows a listener might like. The list is metadata, not an inserted episode or proof that anyone followed the recommendation.

What is a Podroll in a podcast feed?

The Podcast Namespace defines Podroll with a channel-level <podcast:podroll> element. Its Podroll specification says the element contains one or more <podcast:remoteItem> entries, with each entry pointing to a recommended show.

<podcast:podroll>
  <podcast:remoteItem
    feedGuid="917393e3-1b1e-5cef-ace4-edaa54e1f810"
    feedUrl="https://feeds.podcastindex.org/pc20.xml"
    title="Podcasting 2.0"
  />
</podcast:podroll>

The Podroll belongs under the RSS channel because it describes recommendations from the show as a whole, not inside an episode item. The podcast RSS feed glossary covers that structural difference.

How remoteItem identifies a recommended show

The remoteItem specification requires a feedGuid. For a Podroll, that value is the recommended show's channel-level <podcast:guid>.

A remote item can also include:

Attribute	Podroll use
`feedGuid`	Required stable identifier for the recommended feed
`feedUrl`	Optional fallback location for the feed
`title`	Optional display hint for people or apps
`itemGuid`	Available in remoteItem, but normally omitted from a show-level Podroll
`medium`	Optional hint when the remote feed is not a podcast

When both a feed GUID and feed URL are present, the namespace documentation tells capable apps to resolve and use the GUID. The feed URL remains useful as a fallback for an app that cannot resolve the identifier.

The title does not replace a lookup. The Podroll documentation says information discoverable from the GUID takes precedence when values differ, protecting the relationship when a show changes its title or feed address.

The GUID is for the show, not an episode

The Podcast Namespace GUID specification defines <podcast:guid> as a unique global identifier for a podcast. It sits under the channel and is meant to follow the show when its feed URL changes.

Do not substitute an episode item's ordinary RSS <guid>, which belongs to one episode and serves a different job. A Podroll's required feedGuid points to the recommended podcast itself.

Before adding a show, inspect its live feed or resolve it through a source that preserves the channel-level Podcast Namespace GUID. Podcast Index can help with catalog lookup, but the current feed remains the place to check publisher-declared metadata.

Podroll versus feed drop and directory list

A Podroll does not place another show's audio in your feed. A feed drop or cross-promo episode changes what subscribers receive as content. A Podroll adds a recommendation relationship that supporting software may choose to display.

It also differs from a directory's editorial collection. A podcast directory may rank, categorize, or feature shows under its own rules. A Podroll originates with the recommending feed, though each app decides whether and how to use it.

The live feed can confirm that you published an entry. App display, position, clicks, and follows require their own evidence.

How to publish and verify a Podroll

Choose shows you can recommend clearly and review the list with the same care you would apply to links in show notes. For each show, record the channel-level podcast GUID, current feed URL, display title, date checked, and reason for inclusion.

Then run a short verification sequence:

Add one <podcast:podroll> block under the channel.
Add one <podcast:remoteItem> for each recommended show.
Confirm every feedGuid against the intended show, not an episode.
Include feedUrl and title when your publishing system supports them.
Validate the RSS and inspect the raw live feed after publication.
Check the show in at least one app that supports Podroll display.

Recheck the list on a schedule and whenever a recommended show changes ownership, title, or editorial direction. A stable GUID preserves identity across feed moves, but it cannot tell you whether the recommendation still fits.

If an app ignores Podroll, validate the live feed before changing the entry; when an app shows stale information, compare its resolved record with the current feed before editing a correct source entry.

For promotion beyond feed metadata, use the campaign methods in our podcast marketing strategies guide. Keep Podroll presence, app display, referral traffic, and audience growth in separate report fields.

Start with Podder Analytics to watch episode delivery while you evaluate Podroll support and referral evidence separately.