Manage your feeds

Google might occasionally decide that the currently served feed is not the most representative feed for a show, and will start serving a different feed for that show. Google-initiated feed changes do not occur often.

How do I know the feed has changed?

If you are using Podcasts Manager, you'll see a notification for your show if you haven't verified ownership of the new feed. If you notice a sharp drop to zero in your listening minutes on Google, this is likely the reason. You will see a short, symmetrical dip in Google subscriptions for the show. This dip should correct itself automatically. This is simply an accounting artifact, and doesn't reflect any real change in subscriptions.

If you think a feed change has occurred, and you don't see a notification in Podcasts Manager, you can learn the current feed for your show to see whether it has changed (assuming you know which feed was served before).

What do I do if my feed has changed?

If Google has started serving a new feed for your show:

1. If using Podcasts Manager, open your show in Podcasts Manager and follow any instructions that you see promptly to avoid temporary data loss for your show.
2. Find out what is the newly served feed for your show
3. Make sure that you can capture listening data for the new feed.
   • If using Podcasts Manager to monitor your listening data, you'll be prompted to verify ownership of the new feed if necessary; if you don't see a prompt in Podcasts Manager, nothing more to do.
   • If using another service to monitor your listening data, make sure your new service is monitoring the newly served feed.

Additional information

When the feed changes, listeners will see the new feed automatically (see more details below) without any warning about the change. If your analytics are not set up to capture data for the new feed, you'll see a fairly steep drop to zero 

When a feed change happens (whether initiated by the publisher or Google), new subscribers (and listeners using the Google Podcasts website) will see the new feed immediately, but it might take a day or two to propagate feed changes to currently subscribed users on other apps or surfaces. This means that subscribed users might continue to see the old feed for a day or two after the change.

Google-initiated feed changes should not affect your subscriber count or listens. If your analytics service can't track both the old and new feeds, then you might appear to lose (or gain) listeners when the served feed changes, but this is only an accounting issue, not an actual change in user behavior.

In Podcasts Manager

If Google changes the served feed for a podcast, the following behaviors can be observed in Google Podcasts Manager for your show:

• You will see a short, symmetrical dip in Google subscriptions for the show. This dip should correct itself automatically. This is simply an accounting artifact, and doesn't reflect any real change in subscriptions.
• 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.
  • You might see a dip in listened minutes if you need to verify the new feed and this is not the result of a feed change that you initiated. This dip is an accounting artifact and doesn't reflect a dip in actual listened minutes.
  • 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, episode data for your show will eventually go down to zero, because Podcasts Manager only saves listening data if a show has a verified owner.
  • From the time that you send a verification code until you complete the verification process, all Podcasts Manager users will lose access to the show in Podcasts Manager (listeners on Google Podcasts are not affected).

If you want to verify ownership of a feed on Google, you must do so using Podcasts Manager. Verifying ownership enables you to request a change in the served feed, see user listening and search statistics on Google, and more.

If a feed is associated with a show that is owned by someone else on Podcasts Manager, you cannot verify ownership of that feed.

• To verify ownership of a feed for a new show, follow the instructions to add a new show to Podcasts Manager.
• If you want to add a verified feed to an existing show, see here.
• 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 new served feed to your show:
  1. Add the new feed, then
  2. Change the served feed to your new feed.
• If you have an entirely new podcast:
  • Podcasts Manager users, follow the instructions for adding a new show.
  • If not using Podcasts Manager, see Get started.
• If you want to move a feed to another URL, see Change the served feed.

• To remove the feed and start serving a different feed instead, see Change the served feed.
• To stop serving your show entirely, see Remove a podcast.

Note that any feed shown in your Podcasts Manager feed history will remain there forever, whether or not the feed still exists.

If you think that Google has chosen the wrong feed to represent your podcast, you can tell Google explicitly which feed you want served for your show. (This affects your show only on Google surfaces.)

Similarly, if you have moved your feed to a new URL, or have added a new feed that should be served for your show, here is how to tell Google about the change. (For feed moves that don't change the feed URL, you don't need to do anything.)

To change the served feed or move your feed:

1. Verify that your new feed is up and available. Don't take the next steps until your new feed is available to be read by Google.
2. Do not delete the old feed until the desired feed is served. If you remove your old feed before Google has started serving your new feed, then unexpected things can happen (Google might stop serving your show entirely, or might start serving an unexpected feed for your show). How to check which feed is served.
3. Change the feed pointed to by your show homepage. If the served feed and the homepage don't point to each other, this can hurt your ranking. (You can also perform this step later, until after the feed change has occurred.)
4. Specify the new feed for Google to serve:
   If you manage your podcast in Google Podcasts Manager

   1. Click Settings > Feeds on the show homepage in Podcasts Manager.
   2. Click Change served feed. You will be prompted to select which new feed to serve:
      1. If the feed is in your show's feed history, choose the feed from the list, and the change should happen in a day or two without any additional verification.
      2. If the feed is not in your feed history, enter the feed URL and you'll be prompted to verify ownership of the feed, as with any new feed. You will receive a verification code by email, and must provide the code in the verification flow to complete the process of changing the feed. Note that you will lose access to the show on Podcasts Manager when you click the "send code" button, so you should complete ownership verification promptly once the code is sent.
   3. Periodically visit your show in Podcasts Manager to see if Google has made the change.
   4. Update your podcast hosting service and/or your RSS feed, as appropriate, to alert non-Google podcasting directories and apps about the change.
   If you are using a podcast hosting service

   1. Search your hosting service's documentation for instructions about how to move a feed and how to tell podcast directories about the move. Your service should have a mechanism for moving feeds. If not, you can sign up for Google Podcasts Manager, then follow the instructions for managing your podcast using Google Podcasts Manager.
   2. Ask Google to crawl your new feed if your hosting service hasn't already done so. Or simply wait for a regularly scheduled crawl (Google typically crawls feeds several times a day). It will take a few days for your feed to change on Google Podcasts, and a few more days for the changes to propagate out to all subscribed users.
   3. We strongly recommend also using Google Podcasts Manager to tell Google directly about the change. Google Podcasts Manager is simple to enable.
   If you manage your RSS feed directly

   1. Your new feed: Post your feed in the new location and add the following tag, replacing new_feed_URL with the URL of the new feed location (yes, the new feed file points to itself):
      <itunes:new-feed-url>new_feed_URL</itunes:new-feed-url>
   2. Your old feed: Create a 301 (permanent) redirect from your old feed URL to your new feed URL.
   3. Ask Google to recrawl your old feed , or simply wait for a regularly scheduled crawl (Google typically crawls feeds several times a day). It will take a few days for your feed to change on Google, and a few more days for the changes to propagate out to all subscribed users.
5. It can take a few days for the feed change to happen. Check back every few days to see whether the feed change has occurred. (How to check which feed is served.)
6. After the feed change has occurred, you can delete the old feed, if you wish.