Developers & Technical · Guide · Writing & Content
What Is Schema Markup?
Schema markup, rich results, and JSON-LD explained without jargon — with the 5 schema types most sites actually need.
Schema markup is structured data you add to your HTML that tells search engines what your page is actually about. A recipe page, a product page, and a job posting all look like “a page” to a plain web crawler. With schema, they become a recipe, a product, and a job — each with their own structured fields and each eligible for rich results in search.
The payoff is real. Pages with valid schema can earn star ratings, FAQ accordions, price displays, breadcrumbs, and knowledge-panel entries — all of which expand the listing and push competitors off the screen. This guide covers what schema is, which types matter, and how to implement it without breaking your site.
Advertisement
What schema markup actually is
Schema is a shared vocabulary — maintained at schema.org — that Google, Bing, Pinterest, and other search engines understand. You embed it in your page as JSON-LD, a small block of JavaScript-flavored JSON, and it describes the entity on the page: article, product, event, person, organization, and around 800 others. Crawlers read the JSON, match it to their knowledge graph, and optionally show a richer result in search.
JSON-LD vs microdata vs RDFa
There are three ways to write schema. Google explicitly recommends JSON-LD because it lives in a single <script> tag in the <head>or <body>, doesn’t interfere with visible HTML, and is easy to maintain. Microdata and RDFa embed attributes directly in HTML tags — more fragile, harder to audit. Pick JSON-LD. Use our schema markup generator to build it without memorizing the syntax.
The schema types worth your time
Not every schema type triggers a rich result. The high-value ones in 2026 are: Article (news, blog posts), FAQPage (shows accordion in results), HowTo (numbered step carousel), Product (price, availability, ratings), Recipe (image, time, calories), Event (dates, venue), BreadcrumbList (replaces URL with path), Organization (knowledge-panel logo), and LocalBusiness (hours, address, map pin).
FAQPage is the fastest win
If you write any content that answers questions, add FAQPage schema. It’s the cheapest rich result to earn — Google shows your FAQ as a collapsible accordion under your listing, doubling vertical real estate. You can generate the JSON-LD directly with our FAQ schema generator. Note: only questions with public, visible answers on the page are eligible.
How to add it to your site
Paste the JSON-LD block inside a <script type="application/ld+json">tag anywhere in the page. In Next.js or similar frameworks, generate it server-side and render it in the page head. Don’t inject it with client-side JavaScript — Googlebot sometimes doesn’t wait for JS to execute before reading the markup.
Validate before you ship
Google’s Rich Results Test (search.google.com/test/rich-results) and the Schema Markup Validator (validator.schema.org) are the two tools you need. Paste a URL or the raw HTML and they flag every required property you forgot. One invalid character in the JSON and the entire block is ignored, so validating is not optional.
Match the schema to the visible content
Google’s spam policy requires schema to describe content that is actually visible to the user. Claiming a 5-star rating in schema that doesn’t appear on the page can earn a manual action and tank rankings. The rule: if it’s in the schema, it should be on the page too.
Watch for conflicting schema
Having both Article and NewsArticle schema on the same page, or two Product blocks for the same product, confuses crawlers. Audit old pages before adding new schema — WordPress plugins sometimes auto-add their own markup that collides with yours.
Breadcrumb schema is quietly powerful
BreadcrumbList replaces the raw URL in the search result with a readable path — Home > Guides > Schema Markup. It takes five minutes to add site-wide, lifts CTR on every indexable page, and has no downside. Do this first if you haven’t already.
Don’t chase every rich result
Review schema availability in your vertical. Recipe schema is useless for a SaaS site; Product schema is pointless on a blog. Pick the two or three types that map to your content and implement them well. Twenty half-broken schema blocks are worse than two correct ones.
Review monthly in Search Console
Google Search Console has an “Enhancements” section that shows every schema type it detected on your site, plus errors and warnings. Check monthly. Any new error usually means a template change broke the markup on a whole section of pages.
Related: SEO basics for beginners, how to write a meta description, and how to format JSON properly so your schema validates on the first try.