Read more about how Google manages podcasts with multiple feeds.

If your podcast has multiple feeds, be aware that Google will try to group similar or identical feeds together and serve only one of them.Therefore you should be sure that, at minimum, the feed and the homepage, plus all audio file URLs in tags be using the same protocol (ideally HTTPS).

If your feed or homepage is hosted at one protocol (HTTPS) but the linked resources are hosted at another protocol (HTTP), Google Chrome will display a click-through warning to users before loading those resources, or possibly not allow them to be loaded at all. The RSS feed and all episodes should be located either on HTTP or HTTPS. Use either HTTP or HTTPS, but not both.A majority of the episodes must be in any of the supported audio formats and have the proper file name extensions.You can check by visiting your feed in an incognito window. The feed and audio files should not require any authentication or be blocked to Google in any way.You must provide an image for your podcast.We also recommend some additional tags for a better podcast experience. Some tags are not required to appear as a podcast in search, but are required to be eligible as a recommended podcast on Google surfaces. Feeds without all the required tags might not be indexed by Google. Include all the required podcast-level and episode-level tags.Google doesn't use all the RSS feed tags, but the examples on this page show the important ones. This RSS feed should be well-formed, and conform to the RSS 2.0 specification as much as possible.

Rss podcast meaning