Schema Markup That Wins Rich Results: The Types Worth Your Time in 2026

Structured Data Is Not a Ranking Factor

Google has been consistent about this: structured data does not directly boost rankings. What it does is make you eligible for rich results — star ratings, FAQ accordions, breadcrumb trails, recipe cards, sitelinks.

The mechanism is click-through rate, not position. A result occupying three times the vertical space with review stars attached earns dramatically more clicks from the same rank. That is the entire business case.

It also matters increasingly for AI answer engines, which parse JSON-LD as a reliable structured summary of a page rather than inferring it from prose.

Use JSON-LD, Not Microdata

Three syntaxes are valid. Only one is worth using.

• JSON-LD — a <script type="application/ld+json"> block. Decoupled from your markup, so redesigns do not break it. Google's explicitly recommended format.
• Microdata — attributes woven into HTML. Brittle; one refactor and it is gone.
• RDFa — same problem, more verbose.

Write JSON-LD. It can go in <head> or <body>, and Google reads it either way — including when injected by JavaScript, though server-rendering it is more reliable.

The Types That Actually Produce Visible Rich Results

BreadcrumbList

The highest ratio of effort to payoff on this list. Replaces the raw URL in the result with a readable hierarchy.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com" },
    { "@type": "ListItem", "position": 2, "name": "Guides", "item": "https://example.com/guides" },
    { "@type": "ListItem", "position": 3, "name": "Sitemaps", "item": "https://example.com/guides/sitemaps" }
  ]
}

FAQPage

Renders expandable questions directly in the result. Two hard requirements: the questions and answers must be visible on the page, and the content must be genuinely informational rather than promotional. Marking up invisible or advertising copy is a manual-action risk.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Is the tool free?",
    "acceptedAnswer": { "@type": "Answer", "text": "Yes. Every tool is free with no signup." }
  }]
}

Product with Offers and AggregateRating

Price, availability and star ratings in the SERP. AggregateRating requires reviews that are visible on the page and collected from real customers — self-serving markup for your own business without genuine reviews is a policy violation.

Article and BlogPosting

Feeds Top Stories and the article carousel, and supplies the date and author Google displays. Include headline, datePublished, dateModified, author, publisher and image.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Schema Markup That Wins Rich Results",
  "datePublished": "2026-08-16",
  "dateModified": "2026-08-16",
  "author": { "@type": "Organization", "name": "ProfitTool" },
  "publisher": {
    "@type": "Organization",
    "name": "ProfitTool",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  },
  "image": "https://example.com/og-image.png"
}

Organization and WebSite

Site-wide, on the homepage. Organization feeds the knowledge panel; WebSite with potentialAction can produce a sitelinks search box.

SoftwareApplication

For tools and apps: shows category and price. Combined with genuine ratings it produces a compact app card.

LocalBusiness

Non-negotiable if you have a physical location. Drives the map pack alongside your Google Business Profile.

The Types That Rarely Do Anything

Do not spend a sprint on these expecting SERP changes: HowTo (Google removed its rich result), Person on ordinary author pages, Service, WebPage on its own, or ImageObject outside licensing contexts. They are still useful as machine-readable context for AI crawlers — just do not promise anyone a visual change.

Rules That Get Markup Ignored

1. Marking up content that is not on the page. The single most common disqualifier.
2. Missing required properties. Each type has a required set; omit one and the item is dropped silently.
3. Fake or self-issued reviews. A manual-action category, not a warning.
4. Contradicting your visible content. A price of 9.99 in JSON-LD and 19.99 on the page.
5. Wrong data types. "price": "$9.99" is invalid — the currency belongs in priceCurrency and the value must be a bare number.
6. Blocking the page in robots.txt. No fetch, no parse.

Link Your Entities Together

Give each node an @id and reference it from the others. This turns a pile of disconnected blocks into a graph Google can traverse:

{
  "@type": "BlogPosting",
  "@id": "https://example.com/post#article",
  "publisher": { "@id": "https://example.com/#organization" },
  "breadcrumb": { "@id": "https://example.com/post#breadcrumbs" }
}

Validate Twice

Two tools, two jobs:

• Google's Rich Results Test — tells you what Google can actually render. This is the one that decides eligibility.
• Schema.org Validator — tells you whether your JSON-LD is technically valid, including types Google does not use.

Then watch Search Console → Enhancements for live errors across the whole site.

Generate blocks with the Schema Markup Generator, check how the result will look with the SERP Preview tool, and get your titles and descriptions right with the Meta Tag Generator.

Related: Meta Description Best Practices and SEO Title Tag Best Practices.