Home  ›  When Your Trying to Upload Podcast but It Says Http Problem

When Your Trying to Upload Podcast but It Says Http Problem

Written By mercredi 13 avril 2022 Add Comment Edit

Find your show or episode on Google Podcasts

To find your testify on Google Podcasts

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

To observe your episode in Google Podcasts

  • Open up your bear witness in Google Podcasts and search for your episode name
    or
  • Simply search for your bear witness and episode proper noun 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, try the following troubleshooting steps. Note that Google doesn't guarantee that every podcast volition testify upwardly on Google.

1. Bank check that your feed is indexed

A feed must be indexed by Google earlier it can appear on any Google Podcasts platform. Being indexed means that Google has establish, read, and stored your RSS feed in the Google alphabetize.

To check whether your feed is indexed by Google:

  1. Search for your bear witness on Google Podcasts:
    1. Open Google Podcasts.
    2. Search for your podcast.
  2. If the show isn't nowadays:
    1. Did you just publish your feed for the starting time time? If then, exist enlightened that information technology can accept upwards to 6 days to brand your evidence available in Google Podcasts after Google has constitute and processed your feed.
    2. Check that Google could reach your RSS feed:
      • Visit your RSS feed URL in your browser. If your browser tin't find the feed, or if you're required to log in, and then be sure that your feed exists and is available at the URL where you think it is.
      • Check that your feed isn't blocked by a robots.txt rule:
        1.  Open the Google Rich Results examination
        2. Enter the URL of your RSS feed and click Test URL
        3. If the result is a crimson "Crawl failed" warning, then click the Details > Crawl row to expand it.
        4. If the details say "Blocked by robots.txt", then you or your site host is blocking Google from indexing your RSS feed. Speak to a developer to notice out why your feed is blocked, and how y'all can unblock it.
      • Bank 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 Get Info.
        3. Check the last successful fetch time. This is the last fourth dimension that Google was able to come across your feed (not whether feed was valid). If there is no fetch time, asking a recrawl of your feed, await a few days, and then check Google Podcasts again to come across if your show is at present appearing. If the feed was fetched simply is still not appearing, move on to step two.

2. Check the validity of your RSS feed

Confirm the validity and abyss of your RSS feed:

  • Cheque validity: Use an RSS validator to confirm that your feed is well-formed, but notation that Google can tolerate some RSS errors. Validate your feed by URL, rather than simply pasting your lawmaking into a validator, to ensure that the feed is reachable.
  • Check completeness: Confirm that your feed includes all Google-required podcast-level tags for podcasts, and at least one 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 prove does contain a blocking tag, it won't appear on Google.
    • <itunes:block>yes</itunes:block>
    • <googleplay:cake>yes</googleplay:block>

3. Ostend that Google can admission your feed and homepage

  1. Confirm that Google can access your feed. A quick way to exercise this is to enter the feed URL and homepage URL in an incognito window.
  2. If y'all have a homepage, but Google doesn't seem to know about information technology:
    1. Confirm that Google can admission your homepage. Use the Mobile Friendly test tool on your homepage, and see if it reports any issues with noindex or robots.txt dominion. These bug tin can prevent Google from reading your homepage. Fixing those issues is beyond the scope of this document, just read the linked documentation to learn how to address these issues.
    2. In your homepage, confirm that yous accept a link to your served RSS feed URL, and that the URL is correct.
    3. Ostend that the <link> element in your feed points to the homepage.

Notation that it takes Podcasts Director about a 24-hour interval to confirm fixes to an inaccessible or broken feeds, so wait a day and confirm that the alarm about an inaccessible feed has disappeared from your evidence in Podcasts Managing director.

Episode is not on Google

  • If your evidence is bachelor to listeners on Google Podcasts platforms, but new episodes aren't actualization (or other changes aren't appearing):
    • Confirm that you oasis't blocked your episode
    • See Google isn't noticing your feed updates.
    • Remember that it tin can take a few days for a newly posted episode to appear. If you lot're in a bustle, yous can endeavor to speed things upwardly past explicitly requesting a recrawl of your feed.
  • Google Podcasts has a limit to the number of episodes per show; older episodes tin be dropped when that limit is reached.

If an episode is missing from Podcasts Manager (not Google Podcasts), run across Episode is missing from a show in Podcasts Manager.

Podcast is already claimed

If you try to verify ownership of a feed, just go a warning that the podcast is already claimed, you should contact the owner listed in the currently verified feed. Visit the feed that you tried to claim* and wait for the owner email listed in the<itunes:owner> tag. Transport an email to that owner asking for access to the bear witness in Podcasts Managing director.

* If yous asked to claim feed one only were directed to claim feed ii, contact the owner of feed ii, non the possessor of feed ane.

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

Not allowed to verify ownership 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 Managing director. If you lot try to exercise then, Podcasts Manager will prove an error bulletin, along with the URL of the feed that Google currently serves for this podcast. You can effort to contact the possessor 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 claim.

No podcast-level result in Google Search

A podcast-level search result shows data almost your whole podcast, and also includes a carousel of episodes just for your podcast, equally shown hither (the exact layout may modify):

If your podcast homepage shows upward in search, simply without any episodes

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

  • Confirm that your feed is associated with your homepage
  • Confirm that your feed lists at to the lowest degree one episode. Utilise an RSS validator on your served feed.
  • Confirm that Google has crawled your feed and website recently plenty to detect any changes or fixes y'all've fabricated.

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

  • Ostend that your feed is associated with your homepage.
  • Confirm that Google tin can access the linked homepage. Enter the homepage URL in an incognito window
  • Confirm that your homepage complies with Google webmaster guidelines. Your homepage, unlike your RSS feed, must comply with those guidelines in order 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 different format is more appropriate for search results for your podcast.

Google isn't noticing your feed updates

It takes Podcasts Manager about a day to notice most feed updates. Additionally, there is a two-3 day information latency in Podcasts Manager information, so it can take a few days after a successful fix or newly discovered feed to begin to see information for your testify.

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

If your podcast already appears on Google, but updates are non being picked up (for instance, new episodes, or podcast description changes):

  1. Be aware that removing an episode volition remove it from Google Podcasts platforms for listeners, but if the episode has any listening data in the last 16 months, it volition stay on Podcasts Director.
  2. Google should pick upwards changes to an existing feed in less than a 24-hour interval. If it's only been 10 minutes since yous published your modify, wait a few hours then check once more.
  3. Confirm that you are updating the served feed for your show. If you have multiple feeds associated with your show, Google will non publish changes made to any non-served feeds.
  4. Bank check your feed crawl status:
    1. Open the Google PubSubHubbub site.
    2. In the Publisher Diagnostics enter your feed URL in the Topic URL text box, then click Get Info.
    3. Bank check the last successful fetch time, and see if information technology is more recent than the terminal unsuccessful fetch. If the most contempo fetch was unsuccessful, look at the last fetch mistake to run across 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 be able to read information technology. Cheque the validity of your feed.

Lost access to your show

Here are the possible reasons that y'all tin can't access your evidence whatever more than in Podcasts Managing director:

  • If you lot tin can neither open the show in Podcasts Manager nor run across it in your show list, a testify Admin has revoked your access to the prove. If this is the case, y'all'll need to contact an Admin or Editor of the bear witness to re-grant you access.
  • If you can't open the evidence, simply get rerouted to a "Please verify your feed" page, and you see "Awaiting verification" adjacent to the bear witness name in the show list, then either:
    • You lot never finished verifying buying of the feed, and you must do so.
    • The served feed has changed and you or someone else has started, but not completed, verifying buying of the new feed. In this instance, anyone trying to access the show will exist prompted to complete verification of the newly served feed.

Request access to a show

If you don't have admission to an existing prove, ask a bear witness 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:possessor> tag of the feed.

Episode is missing from a prove in Podcasts Managing director

If you've posted an episode to your feed, but you don't encounter it in Podcasts Manager, recollect these requirements to appear in the episodes list. If your episode fulfils these requirements and you lot yet don't see it listed in your prove on Podcasts Manager:

  • Alter the selected fourth dimension catamenia. Remember that only episodes that were published earlier or within the selected time period are shown in the episode list. Choose All Fourth dimension for the selected time flow to zoom out to include all information for all episodes.
  • Make sure that the episode appears in the served feed for your bear witness. Changes made to any other feeds, including new episodes added, will not be reflected on Google Podcasts platforms.
  • Refresh your browser tab. Podcasts Manager won't refresh the page with new data unless yous reload the folio. Switching shows in your show list won't load new data either.
  • Confirm that Google has seen your updates. Monitor the feed crawl status on your served feed to see if Google has seen your changes. Use the feed clamber diagnostics to confirm that Google could admission the feed, and that the feed didn't have any critical errors.
  • Confirm that your feed is being served. Open the Google Podcasts app, load your podcast, and run across whether the episode appears there.
  • If an episode was previously present in the show but is now no longer served, remember that Podcasts Manager retains data for simply 16 months. Episodes that are no longer served will not exist shown in the report 16 months subsequently the last recorded listening information.

Episode has no data, but appears in Podcasts Manager

Recall that an episode must have data in guild to appear in Podcasts Managing director. If your episode appears in Podcasts Manager merely doesn't prove any data in the report, you're probably zoomed in to a time period without data. Change your date selection to All time to encounter where your listening data occurs.

Episode appears twice in your show

Podcasts Director uniquely identifies an episode past the episode URL. If you modify the URL of an episode in any fashion (other than irresolute the casing), then the new URL will be considered a new episode, with the same name equally the old episode (unless you've changed the title as well).

Duplicate shows in my show list

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

Sharp drop-off in information for episodes or show

If you run across an precipitous drop-off of data for one or more episodes:

  • If the served feed changes and nobody has reverified ownership in Podcasts Director, your show volition cease to show any data from the new feed. Information loss will be visible two-3 days later the feed change if the new feed is not verified. testify Admins and Editors should encounter a notification when this occurs; show Viewers might not see any notification.
  • Another possibility is that the episode is blocked by a <googleplay:block> or <itunes:block> tag. These tags can cake an episode from being shown to users in Google Podcasts platforms.
  • Some other possibility is that the audio file URL is broken; open up your served RSS feed and re-create the URL into a new browser window to see whether the audio file URL is correct.

Slow drop-off in data

If information for an episode merely tails off, it'southward likely that users have simply stopped listening to your episode.

Served feed changed, only can't reverify

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

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 lot 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 testify (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 selection. If this does not work, you can file an appeal to modify the served feed.

If you are using Podcasts Manager, you tin change the served feed yourself.

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

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

  1. At the time of your request, Google didn't know most your feed. This is why you were allowed to submit the asking without any suggestions from Podcasts Manager.
  2. Google then crawls the feed and decides that it'south function of a known feed group; that is, it's similar plenty to some other feed that it's essentially a duplicate of that known feed.
  3. If you lot are already a verified fellow member of the Podcasts Manager show represented past that feed group, your new feed is a duplicate (non-served) feed for the show, which is already verified, Podcasts Manager tells you lot that you've already verified this feed.

If you think that this new feed is not a duplicate of an existing feed, y'all tin request a modify in the served feed. Withal, Google does not provide a fashion to let you request serving of ii 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

Confirm that the episode is playable for an incognito user:

  1. Find the served feed for your show.
  2. In that feed, notice 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, it won't play on Google Podcasts. Make sure that there aren't whatsoever login requirements for the episode.

It'south 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 opposite). Check the audio file URL and confirm that it uses the same protocol (HTTP or HTTPS) every bit the hosting folio or feed. If not, make certain that the page, 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

Information technology'southward likely that y'all 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). Cheque the audio file URL and ostend 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 aforementioned 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 come across when Google was concluding able to admission your RSS feed. Note that this doesn't mean that Google was able to read and understand the feed, only that it accessed the feed.

Block or remove a show

See Remove a show.

Other show actions on Google Podcasts

Meet how to manage your prove on Google Podcasts.

Other show actions on Google Podcasts Manager

See how to manage your show on Google Podcasts Managing director

pattersonyous1990.blogspot.com

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

0 Response to "When Your Trying to Upload Podcast but It Says Http Problem"

Enregistrer un commentaire

Inscription à : Publier les commentaires (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel