What is JSON-LD?
JSON-LD, JavaScript Object Notation for Linked Data, is the format Google recommends for adding structured data to a web page. It is a way of describing a page's content in a machine-readable form — marking up that a page is about a product, an article, an organization, or an event, with all the relevant details — placed in a block of code separate from the visible content. JSON-LD is how a site communicates explicit, unambiguous information about its content to search engines, which powers rich results and supports the entity understanding that both Google and AI systems rely on.
What is JSON-LD used for?
JSON-LD is used to add structured data to a page, describing its content in a way search engines can read precisely. Rather than leaving Google to infer what a page is about from its text, JSON-LD states it explicitly — that this is a product with this price and availability, this is an article by this author, this is an organization with these details. This explicit description removes ambiguity about the page's content and meaning.
Its most visible payoff is rich results. The structured data added via JSON-LD makes a page eligible for enhanced search result displays — star ratings, prices, FAQs, event details, and other rich features — that make the result more prominent and informative. These enhanced results can improve the click-through rate by giving searchers more reason to click, which is the direct, measurable benefit of JSON-LD.
It also feeds the entity understanding that underpins modern search. By describing organizations, people, and things and their relationships explicitly, JSON-LD helps Google build the entity SEO understanding that supports rankings and the knowledge panel, and increasingly helps AI systems understand and cite content. This makes JSON-LD relevant well beyond rich results, as the what is GEO guide covers.
Why does Google recommend JSON-LD?
Google recommends JSON-LD over the older structured data formats because it is cleaner and easier to implement and maintain. Where older formats required marking up the structured data within the visible HTML elements, intertwining it with the content, JSON-LD places all the structured data in a separate block. This separation makes it easier to add, edit, and manage without touching the visible content.
The separation also reduces errors. Because the JSON-LD block is distinct from the page's content markup, changes to the page's design or content are less likely to break the structured data, and the structured data is less likely to interfere with the page. This robustness is part of why Google prefers it and why it has become the standard format for structured data.
It is also flexible and comprehensive. JSON-LD can describe the full range of structured data types and the relationships between entities, which makes it capable of expressing everything from a simple product to a complex web of related organizations and content. This combination of ease and capability is why it has become the recommended and dominant format, as the schema markup entry and the Wix structured data guide explain.
How does JSON-LD relate to schema markup?
JSON-LD and schema markup are related but distinct concepts that are easy to conflate. Schema markup refers to the vocabulary — the standardized set of types and properties, defined by schema.org, that describe things like products, articles, and organizations. JSON-LD is the format in which that vocabulary is written into a page. Schema is what is being described; JSON-LD is how it is written down.
In practice they work together: a page uses the schema.org vocabulary, expressed in the JSON-LD format, to describe its content. When someone implements structured data using JSON-LD, they are writing schema.org types and properties in the JSON-LD syntax. The two terms are often used loosely as if interchangeable, but understanding the distinction clarifies what each refers to.
Both serve the same goal of making content machine-readable. Whether described as adding schema markup or implementing JSON-LD, the purpose is to give search engines explicit, structured information about a page's content, which powers rich results and supports entity understanding. The structured data entry covers the broader concept that both terms point to.
How do you implement JSON-LD?
Implementing JSON-LD means adding a block of structured data, written in the JSON-LD format using schema.org types, to the relevant pages. The block describes the page's content — the appropriate type and all its relevant properties — and is placed in the page's HTML. The structured data must accurately reflect the page's actual visible content, because marking up content that is not on the page violates Google's guidelines.
On modern platforms, much of this is generated automatically. Builders like Wix, Wix Studio, and Framer produce appropriate structured data for common content types like articles, products, and organizations without manual coding, which handles the most common cases. Custom or more advanced structured data may require adding JSON-LD manually or through the platform's custom code features, as the Wix structured data guide and Framer structured data guide cover.
Testing confirms the structured data is valid and eligible for rich results. Google's structured data testing and rich results tools validate the JSON-LD, flag errors, and indicate which rich result types the page qualifies for, and Google Search Console reports on structured data across the site. This verification ensures the implementation actually works rather than just being present, which is the difference between structured data that produces results and structured data that quietly fails.
When should you use JSON-LD?
JSON-LD is worth using on any page whose content matches a structured data type that can produce rich results or support entity understanding. Product pages, articles, organization information, events, recipes, FAQs, and breadcrumbs all have structured data types that benefit from JSON-LD, and marking them up makes the pages eligible for enhanced search displays and clearer understanding.
It is increasingly important for AI search and entity recognition. As AI search grows, the explicit, machine-readable information JSON-LD provides helps AI systems understand and cite content, and it strengthens the entity SEO signals that determine how a brand is recognized. This forward-looking value means JSON-LD matters beyond its immediate rich-result payoff, supporting the broader GEO readiness.
For most businesses, the practical approach is to ensure the structured data the platform generates is present and correct, and to add JSON-LD for the content types that would benefit but are not covered automatically. This captures the rich-result and entity benefits without unnecessary complexity. A free SEO scan can establish what structured data a site currently has and where adding JSON-LD would help.
