# Schema markup AI Overviews actually use > Which Schema.org types AI engines read in 2026 and which they ignore - FAQPage, HowTo, Article, Product, Organization+sameAs - plus JSON-LD placement and fixes. _Source: https://seomatrix.ai/blog/schema-for-ai-overviews/ · Updated: 2026-07-19_ --- 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 `