Schema Markup Guide: JSON-LD Structured Data for Rich Results

Search engines don’t understand web pages the way humans do. When you write “The article was published on 15 June 2026 by Jane Smith,” Google can infer the date and author with reasonable confidence, but it’s guessing. Schema markup tells Google exactly what each piece of information means — in a machine-readable format that leaves no room for misinterpretation.

This guide covers everything from why schema markup matters to how to implement and validate it using the Schema Markup Generator.

What is schema markup?

Schema markup is structured data — a standardised vocabulary defined at schema.org — embedded in your web page to describe its content to search engines. The most common implementation format is JSON-LD (JavaScript Object Notation for Linked Data), a <script> block that sits in your page’s <head> or <body>.

A basic Article JSON-LD looks like this:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to bake sourdough bread",
  "author": { "@type": "Person", "name": "Jane Smith" },
  "datePublished": "2026-06-15"
}

That’s it. Three fields tell Google the page type, who wrote it, and when — information Google would otherwise have to extract and guess.

Why it matters: rich results

The main reason to implement schema markup is rich results — enhanced SERP appearances that go beyond the standard blue link + description. Rich results can include:

FAQ dropdowns (FAQPage schema) — expandable Q&A pairs directly in the search listing
Review stars and price (Product schema) — price range and rating visible without clicking
Event listing (Event schema) — date, time, and location shown inline
Recipe info (Recipe schema) — cooking time, calories, and rating
How-to steps (HowTo schema) — numbered steps preview in search
Breadcrumb trail (BreadcrumbList schema) — shows your site hierarchy below the URL

Studies consistently show rich results earn higher click-through rates than plain listings at the same position — often 20–30% higher for FAQ and review schemas.

The 10 supported schema types

Article

Used for blog posts, news articles, and editorial content. Key fields: headline, author, datePublished, dateModified, publisher, image. Required for Google News eligibility.

FAQPage

Each page with a list of questions and answers qualifies. When implemented correctly, up to 3 Q&A pairs appear as expandable dropdowns directly in the search result — below the title and description — without the user clicking.

Product

For e-commerce product pages. The offers object with price and priceCurrency unlocks the price display in results. Add an AggregateRating object (from review platforms or your own data) to get star ratings.

LocalBusiness

Puts your business information in Google’s Knowledge Panel: name, address, phone, hours, and website. Crucial for “near me” searches and local SEO.

Organization

Similar to LocalBusiness but for non-location businesses. Covers name, URL, logo, and sameAs links to your social profiles — helping Google associate your social accounts with your website.

Event

Shows event name, start date, end date, and location in search results. Supports Online, Offline, and Mixed attendance modes for hybrid events.

Person

For author bio pages, professional profiles, and personal sites. Helps Google associate articles with their author for E-E-A-T (Experience, Expertise, Authoritativeness, Trust) signals.

BreadcrumbList

Replaces the raw URL below the title with a readable trail like “Home > Blog > SEO > Schema Markup Guide.” Improves appearance and helps Google understand your site structure.

HowTo

Step-by-step instruction content. When a HowTo appears for a featured snippet, the steps can appear with names and text in search results — a significant visual advantage over competitors.

Recipe

Adds cooking time, calorie count, ingredient summary, and rating to recipe pages in search results.

Implementation walkthrough

Step 1: Choose your schema type

Visit the Schema Markup Generator and select the type that matches your page content. Most pages have one primary schema type, though you can add multiple (a BreadcrumbList alongside an Article, for example).

Step 2: Fill in the fields

Not all fields are required — only populate what you know. The generator excludes empty fields automatically, so your JSON stays clean without null values.

Step 3: Copy the script tag

Click “Copy script tag” to get the complete <script type="application/ld+json">...</script> block. Paste it inside your page’s <head> element — before the closing </head> tag.

Step 4: Validate with Google

Go to Google’s Rich Results Test. Paste either your page URL or the raw markup. The tool shows:

Which schema types were detected
Which rich result types your page qualifies for
Any errors or warnings in your markup

Also check the Schema Markup Validator for schema.org compliance separate from Google’s requirements.

Step 5: Monitor in Search Console

After deploying, go to Google Search Console → Enhancements. Each rich result type you’ve implemented appears as a separate report, showing how many pages have valid markup and whether any errors were found.

Common mistakes

Using the wrong schema type for the content. A FAQ section on a blog post should use FAQPage schema, but if the page is primarily an article, you should probably use Article schema for the main content and add a separate FAQPage block for the Q&A section — not use FAQPage for the whole page.

Inconsistent data between schema and visible content. Google expects schema data to match what’s visible on the page. If your Product schema says the price is $29.99 but the page shows $39.99, the markup may be ignored or result in a manual action.

Leaving empty arrays or null values. Some schema generators emit "author": null or "faqs": [] when fields are empty. These are harmless but cluttered. The Schema Markup Generator excludes empty fields automatically.

Nesting schema inside the body incorrectly. JSON-LD in the <body> works but can be missed by some crawlers. Always prefer <head> placement.

Schema markup and the broader SEO setup

Schema markup works best as part of a complete on-page SEO stack. After implementing your structured data:

Check your Meta Tags — title and description affect click-through from search results
Add a Canonical Tag — prevents duplicate content issues on syndicated or paginated content
Review your robots.txt — ensure Googlebot can reach the pages with your schema markup

Together, these four elements — schema markup, meta tags, canonical tags, and robots.txt — give search engines a clear, accurate picture of your content.

Use the Schema Markup Generator to create valid JSON-LD for any of the 10 supported schema types, copy the script tag, and drop it into your page today.

Frequently Asked Questions

Does schema markup improve Google rankings?

Not directly — Google states structured data is not a ranking signal. But it unlocks rich results (FAQ dropdowns, product stars, event listings) that increase click-through rates, which can indirectly improve ranking over time.

Where should I put the JSON-LD script tag?

Inside the <head> element. Google also reads JSON-LD in the <body>, but <head> is standard and ensures the markup is processed before page content. You can have multiple JSON-LD blocks on the same page for different schema types.

What is the difference between JSON-LD and Microdata?

JSON-LD is a standalone <script> block embedded in the page — it doesn't modify your HTML structure. Microdata uses HTML attributes (itemscope, itemtype, itemprop) directly on your existing elements. Google recommends JSON-LD because it's easier to add and maintain without touching content markup.

Can I use multiple schema types on the same page?

Yes. A page can have an Article schema in one <script> block and a BreadcrumbList schema in another. Google processes all of them independently.

AI Text Summarizer

AI Image Packs

Schema Markup Guide: How to Add Structured Data for Rich Results

Key Takeaways