Schema Markup: The Rich Results Field Guide

Schema markup is the difference between a blue link and a rich result. In 2026, the vocabulary is broader than ever, but the rich-result surface area is narrower than people think. This guide separates the schema that works from the schema that wastes effort.

What schema markup actually does

Schema markup is structured data that helps parsers understand the meaning of a page’s content. Google reads JSON-LD, RDFa, and microdata — JSON-LD is the modern default. Markup does not directly rank; it earns eligibility for rich results.

The rich results that still work in 2026

Article

Required for Top Stories eligibility on news sites. Properties: headline, datePublished, author, image, publisher. Rich result: Top Stories carousel, sometimes with a thumbnail.

FAQPage

Q&A pairs. Rich result: expandable Q&A below the snippet. Note: Google throttles display — showing FAQ rich results only on certain queries, certain verticals. Do not assume you’ll get it.

HowTo

Step-by-step instructions. Rich result: list-style snippet with optional images. Mostly desktop-only in 2026. Strong CTR when it appears.

Product

Required for product rich results: price, availability, ratings. Strongest impact on ecommerce CTR.

LocalBusiness

NAP, hours, geo coordinates, address. Rich result: knowledge panel for branded queries.

Organization

Logo, social profiles, contact. Drives the site-links search box and knowledge panel for branded queries. Every site should have one on the homepage.

BreadcrumbList

The path from the homepage to the current page. Rich result: breadcrumb trail in the snippet. Easy win; small CTR lift.

Video

Required for video rich results: thumbnail, description, duration, upload date.

The schemas that don’t earn rich results anymore

• Review / AggregateRating — Self-served reviews are filtered. Only third-party review sites earn star rich results.
• Recipe — Eligibility throttled hard. Only top recipe sites see rich results.
• Event — Only for ticketing partners in some regions.
• JobPosting — Restricted to specific verticals and ATS integrations.

The JSON-LD format

JSON-LD in a script tag in the head:

<script type="application/ld+json">
  &#123;
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "How to Write Schema Markup That Actually Renders",
    "datePublished": "2026-02-10",
    "author": &#123; "@type": "Person", "name": "Ada Lovelace" &#125;
  &#125;
</script>

Use our Schema Generator to skip the boilerplate.

Validation

Two tools, always:

1. Rich Results Test — what Google specifically supports.
2. Schema.org Validator — the spec, regardless of Google’s surface area.

Resolve every error. Warnings can stay; errors mean your markup may be ignored entirely.

Common schema mistakes

• Microdata or RDFa. Stick with JSON-LD — easier to debug, easier to maintain.
• Nested markup that contradicts itself. Article says author=X, breadcrumb says author=Y.
• Markup that does not match visible content. Markup says 5 stars; no rating visible on page.
• Missing required properties. Each type has required and recommended fields. Skip required = no rich result.
• Stale markup. The event date is in the past; the price has changed; the recipe no longer exists.

Wrap-up

Schema markup is the easiest rich result to earn. Use our generator, validate, ship, monitor in Search Console. Skip the schemas that don’t pay off — your time is the scarcest resource in SEO.