If you judge FAQ schema by Google's own tools, it's dead. Google pulled FAQ rich results from Search in May, then took the FAQ data out of the Search Console API in August. No report in Google's stack shows the markup doing anything for you anymore.
AI engines kept citing FAQs anyway. Neil Patel's content type performance survey found they cite content in FAQ format 41% of the time, which puts the format fourth on his list:
| Content type | How often AI engines cite it |
|---|---|
| Original research | 82% |
| Comparison content | 76% |
| Best-lists | 57% |
| FAQ format | 41% |
So you're holding two true facts at once: the rich result in Google is gone, and FAQ structure is worth more in AI answers than it has ever been. Two findings explain the gap. One is a test from February 2026 that shifted how AEO people think about JSON-LD, and the other is an answer pattern found in 72% of the pages ChatGPT cites. I'll cover both, along with the placement rule most teams get wrong.
What actually happened with FAQ rich results
Google took three years to retire this feature:
| When | What Google changed |
|---|---|
| August 2023 | FAQ rich snippets limited to government and health authority sites |
| May 7, 2026 | FAQ rich results removed from Search entirely |
| August 2026 | FAQ Performance data removed from the Search Console API |
The first cut did most of the damage. Once eligibility shrank to government and health authority sites, something like 90% of the FAQ rich results teams were getting went away. The May removal finished off the rest. After the August change, there was no first-party Google surface left where you could see FAQ schema do anything.
What Google left alone matters more to you. Schema.org still treats the FAQPage schema as valid, and you won't get a Google penalty for leaving the markup on your pages. Google just no longer turns it into a rich result in the regular blue links. That narrow change is the whole opening for AI citation work, because the markup is still sitting in your HTML.
Google officially killed FAQ rich results. For three years, the playbook was simple - add FAQPage schema, get extra SERP space, boost CTR. Sites were doing it everywhere, half of them with questions nobody was actually asking. Google noticed. And eventually just ended it
Liam | Coinpresso@LiamCryptoSEOMay 10, 2026Why AI still rewards FAQ structure
The proof came from Will Williams-Cook in February 2026, and his test was almost too simple. He put an address inside a JSON-LD block that was technically invalid, and the address wasn't anywhere else on the page. Then he asked ChatGPT and Perplexity where the place was. Each of them came back with the address, copied exactly out of that broken block.
So what does that tell you? To an LLM, JSON-LD is just more text. During retrieval and grounding the model tokenizes it like everything else on the page, and it skips the structured-data parsing a search engine does. When you write a tidy FAQPage block, you hand the model a question sitting right next to its answer, in a unit of text it can lift out and cite whole. The schema helps because that text is so easy to scan. The structured data carries no special weight with the AI.
FAQ schema is Officially removed from Google Search Console Should i remove it from my website or leave it as it is for llms?
Today I saw nothing related to FAQs schema in GSC enhancements which means its officially removed Now my Question Should i Keep it for llms or remove it?
That r/TechSEO thread from June 2026 ran to 57 comments, and the practitioners in it settled on keeping the schema. It costs you nothing to leave in place and LLMs read it. Google isn't penalizing it either. The teams removing it in 2026 are treating a change to Google's rich results as if it said something about AI citation weight.
The 40 to 60 word answer capsule
Research on ChatGPT-cited pages is very specific about length. Answers of 40 to 60 words do best.
In that analysis, 72.4% of the pages that got cited used answer blocks of that length. Those blocks kept the same four-part shape, too. Your first sentence gives the direct answer. The second backs it with a statistic or some other hard number, the third says when the answer applies, and the fourth adds whatever constraint or caveat the reader needs.
Keep your links out of it. Nine in ten of the capsules that worked had no hyperlink anywhere inside them, because a link mid-answer breaks up the piece the model wants to lift out whole.
Here's one that works for the question "How much does FAQPage schema cost to implement?":
"FAQPage schema costs nothing to implement if your CMS supports it via a plugin. WordPress sites using Yoast or Rank Math generate it automatically. Custom stacks need about 30 minutes of developer time per template. The main cost is auditing text-to-schema consistency after the fact, which is where most implementations break."
Count it and you get 51 words in four sentences, with no links. Each sentence does one job from the pattern, in order: the answer, the number, the scope, the constraint. Copy that shape when you write yours.
We'll show you exactly where your brand stands in AI search.
No commitment. $0 due today, cancel anytime. See how ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode talk about your brand today.
Structure that wins position zero
Position zero means something else in an AI answer than it did when you were chasing featured snippets. The model isn't reading a ranked list and taking whatever sits on top. It writes its answer out of pieces it extracts from several sources it trusts. FAQ content is unusually easy to lift out, since the question marks where to start and the answer is complete on its own. The 2026 GEO-SFE framework study put numbers on this.
In that study, structural readiness tracked citation rate with a correlation of +0.71, against +0.42 for domain authority. Of the levers you control, structure is the stronger one.
It also found that 68% of the pages cited in AI Overviews aren't in the organic top 10. Winning the citation depends more on how your answer is built than on where the page ranks.
Something a lot of people are getting wrong right now: Google said FAQ schema doesn’t help SEO anymore. Yes. True. But for AEO? FAQ schema is one of the strongest predictors of AI citations. The clue’s in the name! Answer Engine Optimization. So yes… Put FAQs on every https://t.co/QUB2liFseZ
Mark A | Churn Tools@growth_pigeonMay 15, 2026
That tweet has both halves right. Google is correct that FAQ schema no longer helps SEO, and for AEO the same schema is still one of the strongest predictors of AI citation. You don't have to pick one, since Google search and AI grounding run on separate retrieval systems that judge quality by different signals.
Where FAQ blocks should live on the page
The old SEO habit was to stick the FAQ at the end of the page and let it pick up long-tail searches. For AEO, that placement is now wrong. In a study of pages cited in AI Overviews, 55% of citations came from the top 30% of the content.
Why so close to the top? Models trim long pages when they retrieve them, and often never get as far as your footer, so a FAQ down there misses the window where most citations get pulled. On average, pages with the FAQ block in the main content area earned 4.9 AI citations, while footer FAQs earned 4.4.
So put a short FAQ in the top third, right after your intro, with the three to five questions that matter most. Then go deeper on those same answers further down.
Every new page our content engine writes opens with the answer, under headings phrased as questions. Our AI visibility tracker then shows you which pages on your site get cited, so you can check that the structure pays off.
Know exactly what AI says about your competitors.
RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode. See where they show up and you don't.
The contradictory citation data
One study catches plenty of teams out, because it seems to say FAQ schema hurts. SE Ranking looked at 12,000 URLs in 2026 and found a slight negative correlation. The other data points the opposite way, so look at all three together:
| Source | What it found |
|---|---|
| SE Ranking, 2026, 12,000 URLs | 3.6 AI citations on average with FAQ schema, 4.2 without |
| Averi, 2026 case study | 3.2x more AI Overview appearances once FAQ schema was added |
| Frase | 41% citation rate for schema-enhanced pages, 15% without |
The way I square them is a weight ratio. Domain authority seems to count about 3.5 times as much as FAQ schema in whether a page gets cited. If your site has high authority, you often cover FAQ-style questions in your prose already, with no schema needed, so the markup adds only a little on top. If your authority is low, you gain the most, because the schema carries more of the load in showing your site gives good answers.
Most SaaS teams under Ahrefs DR 60 get a meaningful lift from FAQ schema. Past DR 80 the gain shrinks, but it still shows up in how often you appear in AI Overviews. Check your own numbers before you assume an average taken across many sites holds for your domain. If you want citation share attributed page by page, our pricing page has the whole cross-engine tracking setup.
Are we overusing FAQ schema in the AI search era?
Common FAQ mistakes that kill citations
The same four mistakes keep turning up in almost every FAQ setup I've audited in 2026. None of them is hard to fix.
Duplicate FAQPage blocks top the list. You get them on WordPress when Yoast or Rank Math generates the schema automatically and a developer has also hand-coded JSON-LD into the template. Search Console warns about the duplicate, and AI engines trip over two texts that disagree. Pick one way to output the schema and switch the other off.
Right behind that is a mismatch between the answer in your JSON-LD and the answer on the page. When the two say different things, the model has no way to tell which one is authoritative, so it throws both out of extraction. Paste the visible answer into the schema word for word, or have one source generate both.
Then there's the generic stuff: auto-generated questions that no real user ever asks. Some tools churn out "What is your product?" and "How much does it cost?" without anyone checking what buyers put to AI models, and grounding ignores the result. Before you write any, dig through your support tickets and sales call transcripts for the questions buyers really ask.
The last one is a one-word typo. The field you want is acceptedAnswer, nested under mainEntity, but about 8% of the FAQPage markup I come across uses suggestedAnswer instead. Schema.org doesn't recognize that as a valid field, so the whole block gets ignored. Run yours through the Schema.org validator before it goes live.
26 content formats. Published on your domain. Matched to your brand.
Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode.
FAQ
Did Google really kill FAQ rich results? Yes, Google switched them off on May 7, 2026. The FAQ data came out of the Search Console API that August. That ended a three-year phase-out, which started in August 2023 when eligibility shrank to government and health sites. Schema.org still counts FAQPage markup as valid.
Do AI engines actually read FAQPage JSON-LD schema? They do, though Google reads it differently. Will Williams-Cook's test in February 2026 showed that LLMs treat JSON-LD as plain text to tokenize, with no structured-data parsing. His address existed only in an invalid schema block, and ChatGPT and Perplexity both repeated it verbatim.
What is the ideal FAQ answer length for AI citation? Aim for 40 to 60 words. That's the range 72.4% of ChatGPT-cited pages used. Lead with the direct answer and add a supporting statistic. Then say when it applies and note any constraint, and keep hyperlinks out of the block.
Where should FAQ blocks live on a page for maximum citation? Put them in the top third. Of all AI citations, 55% are pulled from the opening 30% of a page. A FAQ in the main content area averages 4.9 citations, against 4.4 when it sits in the footer.
What's the most common FAQ schema mistake in 2026? It's duplicate FAQPage blocks. They show up when Yoast or Rank Math auto-generates the schema on a WordPress site and a developer has hand-coded JSON-LD into the template as well. You get a Search Console warning, and AI engines get two texts that conflict.
