Understanding the special requirements for a podcast site
While a podcast’s website may seem on the surface to be just another website, the data requirements to push that content out to multiple platforms are a bit more complex. In order to be on multiple podcast repositories, a podcast needs to have a properly formatted RSS feed with specific data for both the podcast as well as each episode.
This requires additional data and specific formats for the data.
Since we typically build for the web, we usually keep our URLs as relative paths for the project, such as
/episodes/my-first-episode/. These work perfectly for how the web works. Each browser knows this is relative to the root domain of the website the user is viewing. When pushing your content out to additional places, the paths need to be absolute, such as
Podcast applications also have additional requirements for data and formatting, such as the following: