Key Takeaway
Google fully removed FAQ rich results on May 7, 2026 (first restricted to gov/health sites in 2023). But FAQ schema matters more now, for AI. The catch: LLMs read your JSON-LD as plain text, not structured data, so the markup itself is not a citation lever. What gets cited is the visible question-and-answer content the schema mirrors. Work the two layers: keep valid JSON-LD to feed Google's understanding (which AI grounds on), and write 3-5 self-contained, 50-300 word answers that lead with the answer, because that is the text answer engines extract.
On May 7, 2026, Google quietly stopped showing FAQ rich results in Search. No accordion of questions under your listing, no extra real estate, no click-through bump. The feature that launched a thousand "add FAQ schema for more SERP space" posts is gone, and Google did not bother to explain why.
So here is the strange part. FAQ schema, the FAQPage structured data that marks up a list of questions and their answers so machines can read them, matters more today than it did when the rich result was alive. It just matters for a different reader. Not Google's blue links. The AI systems that now answer a growing share of your audience's questions before they ever reach a results page.
Most FAQ schema guides still sell you the dead feature. This one is about the live one. I will walk through what actually changed, what large language models do with your FAQ schema (it is not what the vendors claim), and how to implement FAQPage schema so ChatGPT, Perplexity, and Google's AI Overviews pull your answers into theirs. With real code.
The feature everyone optimized for is gone
The timeline is worth getting right, because it explains why so much published advice is now wrong.
In August 2023, Google restricted FAQ rich results to "well known, authoritative government and health websites." The rest of us lost the SERP feature overnight. Most people missed it, because the schema stayed valid and the markup kept validating clean.
Then on May 7, 2026, Google finished the job. FAQ rich results stopped appearing for everyone. The tooling follows on a schedule: the Search Console rich result report and the Rich Results Test drop FAQ support through June 2026, and the Search Console API ends its FAQ support in August 2026. Google added a deprecation notice to its docs and said nothing more.
Here is what did not change. Your existing FAQ schema is not a problem. Google has long held that unused structured data does not hurt a page, and FAQPage is still a valid Schema.org type. You do not need to rip it out. You need to understand what it is for now.
So why does FAQ schema still matter?
Because the question-and-answer format is the most extractable shape of content on the web. Extraction is the whole game in AI search, and a clean FAQ schema hands the machines a running start.
When someone asks ChatGPT or Perplexity a question, the system does not read your page the way a person does. It reads in fragments. It breaks the text into chunks, ranks them for relevance, and stitches the strongest ones into an answer with citations. A question followed immediately by its answer is already shaped like the output it wants. You did the chunking for it.
That is why FAQ schema content shows up so often in AI answers. It is not magic in the markup. It is the structure. And that gap, between the markup and the structure, is where almost every FAQ schema guide goes wrong next.
What AI actually does with your schema
Here is the uncomfortable truth: large language models do not parse your JSON-LD as structured data. They read it as text.
Schema markup is built to be machine-readable in a formal sense, a labeled set of key-value pairs a parser can interpret. Google's traditional systems use it that way. LLMs do not. When a model tokenizes your page, the JSON-LD inside your