Structured Data (JSON-LD / Schema.org)
Structured data is machine-readable markup, usually JSON-LD following schema.org vocabulary, that describes what a page is about so search engines can understand it and show rich results.
also: JSON-LD · schema.org · rich results · schema markup · structured data
A page's text tells a human what it is; structured data tells a machine. By embedding a JSON-LD block that says 'this is an Article by this author, published on this date' or 'this is a Product with this price and rating', you remove the guesswork from how a search engine interprets the page. The vocabulary is schema.org and the preferred format is JSON-LD, a script block that sits in the HTML without changing what users see.
The payoff is eligibility for rich results: review stars, FAQ drop-downs, breadcrumb trails, and the entity panels that take up more of the results page and pull more clicks. It is also how you feed knowledge graphs and, increasingly, AI answer engines that read structured data to cite sources. The markup must match the visible content, or it is ignored (or penalised), so structured data describes the page, it does not embellish it.
related_terms
faq
Questions & answers
- What is the difference between JSON-LD and schema.org?
- Schema.org is the shared vocabulary (the types and properties like Article, Product, FAQPage). JSON-LD is the format you write it in: a script block of JSON embedded in the page. Google recommends JSON-LD as the way to express schema.org data.
- Does structured data improve rankings?
- Not directly as a ranking boost, but it makes pages eligible for rich results and entity features that raise visibility and click-through, which moves traffic. It also helps search engines and AI answer tools understand and cite the page. The markup must accurately reflect the visible content to qualify.
Want this applied to your stack, not just defined?
The free tools run the numbers; an audit tells you where the real cost and risk are. Book a call, or leave your email and I'll reach out.
Prefer proof first? See how this plays out in real case studies →