JSON-LD Schema Rich Results Basics

JSON-LD essentials: Schema.org patterns that support rich results

Organization, Article, FAQPage, and Product basics—what to validate, common mistakes, and how structured data complements on-page SEO.

Written by Priya Nandakumar · Lead Editor, Structured Data & GEO

Former agency SEO director; schema.org working-group observer sessions; training in passage-driven information architecture for AI Overviews and assistant citations.

Editorial policy · Privacy · Terms

Why JSON-LD

JSON-LD keeps structured data maintainable: one script block or tag manager slice instead of fragile microdata sprinkled across templates. Search engines use eligible markup for rich results eligibility—not a ranking guarantee, but a clearer semantic contract.

High-value types by surface

Organization / WebSite: brand identity, sitelinks prerequisites where applicable.
Article / BlogPosting: dates, authors, and headline discipline for news and editorial.
FAQPage: only when visible FAQs exist on-page; avoid fabricated Q&A.
Product / Offer: feeds shopping surfaces where commerce applies.

Validation hygiene

Run markup through Rich Results tests and monitor Search Console enhancements. Watch for contradictions between JSON-LD and visible content—that mismatch can disqualify rich results.

GEO overlap

Clear entities and factual statements in visible HTML remain primary; schema reinforces what the page claims, helping parsers align summaries with your authored facts.

FAQ

When should I use FAQPage schema?

Use FAQPage JSON-LD only when the questions and answers appear visibly on the page and reflect authentic user concerns—never fabricate Q&A solely for rich results.

Does structured data guarantee rich results?

No. Structured data improves eligibility for enhancements; Google still validates content alignment and may omit rich results when markup contradicts visible copy.

Compliance-focused overview—not legal advice for regulated industries.