Learn

Structured data vs schema markup vs JSON-LD: the difference

People use structured data, schema markup and JSON-LD as if they were one thing. They are three layers: a concept, a vocabulary and a syntax. Knowing which is which makes Google's documentation easier to read, and it explains why a feature can vanish from search while your markup stays valid.

By Adem ÇakalPublished 3 sources6 min read
Short answer

Structured data means facts about a page written in a standard machine-readable form. Schema.org is the shared vocabulary of types and properties, such as Product or Organization. JSON-LD, Microdata and RDFa are the syntaxes you write it in. "Schema markup" usually means schema.org vocabulary written in one of those syntaxes.

The three layers

TermWhat it isExample
Structured dataThe general idea: explicit, labelled facts on a page"This page describes a software product with this name and price"
Schema.org vocabularyShared type and property namesSoftwareApplication, offers, name
Format or syntaxHow the vocabulary is written into HTMLJSON-LD, Microdata, RDFa
Google featureA search appearance that Google builds from some markupProduct, Breadcrumb, Event in the Search Gallery
Vocabulary combined with a format produces markup; Google decides whether a feature uses it Vocabulary schema.org types Format JSON-LD, Microdata, RDFa Google feature only if Google supports it + = Valid markup is necessary, but Google chooses which features exist.
Layers as described in Google's introduction to structured data.

The same fact in three formats

One statement, a page about a software product, written each way. Google treats all three as equally acceptable when valid, and prefers JSON-LD for maintenance.

<!-- JSON-LD: a separate script block -->
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"SoftwareApplication","name":"Acme Tracker"}
</script>

<!-- Microdata: attributes on visible elements -->
<div itemscope itemtype="https://schema.org/SoftwareApplication">
  <span itemprop="name">Acme Tracker</span>
</div>

<!-- RDFa: attributes on visible elements -->
<div vocab="https://schema.org/" typeof="SoftwareApplication">
  <span property="name">Acme Tracker</span>
</div>

Check yours with the schema checker. Google says its own documentation, not schema.org, is the reference for what Search uses, because many schema.org types have no Google feature.

What Google supports and what it retired

The Search Gallery today lists 25 features, among them Article, Breadcrumb, Dataset, Event, Job posting, Local business, Organization, Product, Q&A, Recipe, Review snippet, Software app and Video. Features come and go, so the dates below come from Google's updates log.

FeatureDate in Google's logWhat the log says
HowTo rich resultSeptember 14, 2023HowTo documentation removed; the rich result no longer shows on desktop or mobile
FAQ rich result, restrictionSeptember 14, 2023Documentation changed so the result appears only for well-known, authoritative government and health sites
Sitelinks search boxNovember 29, 2024Documentation removed; the feature is no longer available in results
FAQ rich result, deprecationMay 8, 2026 (notice)Feature stops appearing in Search from May 7, 2026
FAQ rich result, documentationJune 15, 2026Remaining FAQ documentation removed

The FAQ date is easy to misquote: the notice was posted on May 8, and the end of display is dated May 7. If you generated FAQ markup before, our FAQ schema generator still produces valid schema.org output, but do not expect a Google result from it.

A practical rule

Add markup when it describes content already visible on the page and a supported feature exists for it. Treat the Search Gallery as the source of truth, and re-check it when a feature you rely on is mentioned in the updates log.

Common mix-ups

  • "Schema" and "schema.org" are not a format. Saying you added schema tells nobody whether you used JSON-LD, Microdata or RDFa. Name the format when you brief a developer.
  • Valid is not eligible. A page can pass a syntax validator and still not qualify for a Google feature, because Google lists required and recommended properties per feature and expects the markup to match visible content.
  • Supported by schema.org is not supported by Google. The vocabulary has far more types than the Search Gallery has features. A type with no gallery entry may still be harmless, but it will not create a Google appearance.
  • Retired does not mean invalid. HowTo, FAQ and sitelinks search box markup can remain syntactically correct after Google stops showing the feature. That is why a clean report in a validator says nothing about whether a search appearance exists today.

Before you build markup for a client, open the Search Gallery, find the exact feature name, and read its required properties. If the feature is not in the gallery, ask what the markup is for, since the answer may be a different tool or no markup at all.

Questions people ask

Which format should I use for Google?

Google says JSON-LD, Microdata and RDFa are all fine if the markup is valid, and recommends JSON-LD in most cases because it is easiest to implement and maintain at scale.

Will valid markup give me a rich result?

No. Google says structured data can enable enhanced results, but eligibility depends on following its guidelines and including the required properties, and display is never guaranteed.

Should I remove FAQ markup now that the rich result is gone?

Google has not said that FAQ markup is harmful. The feature no longer appears in Search, so it earns no Google rich result. If other tools or readers use it, keeping it is a judgment call. Validate it with our schema checker.

Where is the authoritative list of what Google supports?

Google's Search Gallery of structured data features. Google says its own documentation is definitive for Search behaviour, not the schema.org site.

Sources

  1. Google Search Central: Introduction to structured data, accessed 2026-11-12.
  2. Google Search Central: Structured data search gallery, accessed 2026-11-12.
  3. Google Search Central: Search documentation updates, accessed 2026-11-12.