Podcast Requirements and Content Guidelines

Podcast RSS Feed Technical Requirements

Your hosting provider should be able to help you address technical requirements. Failure to comply with these requirements will result in feed validation errors.

– RSS feed URLs must adhere to RSS 2.0 specifications, be publicly addressable (not password-protected), and include the following XML declaration:


– Display your show artwork and allow streaming playback of your episodes by enabling your hosting server for HTTP HEAD requests and byte-range requests.

– Each episode must have a unique tag, along with its three required components — URL, length, and type — which specifies the location and host of the episode. Platocast Podcasts will ignore duplicate URLs.

– All episodes must contain a globally unique identifier (GUID), which never changes.

– Use only ASCII filenames and URLs that include a-z, A-Z, or 0-9. For more information, see encoding best practices.
Respect case-sensitivity across all XML tags in podcast RSS feeds.

Incorrect Casing:

<itunes:category text=”Kids &amp; family” />

Correct Casing:

<itunes:category text=”Kids &amp; Family” />

– Date and time must conform to RFC 2822 specifications. The date must be “day of week, day month year” and the time must be in 24-hour format (without including a.m. or p.m.) with the time zone offset included. For example:

Incorrect Date Format:
7/6/2014 1:00:00 PM

Correct Date Format:
Wed, 6 Jul 2014 13:00:00 PDT Wed, 6 Jul 2014 13:00:00 -0700

– Use ‘ (for single quote) or ” (for double quote). Avoid using HTML naming conventions such as ’‘ “ or ”. For more information, see XML Character and Entity References.

Incorrect Character Format
Love to get outdoors and discover nature’s treasures? Hiking Treks is the show for you.

Correct Character Format
Love to get outdoors and discover nature’s treasures? Hiking Treks is the show for you.

– If using these symbols, use the appropriate programming:

Incorrect Code:

Correct Code:

Incorrect Code:
© 2020 John Doe
Correct Code:
© 2020 John Doe

Tip: Enter all other characters directly in an editor that supports UTF-8.

Content Guidelines:

Platocast strives to present your content in a clean and accurate form. We know it takes effort to get it exactly right, so we’ve created this reference guide to help you format your content, art, and metadata for the optimal experience.

– Following these guidelines will make it less likely that we have to remove your content submission from Platocast Podcasts.

– Use of Platocast Inc. Copyrighted Terms. Podcasts not produced by Platocast Inc. must not use Platocast trademarks (such as the Platocast logo, Platocast Inc., or Platocast Podcasts) in the podcast RSS feed in a way that makes the content appear to be Platocast-branded or created by Platocast. The term “Platocast Podcasts” should be used to refer to the entire Platocast Podcasts ecosystem, including Platocast Podcasts for iOS and Platocast Podcasts for Mac. To learn more, see Guidelines for Using Platocast Trademarks and Copyrights.

– Accuracy. Metadata and cover art must match and accurately represent the audio content of the podcast. For example, if the cover art and the audio are for a podcast titled “Hiking Treks,” but the metadata is for “The Hungry Tourist,” then the items don’t match.

– Cultural Sensitivities. It is the podcast creator’s responsibility to be knowledgeable about local regulations and cultural sensitivities. Content distributed must be legal and appropriate for the countries or regions where the content is cleared. This content may be removed if it does not follow this guidance.

– Editorial Corrections. Platocast Podcasts reserves the right to modify metadata, such as Hosts and Guests, as reasonably necessary to improve the customer experience.

– Explicit Content Flagging. Explicit content must be flagged with an Explicit tag at the show level if one or more episode is explicit. Additionally, the explicit episodes in question must also be flagged with the Explicit tag.

– Language. The appropriate language must be identified in the podcast RSS feed at the show level.

– Misleading. Content may be removed if designed to mislead customers by mimicking popular content or search terms.

– Nazi Propaganda. Content must not depict Nazi symbolism as restricted by local law, such as the Strafgesetzbuch section 86a, or any other country that restricts Nazi propaganda. If content violating Strafgesetzbuch section 86a is submitted three times, your entire catalog could be removed from Platocast Podcasts.
Password Protected. Content that requires a password to access is prohibited.

– Prohibited Content. Content that is illegal or promotes illegal activity, self-harm, violence, or illegal drugs, or content depicting graphic sex, gore, or is otherwise considered obscene, objectionable, or in poor taste is prohibited.

– Repeated Submissions. Content may be removed if multiple copies of a podcast or episode are submitted.

– Rights Infringement. Podcasts can’t contain materials that infringe on the rights of others (for example, copyright, right of publicity, trademark, and so on).

– Self-Censored Titles. Do not self-censor language in titles or descriptions. These metadata fields must be written as intended, and all words should be completely spelled out. Platocast Podcasts automatically censors certain explicit words in titles. For example, you do not need to insert asterisks within explicit words unless they were included in the original title (for example, f**k and s**t).

– Spam. Spam content or other content created with the sole purpose of advertising or marketing products, content, or services outside of Platocast Podcasts is prohibited.