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. Schema implementation requires clean HTML and proper rendering — see Technical SEO for the rendering audit.

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 lives in a <script type="application/ld+json"> tag in the <head>. It is not visible to users — it is machine-readable metadata. Here is a complete FAQPage example that passes the Rich Results Test:

<script type="application/ld+json">
  &#123;
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      &#123;
        "@type": "Question",
        "name": "What is schema markup?",
        "acceptedAnswer": &#123;
          "@type": "Answer",
          "text": "Schema markup is structured data that helps search engines understand the meaning of your page content, written in JSON-LD format and placed in the page head.",
          "upvoteCount": 42
        &#125;
      &#125;,
      &#123;
        "@type": "Question",
        "name": "Does schema markup improve rankings?",
        "acceptedAnswer": &#123;
          "@type": "Answer",
          "text": "Schema markup does not directly affect ranking. It earns eligibility for rich results — enhanced SERP listings — that can improve your CTR.",
          "upvoteCount": 31
        &#125;
      &#125;
    ]
  &#125;
</script>

A common mistake is mismatched Question count between the markup and the visible FAQ on the page. If your page shows 5 questions, your JSON-LD must have 5 Question entries in mainEntity. Use our Schema Generator to build correct markup without hand-editing JSON.

Validation workflow

Run validation at three points — never skip the first two:

1. During development. Paste your HTML into the Rich Results Test after every markup change. Errors surface immediately.
2. Before shipping. Re-run the Schema.org Validator on the final page. Warnings are acceptable; errors mean Google ignores the markup.
3. After publishing. Check the Search Console Enhancements tab for the specific schema type. It shows which URLs Google successfully parsed and any errors detected at crawl time.

Resolve every error before it compounds. A stale error in a template file silently infects every page that uses it.

Common schema mistakes

• Microdata or RDFa. JSON-LD is the modern standard — easier to debug, easier to maintain, and Google’s preferred format since 2015.
• Nested markup that contradicts visible content. Article schema says the author is Jane Doe; the breadcrumb says the author is John Smith. Google notices the conflict.
• Markup that does not match the page. Schema claims 5 stars; no star rating appears anywhere on the page. This is a policy violation.
• Missing required properties. Each schema type has mandatory fields. Article requires headline, datePublished, author, image, and publisher. Skipping any of these forfeits the rich result.
• Stale markup. The event date is in the past. The product price changed three months ago. The job posting was filled. Google serves markup that no longer reflects reality — and penalizes sites that persist in doing so.
• Duplicate type stacking. Adding Article and WebPage to the same page when only one primary type applies. Pick the most specific type and stick to it.

Monitoring in Search Console

The Enhancements tab is where schema goes to be validated in production. It shows:

• Success count — how many URLs Google parsed successfully.
• Error count — which URLs have unresolvable markup errors.
• Warnings — non-blocking issues, typically missing recommended (not required) fields.

Check this tab monthly. If a template change introduces an error, you want to catch it before it affects hundreds of pages.

Wrap-up

Schema markup is the cheapest rich result to earn. Use our generator, validate at every stage, and check Search Console after publishing. Skip the schemas that don’t pay off — your time is the scarcest resource in SEO.