New Schema Types That Matter for GEO in 2026

The schema types that matter most for GEO in 2026 are Organization, FAQPage, HowTo, Article, and Person, with entity disambiguation markup (SameAs, knowsAbout) becoming the highest-use implementation this year. Schema tells AI engines not just what your page says, but what your content is - and that distinction now determines whether you get cited or ignored.

Here's the context: Google's March 2026 core update changed what schema is for. It narrowed rich result eligibility for several widely-abused schema types, including FAQ and HowTo on non-primary content pages, while simultaneously making structured data more important for AI answer synthesis. The two effects pull in opposite directions if you're still optimising schema for traditional rich snippets. If you're optimising for GEO, the picture is cleaner: entity-level trust signals matter more than display triggers.

According to PingPrime's audits across 27 brands in 2025-2026, 68% of brand content is not extractable by LLMs due to inadequate structure, and missing or broken markup is the number one error. That's not a small problem. It means the majority of brands have already lost visibility they don't know they're missing.

Why Does Schema Matter Differently for GEO Than for SEO?

For GEO, schema is a trust signal and an extraction aid, not a display trigger. When Google's Gemini-powered AI Mode reads your page, it uses schema to verify claims, establish entity relationships, and assess source credibility during answer synthesis - regardless of whether a traditional rich result appears. That shift, documented in the March 2026 structured data update, is the most important strategic change in how to think about structured data since rich snippets launched.

The practical consequence: a page with accurate, well-implemented schema gets cited in AI answers even when it earns no visible SERP feature. A page without schema may rank organically but remain opaque to AI synthesis. These are two different success metrics, and conflating them leads to bad implementation decisions.

It's also worth noting the nuance Google introduced in its May 2026 AI optimisation documentation: "special schema is not needed for visibility in generative AI features." That sounds like a dismissal, but read it carefully. It says schema isn't a magic shortcut. It doesn't say schema has no effect. The broader evidence from the March 2026 update and from PingPrime's audit data points clearly in the other direction: structured data that accurately describes content increases AI citation probability.

Which Schema Types Have the Highest GEO Impact in 2026?

Seven schema types concentrate the GEO value in 2026. The table below lays out each type, its primary function for AI engines, and where implementation tends to be weakest in practice.

We'd add Speakable as an eighth type worth watching. It explicitly flags content sections for voice AI extraction. With Google AI Overviews now defaulting to roughly 60% of US informational queries, and voice interfaces growing alongside text-based AI search, Speakable is no longer a niche implementation.

What Changed After the March 2026 Core Update?

The March 2026 update hardened one rule that was previously just a best practice: schema must match the primary content topic of the page, not peripheral or supplementary content. The update dropped FAQ rich results by 47% post-update, almost entirely hitting pages that had bolted FAQ markup onto content where it didn't belong. Sites with schema aligned to genuine content intent retained their results and, in some cases, improved.

The practical rule: if the schema type doesn't describe the main reason a user would visit the page, don't add it. A product page should have Product schema. A how-to guide should have HowTo schema. Adding FAQPage to a pricing page because you have a small FAQ section at the bottom is exactly the behaviour the update targeted.

For AI search specifically, the update also produced a 3.2x AI Mode citation lift with properly implemented schema. That's the real number to pay attention to. Schema that accurately describes content increased the probability of citation in AI-generated answers even when no traditional rich result appeared. That's the new value proposition of structured data.

Entity Disambiguation: The Underused Schema Priority

The highest-use schema implementation in 2026 is also the most commonly skipped: entity disambiguation through SameAs, knowsAbout, and Organization schema pointing to authoritative external identifiers. Think Wikidata, LinkedIn, Crunchbase, GRID for research institutions.

Here's why this matters. When an AI engine synthesises an answer about your brand or cites your content, it needs to resolve your entity with confidence. If your Organization schema doesn't include SameAs links to external knowledge bases, the AI may conflate you with a similarly named company, underweight your content, or simply cite a competitor that has cleaner entity signals. This isn't theoretical. It's what happens when AI engines operate at scale across millions of queries.

The fix is straightforward. In your Organization schema, add a SameAs array with links to your Wikidata entity, LinkedIn company page, and any relevant industry databases. Add knowsAbout properties that reflect your genuine topical coverage. These signals feed directly into Knowledge Graph entity recognition, and Knowledge Graph presence correlates with higher AI citation rates.

The same logic applies to Person schema for authors. Named author pages with alumniOf, hasCredential, and knowsAbout properties tell AI engines that a specific, credentialed human wrote the content. That matters for E-E-A-T signals, and E-E-A-T signals matter for GEO. Generic "Staff Writer" bylines with no structured data attached accomplish nothing.

Implementation Priority: Where to Start

If your team is starting from scratch or auditing existing markup, this is the order we'd recommend:

1. Organization schema with SameAs on every page via a site-wide JSON-LD block in the document head. This is your entity foundation. Without it, everything else is built on sand.
2. Article schema with linked author entities on all editorial content. Include datePublished, dateModified, and an author property that points to a Person schema entity, not just a string.
3. FAQPage schema on pages where FAQ content is the primary content type, not an afterthought. Post-March 2026, this means genuine Q&A pages, not conversion pages with a FAQ module at the bottom.
4. HowTo schema on instructional content where steps are the core structure. Remove it from any page where the steps aren't the main reason someone would visit.
5. Person schema for every named author, with credentials and topical expertise filled in. Build dedicated author profile pages with visible credentials, then link Article schema to those entities.

JSON-LD in the document head remains the preferred implementation format after March 2026. Google has not changed this preference. Microdata and RDFa are not more effective, and in-body JSON-LD injection via JavaScript introduces crawl risk. Keep markup in the head, validate it in Google's Rich Results Test, and check it against Schema.org's validator for structural accuracy.

One more thing worth flagging: AI referral traffic, while still a small percentage of overall web traffic, converts at a greatly higher rate than organic search in observed data. The Ahrefs 2025 analysis cited in the 2026 research brief found that AI search visitors generated 12.1% of signups despite being only 0.5% of total traffic. Getting schema right is how you earn more of those visits. If you want to understand which prompts are driving your AI visibility in the first place, BrandPrompts can help you identify and track the right query sets across engines.

FAQ: Schema and GEO in 2026

Does Google still use FAQPage schema for rich results in 2026?

Google retired FAQ rich results for most pages in May 2026. However, FAQPage schema remains valid Schema.org markup and continues to help AI crawlers parse question-and-answer content during indexing. For GEO purposes, the markup still has value as an extraction aid even without a visible SERP feature.

Is JSON-LD still the right format for implementing schema?

Yes. JSON-LD delivered in the document head is Google's stated preference and has not changed after the March 2026 update. Microdata and RDFa have not become more effective. Avoid JavaScript-injected JSON-LD where possible, as it introduces indexing risk.

Do I need schema for ChatGPT and Perplexity, or just Google?

Schema helps across engines, but the mechanisms differ. For Google AI Overviews and AI Mode, schema is a direct trust and extraction signal. For ChatGPT, which retrieves via Bing, clean structured data aids Bing indexing and entity recognition. For Claude, which uses Brave Search, the same principle applies. No engine penalises accurate schema, and all benefit from cleaner entity signals.

What's the most common schema mistake brands make for GEO?

Implementing schema that doesn't match the primary content of the page. Adding FAQPage to a product page because there's a small accordion FAQ at the bottom, or adding HowTo schema to a landing page because it has numbered bullet points. After the March 2026 update, content-schema alignment is enforced more strictly, and mismatched markup is now more likely to hurt than help.

How does entity schema affect AI citation rates?

Sites with clean entity schema, specifically Organization markup with SameAs links to Wikidata, LinkedIn, and relevant databases, are cited more frequently by AI answers because the AI can confidently resolve who or what the source is. When entity resolution is ambiguous, AI engines default to sources they can identify with confidence. Entity disambiguation removes that ambiguity and improves your citation probability across all major engines.