
Key points
- Use JSON-LD in a
<script type="application/ld+json">block. Google recommends it over Microdata and RDFa. - Markup must describe what is visible on the page. Valid markup makes a page eligible for rich results; it never guarantees them.
- Check syntax (valid JSON, @context, @type), then required properties for each type, then confirm eligibility with Google's Rich Results Test.
What structured data is for
Text on a page is written for people. Structured data repeats the key facts in a fixed vocabulary, schema.org, so crawlers do not have to guess. A recipe page can state its ingredients and cooking time, a product page its price and availability, a business its address and opening hours.
For search engines this adds certainty. For you it can make a page eligible for features such as star ratings, product information, breadcrumbs or event details. Eligibility is not a promise: Google decides when and whether to show them.
A minimal JSON-LD block
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Structured data explained",
"image": "https://example.com/cover.jpg",
"datePublished": "2026-03-27",
"author": { "@type": "Person", "name": "Jane Smith" }
}
</script>
@context says which vocabulary is used and @type says what the thing is. Everything else are properties of that type. Blocks can sit in the head or the body, and several blocks can live on one page, or be combined with @graph.
Types worth adding first
- Organization and WebSite on the home page: name, URL, logo and social profiles.
- Article or BlogPosting on posts: headline, image, dates, author.
- BreadcrumbList on pages deep in the site.
- Product with offers, LocalBusiness with address, Event, Recipe, VideoObject where they apply.
Do not mark up content that is not on the page, and do not add review stars you did not collect. Markup that misleads can lead to a manual action against the site.
Required and recommended properties
Google publishes, for every supported type, which properties are required for eligibility and which are recommended. A Product needs a name and at least one of offers, review or aggregateRating. An Event needs a name, a start date and a location. Missing a required property usually means the page is not eligible; missing a recommended one just means less detail.
Common mistakes
- Invalid JSON: a trailing comma, single quotes, or an unescaped quote in a string.
- Missing @context or @type, or a wrong context URL.
- Relative URLs and bad dates. Use full https:// addresses and ISO 8601 dates such as
2026-03-27. - Markup that does not match the page: a price that differs from the visible price, or an author who is not named on the page.
- Duplicate blocks from a theme and an SEO plugin both outputting the same type.
- Markup added only by JavaScript that crawlers may miss. Prefer server-rendered JSON-LD.
FAQ rich results are now limited by Google mainly to well-known government and health sites. FAQPage markup is still valid and harmless, but do not expect it to change how your results look.
How to test
- Run the page through a structured data validator to catch syntax errors and missing required fields.
- Use Google's Rich Results Test to confirm which rich result types the page is eligible for.
- After publishing, watch the enhancement reports in Search Console for errors across the whole site.
See also: Open Graph and social previews.
FAQ
Is structured data a ranking factor?
Google says structured data is not a direct ranking factor. It helps Google understand a page and can make it eligible for richer results, which can improve clicks.
JSON-LD or Microdata?
JSON-LD. It lives in one block, is easier to maintain and is what Google recommends. Microdata and RDFa still work.
Can a page have more than one type?
Yes. A product page can carry Product, BreadcrumbList and Organization together. Link them with @graph or separate blocks.
Does it work for AI answers?
Clear, accurate markup gives any machine reader a reliable summary of the page. No provider has promised how it is used, so add it for search engines first.