Ever noticed how some Google results show star ratings, recipes with cooking times, or event dates — and yours doesn’t? The difference is usually structured data, most commonly written as JSON-LD.
What it is
JSON-LD is a block of JSON placed in a page’s <head> that describes what the page is — a recipe, a product, an article, a business:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Recipe",
"name": "Sourdough Bread",
"cookTime": "PT45M"
}
</script>
Search engines read it and can display your content as a rich result — stars under your link, step-by-step instructions, prices, events.
The schema types that matter most
| Type | Rich result |
|---|---|
Product + Review |
Star ratings in search |
Recipe |
Ingredients + times + stars |
FAQPage |
Expandable questions |
Article/BlogPosting |
Headline, author, dates |
Event |
Date, venue, tickets |
LocalBusiness |
Hours, address, phone |
The honest expectations
- Structured data doesn’t guarantee rich results — it makes your page eligible. Google decides.
- False data is worse than none: claiming review stars you don’t have violates Google’s policies and can earn a manual action. Describe your page truthfully.
- Validate before deploying: a typo in JSON-LD silently disables the whole block. Google’s Rich Results Test and the Schema.org validator both check.
Generating
The JSON-LD generator builds valid blocks for the common types — fill in the fields, paste into <head>. It’s the fastest way to stop leaving rich results on the table.
Structured data is the difference between “in the results” and “standing out in them.”