WordPress HTTPS RSS Feed Won’t Validate – Solved

I was adding a website to Alltop for someone the other day and the aggregation service would not accept the feed. The feed was submitted years ago and working just fine up until a recent HTTPS migration. The feed was being generated by a theme which I have used on many occasions and works perfectly when it is HTTP. So, what is the problem?

Upon running the feed through a feed validation services such as the W3C Validator, the feed validated but there were some odd recommendations:

• content:encoded should not contain srcset attribute
• content:encoded should not contain sizes attribute
• content:encoded should not contain iframe tag
• style attribute contains potentially dangerous content: max-height
• content:encoded should not contain data-lang attribute

Googling these shows me thousands of others totally baffled by the messages. SRCSET attributes are a great thing. Size attributes are totally normal. Any article with an embeded YouTube video will have an iframe. No, there is no dangerous content. The data-lang attribute suggestion is silly and is what you get if you embed a tweet.

The solution

I reached out to Alltop support for help and quickly heard back from Will Mayall with some friendly advice to submit the feed using a Feedburner feed. People running podcasts and syndicating their blog and what are much more familiar with this than I am as this was literally the first feed I have submitted anywhere in years. Upon Googling a few questions, I see loads of people having issues submitting their HTTPS RSS feeds (and HTTP RSS feeds) to various places such as SoundCloud and iTunes. That said, I have no idea at all if iTunes accepts FeedBurner feeds- maybe I am about 5 years late to this party and everyone already uses FeedBurner.

But, if you are having issues submitting your RSS feed after an HTTPS migration, FeedBurner may be able to help you.

To “burn your feed” with FeedBurner simply log in to FeedBurner and supply them with your RSS feed’s URL and pick up your new FeedBurner URL.

In may case this is what the URLs look like:

• WordPress generated RSS Feed URL: http://www.telapost.com/feed/
• FeedBurner RSS Feed URL: http://feeds.feedburner.com/telapost/Jsfc

Was this helpful?

If you have been having issues with your HTTPS RSS feed please feel free to comment below.

• Author
• Recent Posts

Len

President at Telapost

I create content and do SEO for law firms, small businesses and companies worldwide. I have been generating traffic online since 1992. I have owned multiple successful companies. I'm an organic eater, nature lover and German Shepherd owner. Feel free to contact me here.

Latest posts by Len (see all)

• Google “Pure Spam” Penalty Deindexes Sites March 6 2024 - March 12, 2024
• What Happened to ChicagoNow.com? - August 30, 2022
• The December 2021 Google Local Pack Algorithm Update - December 17, 2021