By Rahul Saini, Author at Search Counsel Co. Last updated [July] 2026.

If you searched “schema markup,” you want to know what to add, what still earns rich results after Google’s recent changes, and how to do it right. Here’s all of it. This guide covers what schema is, whether it affects rankings, the 2026 shift in what it’s for, the types that matter, how to add and test it, and how it now feeds AI. It’s where your semantic SEO and extractable content get spelled out in a language machines read directly.

1) What is schema markup?

Three terms get used interchangeably, and they shouldn’t. Structured data is the broad idea of organizing information in a machine-readable format. Schema markup is the specific vocabulary for doing that, defined at Schema.org and shared across Google, Bing, and others. JSON-LD is the code format Google recommends for writing it.

In plain terms, schema labels the parts of your page. It tells a search engine “this is the author,” “this is the publish date,” “this is a step in a recipe,” so the machine understands the meaning behind your words. JSON-LD keeps that labeling in a separate script block, apart from your visible HTML, which makes it easy to add, template, and maintain. Microdata and RDFa are older formats that weave markup into your HTML; they still work, but there’s no reason to choose them for a new site.

2) Is schema markup a ranking factor?

No, not directly, and Google has been consistent about that. Adding schema won’t lift your position by itself. What it does is enable things that matter around ranking: eligibility for rich results, clearer understanding of your content, entity recognition in the Knowledge Graph, and, increasingly, trust signals AI engines use. It sits alongside the other ranking factors rather than among them.

The click-through effect is real. Rich results, the enhanced listings schema can produce, stand out and get clicked more. Nestlé measured pages shown as rich results getting an 82% higher click-through rate than non-rich listings. So schema is a lever for visibility and clicks, and now for AI citations, even though it’s not a ranking factor in the strict sense.

3) Rich results and the 2026 shift

This is the part most older guides get wrong. Schema used to be mostly about winning rich results, those star ratings, FAQ dropdowns, and breadcrumb trails in the SERP. Google has steadily narrowed which ones show. FAQ rich results are now limited to authoritative government and health sites, so a typical business won’t get FAQ dropdowns no matter how clean the markup. HowTo rich results were deprecated. A 2026 update trimmed these further.

But the value of schema didn’t fall, it moved. The shift is from schema as a display trigger to schema as an AI trust and entity signal. Google’s AI systems read structured data to verify claims, resolve who or what a source is, and judge credibility when building an answer, which can earn you a citation even when no rich result appears. In one controlled experiment, of three near-identical pages, only the one with clean schema was cited in an AI Overview and ranked well, while the version with no schema failed to index at all. So you still add FAQ and HowTo schema, not for the dropdown, but so machines understand and can extract your content.

4) The schema types that matter

Schema.org has hundreds of types, but a handful cover most real needs. Discipline beats volume: a few accurate blocks outperform fifty half-built ones.

For most content sites, the foundational set is Organization, BreadcrumbList, and the right content type (Article), plus FAQPage where it fits. Start there and add more only when a specific rich result genuinely matches your content.

5) How to add schema markup

The cleanest method is a JSON-LD block in the page head. Here’s a minimal Article example:

A few practical notes. Most people add schema through a CMS plugin like Yoast or Rank Math, which generates it for you; you can also hand-code it or deploy through a tag manager, though tag-manager schema needs extra testing because it renders through JavaScript. Multiple JSON-LD blocks on one page are fine, and you can nest related entities in a single block using an @graph array, connecting them with @id references. If your CMS makes JSON-LD impractical, that’s the main case for older formats. For deeper, site-wide implementation, this crosses into technical SEO.

6) Google’s structured data rules

Google’s guidelines are strict, and breaking them can trigger a manual action. The essentials:

• Mark up only visible content. If it’s not on the page for users to see, don’t put it in your schema. Marking up hidden content is treated as spam and sits firmly in black-hat territory.
• Match the page exactly. The schema must describe the actual content. Don’t describe a performer, product, or review that isn’t there.
• Be complete. Include the required properties for your type. Partial markup, like Product schema missing its rating, produces no rich result at all.
• Be accurate and honest. No fake reviews, no misleading or irrelevant markup, no impersonation.
• Use the most specific type. Pick the closest Schema.org type and property names for your content, and put the schema on the page it describes.

7) How to test and monitor

Never deploy schema without validating it. Two tools, two jobs.

• Rich Results Test. Google’s tool shows which rich results your markup is eligible for and previews them. Use its URL mode for schema injected by JavaScript or a tag manager, since code-snippet mode won’t run it.
• Schema Markup Validator. The Schema.org validator checks your markup against the spec, catching issues that don’t affect Google but might affect other engines.
• Search Console. After deploying, watch the Enhancement and rich-result reports in Google Search Console to catch errors across your live pages over time.

8) Schema for AI and entities

This is why schema matters more now, not less. Structured data gives AI engines machine-readable context about your entities, attributes, and relationships, which they use to interpret and reference you reliably. Clean schema helps an AI confidently resolve who you are, and sources it can resolve get cited more often.

Two moves have the highest impact. First, use Organization and Person schema with sameAs links to your authoritative profiles, Wikidata, LinkedIn, and the like, to strengthen how Google recognizes your brand as an entity, the schema side of the entity work that gates AI visibility. Second, mark up FAQ and Q&A sections so each pair is a labeled, extractable unit, which supports the extractable content that wins citations. Together these feed your wider AI search optimization, and they reinforce the trust signals AI weighs when choosing sources. Our guide to schema for AI citations goes deeper on that specific angle.

9) Common schema mistakes

The errors that waste the effort or cause harm.

• Marking up invisible content. The fastest way to a manual action. Only mark up what’s on the page.
• Incomplete markup. Missing required properties means no rich result. Complete it or skip it.
• Wrong type. Tagging a category page as Product, or a blog as something it isn’t. Use the accurate type.
• Schema drift. Stale prices, dates, or authors in the JSON-LD after the page changed. Generate from live data.
• Chasing dead rich results. Building FAQ or HowTo markup expecting dropdowns that no longer show for most sites. Add them for understanding, not display.
• Never validating. Deploying without the Rich Results Test, then wondering why nothing shows.

10) Sources used for this guide

This guide leans on Google’s documentation and current structured-data research.

FAQ: schema markup

Conclusion: label your page for the machines

Schema markup is how you hand search engines and AI a clean description of your page instead of making them guess. Write it in JSON-LD, mark up only what’s really there, start with the foundational types, validate before you publish, and keep it in sync with your content. The rich-result payoff has narrowed, but the bigger one has grown: schema is now how machines confirm who you are and decide whether to cite you.

That completes the on-page toolkit. To bring it together, revisit how entities make you legible to search in semantic SEO, structure pages to be quoted in our extractable content guide, or return to the complete guide to on-page SEO.