probeo

How to add or fix the @context so the JSON-LD block is properly understood?

jsonld-missing-context page

The issue

A JSON-LD block without @context says nothing a search engine can use. Its properties are just names, the block is skipped, and the page shows no sign of it.

The cause is that @context tells the reader which vocabulary the block uses. Without it, name or price has no defined meaning. With https://schema.org, each property maps to schema.org’s definition.

Scope

Each top-level object needs a @context, including each object in a root array. Objects nested inside one, and nodes in a @graph, inherit it. A missing context in one block doesn’t affect the others on the page.

How to check you have it

  • In probeo: the page reports Missing @context — expected "https://schema.org".
  • By hand: view the page source and confirm each JSON-LD block, and each object in a root array, starts with "@context": "https://schema.org".
  • With a validator: paste the block into the Schema Markup Validator. Confirm it lists the schema.org types you expect.

The fix

Add "@context": "https://schema.org" at the top of each top-level object.

If a block holds several entities, a single object with a @graph lets them share one context.

Done when: every top-level object declares schema.org as its context, and the check above comes back clean.

Do not

  • Do not leave @context out on the assumption that search engines will infer the vocabulary.
  • Do not declare @context only on a nested object; it belongs at the top.

FAQ

Can @context appear anywhere in the JSON-LD block?

No. @context must be at the root level of the object or array. Nested @context changes vocabulary scope for child objects but does not replace root-level context requirements.

What happens when @context points to a non-schema.org vocabulary?

Search engines may not recognize the vocabulary. Google and other structured data consumers expect schema.org context for SEO-relevant structured data.

Does @context order matter relative to other properties?

No. JSON objects are unordered. Parsers locate @context regardless of its position within the object. Convention places it first for readability.

How does missing @context differ from incorrect @type?

Missing @context removes all vocabulary mapping. Incorrect @type assigns the wrong entity classification but properties remain interpretable. Context defines meaning; type classifies entities.

Can multiple contexts be combined in a single JSON-LD block?

Yes. @context can be an array of multiple vocabulary URLs. This allows mixing schema.org with custom vocabularies, but adds complexity that search engines may not fully interpret.

Should @context use http or https for schema.org?

Use https. Schema.org now recommends HTTPS URLs. Some validators accept HTTP for backward compatibility, but HTTPS is the current standard.

Which product detects this

Probeo checks this on every page of your site as part of Site Clarity. This page explains one instance; the product tells you every page that has it.