Manage your feeds

Read some background about how feeds relate to shows on Podcasts Manager.

Related topics:


How feed changes affect your show

Changes in a podcast's served feed do not occur often; however, when they do, you should verify ownership of the new served feed quickly to avoid losing new data.

If Google changes the served feed for a podcast:

  • If the newly served feed was previously verified for this show, the change happens invisibly to the show in Podcasts Manager (though you can see the new served feed in the feed history).
  • If the feed changes to a new, never-verified feed:
    • You will see a notification in your Podcasts Manager show about the feed change, with a prompt to verify the new feed.
    • Any episode that appears on both the old and new feed can no longer accrue listening data until ownership of the new feed is verified for the show. Listening data during this intervening period is lost permanently, though there is typically a 2-3 day grace period where you might continue to see data. Thus, a feed change will typically be visible as a dip in your show data; the faster you verify the new feed, the shorter the dip.
    • If you do not verify the newly served feed, data for episodes in the new feed will eventually go down to zero.

From the time that you send a verification code until you complete the verification process, all users will lose access to the show in Podcasts Manager. However, new data for the show is dropped from the time that the feed changes until you complete the verification process. Therefore, if you think that you can complete the verification process soon, send the code to continue aggregating data, even though you will lose access to the show until you complete the verification process. If you don't think that you will ever be able to complete the verification process, we recommend not sending the code, as you will lose access to the show until you complete the verification process.

See an example of a show's feed history over time.

Verify a feed
  • To verify the feed for a new show, follow the instructions to add a new show to Podcasts Manager.
  • If you have requested a verification code but have not received it:
    • Check your spam or filtered messages, to see if the email with the code was filtered out.
    • Be sure that you are checking the email account listed in the feed RSS file. The code will be sent to this email address.
  • If Google has changed the served feed for your show, you will see a notification in Podcasts Manager, with a link to the verification wizard. Anyone with access to the show can click the link and reverify the show. See How feed changes affect your show.
  • If you want to add a feed to an existing show, read this.
See your verified feed history

You can see a list of all served feeds that were successfully verified for your Podcasts Manager show. You can't see any feeds associated with the show before the show was claimed in Podcasts Manager.

To see your show's verified feed history:

  1. Click Settings Settings > Feeds on the show's homepage. Any feed listed was verified and served at least once for this show, during the lifetime of the show in Podcasts Manager.
See the served feed for your show

 To see the served feed for your show:

  1. Click Settings Settings > Feeds on the show's homepage to see a list of all feeds that were ever verified for your show. The currently served feed is marked Served.

If you see a warning that the show is now served from a different feed, click Verify new feed to see the URL of the new served feed in the verification wizard.

If you are not using Podcasts Manager, you can find the served feed for a show by subscribing to it in the Google Podcasts app, Click Settings More> View RSS feed  then copy the feed URL or click Open in Chrome.

Add a new feed to your show
You cannot arbitrarily add additional feeds to an existing show in Podcasts Manager.
Remove a feed from your show
You can't remove feeds from your show's feed history in Podcasts Manager. You can delete or block the actual RSS feed to prevent a feed from being used by Google, but any feed shown in your feed history will remain in the show's feed history.
  • If you want to move a feed to another URL, see here.
  • If you want Google to use another feed, see Change the served feed.
  • If you simply remove or block the show's current feed file, Google will promote another feed in your feed group as the served feed, if another eligible feed is available. If no other eligible feeds exist, your show will cease to be available on Google Podcasts, but will still be available on Podcasts Manager (although no new data will accrue, except from downloaded episodes).
Change the served feed

If you think that Google has chosen an incorrect feed to represent your podcast, you can file a request to change the served feed for your podcast. This process takes several weeks, and is subject to the discretion of Google.

To request that Google serve a different feed for your show, file a request using this form.​​​​​​

A note about custom feeds
You shouldn't try to verify ownership of custom feeds in Podcast Manager. A custom feed is a feed that is not accessible to Google because it is blocked, requires an access token, or is otherwise inaccessible to Google. Podcasts Manager cannot show any data for custom feeds, and these feeds are not available on Google Podcasts.

Feed FAQs

For help troubleshooting your feed issues, see the Troubleshooting guide

How can I tell Google which feed to served for my podcast?

What happens to my Podcasts Manager show if Google changes the served feed?

  • If you've claimed ownership of the served feed, and Google later selects a different feed, you'll see a notification in Podcasts Manager warning you about the change, with a link to verify the new served feed. (You'll also get an email telling you about the change). If you don't verify ownership of the new feed within a certain period of time, you will not be able to see any new data for the show, even if your (non-served) verified feed has some of the same episodes.
Was this helpful?
How can we improve it?