![]() I also submitted the same feed URL to Spotify. Using the Feedburner URL, I then submitted my new feed to iTunes. Step 5 - Submit Requests to Podcast Platforms Those tools include analytics and feed customization. Step 4 - Submit your RSS feed to Feedburnerįeedburner offers a few excellent tools that are free of charge. I suggest reading this Github snippet for an idea on how to do that. I also had to create a Lambda function that will clear my CloudFront cache whenever I publish an update. I chose to publish my rss feed to /rss/podcast.xml. Step 3 - Publish your RSS feed to your server Note: Apple iTunes does not recognize HTML within a podcast description so please be very careful with how you use this "feature". The app also makes it easy to create custom HTML for your podcast descriptions. You can also create custom attributes for your feed. The service works well with AWS S3 buckets as well as FTP. Therefore, I have my podcasts in one S3 bucket that is linked to AWS Cloudfront and my podcast.xml file within another S3 bucket. The apps philosophy acknowledges that were you store your mp3 / mp4 files might not be in the same server where you store your RSS feed. It's a desktop app that makes it easy to create RSS feeds as well as Podcast feed specifically designed for iTunes.įeeder is fantastic. Therefore, I decided to use Feeder 3 for Mac OS. It just doesn't make sense because the likelihood for mistakes are high. Step 2 - Create an RSS feedĪlthough I have 20 years experience writing HTML, I would never attempt to create my own XML feed. Here are the steps on how to create renditions using Elastic Transcoder. If you want to go one step further, I created an automated process that allows you to upload a high resolution WAV file to one S3 bucket and get a suite of renditions including MP3 and MP4 in less than 5 minutes. AWS is very affordable and if you attached CloudFront to serve as a CDN, then you'll be able to easily scale. I chose to upload my podcasts to Amazon Web Services S3. AWS Elastic Transcoder for media renditions.AWS CloudFront for Content Delivery and caching.AWS CodeCommit for git storage and CodeDeploy for delivery.I did have to pay some money but it was only to create multiple renditions for syndication. This stack allowed me to reduce to cost of managing a reliable, scalable service to $0. Here is the stack I developed using only Amazon Web Services. Its the first place you should get listed. Apple Podcasts is the most popular podcast listening app and accounts for 37.4 of podcast downloads. I went through the excercise of providing a self-hosted solution and below are my steps. Apple Podcasts (formerly iTunes) Compatibility: iOS, Apple CarPlay, Mac, PC with Alexa-enabled smart speakers. The self-hosted solution requires a little bit more work but may be worth it if you have specific goals. The price is reasonable and the integration with Wordpress is the best bang for your buck. Blubrry - Without a doubt I pick this service.If you're willing to pay a few dollars a month, then I highly suggest you simply use one of these 3rd party-hosted solutions. There are a few different ways to submit your podcast to iTunes and Spotify.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |