Schema Markup and Rich Results: The Honest Guide for 2026

Schema markup is code you add to your pages that describes your content in a structured way — telling search engines "this is an article, written by this person, published on this date" instead of making them guess. Done right, it unlocks rich results: star ratings, product prices, breadcrumbs, and other enhanced listings that earn more clicks. But the landscape changed a lot: some rich results you may have heard about, like FAQ dropdowns, no longer exist. This guide gives you the honest, current picture — what schema still earns you in 2026, how to implement it, and what to stop doing.

What schema markup actually does

Search engines are good at reading text but bad at certainty. When your page says "Apple," is that the fruit or the company? When it shows "4.8," is that a rating or a version number? Schema markup — standardized vocabulary from schema.org, usually written as JSON-LD — removes that ambiguity by labeling your content's parts explicitly.

Two things schema does not do, despite what some guides claim:

• It's not a ranking boost. Google has never said schema directly improves rankings. It improves understanding and eligibility for rich results — which can earn more clicks, which is the real prize.
• It's not required for AI features. Google has said there's no special schema needed for AI Overviews or similar features. Accurate structured data helps systems understand your page, but no markup type is a ticket in.

The honest value proposition: schema makes your listings clearer and occasionally richer, and richer listings get clicked more. That's worth doing — just with realistic expectations.

Rich results that still exist in 2026

Google maintains a gallery of search features powered by structured data. The ones still earning real estate for typical sites include:

• Article — enhanced article listings, especially for news and blog content (headline, images, dates).
• Product — price, availability, and review snippets on product pages. One of the highest-value rich results in e-commerce.
• Review snippets — star ratings aggregated from reviews on your page.
• BreadcrumbList — shows your page's position in the site hierarchy instead of a raw URL.
• Organization / LocalBusiness — powers knowledge panels and local listings with logo, contact info, hours.
• Video — video thumbnails and details in results.
• Event — dates, venues, and ticket info for events.
• Recipe — cooking time, ratings, and images for recipe pages.
• JobPosting — structured job listings in Google for Jobs.

Eligibility is strict: the markup must describe content that's visible on the page, and each type has detailed guidelines. Google's structured data documentation is the reference for what's currently supported.

What happened to FAQ rich results

This one needs a clear explanation, because outdated advice is everywhere. FAQ rich results — the expandable Q&A dropdowns that used to appear under listings — went through a long wind-down:

• May 2019: Google launched FAQ rich results. Sites adding FAQPage markup saw listings expand dramatically, and the tactic spread fast.
• August 2023: Google restricted FAQ rich results to "well-known, authoritative government and health websites," cutting off virtually every commercial and publisher site. Google's August 2023 announcement cited the goal of a cleaner, more consistent search experience.
• May 2026: Google ended FAQ rich results entirely — for all sites, including the government and health sites that had kept access. Google's documentation noted the removal, with the search appearance filter and reporting following in June 2026.

So if a guide tells you FAQPage schema will get you "free featured snippets," that guide is years out of date. The rich result is gone.

Does that mean you should remove existing FAQPage markup? Not necessarily. Google has said structured data that isn't used for a visible feature causes no harm — it just has no visible effect. And a well-organized FAQ section still serves readers and gives AI systems clean Q&A content to work with. Keep the FAQ content for humans; just don't expect a rich result from the markup anymore.

HowTo rich results followed a similar path — restricted to desktop in August 2023, then effectively retired. Same lesson: never build a strategy around a single rich result type, because Google trims them regularly.

Implementing schema: JSON-LD basics

Google recommends JSON-LD — a script block in your page's <head> — over older formats like microdata. It's cleaner, easier to maintain, and doesn't clutter your HTML. Here are the most useful types with minimal examples.

Article

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "datePublished": "2026-10-01",
  "dateModified": "2026-10-07",
  "image": "https://example.com/image.jpg",
  "publisher": {
    "@type": "Organization",
    "name": "Your Site Name"
  }
}
</script>

Use dateModified whenever you update the article, and keep it in sync with the visible date on the page. Mismatched dates erode trust.

Product with reviews

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Widget Pro",
  "image": "https://example.com/widget.jpg",
  "description": "A short, honest product description.",
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "128"
  }
}
</script>

Critical rule: only mark up reviews that are actually on the page and collected by you. Fabricating ratings in markup is one of the fastest ways to earn a manual penalty.

BreadcrumbList

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Blog",
     "item": "https://example.com/blog"},
    {"@type": "ListItem", "position": 2, "name": "SEO Guides",
     "item": "https://example.com/blog/seo"},
    {"@type": "ListItem", "position": 3, "name": "Schema Guide"}
  ]
}
</script>

Breadcrumbs are low effort and widely eligible — there's little reason not to include them on any site with hierarchical content.

Organization

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://x.com/example"
  ]
}
</script>

Put this on your homepage. The sameAs links help search engines connect your site to your official profiles — useful for knowledge panels and brand disambiguation.

Testing and validating your markup

Never deploy schema untested. Two official tools:

• Rich Results Test (search.google.com/test/rich-results) — paste a URL or code snippet and Google tells you which rich results the page is eligible for, plus any errors. Note that FAQ support was removed from this tool in 2026 along with the feature itself.
• Schema Markup Validator (validator.schema.org) — checks your markup against the schema.org vocabulary itself, catching syntax and structural errors regardless of Google's feature support.

Test in this order: validator first (is the code correct?), Rich Results Test second (is the page eligible for anything?). Then check Google Search Console's enhancements reports after deployment to catch issues at scale.

Mistakes that get schema ignored — or penalized

1. Marking up invisible content. Every entity in your structured data must be visible to users on the page. Hiding extra keywords, reviews, or FAQs in markup alone is cloaking, and Google issues manual actions for it.
2. Wrong type for the page. FAQPage is for pages where the site provides the questions and single definitive answers. Forums and Q&A communities where users submit answers need QAPage instead. Using the wrong type gets the markup ignored.
3. Fake reviews and ratings. Aggregate ratings must reflect real reviews on the page. Made-up counts or self-awarded five stars are a penalty waiting to happen.
4. Copy-pasting markup across pages. Each page's schema must describe that page. A product template with another product's price, or article markup with the wrong date, creates exactly the inconsistency rich-result systems are designed to reject.
5. Chasing retired features. Building pages around FAQ or HowTo rich results in 2026 is building on a removed foundation. Check Google's current gallery before investing.
6. Schema instead of content. Markup describes content; it doesn't substitute for it. A thin page with perfect schema still loses to a thorough page with basic schema.

A practical priority list for small sites

If you're starting from zero, implement in this order — highest value per effort first:

1. Organization on the homepage (brand clarity, knowledge panel support).
2. BreadcrumbList sitewide (easy, broadly eligible).
3. Article on every blog post and guide (dates, authorship, images).
4. Product + reviews if you sell anything (price and stars in results are worth real money).
5. LocalBusiness if you serve a local area (feeds local listings).
6. Video / Event / Recipe / JobPosting only if that content type is core to your business.

Most WordPress SEO plugins generate the basic types (Organization, Article, BreadcrumbList) automatically — check what's already emitted before hand-coding anything, to avoid duplicate or conflicting markup.

Schema is one layer of a technically healthy site. Pair it with accurate meta titles and descriptions, a clean XML sitemap so Google discovers your marked-up pages, and a robots.txt that doesn't accidentally block the crawlers you want reading them.

Frequently asked questions

Does schema markup improve Google rankings?

Not directly. Google has never listed structured data as a ranking factor. Its value is indirect: eligibility for rich results (which earn higher click-through rates) and clearer understanding of your content. Treat it as a CTR and clarity tool, not a ranking tactic.

Should I still use FAQPage schema now that FAQ rich results are gone?

It's harmless but produces no visible result in Google Search. Keep your FAQ content well-structured for readers and AI systems — the Q&A format still helps both — but don't expect the markup itself to change how your listing looks.

What's the difference between FAQPage and QAPage?

FAQPage is for pages where the site itself provides questions with single, definitive answers. QAPage is for community Q&A — forums and product pages where users submit multiple answers to one question. Using FAQPage for user-generated Q&A gets the markup ignored.

JSON-LD, microdata, or RDFa — which should I use?

JSON-LD. It's Google's recommended format, it lives in a separate script block instead of being woven through your HTML, and it's far easier to maintain and debug. There's no SEO advantage to the older formats.

How do I know if my rich results are actually showing?

Check Google Search Console under Enhancements for valid items per type, and use the Rich Results Test on individual URLs. For actual SERP appearance, search your target queries in an incognito window — but remember rich results vary by query, device, and location.

Can bad schema get me penalized?

Yes, for spammy markup — fake reviews, hidden content in structured data, or markup that misrepresents the page can trigger manual actions. Honest mistakes (wrong types, syntax errors) just get ignored, not penalized. When in doubt, validate before deploying.