Welcome, PowerPress user! This page will assist you with submitting your podcast to iTunes.
If you are not hosting with us a quick reminder that you can easily post – upload – publish directly from your WordPress dashboard if you have a Blubrry Podcast Hosting Account.
Before you submit your podcast to iTunes
Before you submit your podcast to iTunes make sure you meet the following minimum requirements.
- Your artwork is a square jpg or png formatted image at least 1400 x 1400 and at most 3000 x 3000 in size in RGB color space (1400 x 1400 jpg image recommended).
- A unique podcast program title (check iTunes to make sure your program title is unique).
- At least one iTunes category selected.
- Valid email address in the iTunes email field (notifications from Apple will be sent to this address)
- Have created at least one blog post with media (a podcast episode) in either mp3, m4a, mp4, m4v, pdf, or epub format.
If you have completed the above steps, you are now ready to submit your podcast to iTunes and other podcast directories.
Submit your podcast to the iTunes Store podcast directory
- Sign in to iTunes Podcast Connect
- Click the at the top left of the iTunes Connect dashboard.
- Enter your RSS feed into the provided text box and then click the “Validate” button.
- A Feed Preview will load if you do not have any validation errors. Please take a moment and review your podcast artwork, description, general information (e.g. description, categories, etc), and episodes. Please see the Validation Errors section if you have any problems validating your podcast feed.
- If everything within the Feed Preview is correct, click the “Submit” button.
Your podcast is now submitted to the iTunes Store podcast directory.
After you submit your podcast to iTunes
All podcasts submitted to iTunes are moderated. The process can take up to 10 days, though most submissions are approved within 3 days and on occasion only a few hours.
Apple will email the address you entered as your iTunes email in PowerPress settings when your podcast is approved. The message will be titled “iTunes Store Podcast Approved Notification” and will include your own unique iTunes subscribe URL. Please copy this URL and save it into the PowerPress settings > iTunes tab section in the “iTunes Subscribe URL” field.
Typical iTunes Podcast Connect Validation Errors
Error: Can’t read your feed.
iTunes is unable to find a podcast feed at the URL specified.
Confirm that the feed URL entered is valid. We recommend testing the feed URL using the Firefox web browser. A valid RSS feed will appear in Firefox like the example below allowing you to view the podcast feed in a readable way.
Some URLs that use secure https:// may not be supported by iTunes. The SSL certificate authorities (also referred to as the certificates chain file) must include a root or intermediate certificate that is packaged in the Java Development Kit (JDK). Some SSL certificates may require a special chain file to work.
Error: Podcast artwork must be between 1400 x 1400 and 3000 x 3000 pixels, JPG or PNG, in RGB color space, and hosted on a server that allows HTTP head requests.
The podcast artwork is not of the appropriate size, format, color space and/or hosted on a HTTP/1.1 complaint web server.
Confirm that the artwork image is the appropriate size by viewing it directly in the web browser. We recommend testing the image using the Firefox web browser. In Firefox, right click on the image and select “View Image Info”. A valid iTunes image will have the following attributes:
- JPEG Image or PNG Image
- Identical width and height
- Width and height greater than or equal to 1400 and no greater than 3000
If the above attributes are true, then the issue is either with the web hosting or with the image’s color space. The color space issue can easily be resolved by saving the PNG image as a JPG with your favorite image editing software. The process of saving the PNG as a JPG will convert the color space to RGB as well as shrink the file size in bytes.
If your image is in JPG format and you still receive the error above, your web hosting provider may be the issue. Contact your web hosting to verify that your service supports HTTP/1.1 HEAD requests. The following curl command can be used to verify your server supports HTTP HEAD requests.
curl -i -X HEAD http://example.com/path/to/image.jpg