← All articles

Podcast publisher tag: link a show to its publisher

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 publisher tag links a show feed to the parent feed for the entity that owns or publishes it. Written as <podcast:publisher>, it gives compatible podcast apps a structured reference to that publisher feed instead of leaving the relationship in a show description or website link.

A publisher feed is a separate feed representing the publishing entity. The tag in the show feed points to it through one nested remote item. It does not hold a publisher name, logo, or list of shows by itself.

How the podcast publisher tag works

The official Podcast Namespace publisher specification defines <podcast:publisher> as a child of <channel>. Only one publisher element is allowed in a channel.

That element must contain exactly one <podcast:remoteItem> with medium="publisher". Check the final XML because the wrapper and nested reference have different roles. The remote item identifies the publisher feed:

<channel>
  <title>Field Notes</title>
  <podcast:publisher>
    <podcast:remoteItem
      medium="publisher"
      feedGuid="003af0a0-6a45-55cf-b765-68e3d349551a"
      feedUrl="https://example.com/publisher.xml"
    />
  </podcast:publisher>
</channel>

The nested remote item supplies the publisher feed address. Check that structure in generated RSS, especially if your host exposes publisher settings through a form rather than raw XML.

For the broader role of added RSS elements, read our guide to RSS namespace podcast metadata. The publisher tag uses that extension model without changing the standard channel title, description, or episode items.

Required structure and attributes

The publisher contract is short, but each part has a specific job:

PartRequirementPurpose
`<podcast:publisher>`One per channelDeclares the link to the parent publisher feed
`<podcast:remoteItem>`Exactly one inside publisherPoints to the publisher feed
`medium="publisher"`Required for this useIdentifies the referenced feed as a publisher feed
`feedGuid`Required by remoteItemIdentifies the remote feed with its Podcast GUID
`feedUrl`Highly recommended hereGives apps a direct publisher-feed URL

The remote item specification generally prefers feedGuid for addressing another feed. The publisher specification also highly recommends feedUrl for the widest compatibility. Including both gives a capable app the stable GUID and a direct URL when GUID resolution is unavailable.

Do not place several remote items inside one publisher element. A publisher element with two candidate feeds breaks the documented exactly-one structure. If the publisher feed moves, update the URL while retaining the same feed GUID when it is still the same feed.

The referenced feed's medium is part of the contract. The podcast medium tag explains how a feed declares its content type. In this case, the remote item says publisher so an app knows what kind of feed it should expect before fetching it.

What the tag tells an app

The publisher tag tells an app where the show's parent publisher feed is located. The specification describes this as useful when a parent publishing entity wants to attest ownership over the podcast feeds it owns or publishes.

Presentation depends on the app. Valid XML does not guarantee a publisher page, network badge, grouped catalog, or any other particular interface.

The relationship also differs from ordinary podcast network membership language. A network name written in prose may describe a sales, production, or distribution arrangement, while <podcast:publisher> points to a publisher feed with a defined RSS structure. Our overview of podcast network membership covers the broader business label.

How to add and verify the publisher tag

Start with the canonical URL and Podcast GUID of the publisher feed. Add one <podcast:publisher> directly under the show's <channel>, then put one self-closing remote item inside it. Set medium to publisher, add the publisher feed's feedGuid, and include feedUrl.

Open the public RSS feed after publishing. Confirm all of the following:

  1. The publisher element is under <channel>, not inside an episode <item>.
  2. Only one publisher element appears.
  3. It contains exactly one remote item.
  4. The remote item has medium="publisher".
  5. The GUID matches the publisher feed's Podcast GUID.
  6. The feed URL opens the intended XML without authentication or a redirect to an HTML homepage.

A general podcast feed cleanup pass can catch duplicated or stale metadata around the tag. After the XML check, inspect apps that claim support for publisher feeds. Feed validation confirms the structure you supplied; app inspection shows how one implementation uses it.

Once your publisher relationship is clean, start with Podder Analytics to review show performance separately from publisher-feed metadata.

FAQ

What is the podcast publisher tag?

It is a channel-level Podcast Namespace element that points from a podcast feed to the parent feed for the entity that owns or publishes the show.

What must podcast:publisher contain?

It must contain exactly one podcast:remoteItem element with its medium attribute set to publisher.

Should a publisher reference include feedUrl?

Yes. The publisher specification highly recommends feedUrl for the widest compatibility, alongside the remote item's required feedGuid.

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