Podcast RSS Feed SEO: The Fields That Rank

QuickReel Team avatar
QuickReel Team22nd November, 2026
Podcast RSS Feed SEO: The Fields That Rank

Your RSS feed is the single file every podcast directory reads, but the fields that move discovery are a short list, and one of the most-optimized tags is dead. To rank, fill the feed fields Apple and Spotify actually index for search: your show title, author, category, and episode titles. The tag you may have stuffed does nothing on Apple, it was dropped from Apple's spec years ago. Below is a field-by-field audit of what is read, what is ignored, and what is worth your time.

There is a lot of recycled advice telling you to "optimize your RSS feed" without saying which of the fifty-odd possible tags any engine reads. Most of it tells you to load up fields that have been ignored since the iTunes era. This guide does the opposite: it sorts every meaningful feed tag into required, recommended, situational, or genuinely dead, names the source for each, and tells you the three fields worth real effort. Open your feed once, fix four things, and move on.

What is an RSS feed and why does it control discovery?

A podcast RSS feed is a public XML file your host generates. It lists your show metadata, title, artwork, category, author, and every episode. Apple Podcasts, Spotify, Amazon Music, and every other directory read that one file to display and index your show, so the feed controls what each platform knows about you.

You almost never edit the XML by hand; you change fields in your host's dashboard, and the feed updates. Each episode carries its audio URL inside an tag and a permanent GUID. That single-source design is why the feed matters for discovery. If a field is wrong or empty in the feed, it is wrong everywhere at once. And because each engine reads only specific fields for search, optimizing the wrong ones is busywork. The job is not to fill every tag, it is to fill the few that an indexer parses.

One feed, every directory A single RSS feed is read by Apple Podcasts, Spotify, Amazon Music, and Google. Fix a field once and it changes everywhere. Your RSS feed one XML file Apple Podcasts Spotify Amazon Music Google / YouTube Music Castbox, Player FM, …
One feed populates every directory. A field error in the feed is an error everywhere.
Illustration depicting Your RSS Feed and How It Affects Discovery

Which RSS tags do directories actually read?

Few of them. Apple groups its iTunes-namespace tags into required, recommended, and situational tiers, and treats an older set as dead but tolerated. For search specifically, the list is shorter still: Apple indexes your show title, episode titles, and the author field, not your description (Ausha).

The required channel tags are , , and ; the recommended ones are and ; the rest are situational (podcast-standard.org).

So the discovery-relevant feed is small. Get the required tags right so you pass validation and appear at all, then pour your keyword effort into title and author, which are the only fields a search query is matched against on Apple. Everything else is plumbing or polish.

The four tiers of iTunes-namespace feed tags Required: itunes:image, itunes:category, itunes:explicit. Recommended: itunes:author, itunes:owner. Situational: itunes:type, itunes:title, itunes:episode, itunes:season, itunes:episodeType, itunes:new-feed-url, itunes:block, itunes:complete. Dead but tolerated: itunes:keywords, itunes:subtitle, itunes:summary. Sort your feed tags before you touch one Required Recommended Situational Dead (tolerated) itunes:image itunes:category itunes:explicit itunes:author itunes:owner itunes:type itunes:title itunes:episode itunes:season itunes:episodeType itunes:new-feed-url itunes:block itunes:complete itunes:keywords itunes:subtitle itunes:summary Tiers per Apple, via podcast-standard.org. "Dead" = removed from Apple's spec, still present in many feeds.
The tag tiers. Source: podcast-standard.org "Apple Podcasts Tags," 2026.

The tags that are dead, and the ones that just look dead

The tag is the clearest casualty. It was dropped from Apple's official spec years ago and is ignored for Apple search and ranking; the only residual Apple use is occasional ownership verification, where Apple asks you to drop a code into the field to prove you control the feed (Transistor). It still appears in about 24% of show-level feeds (podcast-standard.org), a quarter of podcasters optimizing a field no major engine reads for search.

Two more sit in the same "dead but tolerated" bucket: and . Apple no longer relies on them, but some smaller apps still display them, so leaving them populated is harmless (podcast-standard.org). The distinction worth holding: dead for ranking is not the same as invalid. A legacy tag will not break your feed or fail validation. It just earns you nothing on the platforms that matter, while costing you the time you spent crafting it.

There is one honest nuance on keywords. Historically a few directories, Castbox and Player FM among them, did still read the keyword tag, so adding a short, accurate list is not actively harmful (Transistor). Treat it as a five-minute afterthought, never a strategy. And do not solve the dead-keyword field by stuffing keywords into your title instead: Apple penalizes shows that pack keywords into searchable fields, and people have been removed from Apple Podcasts for it (The Audacity to Podcast).

Presence of each tag across real feeds itunes:image 99 percent, itunes:author 99 percent, itunes:category 99 percent, itunes:summary 79 percent, itunes:episodeType 85 percent, itunes:keywords 24 percent, podcast:transcript 6 percent. What real feeds actually contain itunes:image99% itunes:author99% itunes:category99% itunes:episodeType85% itunes:summary (dead)79% itunes:keywords (dead)24% podcast:transcript6% Share of feeds containing each tag. Source: podcast-standard.org tag-usage stats, 2026.
A dead tag (keywords) is still in a quarter of feeds; a useful new one (transcript) is in almost none. Source: podcast-standard.org, 2026.
Illustration for 'How to optimize your podcast feed in five steps'

How to optimize your podcast feed in five steps

Work these in order. The first three carry almost all the weight, and most take minutes in your host's dashboard.

  1. Front-load your primary keyword in the show title. The title is the single strongest search field on Apple (Ausha). "The Resting Heart Rate Podcast" beats a clever name that says nothing, but stay distinctive and avoid stuffing. See our breakdown of how Apple Podcasts search ranking actually works.
  2. Optimize the author field, it is indexed and underused. Apple reads the author tag for search, so lead it with your niche rather than only your name: "Endurance Coaching, Greg Wasserman." It reads slightly worse to a human and ranks meaningfully better.
  3. Write episode titles around what listeners search. Episode titles are indexed; "Ep. 47, Wild Wednesday" ranks for nothing. Lead with the topic phrase, every time. Our guide to episode titles that get found has the formats.
  4. Set category, explicit, and type correctly. Pick the most accurate (it is required and drives where you are browseable), set honestly, and use to mark the show episodic or serial so episodes order correctly.
  5. Add a tag per episode. This newer Podcasting 2.0 tag links a machine-readable transcript and is in only about 6% of feeds today (podcast-standard.org). It feeds Apple's and Spotify's in-app transcripts and gives indexers full text to read, a rare under-used edge. Pair it with a transcript-for-SEO setup.

Common feed mistakes that quietly cost you discovery

Most feed problems are self-inflicted and invisible until you look. These five are the ones I see most.

  • Optimizing dead fields. Hours on and a keyword-stuffed summary, none of which Apple reads for search (podcast-standard.org). Redirect that energy to title and author.
  • A brand-only title. "Beyond the Mic" is invisible for every topical search. If you will not rename, at least carry the topic in your author field and every episode title.
  • Wrong or missing category. It is a required tag and it controls where you can even be browsed. A mismatched category buries you in the wrong neighborhood.
  • Changing your feed URL without . Migrating hosts without redirecting strands your subscribers and resets your history. Use the new-feed-url tag during a move.
  • Editing a published episode's GUID. The GUID must never change; altering it makes directories treat the episode as brand new, duplicating it for listeners.
Illustration for 'Do Spotify and Google read the same feed fields as Apple?'

Do Spotify and Google read the same feed fields as Apple?

Mostly the same file, different priorities. Spotify and Amazon Music both read your and , so unlike Apple they reward a strong, keyword-aware description, do not write that field off just because Apple ignores it for search (podcast-standard.org). Google indexes your show and episode pages more like web pages, leaning on descriptions and transcripts.

The practical takeaway: write your title and author for Apple, your descriptions for Spotify and Amazon, and add transcripts for everyone. One feed, three audiences, no field wasted. For the platform-specific playbook, see Spotify podcast SEO.

Which fields each engine reads Apple search reads title and author. Spotify and Amazon read title, description, and summary. Google reads description and transcript. All read category. Write each field for the engine that reads it Apple search Spotify / Amazon Google - Show title - Author field - Episode titles - Category - Title - Description - itunes:summary - Category - Description - Transcript - Show/episode pages - Category Sources: podcast-standard.org; Ausha field tests. Apple does not index descriptions for search.
The same feed, read three ways. Source: podcast-standard.org; Ausha algorithm tests.

Where clips fit into all this

A perfectly tuned feed makes you findable; it does not make you found. Almost no new listener starts inside a directory's search bar, they meet a 45-second clip on Instagram or YouTube, like it, and search your name. Your front-loaded title and author are what they land on. Short-form video can drive up to 40% incremental new audience for video shows, and 57% of listeners now rely on social media for podcast recommendations, the first time it passed friends and family (Inside Radio).

The honest framing: fixing your feed is a one-time hour that removes a ceiling. Clips are the recurring work that fills the room under it. Do the feed audit this week, then spend your real effort on the distribution that brings searchers to the metadata you just cleaned up.

FAQ

Does the itunes:keywords tag still help podcast SEO? Not on Apple. The tag was removed from Apple's spec years ago and is ignored for search and ranking; Apple's only residual use is occasional ownership verification (Transistor). A few smaller directories historically still read it, so a short, accurate list is harmless, but it is a five-minute afterthought, not a strategy.

Which RSS fields should I actually optimize for discovery? Your show title and author field (the two fields Apple search indexes), your episode titles, and your description and for Spotify and Amazon (podcast-standard.org; Ausha). Front-load the keyword in the title and author; do not stuff.

Does Apple Podcasts read my show description for search? No. Independent field testing found the show and episode description has little to no measurable effect on Apple ranking, while title and author move it (Ausha). Spotify and Amazon do read descriptions, so still write them well, just for the right platform.

Will an old or deprecated tag break my feed? No. Legacy iTunes-namespace tags like and validate fine and will not stop your feed from being accepted (podcast-standard.org). They simply earn nothing for ranking. "Deprecated" means ignored, not invalid.

What is the podcast:transcript tag and should I add it? It is a Podcasting 2.0 tag that links a machine-readable transcript (VTT or SRT) for an episode. It is in only about 6% of feeds, yet it powers in-app transcripts on Apple and Spotify and gives indexers full text to read (podcast-standard.org). Add it, it is a rare, under-used edge.