Should I use https schema markup after http-https migration?

[admiral99]

Dear Moz community,

Noticed that several groups of websites after HTTP -> HTTPS migration update their schema markup from, example :

{
"@context": "http://schema.org",
"@type": "WebSite",
"name": "Your WebSite Name",
"alternateName": "An alternative name for your WebSite",
"url": "http://www.your-site.com"
}

becomes

{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Your WebSite Name",
"alternateName": "An alternative name for your WebSite",
"url": "https://www.example.com"
}

Interesting to know, because Moz website is on https protocol but uses http version of markup. Looking forward for answers

[admiral99]

Thank you very much for the answer.

[BritneyMuller]

Thanks for your great question!

Schema.org has stated that using either is fine. Here is their longer form answer from their FAQ page on which to use:

"There is a general trend towards using 'https' more widely, and you can already write 'https://schema.org' in your structured data. Over time we will migrate the schema.org site itself towards using https: as the default version of the site and our preferred form in examples. However 'http://schema.org' -based URLs in structured data markup will remain widely understood for the forseeable future and there should be no urgency about migrating existing data. This is a lengthy way of saying that both 'https://schema.org' and 'http://schema.org' are fine."

That being said...I think I'll go switch outdoorsrank.com to https now. Think they will keep http:// around for a while, though. Especially considering SEOs who implemented Schema before https and G doesn't want to penalize site owners for not knowing any better? <- My personal thoughts on this.

Thanks again!