Schema markup: which types are worth adding in 2026

Structured data tells search engines what your content is rather than making them infer it from prose. It is not a ranking factor. It changes how your result is displayed, and - increasingly the bigger reason - it gives AI answer engines unambiguous facts to quote.

Use JSON-LD

Three formats exist. Use JSON-LD.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Acme",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Any",
  "offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" }
}
</script>

Google explicitly recommends it, and unlike microdata and RDFa it lives in one block instead of being tangled through your markup - which means it does not break when someone restyles the page.

What still produces rich results

BreadcrumbList - replaces the URL in the result with a readable path. Cheap, universally supported, and the highest ratio of effect to effort on this list. Put it on every page except the homepage.

Product with Offer and AggregateRating - price, availability and stars in the result. Requires real reviews on the page; fabricating them is a manual action.

Article - feeds Top Stories and Discover. Needs headline, datePublished, dateModified and author.

Organization - powers the knowledge panel for brand searches. One block on the homepage with name, url, logo and sameAs links to your social profiles.

SoftwareApplication / WebApplication - for tools and apps. No rich result of its own in most cases, but it is the clearest way to tell an AI engine that a page is a free tool that does X.

Event, Recipe, JobPosting, VideoObject - strong rich results in their verticals.

What Google retired

FAQPage - restricted to authoritative government and health sites in 2023. Still worth adding, but for AI parsing, not for rich results.

HowTo - rich results dropped entirely in 2023. Same reasoning applies.

Review on a page reviewing your own product - self-serving review markup has been ignored for years.

Do not remove FAQ and HowTo markup you already have. It costs nothing and remains the most machine-readable form of that content.

Rules that keep you out of trouble

Mark up only what is visible. This is the rule with real consequences. Structured data describing content a user cannot see on the page is a manual-action risk. An FAQ in an accordion is fine - it is in the DOM and reachable. An FAQ that only exists in JSON-LD is not.

Be accurate. Prices, availability and ratings must match the page. A stale price in JSON-LD is worse than none.

Validate against the Rich Results Test, not a JSON linter. Valid JSON can be invalid schema - missing a required property produces syntactically perfect, functionally ignored markup.

One @graph or several script tags, both fine. Do not duplicate the same entity in both.

Server-render it. Structured data injected by client-side JavaScript is often missed. If your framework renders JSON-LD in a useEffect, it may as well not exist.

What to add to a small site, in order

1. Organization on the homepage.
2. BreadcrumbList on every other page.
3. Article on every blog post.
4. SoftwareApplication on product and tool pages.
5. FAQPage wherever a real, visible FAQ exists.

That is an afternoon of work, and it covers everything a site under fifty pages needs. Anything beyond it is diminishing returns until you have a vertical that supports a specific rich result.