Can Schema Markup Validator interpret a custom JSON-LD context?

Definition: Schema.org Markup Validator has a documented JSON-LD limitation: it focuses on Schema.org and will not fetch or interpret other @context URLs. JSON-LD itself permits contexts embedded in a document or referenced by URL, so the limitation belongs to this validator's documented scope.

Key facts

• As of 16 September 2026, the Schema.org validator documentation describes a service for Schema.org-based structured data and lists JSON-LD 1.0, RDFa 1.1, and Microdata extraction.
• The W3C JSON-LD 1.1 specification says a context maps terms to IRIs and can be embedded in a document or referenced by a URL.
• Google's structured data documentation describes the Rich Results Test as a tool for validating structured data and says most Search structured data uses Schema.org vocabulary.

What is the documented limitation?

The answer is no for a custom context URL outside the Schema.org context. The Schema.org page says, “The tool is focused on Schema.org. In the case of JSON-LD, this means that it will not fetch or interpret other @context URLs.” The wording covers fetching and interpretation, so a remote context that defines a separate vocabulary is outside the behavior the page documents.

The same page describes the service as a validator for “Schema.org-based structured data embedded in web pages.” It lists syntax checks, a summary of the extracted structured data graph, and support for markup supplied directly or found at a page URL. Those functions describe how the tool reads a page and presents its graph. They do not extend the documented context scope.

How does this differ from JSON-LD support for contexts?

JSON-LD is a serialization format with its own context model. The W3C specification says that a context maps terms to IRIs and that an entry with the key @context introduces it. A context can be embedded in the JSON-LD document or referenced using a URL. The standard also describes applying a custom context through the JSON-LD 1.1 API.

The following extract shows the URL form used in the specification:

{
  "@context": "https://json-ld.org/contexts/person.jsonld",
  "name": "Manu Sporny"
}

That capability belongs to JSON-LD processing generally. It does not override the separate Schema.org validator documentation, which excludes fetching or interpreting other context URLs. The page does not document a separate acceptance rule for every possible inline custom context, so the clear limitation is the one it states for other @context URLs.

Which checker should you use for a website?

Use the Schema.org Markup Validator when the task is to inspect Schema.org data. It can fetch a page from a URL, validate markup provided directly, extract JSON-LD injected by JavaScript, and combine JSON-LD script elements with RDFa and Microdata. For a remote custom context, treat its documented result as limited by the context rule above.

Google documents a separate check for Google Search. Its structured data page calls the Rich Results Test “an easy and useful tool for validating your structured data” and says Google Search supports JSON-LD, Microdata, and RDFa unless a feature's documentation says otherwise. The same page says Google Search Central documentation is definitive for Google Search behavior, even though most Search structured data uses Schema.org vocabulary. A result from one checker therefore describes that checker's scope.

Related terms

• JSON-LD
• Structured data
• Schema.org @id

FAQ

Does a custom context URL make JSON-LD invalid?

No. The W3C specification documents URL-referenced contexts as part of JSON-LD. The Schema.org validator's limitation concerns what that service fetches and interprets.

Can I paste markup into Schema.org Markup Validator?

Yes. The Schema.org documentation says the service can validate markup provided directly, as well as fetch pages from a URL.

Is Schema.org Markup Validator the same as Google's Rich Results Test?

No. Schema.org documents its own validator, while Google documents the Rich Results Test for structured data and feature checks in Google Search.

Sources

1. Schema.org, "Schema.org Markup Validator", 16 September 2026
2. W3C, "JSON-LD 1.1", 16 July 2020
3. Google Search Central, "Introduction to structured data markup in Google Search", 10 December 2025

---

Check how a page reads to answer engines. Open the GEO score analyzer