This seems to be an issue related to WordPress core. In the past, the problem would be that if you did not have any regular posts in your site then any custom feed (such as the podcast feed) would return a 404 error, but the feed would still display. I managed to find a work around for that inside the plugin by forcing the HTTP status code to not be 404, however, it seems that the issue inside WordPress core has graduated to the point where it just doesn’t show the feed at all anymore.
Finding a fix for this is going to be difficult and might ultimately mean patching core, but in the mean time the only way to fix this is to add at least one regular post to your site. It can be a blank post with no title, but it needs to be published in order for custom feeds to be shown.
A potential method of getting around this for most people (might not work for everyone) is to use the raw feed URL, which will be this: https://example.com/?feed=podcast
– that URL will bypass WordPress’ custom feed mechanism and just return the feed content in the correct format. iTunes allows you to change your feed URL, as do most other podcasting services, so I recommend you give that a shot for now.
As a side note, don’t use the podcast/feed
URL as that is WordPress built-in URL for the podcast
custom post type – it does not contain all the tags that iTunes requires. You need to use the podcast/feed
URL that this plugin provides.
I hope this helps!
Cheers,
Hugh