Play Music Error Loading Top Podcast Series. Please Try Again.

Discover your evidence or episode on Google Podcasts

To observe your evidence on Google Podcasts

• If your show is registered in Google Podcasts Manager:
  1. Open up your bear witness in Google Podcasts Managing director.
  2. Click your show's icon.
• If your testify isn't registered in Google Podcasts managing director:
  1. Open Google Podcasts.
  2. Search for your podcast.

To discover your episode in Google Podcasts

• Open up your show in Google Podcasts and search for your episode name
  or
• But search for your show and episode name in Google Search, or in Google Podcasts search

Podcast is not on Google

If your podcast isn't appearing in Google Search or Google Podcasts, attempt the following troubleshooting steps. Annotation that Google doesn't guarantee that every podcast volition show up on Google.

i. Check that your feed is indexed

A feed must exist indexed past Google before it can appear on any Google Podcasts platform. Being indexed means that Google has found, read, and stored your RSS feed in the Google alphabetize.

To check whether your feed is indexed by Google:

1. Search for your show on Google Podcasts:
   1. Open Google Podcasts.
   2. Search for your podcast.
2. If the bear witness isn't present:
   1. Did yous just publish your feed for the beginning time? If so, be aware that it can have up to six days to make your prove bachelor in Google Podcasts later Google has found and candy your feed.
   2. Check that Google could reach your RSS feed:
      • Visit your RSS feed URL in your browser. If your browser tin can't find the feed, or if you're required to log in, then be sure that your feed exists and is available at the URL where you retrieve it is.
      • Check that your feed isn't blocked past a robots.txt rule:
        1.  Open the Google Rich Results exam
        2. Enter the URL of your RSS feed and click Exam URL
        3. If the result is a cherry-red "Clamber failed" alarm, and then click the Details > Crawl row to expand information technology.
        4. If the details say "Blocked past robots.txt", then y'all or your site host is blocking Google from indexing your RSS feed. Speak to a programmer to notice out why your feed is blocked, and how you can unblock it.
      • Check the results of the last time Google tried to visit your RSS feed:
        1. Open the Google PubSubHubbub site.
        2. In the Publisher Diagnostics enter your feed URL in the Topic URL text box, then click Go Info.
        3. Cheque the last successful fetch time. This is the last time that Google was able to meet your feed (non whether feed was valid). If at that place is no fetch fourth dimension, asking a recrawl of your feed, look a few days, then check Google Podcasts over again to see if your prove is at present appearing. If the feed was fetched but is nevertheless not appearing, move on to pace 2.

2. Check the validity of your RSS feed

Confirm the validity and abyss of your RSS feed:

• Check validity: Use an RSS validator to confirm that your feed is well-formed, but note that Google can tolerate some RSS errors. Validate your feed by URL, rather than simply pasting your code into a validator, to ensure that the feed is reachable.
• Check completeness: Ostend that your feed includes all Google-required podcast-level tags for podcasts, and at least ane episode with the required episode tags.
• Confirm that your feed isn't blocked: Your feed should not include either of these tags. If the episode or evidence does contain a blocking tag, it won't appear on Google.
  • <itunes:block>aye</itunes:block>
  • <googleplay:cake>yes</googleplay:block>

3. Confirm that Google can access your feed and homepage

1. Confirm that Google can access your feed. A quick fashion to practice this is to enter the feed URL and homepage URL in an incognito window.
2. If you lot have a homepage, but Google doesn't seem to know virtually it:
   1. Confirm that Google tin can admission your homepage. Employ the Mobile Friendly test tool on your homepage, and see if information technology reports whatever issues with noindex or robots.txt rule. These issues can forbid Google from reading your homepage. Fixing those issues is beyond the telescopic of this certificate, but read the linked documentation to learn how to address these bug.
   2. In your homepage, ostend that you have a link to your served RSS feed URL, and that the URL is correct.
   3. Confirm that the <link> element in your feed points to the homepage.

Notation that information technology takes Podcasts Manager nearly a day to confirm fixes to an inaccessible or broken feeds, and then await a day and confirm that the warning nigh an inaccessible feed has disappeared from your testify in Podcasts Manager.

Episode is not on Google

• If your prove is available to listeners on Google Podcasts platforms, but new episodes aren't appearing (or other changes aren't appearing):
  • Confirm that you haven't blocked your episode
  • See Google isn't noticing your feed updates.
  • Remember that it can accept a few days for a newly posted episode to appear. If yous're in a bustle, y'all can try to speed things up by explicitly requesting a recrawl of your feed.
• If an episode is missing from Podcasts Manager, run across Episode is missing from a show in Podcasts Manager.

Podcast is already claimed

If you lot try to verify ownership of a feed, but get a warning that the podcast is already claimed, you should contact the owner listed in the currently verified feed. Visit the feed that y'all tried to claim* and look for the owner email listed in the<itunes:owner> tag. Send an email to that owner request for access to the prove in Podcasts Manager.

* If you asked to claim feed 1 but were directed to merits feed two, contact the owner of feed two, not the possessor of feed 1.

If you think that an unauthorized person has claimed ownership of your feed, you can contact united states with the details of your claim.

Non immune to verify buying of a feed (feed already associated with a show)

You cannot verify ownership of a feed for a show that is already owned by someone else in Podcasts Manager. If you endeavor to do so, Podcasts Manager will show an error message, along with the URL of the feed that Google currently serves for this podcast. You can attempt to contact the owner of the feed, or if y'all think that an unauthorized person has claimed buying of your feed, you can contact Google with the details of your merits.

No podcast-level result in Google Search

A podcast-level search result shows information about your whole podcast, and also includes a carousel of episodes just for your podcast, as shown here (the exact layout may modify):

If your podcast homepage shows up in search, merely without any episodes

If you don't see any episodes listed with your podcast homepage in Google Search results:

• Ostend that your feed is associated with your homepage
• Confirm that your feed lists at least one episode. Utilise an RSS validator on your served feed.
• Ostend that Google has crawled your feed and website recently enough to observe whatsoever changes or fixes y'all've fabricated.

If your podcast is in search results, only without any special formatting:

• Confirm that your feed is associated with your homepage.
• Confirm that Google tin access the linked homepage. Enter the homepage URL in an incognito window
• Confirm that your homepage complies with Google webmaster guidelines. Your homepage, dissimilar your RSS feed, must comply with those guidelines in club to appear in Search results.
• Google doesn't guarantee special formatting or features for podcast search results. Even if you have done everything properly, in some cases Google Search might decide that a dissimilar format is more advisable for search results for your podcast.

Google isn't noticing your feed updates

It takes Podcasts Manager about a day to observe most feed updates. Additionally, there is a 2-three day data latency in Podcasts Manager data, then it can take a few days later a successful fix or newly discovered feed to begin to see data for your show.

When removing a show, some methods are faster than others.

If your podcast already appears on Google, merely updates are not being picked up (for example, new episodes, or podcast clarification changes):

1. Be aware that removing an episode will remove it from Google Podcasts platforms for listeners, but if the episode has any listening data in the terminal xvi months, it will stay on Podcasts Manager.
2. Google should choice upwards changes to an existing feed in less than a solar day. If information technology'due south simply been ten minutes since you published your change, wait a few hours and so bank check once again.
3. Ostend that you are updating the served feed for your show. If you have multiple feeds associated with your bear witness, Google will not publish changes made to any non-served feeds.
4. Check your feed crawl condition:
   1. Open the Google PubSubHubbub site.
   2. In the Publisher Diagnostics enter your feed URL in the Topic URL text box, then click Become Info.
   3. Check the terminal successful fetch time, and see if it is more recent than the last unsuccessful fetch. If the almost recent fetch was unsuccessful, look at the last fetch fault to see what went wrong. If the feed hasn't been recrawled for a while, request a recrawl.
5. Check that your feed is valid. If the feed has syntax errors, Google might non exist able to read information technology. Check the validity of your feed.

Lost access to your testify

Here are the possible reasons that you can't access your prove any more in Podcasts Manager:

• If yous can neither open the testify in Podcasts Manager nor run across it in your evidence list, a evidence Admin has revoked your admission to the show. If this is the instance, yous'll need to contact an Admin or Editor of the show to re-grant you access.
• If you tin't open the show, but get rerouted to a "Please verify your feed" page, and you come across "Pending verification" next to the show proper noun in the testify list, and then either:
  • Y'all never finished verifying ownership of the feed, and yous must exercise so.
  • The served feed has inverse and you or someone else has started, but not completed, verifying ownership of the new feed. In this case, anyone trying to admission the bear witness volition be prompted to complete verification of the newly served feed.

Request access to a show

If you don't have access to an existing show, ask a show Admin to grant y'all access. If you lot don't know who to ask, contact the owner'due south email listed in the<itunes:owner> tag of the feed.

Episode is missing from a show in Podcasts Managing director

If you've posted an episode to your feed, but you don't come across it in Podcasts Manager, remember these requirements to appear in the episodes list. If your episode fulfils these requirements and you still don't run into it listed in your show on Podcasts Director:

• Modify the selected time period. Call back that just episodes that were published before or within the selected fourth dimension period are shown in the episode list. Cull All Fourth dimension for the selected time menses to zoom out to include all data for all episodes.
• Make sure that the episode appears in the served feed for your show. Changes made to any other feeds, including new episodes added, will non be reflected on Google Podcasts platforms.

• Refresh your browser tab. Podcasts Manager won't refresh the folio with new data unless y'all reload the folio. Switching shows in your bear witness list won't load new information either.
• Confirm that Google has seen your updates. Monitor the feed crawl status on your served feed to run into if Google has seen your changes. Use the feed crawl diagnostics to ostend that Google could access the feed, and that the feed didn't have any critical errors.
• Confirm that your feed is beingness served. Open up the Google Podcasts app, load your podcast, and see whether the episode appears in that location.
• If an episode was previously present in the show just is now no longer served, call up that Podcasts Director retains data for but 16 months. Episodes that are no longer served will not be shown in the study 16 months subsequently the last recorded listening data.

Episode has no data, merely appears in Podcasts Director

Call back that an episode must have data in order to announced in Podcasts Manager. If your episode appears in Podcasts Manager but doesn't prove whatsoever data in the report, y'all're probably zoomed in to a time period without information. Change your appointment selection to All time to meet where your listening data occurs.

Episode appears twice in your testify

Podcasts Manager uniquely identifies an episode by the episode URL. If you alter the URL of an episode in whatsoever manner (other than irresolute the casing), then the new URL volition exist considered a new episode, with the same proper noun as the old episode (unless you've changed the championship too).

Duplicate shows in my prove listing

If you run across duplicate shows listed in your Podcasts Manager evidence list, you can remove the incorrect evidence from your list. If that doesn't work, yous tin contact us with details.

Sharp drop-off in information for episodes or evidence

If you see an abrupt drop-off of data for one or more episodes:

• If the served feed changes and nobody has reverified ownership in Podcasts Managing director, your bear witness will finish to show any data from the new feed. Information loss volition be visible 2-3 days after the feed change if the new feed is not verified. prove Admins and Editors should see a notification when this occurs; bear witness Viewers might non come across any notification.
• Another possibility is that the episode is blocked past a <googleplay:cake> or <itunes:cake> tag. These tags tin can block an episode from existence shown to users in Google Podcasts platforms.
• Another possibility is that the audio file URL is cleaved; open your served RSS feed and re-create the URL into a new browser window to see whether the sound file URL is right.

Irksome drop-off in data

If data for an episode only tails off, it'due south likely that users accept simply stopped listening to your episode.

Served feed inverse, just can't reverify

If the served feed has changed but y'all can't verify ownership of the feed for some reason, you can file an appeal.

Show isn't associated with your website

If a Google search for your podcast isn't showing your associated website, confirm that your feed and homepage link to each other. This is a very strong signal to Google that the two items are related.

Information discrepancies

You might see discrepancies between the data on Google Podcasts Manager and other hosting services. Read more about data discrepancies here.

Google chose the wrong RSS feed for your show (suggest a different feed for your show)

You can strongly suggest the preferred RSS feed for your show by linking information technology to your homepage, and Google usually respects this choice. If this does not work, yous can file an appeal to change the served feed.

If y'all are using Podcasts Director, you can change the served feed yourself.

I'thousand told that I already verified ownership of a feed, but I didn't

If y'all submit a verification request for a new feed, and Google tells you that you've already verified the feed, hither is probably what is happening:

1. At the fourth dimension of your request, Google didn't know about your feed. This is why yous were allowed to submit the request without whatsoever suggestions from Podcasts Manager.
2. Google then crawls the feed and decides that information technology'due south part of a known feed grouping; that is, it's like enough to some other feed that it's essentially a duplicate of that known feed.
3. If you are already a verified fellow member of the Podcasts Manager evidence represented past that feed group, your new feed is a duplicate (non-served) feed for the bear witness, which is already verified, Podcasts Manager tells you that you've already verified this feed.

If you recall that this new feed is not a duplicate of an existing feed, you lot tin request a alter in the served feed. However, Google does not provide a way to let you request serving of two feeds that it thinks are duplicates.

Playback fails, opens a new tab, or downloads the audio file

If playback fails for an episode on any Google surface

Ostend that the episode is playable for an incognito user:

1. Find the served feed for your show.
2. In that feed, detect the URL listed for the episode
3. Open an incognito window in your browser and enter the episode URL. If the episode won't play for an anonymous user, information technology won't play on Google Podcasts. Make sure that at that place aren't any login requirements for the episode.

It's also possible that you have a problem with mixed content, where your host page or feed is on HTTP but the episode audio file is on HTTPS (or the reverse). Check the sound file URL and confirm that information technology uses the same protocol (HTTP or HTTPS) as the hosting folio or feed. If non, make certain that the folio, feed, and all resources are hosted on the same protocol (Google strongly recommends HTTPS).

If clicking "play" opens a new browser tab, or downloads the audio file

It's likely that you have a problem with mixed content, where your host page or feed is on HTTP but the episode sound file is on HTTPS (or the reverse). Check the audio file URL and confirm that it uses the same protocol (HTTP or HTTPS) as the hosting folio or feed. If not, make sure that the page, feed, and all resources are hosted on the same protocol (Google strongly recommends HTTPS).

Request a recrawl of your feed

Google crawls podcast feeds regularly and ofttimes, but if you need to publish an update to your feed quickly, hither is how to tell Google to recrawl your feed:

1. Visit PubSubHubbub.
2. In Publish > Topic URL, enter your feed's URL
3. Click Publish
4. This will queue the feed.

To check the status of your requested crawl:

1. Visit PubSubHubbub.
2. In Publisher Diagnostics > Topic URL, enter your feed URL
3. Click Get Info.
4. Check the Last successful fetch fourth dimension to see when Google was last able to admission your RSS feed. Notation that this doesn't mean that Google was able to read and empathise the feed, only that information technology accessed the feed.

Block or remove a show

Run across Remove a show.

Other show actions on Google Podcasts

See how to manage your prove on Google Podcasts.

Other bear witness actions on Google Podcasts Director

Run across how to manage your bear witness on Google Podcasts Manager

carnellthalow.blogspot.com

Source: https://support.google.com/podcast-publishers/answer/9482890?hl=en