What is JSON-LD?
Also called JavaScript Object Notation for Linked Data
Definition
JSON-LD is a JSON-based format for expressing linked data. Websites commonly use it to publish Schema.org entities and relationships inside a script element without embedding every property directly in visible HTML.
How does JSON-LD work?
JSON-LD uses a context to map compact terms to shared identifiers. In common website implementations, @context points to Schema.org, @type declares an entity type, and properties supply facts.
An @id can identify a node so other objects can refer to it. Although websites place this data in a script element, JSON-LD is data rather than executable application logic.
- The @context establishes how terms should be interpreted.
- The @type identifies the class of the described object.
- The @id provides an identifier for references between objects.
Why does JSON-LD matter for B2B SaaS?
SaaS sites frequently render content through shared templates and content management systems. JSON-LD lets publishers maintain machine-readable descriptions without weaving property attributes through every visible component.
Google recommends it for supported structured data where feasible. The separation can simplify maintenance, but it also creates a risk that hidden markup becomes stale while visible copy changes. Accuracy matters more than the number of properties included.
- Generate markup from the same facts used in page content.
- Keep organization identifiers consistent across editorial templates.
- Review changes to pricing or ownership wherever those facts appear.
What is an example of JSON-LD?
A homepage could contain a script with type application/ld+json describing an Organization. That object might include @context, @type, @id, name, and url. An article can reference the organization’s @id as its publisher.
This arrangement links two descriptions within the site’s data model. It does not instruct an answer engine to recommend the company or establish ownership of unrelated external entities.
- A homepage organization can use a stable fragment identifier.
- An article publisher can reference that existing organization identifier.
- Official profile URLs can be added only when they identify the same organization.
How do you improve or measure JSON-LD?
Inspect the actual HTML response and rendered document for malformed or duplicate objects. A JSON parser checks syntax, while a structured data validator checks vocabulary and supported feature rules.
These tests answer different questions. Compare values against visible content before publishing.
Track template regressions and conflicting identifiers rather than treating a rising number of JSON-LD objects as a meaningful visibility metric.
- Ensure generated strings are safely serialized as JSON.
- Retest markup when content models or frontend templates change.
- Remove stale facts rather than preserving them for apparent completeness.
Frequently asked questions about JSON-LD
Is JSON-LD a Schema.org type?
No. JSON-LD is a format, while Schema.org supplies types and properties. Organization and Article are examples of Schema.org types that JSON-LD can express.
Does JSON-LD require client-side JavaScript?
No. A server can include JSON-LD directly in the initial HTML. The script element contains data and does not need application JavaScript to execute.
Does Google require every Schema.org property?
No. Requirements depend on the supported search feature. Adding unsupported or inaccurate properties does not make a page more eligible for a search appearance.