Schema.org Context URL FAQ
Schema.org Context is core to JSON-LD Schema validation. As part of the development for Smarter.SEO (aka VISEON.IO) we needed to fully understand various standards to test JSON-LD schema against. Including strict JSON-LD. For our tests and to ensure that our clients are not at risk of their metadata being compliant we first had to resolve the correct syntax for Schema.org context itself. It appears that it is not actually defined.
Short answer: Use “@context”: “https://schema.org”
All of these work identically:
“@context”: “https://schema.org”
“@context”: “https://schema.org”
“@context”: “http://schema.org”
“@context”: “https://schema.org”
HTTPS is modern standard – avoids mixed content security issues
No trailing slash matches most official repository examples
Future-proof against browser security policy changes
Cleaner syntax – shorter and more readable
No. Both “https://schema.org” and “https://schema.org/” resolve to identical JSON-LD contexts. Search engines treat them the same way.
HTTP contexts (“http://schema.org”) still work but may cause issues:
Mixed content warnings on HTTPS websites
Security policy blocks in strict environments
Future deprecation as web moves fully to HTTPS
VISEON flags these for the same mixed content reasons:
“http://linkedin.com/in/username” ? Use “https://linkedin.com/in/username”
“http://twitter.com/username” ? Use “https://twitter.com/username”
“http://facebook.com/pagename” ? Use “https://facebook.com/pagename”
Schema.org’s documentation evolved over time, leading to mixed examples across:
Official website examples
GitHub repository code
Google documentation
Community tutorials
Not currently, but it’s becoming riskier:
– Works today – search engines still process HTTP contexts
– Potential issues – browser security policies may interfere
– Future uncertainty – trend is toward HTTPS-only web
VISEON’s validation is based on current best practices and forward compatibility.
P – Pass: HTTPS contexts (with or without trailing slash)
W – Warning: HTTP contexts (functional but deprecated)
F – Error: Typos, wrong domains, malformed URLs
Quick fix checklist:
- Update context URL: “@context”: “https://schema.org”
- Check social URLs: Convert HTTP to HTTPS in
sameAsproperties - Test with VISEON: Verify no mixed content warnings
- Monitor for changes: Standards evolve – stay updated
Last updated: Based on 2025 web standards and browser security policies
