The complete JSON-LD schema guide for 2026

May 13, 2026·11 min read

If you have ever searched a recipe and seen a card with star ratings, a photo, and cook time directly in the search results, that's JSON-LD structured data at work. This guide explains what it is, which types unlock which rich results, and exactly how to add it to your site without writing a single line of code.

What JSON-LD actually is

JSON-LD stands for JavaScript Object Notation for Linked Data. It's a small block of structured information you embed in your page's HTML that tells search engines, in plain machine-readable terms, what the page is about. It doesn't change how the page looks to humans; it sits invisibly in a <script> tag in the <head>.

Here is what a simple Article schema looks like in JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Make Perfect Sourdough Bread",
  "description": "A complete step-by-step guide.",
  "author": { "@type": "Person", "name": "Jane Smith" },
  "datePublished": "2026-03-15T00:00:00+00:00",
  "image": ["https://example.com/sourdough.jpg"]
}
</script>

That block tells search engines: "This page is an article. Here's the headline, author, publication date, and a featured image." When the search engine trusts the markup, it uses those fields to display a richer search result instead of the plain blue link.

Why rich results matter

A standard search result is a blue link with a meta description below it. A rich result is the same link with extras: stars, prices, cook time, FAQ dropdowns, recipe photo, event date, job title, salary range. Rich results take up more vertical space, draw more attention, and consistently get higher click-through rates than plain results in the same position.

Without structured data, a search result is limited to its title, URL, and meta description. With it, the same result can include images, stars, prices, or dropdown details, making it visually larger and more inviting in the search listing.

The honest reality

Adding valid JSON-LD makes your page eligible for rich results. The search engine still decides whether to actually display them based on content quality, page authority, and policy compliance. Markup makes a page eligible; display is up to the search engine.

The 12 most useful schema types for 2026

Out of hundreds of types in the Schema.org vocabulary, these are the ones that actually map to a rich result your site is likely to need:

Type	Rich result	For
`Article` / `BlogPosting` / `NewsArticle`	Top stories, article cards	Any written content
`Product`	Stars, price, availability	Online stores
`Recipe`	Recipe card with photo, time, rating	Food blogs
`FAQPage`	Expandable Q&A in search	FAQ / help pages
`Event`	Event listing with date, location	Concerts, conferences, webinars
`LocalBusiness` (incl. `Restaurant`, `Hotel`, `Store`)	Map pack, hours, phone	Physical businesses
`Organization`	Knowledge panel	Your company info
`JobPosting`	Job listing card	Hiring pages
`HowTo`	Step-by-step card	Instructional content
`VideoObject`	Video thumbnail in search	Embedded videos
`BreadcrumbList`	Breadcrumb path under URL	Any deep page
`SoftwareApplication`	App card with rating, price	Apps, SaaS

Our JSON-LD Schema Generator supports 42 types in total, including the niche but valuable ones: Movie, Book, Course, Podcast, Dataset, RealEstateListing, Vehicle, and more.

What's actually new in 2026

Structured-data requirements have tightened in the last 18 months. A few changes worth knowing:

Datetime fields require timezones. datePublished: "2026-03-15" now throws a warning. Use "2026-03-15T00:00:00+00:00" instead.
Event requires eventStatus and eventAttendanceMode. Added as a side-effect of the pandemic-era online events boom.
Product warns when priceValidUntil is missing. Offers are expected to have an expiration so stale prices don't appear in results.
VideoObject requires thumbnailUrl as an array. Single-string thumbnails generate warnings.
FAQPage requires at least 2 complete Q&A pairs. Single-question pages no longer qualify for the rich result.

The generator handles all of these automatically. Fill the form, and the tool outputs compliant JSON-LD.

How to add JSON-LD to your site (zero coding)

Pick the schema type. Open the JSON-LD Schema Generator, choose the type that matches your page (Recipe, Product, FAQPage, etc.).
Fill in the form. All the fields you need are right there. Required fields are marked with a red asterisk and validated in real time.
Copy the <script> tag. Click "Copy <script> tag". The generator gives you a fully formed block ready to paste.
Paste it into your page's <head>, ideally right before the closing </head> tag. Most CMSes and theme editors have a "header scripts" or "code injection" setting for this.
Validate. Run your page URL through the official Rich Results Test. Look for "Valid items detected" with zero errors.

Build your JSON-LD in 2 minutes

42 schema types. Live validation. Copy or download.

Open the generator →

Common pitfalls and how to avoid them

1. Marking up content that doesn't match the page

If your page shows a recipe but your JSON-LD describes a different recipe (or a Product, or anything that isn't actually visible to the user), search engines considers this manipulative markup. It can result in a manual penalty. The rule is simple: the JSON-LD must accurately describe what a human sees on the page.

2. Fake reviews and aggregate ratings

Tempting as it is to add "aggregateRating: 4.9, reviewCount: 837" to a brand-new product, doing so when those reviews don't exist is a structured-data policy violation and can get your entire domain demoted in search. If you don't have reviews yet, leave the field out — your page is still eligible for other rich result types.

3. Mixing multiple incompatible types on one page

A single page can have multiple JSON-LD blocks (one for the article, one for the FAQ section, one for the breadcrumbs, etc.) and that's allowed. But putting two contradictory types in the same block — say, a Product that also claims to be an Event — confuses validators. Use one block per concept.

4. Forgetting to update prices and dates

If your priceValidUntil says "2025-06-30" and a user lands on the page in 2026, search engines may demote the rich result. Either keep the date current or remove the field. Same logic applies to endDate on past events.

5. Validating only when you set it up

Run the Rich Results Test on a sample page every few months. Search engines update requirements quietly, and a schema that passed in 2024 might be flagged in 2026. Recipes, Products, and Events are the types most likely to have evolving rules.

Who else reads JSON-LD?

Most major search engines read structured data. Some social and discovery platforms parse JSON-LD for various features. AI assistants increasingly use structured data as a high-signal shortcut for understanding what a page is about.

That last point matters more every year. As more queries shift to AI search, well-marked-up pages get cited more accurately and more often.

The minimum effective dose

If you're going to add only one schema, add BreadcrumbList to every page. It's the smallest type, supported almost universally, and the rich result (breadcrumb path under your URL in search results) is the most consistent payoff for the effort.

After that, add the type that matches your most-visited page templates: BlogPosting for a blog, Product for a store, Recipe for a food site, LocalBusiness for a brick-and-mortar shop. Two well-implemented schemas beat fifteen half-broken ones.

Recap: the 5-minute setup

Open the JSON-LD Schema Generator.
Pick BreadcrumbList. Generate it once for your site's primary template.
Pick the matching content type (BlogPosting / Product / Recipe / etc.) and fill the form.
Copy the <script> tags into your page's <head>.
Validate at the official Rich Results Test. Aim for zero errors.
Wait 1–2 weeks for the search engine to reindex. Rich results begin appearing after that.