You publish an episode, and within minutes or hours it appears in Apple Podcasts, Spotify, Overcast, Pocket Casts and dozens of other apps. Sometimes it takes much longer. Sometimes a show seems invisible in search no matter how good it is. To understand why, it helps to know what happens behind the scenes between your hosting platform and a listener's search box.
This guide explains, without jargon, how podcast directories and search engines discover your show, read your feed, notice new episodes, index your text and decide where you rank. It draws on how podsearch.org works, a full-text search engine built on the open Podcast Index catalog of about 4.7 million RSS feeds, but the same principles apply across the ecosystem.
The RSS feed is your show
Every open podcast is published as an RSS feed: a file at a web address, usually generated by your hosting platform, that lists your show's details and every episode. When you "submit your podcast to Apple" or anywhere else, what you are submitting is the address of that file.
Your feed contains:
- Show-level information: title, author, description, artwork, categories, language, explicit flag, owner name and email, and website.
- Episode-level information: title, description or show notes, publish date, duration, a unique identifier (the
<guid>), and the link to the audio file (the<enclosure>). - Optional extras: Podcast 2.0 tags such as transcripts, chapters, people, a permanent podcast GUID and Podping support.
Directories do not host your audio or store a master copy of your show. They read your feed, copy what they need into their own databases, and point listeners to your audio file. That is why updating your feed, at your host, updates your show everywhere eventually.
Step 1: discovery, how they learn your feed exists
A directory can only index feeds it knows about. There are a few routes in:
- Direct submission. You give the feed URL to a directory, such as Apple Podcasts or Spotify, through their creator tools.
- Open catalogs. The Podcast Index is an open, community-run catalog of podcast feeds. Many apps and services, including podsearch.org, use it as their source of feeds. The Podcast Index website lets you add a feed by its URL, and some hosting platforms submit new shows to it automatically.
- Host integrations. Many hosting platforms distribute to several directories when you tick a box.
- Crawling and links. Some services discover feeds through links on websites and from other catalogs.
What you can do: submit to the major directories yourself, make sure your show is in the Podcast Index (search for it on podcastindex.org or on podsearch.org), and put your feed URL on your website.
Step 2: crawling, how they read your feed
Once a directory knows your feed, it polls it: downloads the file periodically to see what changed. With millions of feeds, nobody can download every feed every minute, so directories decide how often to check each one.
Common approaches include:
- Adaptive schedules. Shows that publish often are checked often; shows that have not published in months are checked rarely. podsearch.org schedules polls based on how recently a show last published: a show that published within the last week is checked far more often than one dormant for a year.
- Conditional requests. Polite crawlers send headers (
If-None-Matchwith an ETag, orIf-Modified-Since) so your host can reply "not modified" without sending the whole file. Most hosts support this automatically. - Push notifications. Instead of waiting to be polled, your host can announce changes. That is what Podping does.
Podping: announcing your new episode
Podping is a notification system for podcast feeds. When your host updates your feed, it sends a "ping" with your feed URL, which is written to the Hive blockchain where any directory can watch for it. The project describes watchers seeing updates within about 20 seconds.
When podsearch.org sees a Podping for a feed it knows, it re-polls that feed right away, typically within seconds to minutes. Without a ping, your new episode waits for the next scheduled poll. Our guide to Podping explains how to check whether your host sends pings.
What you can do: choose a host that supports Podping, keep your feed fast and reachable, and avoid changing your feed URL without a proper redirect.
Step 3: parsing, how they understand your feed
Each directory parses your feed into its own records. This is where feed problems bite:
- Invalid XML (an unescaped
&in a title, a broken tag) can make some parsers reject the whole feed or skip episodes. - Missing or changing
<guid>values cause duplicates or lost episodes. The<guid>is how directories tell "a new episode" from "an edited old episode". If it changes, the episode looks new. - Wrong dates (future dates, or all episodes re-dated when you migrate hosts) confuse "latest episode" and sorting.
- Missing enclosures mean there is nothing to play.
Directories also derive information from your episodes: how many there are, how often you publish, whether the show is still active, how long episodes usually run. Inconsistent data makes these numbers wrong.
What you can do: validate your feed after any change and never change episode GUIDs. Our RSS feed hygiene checklist covers the details.
Step 4: indexing, what becomes searchable
Search engines turn your text into an index, a structure that lets them find episodes by the words in them. What gets indexed depends on the service. In podsearch.org, the indexed fields are:
| Field | Weight in ranking |
|---|---|
| Show title | Highest |
| Episode title | High |
| Show and episode descriptions | Medium |
| Episode content and transcripts, where available | Lower, and included in deeper searches |
That ordering is typical of podcast search: what you put in titles counts most, descriptions count, and transcripts help people find specific moments.
Transcripts make your spoken words searchable
If your feed includes a <podcast:transcript> tag for an episode, services that support it can index what you actually said, not just what you wrote in the notes. That helps listeners find you when they search for a guest, a place or a topic you discussed but did not put in the title.
Categories and language
Your categories and language, set in your feed, decide where you appear when people browse or filter. A show with the wrong language code may vanish from a listener's language filter; a show in a vague category competes with everything in it.
Step 5: ranking, why some shows come first
When someone searches, the engine finds all matching episodes and shows and orders them. Signals commonly include:
- Where the words match. A match in the show title or episode title ranks above a match buried in a description.
- How well they match. All the words, in order, beat some of the words scattered around.
- Recency, for searches where newer is better.
- Show signals, such as how established a show is. podsearch.org, for example, offers an option that prefers established shows and limits how many episodes a single show can contribute to one page.
Some directories also use proprietary popularity and engagement signals that are not visible from outside.
What you can do: put the words listeners would search in your show title (sensibly), write specific episode titles, and write descriptions that say what the episode is about in plain language. Our guide to podcast SEO goes further.
Step 6: labels and filters
Directories increasingly apply labels that affect where you appear:
- Explicit. Set by you in the feed. Listeners in safe modes will not see explicit shows.
- Duplicates. If your show exists under several feed URLs, a directory may merge or hide copies.
- AI-generated content. Some services label machine-generated shows. podsearch.org uses an LLM classifier and labels a show "likely AI" only when it is at least 0.9 confident; coverage is partial and on demand, and shows without a label simply have not been judged. Human-made shows that read their own scripts or use synthetic voices for small parts are not the target, but clear show notes and real host names in
<podcast:person>tags help any classifier.
Why your show might not appear
If listeners cannot find you, work through these common causes:
- The directory does not have your feed. Search for your exact show title. If nothing appears, submit it.
- Your feed is unreachable or invalid. Check that the URL loads and validates.
- You moved hosts without a redirect. The old feed should return a permanent redirect (HTTP 301) to the new one, and include
<itunes:new-feed-url>pointing to the new address, until directories have updated. - Your feed is blocked. A
<itunes:block>tag set toYesasks Apple not to list the show, and some hosts add blocking tags for private feeds. - The episode is too new. Without Podping, it may wait for the next poll.
- Your words are not where search looks. If the topic is only in the audio, add it to the title or description, or publish a transcript.
- Language or category mismatch. A wrong language code hides you from filtered searches.
How to check your show on podsearch.org
- Search your show title in quotes on podsearch.org. If your show appears, the feed is known.
- Search a distinctive phrase from your latest episode title to see whether it has been indexed.
- Try
title:"your show name"to search only show titles.
If your show is missing, make sure it is in the Podcast Index; podsearch.org picks up feeds from that catalog.
A timeline of a new episode
To make the process concrete, here is what typically happens after you publish, for a show whose host sends Podping:
| Time after publish | What happens |
|---|---|
| Seconds | Your host updates the RSS feed and sends a Podping |
| About 20 seconds | Services watching Podping see the notification |
| Seconds to minutes | Those services re-fetch your feed, parse the new item and index it |
| Minutes to hours | Directories that rely on polling reach your feed on their next scheduled check |
| Hours to a day | Slower or less frequent pollers catch up |
For a show without Podping, the first rows disappear and everything waits for each directory's next poll, which is sooner for shows that publish often. Either way, a valid feed with a stable GUID for the new episode is what turns a fetch into a correctly indexed episode.
The open ecosystem works in your favor
It is worth remembering why this system exists. Because podcasts are distributed by open RSS, no single company decides whether your show can be heard. Any app can read your feed, any search engine can index it, and you can move hosts without losing your audience, provided you redirect properly. The cost of that openness is that you are responsible for your feed's quality. The reward is that a clean, well-described feed is treated well everywhere at once.
Frequently asked questions
How long does it take for a new episode to appear in directories?
It varies by directory and by whether your host sends Podping notifications. With Podping, services that watch it, such as podsearch.org, can re-poll within seconds to minutes. Without it, you wait for the next scheduled poll, which is more frequent for shows that publish often.
Do I need to submit my show to every app?
No. Submit to the major directories directly; many other apps use the open Podcast Index catalog, so being listed there reaches them.
Why do I see duplicate episodes in some apps?
Usually because episode GUIDs changed, often during a host migration or a feed rebuild. Keep GUIDs stable.
Does the transcript really help search?
Yes, for services that index transcripts. It makes your spoken words searchable, which helps listeners find specific topics, guests and moments.
What happens if I change my feed URL?
Use a permanent HTTP 301 redirect from the old URL and the <itunes:new-feed-url> tag so directories update. Keep the redirect in place for as long as you can.
Can I see which directories have indexed my show?
Search for your show in each one. On podsearch.org, search the exact title in quotes or use title:"...".
Summary
Directories discover your feed, poll it, parse it, index your text and rank it. You influence every step: get listed in the major directories and the Podcast Index, keep your feed valid with stable GUIDs and correct dates, use a host that sends Podping, put searchable words in titles and descriptions, add transcripts, and redirect properly if you ever move. Do that, and your show is not just published but findable.