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 FAQPage schema does, and doesn’t
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:
- AI-search extraction. 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.
- On-page clarity. 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.
- Entity and vocabulary signal. It tells Google, in structured form, that this page carries authoritative Q&A content on a topic.
Where to use it, and where not to
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 good FAQPage markup looks 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 service implements: structured data that is validated, complete, and matched to visible on-page content.
How to implement and verify it
- 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.
The real payoff: 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. 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 my generative engine optimization service.
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.
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.