: Secure and non-secure Schema.org Markup? Is it possible to have schema.org itemtypes for both secure and insecure ports? I run a static-ish site made in Jekyll, and am implementing Schema.org

@Ann8826881

Typically, user agents wouldn’t dereference these URIs.

There should be absolutely no problem in using the Schema.org HTTP URIs on a HTTPS site. In fact, many other vocabularies (used for Microdata or RDFa) provide only HTTP URIs, so you have no choice there. I’d even say it’s bad practice to provide multiple vocabulary URIs for the same concept, as consumers might not look for and "understand" all variants.

I recommend to use the HTTP variant for Schema.org in your markup, because:


The "canonical machine representation" Schema.org core schema defines only the HTTP URIs.
The HTTP variant is preferred according to this issue in the Schema.org GitHub:


[…] on the basis that we prefer to see the canonical 'http://schema.org/Person' in widespread use, but if someone asks for the https then let's give it to them.

All examples, even on the HTTPS pages, use HTTP (see, for example, the examples on schema.org/Person). In RDFa’s Initial Context, only the HTTP variant is defined, so probably most of the RDFa will use the HTTP variant.




Update 2015-11: With version 2.2, a FAQ entry was added:

Q: Should we write schema.org or schema.org in our markup?

In summary:


HTTPS is now explicitly supported, too.
Sometime in the future, the site will use HTTPS by default, and for the examples URLs with HTTPS will be preferred.
Both variants can be used:


both schema.org and schema.org are fine

Vote Up Vote Down