Feed Error: Twenty13 & Only Powerpress Active

Feed Validator is an old validator and hasn’t been updated in years. It tosses out a lot of warning messages you can ignore. When I looked at the Feed Validator report, I didn’t see anything critical in the warning messages. I also ran your feed thru the internal Blubrry validator and CastFeedValidator and it came up fine.

Shawn,

I think we can ignore the warning messages, but should resolve the one error message it points out. Feed Validator is the one Blubrry recommends on it’s website, so that’s the one I used.

However, the W3C validator reports the same error.

https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.staging1.disruptingjapan.com%2Ffeed%2Fpodcast

My feed has been declined by a number of places because it does not validate, so I really need to get this issues fixed.

I admit the “href must be a full URL” error is a mystery to me, since the URL seems to be fine.

Tim

• This reply was modified 7 years, 7 months ago by timoth3y.

Shawn,

Apple’s PodcastConnect also also reports this feed as broken Failed Validation.

Tim

Hello Tim,

Please let us know where blubrry referrers to use feedvalidator.org? We removed links to it years ago because it does not support HTTPS and does not understand google play or the latest iTunes tags. validator.w3.org uses the same code that feedvalidator.org uses, albeit on a newer server it still does not accept https:// URLs in values, which is problematic since we’re now supposed to all be using HTTPS. As Shawn said, these validators are not helpful for today’s podcast feeds. Also important to note that these validators check syntax of the feed, they do not check podcast specifics, firewall issues, feed size limitations, HTTP head request support, etc… There are more to podcast feeds than just the syntax.

Two good podcast feed valdaitors for future reference: https://castfeedvalidator.com/ and https://podba.se/validate/ Both validators with your feed check out ok. I then checked our internal validator and your feed also checks ok there.

I checked your SSL cert and that checks out ok, so that should not be an issue. Your feed size is at 214Kb which is ok, 500Kb or more can cause delays with directories updating your listing but you’re within that limit.

I looked up your podcast on iTunes: https://itunes.apple.com/us/podcast/disrupting-japan/id923817924?mt=2 It is using a different feed address than the one you quoted: https://www.disruptingjapan.com/feed/podcast/ Note, you cannot re-submit the same podcast to iTunes with a different feed URL, you have to change the title for a new feed otherwise iTunes will reject it with a “Can’t submit your feed. Your feed was previously submitted.” error.

What other directories/services are giving you errors and what are the error messages?

As for iTunes podcast connect, what is the error message you get?

I just tested https://www.disruptingjapan.com/feed/podcast/ (this is the current podcast’s feed on iTunes, not the feed you provided that goes to a staging1. sub domain server) and the server appears to be blocking what are called “HEAD” requests. Please contact your server administrator and have them allow the server to accept HEAD requests, these are required for iTunes to check for feed changes. More than likely an overzealous server administrator concerned about security thought blocking HEAD requests would be ok, but that’s not the case for podcasting.