Do FAQPage and HowTo schema still work in 2026?

Google retired their rich-result treatment for most sites in August 2023, so they no longer add visible SERP features. The markup is still valid Schema.org and still helps crawlers and AI engines parse your Q&A and step content - just don't expect a SERP reward for it.

Where should JSON-LD go on the page?

A single script type=application/ld+json block, in either the head or the body - Google reads both. Keep one connected graph per page, make every value match the visible content, and validate with Schema.org's validator before you ship.

Does schema markup rank you higher in AI Overviews?

No. Schema is an entity and attribution signal, not a ranking factor. It helps engines identify who you are (Organization + sameAs) and who wrote a claim (author), which makes your content safer to cite - but ranking is driven by content quality and relevance.

Schema markup AI Overviews use (2026)

In short: schema markup doesn’t rank you - it tells a machine who you are, what a page is about, and who to attribute a claim to. In 2026 the useful question isn’t “which schema gets me a rich result” but “which Schema.org types do AI engines actually read.” Some still earn visible SERP features, some are pure entity signals, and a couple that people still obsess over - FAQPage and HowTo - quietly lost their Google rewards in 2023. Here’s what to keep, what to drop, and how to ship JSON-LD that validates and gets read.

Schema is an entity signal, not a ranking trick

The oldest myth in structured data is that adding schema “boosts rankings.” It never did, and it matters less than ever. What schema actually does is disambiguate. When an answer engine reads Organization with a sameAs pointing to your Wikidata, LinkedIn, and Crunchbase profiles, it can connect the page to a known entity instead of guessing. When it reads Article with a named author, it knows who to attribute a claim to - which is exactly the check a model runs before it cites you in an AI Overview.

So treat schema the way you’d treat a passport, not a megaphone. It doesn’t make you louder; it makes you identifiable and quotable. That reframing changes which types are worth your time.

Which types AI engines read vs ignore (2026)

Not all markup is equal. Some types drive visible features, some feed the entity graph silently, and some are effectively decorative now.

Schema type	What AI engines do with it	Worth it in 2026
`Organization` + `sameAs`	Resolve you to a known entity (Knowledge Graph, Wikidata)	Yes - foundational
`Article` + `author`	Attribute claims to a named, verifiable author	Yes - the E-E-A-T anchor
`Product` + `offers`/`review`	Read price, availability, ratings for shopping answers	Yes - commerce
`BreadcrumbList`	Understand site hierarchy and a page’s place in it	Yes - cheap, structural
`FAQPage`	Parse Q&A pairs (no Google rich result since 2023)	Partial - parsing only
`HowTo`	Parse ordered steps (no Google rich result since 2023)	Partial - parsing only
`WebSite` + `SearchAction`	Enable the sitelinks search box	Minor

The pattern: the durable value is identity and attribution (Organization, author), then commerce facts (Product), then structure (BreadcrumbList). FAQPage and HowTo are still legal, still parsed, but no longer a SERP win - so mark them up if the content is genuinely a Q&A or a procedure, not as a growth hack.

JSON-LD: placement and shape

Google recommends JSON-LD over Microdata and RDFa, and so does everyone else. The mechanics are simpler than the folklore suggests:

One block, either location. A single <script type="application/ld+json"> works in <head> or <body> - Google renders and reads both. You don’t need it above the fold.
One connected graph per page. Use a top-level @graph array and reference entities by @id so your Article, its author, and your Organization link to each other instead of floating as orphans.
Match the visible content. Every value in the JSON must correspond to something a user can see on the page. A price in schema that isn’t on the page is the fastest way to get markup ignored or flagged.

The mistakes that void your markup

Validate before you ship

Two free checks, both worth running on every template change:

Schema.org’s Schema Markup Validator (validator.schema.org) - checks your markup against the vocabulary itself, independent of any search engine’s feature rules.
Google’s Rich Results Test - tells you whether Google can parse the page and which, if any, rich features it’s eligible for.

They answer different questions: the first is “is this valid Schema.org,” the second is “will Google do anything with it.” A page can pass the first and show no eligible features in the second - which, post-2023, is exactly the normal state for FAQPage and HowTo. If you’d rather automate the whole pass, our schema-fix tool audits every page’s JSON-LD, flags mismatches with visible content, and patches the graph so Article, author, and Organization actually connect.

Checklist

Organization on the site, with a real sameAs array (Wikidata, LinkedIn, socials).
Article (or BlogPosting) with a named author as a Person node.
Product carries offers + genuine review/aggregateRating where applicable.
BreadcrumbList on every deep page.
One @graph per page; entities linked by @id, no orphans.
Every schema value matches visible on-page content.
Passes both validator.schema.org and Google’s Rich Results Test.
FAQPage/HowTo only where the content is genuinely a Q&A or a procedure.

FAQPage / HowTo markup after Google's 2023 rich-result retirement

Visible Google rich result 0%

Still parsed as entity/content data 100%

источник: internal audits, 2026

The chart is the point: the same FAQPage markup that earns zero visible SERP features is still fully parseable content for the crawlers and AI engines that read structured data. Deprecation of a feature is not deletion of the signal.

In short

Schema is an entity and attribution signal, not a ranking factor - build for identity, not for a boost.
The durable types are Organization+sameAs, Article+author, and Product+offers - in that order.
FAQPage and HowTo lost their Google rich results in 2023 but are still parsed content.
JSON-LD goes in one block, head or body, as one connected @graph; every value must match the page.
Validate with both Schema.org’s validator and Google’s Rich Results Test before every deploy.

Sources

Schema.org - the vocabulary itself and its getting-started guide; JSON-LD is the recommended syntax.
Google Search Central, “Structured data markup that Google Search supports” - the authoritative list of which types produce features.
Google Search Central Blog, “Changes to FAQ and HowTo rich results” (August 2023) - the deprecation of FAQPage and HowTo rich results for most sites.
Google Search Central, “Article (Article, NewsArticle, BlogPosting) structured data” - author, datePublished, and attribution fields.

Schema markup AI Overviews actually use