Google retired FAQ rich results on 7 May 2026 and they are served to nobody. FAQPage markup is still worth adding, but only for AI extraction and page clarity, never for a visual result. The markup has to mirror questions and answers a visitor can actually read on the page.
There is a common belief that adding FAQPage schema earns you the expandable question-and-answer dropdowns in Google search results. It does not. Google fully retired FAQ rich results on May 7, 2026, they no longer appear for anyone. Google had already restricted them to government and health sites back in 2023, so for most businesses they had effectively been gone for years. If you’ve added FAQPage markup expecting that visual result, it will not appear.
That does not make the markup worthless. FAQPage is still valid, useful structured data, just for different reasons than most people were sold: it helps AI answer engines extract your answers, and it supports a clearer page for the owner reading it. This post covers what FAQPage actually does, where to use it, and where it does more harm than good.
What does FAQPage schema do, and what doesn’t it do?
FAQPage schema is a JSON-LD markup type, JSON-LD (JavaScript Object Notation for Linked Data) is a format for embedding structured data in a page’s code without changing how it looks to visitors. You add a <script> block that describes your Q&A content in a vocabulary Google understands.
What it does not do is produce a rich result in Google Search. There is no expandable Q&A block under your listing, and no click-through boost from one, because the feature isn’t shown. Treat any tool or agency that promises FAQ rich results as out of date.
What it does do is worth having:
It makes your answers extractable for AI search
Answer engines, Google AI Overviews, ChatGPT, Perplexity, favour content with a clear question-and-answer structure. FAQPage markup makes your answers explicitly machine-extractable, which raises the odds an engine quotes you when an owner asks it a question your page answers.
It gives the owner reading the page a clearer answer
A genuine FAQ section answers the questions an owner has before they call, fees, contract terms, how fast you fill a unit, in a format that’s easy to scan.
It signals authoritative Q&A content on a topic
It tells Google, in structured form, that this page carries authoritative Q&A content on a topic.
Where should you use FAQPage markup, and where shouldn’t you?
FAQPage belongs on pages where a genuine Q&A section fits the intent: service pages, informational guides, resource pages. Keep it off thin or purely promotional commercial pages. Marking up a promotional page as Q&A runs against Google’s content policies, and the answers have to be real, substantive, and actually present on the page.
The hard rule underneath all of it: the markup must mirror content that is visible on the page. Google’s visible-content policy prohibits marking up hidden or invented Q&A, and violating it risks a manual action. Every question and answer in your JSON-LD must match a question and answer a visitor can read.
What does good FAQPage markup look like?
A valid implementation has two parts: the visible FAQ content on the page, and the JSON-LD block in the code that mirrors it exactly. Five to eight questions is a reasonable range; each answer should be substantive enough to stand alone. One or two sentences is usually too thin.
The JSON-LD block follows this structure:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How much does property management cost in Vancouver?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Full-service residential property management in Metro Vancouver is typically charged as a percentage of monthly rent, plus a one-time leasing fee when a unit is filled. We provide a written fee schedule before any agreement is signed."
}
},
{
"@type": "Question",
"name": "Do you manage properties in Burnaby and Coquitlam?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We manage residential rentals across Metro Vancouver including Burnaby, Coquitlam, the North Shore, and Richmond. Coverage in a specific building or neighbourhood can be confirmed on a quick call."
}
}
]
}
</script>Each question maps to one Question object with a name (the question text) and an acceptedAnswer containing the text of the answer. The name must match the visible question on the page and the text must match the visible answer. Questions must be unique, not paraphrases of each other.
This is exactly what my schema markup work implements: structured data that is validated, complete, and matched to visible on-page content.
How do you implement and verify FAQPage markup?
- Write your FAQ section first. Add five to eight real questions to the page with substantive answers, two to four sentences each. The content must be visible on the page.
- Add the JSON-LD block. Place the
<script type="application/ld+json">block in the<head>or before the closing</body>tag. Replace the sample questions with your actual content. - Validate the syntax. Run the page through the Schema.org validator and Google’s Rich Results Test. Expect a clean parse; do not expect an FAQ rich-result preview, there is no longer one to earn.
- Fix any errors. Malformed JSON or a
Questionwithout an answer invalidates the block.
Why is FAQ markup still worth adding for AI search?
The reason to keep adding FAQPage is extractability for AI citation, the process by which tools like Google AI Overviews and ChatGPT pull content from web pages to answer queries.
AI engines prefer pages with clear question-answer structure, which is the second of the two filters that decide whether you get cited. When an engine receives “who does property management in Vancouver?”, it looks for pages that directly address the question in a structured format. A page with FAQPage markup signals that structure explicitly, content organized as discrete answers to discrete questions, not just relevant prose. That improves the probability of citation, which is where the visibility that FAQ rich results used to provide has effectively moved. For the full GEO (generative engine optimization) methodology across all your pages, see the AI answers section of my Visibility work.
The pattern I keep finding is that the content is already there. Property managers have written FAQ sections and built pages that answer real owner questions. The JSON-LD block that turns that content into machine-extractable structure is missing, and it’s a quick fix with a real upside in AI search, even though it will never show a rich result.
When did FAQ rich results actually disappear?
In two stages. Google restricted FAQ rich results to government and health sites in August 2023, which removed them for essentially every commercial business, and then retired the feature outright on 7 May 2026. Since that date they are served to nobody, in any vertical.
The tooling caught up over the months after, which is why yours may have gone quiet on it. Google dropped the FAQ search-appearance filter, the rich-result report and Rich Results Test support in June 2026, and removed the last reporting hook in August 2026. If your schema checker stopped flagging FAQ blocks this summer, nothing broke on your site.
The two-stage retirement is why the myth has been so durable. Plenty of agencies sold FAQPage markup as a rich-result play during the years when the feature technically still existed but was already unavailable to their clients, and the advice kept circulating after the feature was switched off entirely. If a proposal you’re reading still promises expandable question-and-answer dropdowns under your listing, it was written against a Google that no longer exists.
Does FAQ markup help you rank?
No, and it’s worth being exact about this because the answer is easy to overstate in either direction. FAQPage markup is not a ranking factor. Adding it will not move your position for any query, and a page that ranks nowhere will not start ranking because you marked up its questions.
What it changes is what happens to a page that already ranks, and for a local firm ranking is only part of it, since being named in an AI answer also needs entity grounding. Retrieval and ranking are separate stages, and structured Q&A affects the second one: whether an engine that has already found your page can lift a clean answer out of it. That’s why the sequence matters more than the markup. Rank first through the ordinary work, then make the answer easy to extract.
If you want to know whether your pages are structured for AI extraction and whether your existing schema is valid, I’ll run the audit and walk you through exactly what needs to change. Book the audit here. The audit is the next step.