Field note · structured data
Google killed FAQ rich results.
Don't delete the schema.
The visible dropdown is gone. The structured data behind it is now doing more work, not less — it's the cleanest machine-readable signal AI surfaces have for extracting Q&A content. Removing FAQPage schema because Google retired the SERP feature is the wrong move at the wrong time.
By the Lynceus Research Team · Last reviewed: May 2026
What Google did, precisely
The deprecation removed a SERP feature, not a signal.
Google's announcement was specific: the FAQ rich-result dropdown — the expandable Q&A block that appeared on some search results — is being retired in June 2026. The same announcement explicitly stated that FAQPage schema would continue to be used to understand content. Google's Rich Results Test still validates FAQPage markup. The Search Central docs still list FAQPage as a supported Schema.org type.
Two things got conflated in the panic: (1) the visual SERP feature, and (2) the underlying structured-data signal. Only one was retired. The other is now load-bearing somewhere else.
The audience shift
Schema's reader changed from Google to LLMs.
For the past decade, the operational reason to emit FAQPage JSON-LD was the SERP rich result it triggered. Schema was a feature-flag for Google's UI. That era is ending across multiple schema types — Google has been quietly retiring rich-result features for years (FAQ is the highest-profile case, but not the first).
What replaced the SERP-feature audience is the AI-retrieval audience. ChatGPT search, Perplexity, Claude with web search, and Google's own AI Overviews fetch pages live at query time and parse them for relevant spans. Their pipelines are not running a single LLM that "reads" the page — they are running retrieval-augmented systems where a retrieval layer ranks chunks, an LLM composes the response, and citations get attached to extractable spans.
In that pipeline, the most useful chunks are the most self-contained ones. A Q&A pair inside a FAQPage block is the platonic ideal: question explicitly identified, answer bounded and self-contained, no inference required to figure out what user query it satisfies. The same content as a paragraph requires the retrieval layer to guess where the relevant span starts and ends, and the LLM to summarize rather than quote. Schema-rich content wins because it eliminates two layers of guessing.
What we observe in audits
Schema-rich pages get quoted verbatim. Paragraph-dense pages get paraphrased.
Across the AI visibility audits we've run, one pattern is consistent: when the same answer appears on two pages — one structured as a FAQPage with explicit Q&A markup, one as a marketing paragraph — the schema-structured version is cited verbatim more often by Perplexity and ChatGPT. The paragraph version, when used, gets paraphrased and loses the brand's exact framing along the way.
Verbatim quoting matters disproportionately for AI visibility. A paraphrased mention surfaces your brand but in someone else's words; a verbatim quote surfaces your brand and your exact positioning. The latter compounds. The former dilutes.
We haven't published a controlled A/B yet (and any practitioner claiming clean A/B numbers in this space should be questioned hard — the noise floor is high and the confounders are many). What we have is a consistent directional signal across enough audits that we will not remove FAQPage schema from any client page during the optimization engagement. The downside is zero, and the upside is the citation pattern above.
The "LLMs don't use schema" claim
The strongest counter-argument is partially true and almost entirely irrelevant.
A common rebuttal to keeping schema is "Google has explicitly said LLMs don't use structured data." That statement, when actually pulled up and read, is more specific than it sounds. It refers to Gemini's training-time ingestion of structured-data fields, and Google's statement is that Gemini does not specifically condition on JSON-LD blocks during training. That claim may or may not survive scrutiny in 2027, but for the present discussion it's beside the point.
Training-time ingestion is not where AI visibility lives. Live retrieval is. When a user asks ChatGPT search "what's the best CRM for a 50-person team," ChatGPT is not pulling from its training weights — it's running a search, retrieving pages, and composing an answer from current content. The retrieval layer is built on standard indexers that ingest the entire HTML payload, including JSON-LD. Whether the final LLM "parses" the JSON-LD or just sees the rendered text content is immaterial: the retrieval layer above it has already used the structured data to surface the right chunk.
And even granting the most generous version of the counter-claim — that schema has zero signal value in any AI pipeline — the cost of keeping FAQPage schema is roughly nothing. The cost of being wrong about removing it is real visibility loss. Asymmetric trade.
What to do
Three specific actions, in order.
- 01 Audit your existing FAQPage schema for AI extractability, not Google rich-result validity. The Rich Results Test will tell you the markup parses. It won't tell you whether the questions match buyer intent, whether answers are bounded and self-contained, whether each Q&A pair could stand alone as a citation. The latter matters now; the former is decorative.
- 02 Add FAQPage schema to high-intent pages that lack it. Product detail pages, comparison pages, "how does X work" guides, pricing pages. Find the questions buyers are actually asking AI surfaces (the Lynceus audit panel surfaces 8-12 such prompts per category) and answer them directly with FAQPage structure.
- 03 Don't strip the schema from pages where Google's deprecation removed the rich-result feature. If you have FAQPage schema in place, leave it. The audience changed. Treat it as an AI-extraction signal going forward. Document this in your internal SEO playbook so the next person on your team doesn't "clean up" something load-bearing.
Frequently asked questions
Did Google really kill FAQ rich results?
Google announced the retirement of the visual FAQ dropdown in search results, effective June 2026. They explicitly said they would continue to use FAQPage schema to help understand content. The change removed a SERP visual feature, not the structured-data signal itself. Treating the announcement as 'structured data is dead' is a misreading — only the visual rendering is dead, and only for FAQ specifically.
Does that mean I should delete FAQPage schema from my pages?
No. The opposite. The same schema that was producing a SERP dropdown is now producing AI-citation eligibility. ChatGPT search, Claude, Perplexity, and Google's AI Overviews extract content from schema-rich pages more reliably than from pages where the same information is buried in marketing paragraphs. Removing FAQPage markup eliminates a load-bearing signal for AI visibility while gaining nothing — the SERP feature it powered is gone whether you keep the schema or not.
Do LLMs actually use structured data?
There's a confused public debate on this, partly because Google has made carefully-worded statements about Gemini's training pipeline that have been generalized into the broader claim 'LLMs don't use schema.' Two clarifications. First, training-time ingestion and live-retrieval ingestion are different pipelines. Perplexity, ChatGPT search, and Google AI Overviews use live retrieval — they fetch pages at query time and tokenize the content, which includes JSON-LD blocks. Second, structured data is read by the same crawlers and indexers that LLM retrieval pipelines depend on; even when the model itself doesn't 'parse' JSON-LD, the retrieval layer above it does. The practical result is that schema-rich pages are more often selected, more often quoted verbatim, and more often cited with attribution.
What makes FAQPage schema particularly useful for AI?
Three properties. First, it explicitly identifies the question being answered — AI surfaces matching user intent to content can confirm the match without inference. Second, the answer is bounded and self-contained — extractable as a quote without needing to summarize. Third, the schema enumerates Q/A pairs, so a single page becomes many independently-citable chunks. Compare this to a marketing paragraph containing the same answer: the AI has to identify the relevant span, decide where the answer starts and ends, and lose verbatim-quote fidelity. FAQPage schema removes all three steps.
Will Google penalize me for keeping FAQPage schema after deprecation?
No. Google's documentation continues to support FAQPage as a valid Schema.org type. The retirement applies to the rich-result *display feature*, not the structured-data ingestion. Pages with FAQPage schema will continue to validate without errors in Google's Rich Results Test, and the markup will continue to be processed for content understanding. There is no SEO downside to keeping it.
What about Article, Product, and other schema types?
Same pattern. Schema's audience is shifting from Google's SERP rich-result rendering to AI-surface retrieval and citation. Article, Product, Review, Organization, and BreadcrumbList schemas all serve AI extraction in addition to their traditional SERP roles. Treat structured data as machine-readable content rather than SERP-feature triggers, and the value extends well beyond any single Google feature's lifecycle.
How can I tell if my FAQPage schema is helping AI visibility?
Run an AI visibility audit segmented by schema status. Compare AI-citation rates for FAQ-schema'd pages against equivalently-positioned pages without the markup. Track verbatim-quote frequency, not just mention rate — clean FAQ structure tends to lift verbatim quoting specifically. The Lynceus Visibility Audit performs this segmentation by default; see /sample-report for the format.
Is this just a Lynceus pitch?
It's a pitch insofar as we built a measurement product around this exact question. But the underlying observation — that schema-rich content is preferentially cited by AI surfaces — is consistent across every practitioner running rigorous AI-visibility measurement. The OP of the May 2026 r/Agentic_SEO thread that prompted this piece reported the same pattern from client work since August 2025, without any connection to Lynceus. If our pitch is wrong, every measurement-focused operator in the AEO/GEO space is also wrong, which is unlikely.
Measure your current state
Is your FAQ schema doing
what you think it's doing?
The Lynceus Visibility Audit segments AI-citation rates by schema implementation. You'll see exactly which of your pages are cited verbatim, which are paraphrased, and which are skipped — with the schema state of each page side by side.