Structured data is a standardized way to label the parts of a page — a product, a review, a FAQ, an event — so search engines and AI systems understand it precisely. Google reads it to build rich results like star ratings, FAQ dropdowns and breadcrumbs.
Why JSON-LD
There are three formats (Microdata, RDFa and JSON-LD). Google recommends JSON-LD: you place a single <script type="application/ld+json"> block in the head and describe the page as a JSON object. It keeps your markup clean and is easy to generate.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your title",
"author": { "@type": "Person", "name": "Jane Doe" }
}
</script>The four building blocks
Every JSON-LD block uses the same primitives:
@context— almost alwayshttps://schema.org@type— the entity (Article, Product, FAQPage…)@id— an optional stable identifier so entities can reference each other- properties — the actual fields (name, price, author…)
You can connect entities with nested objects or @id references. For example, a Product with an offers object and an aggregateRating object.
The types worth adding first
- Article / BlogPosting — every blog post
- Product with Offer — every product page
- FAQPage — pages with a visible Q&A
- BreadcrumbList — most content pages
- Organization — once, on the homepage
- LocalBusiness — every location page
- WebSite with
potentialAction— site search box
Rules that matter
- Only mark up content that is visible on the page
- Do not mark up fake reviews or ratings you cannot substantiate
- Validate with the Rich Results Test and Search Console's enhancement reports
- Use absolute URLs for images and page URLs
- Match the markup to the page's actual primary topic
Validate in three places
1. JSON validity — the block must parse; a stray comma breaks the whole thing. Use the JSON-LD validator.
2. Schema requirements — required fields for the type (e.g. Product needs name and offers).
3. Rich-result eligibility — the Rich Results Test reports which enhancements the page qualifies for.
Worked example: an article with author and breadcrumb
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"headline": "How to write meta descriptions",
"author": { "@type": "Organization", "name": "Example team" },
"datePublished": "2026-10-01",
"dateModified": "2026-10-07",
"mainEntityOfPage": "https://example.com/blog/meta-descriptions"
},
{
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Blog", "item": "https://example.com/blog" },
{ "@type": "ListItem", "position": 2, "name": "Meta descriptions" }
]
}
]
}Note the @graph array: it lets you publish several entities in one block.
Common errors to check
- Trailing commas and unescaped quotes
- Prices as strings vs numbers (either works, but be consistent)
- Relative image URLs
@typetypos (Blogpostinginstead ofBlogPosting)- Markup for content that renders only after interaction
Generate it
You do not need to hand-write JSON. Our free generators cover the common types: Article, Product, FAQ, HowTo, Breadcrumb and Organization. Paste your fields, copy the block, and validate it.