On this page
Key takeaways
- Google stopped showing FAQ rich results for all sites on May 7, 2026, and dropped FAQ from the Rich Results Test and Search Console reports.
- FAQPage markup is still valid Schema.org. It no longer changes how your page looks in Google, but it gives AI assistants and search engines your questions and answers in a clean, structured form.
- The visible FAQ content matters more than the markup: real buyer questions, as headings, each answered directly in the first sentence.
- Keep existing FAQ markup where it matches real, visible questions and answers. Remove it where FAQs were added only to win rich results.
- Validate FAQPage with the Schema.org validator, since Google’s tools no longer check it.
Does FAQ schema still matter? Yes, but for a different reason than before. Google stopped showing FAQ rich results (the expandable questions under a search result) for all sites on May 7, 2026, so FAQPage markup no longer changes how your page looks in Google. It still gives search engines and AI assistants your questions and answers in a structured form. What matters more now is the FAQ content itself: real questions buyers ask, answered clearly on the page, where ChatGPT, Gemini, Perplexity and Google’s AI Overviews can quote them.
Many sites removed their FAQ schema, or stopped writing FAQ sections, once the rich-result benefit disappeared. That’s understandable, but it misses the point: FAQs were always meant to help people understand a page, not just to earn extra space in search results.
Below: what Google changed, what FAQ markup still does, how to write FAQs AI assistants can use, how to mark them up, and what to do with markup you already have.
What Google changed
FAQ rich results were wound down in two steps:
| When | What changed |
|---|---|
| August 2023 | FAQ rich results limited to well-known, authoritative government and health websites. Everyone else lost them. |
| May 7, 2026 | FAQ rich results stopped appearing in Google Search for all sites. |
| June 2026 | Google said it would drop the FAQ search appearance filter and rich result report from Search Console, and FAQ support from the Rich Results Test. Its FAQ documentation was removed. |
| August 2026 | FAQ support removed from the Search Console API. |
Google’s own note was blunt: the markup won’t cause problems, but it won’t produce visible results in Google Search either.
So if you added FAQ schema to get extra space in search results, that reason is gone. FAQPage is still a valid Schema.org type, though, and there are still reasons to use it. If you’re wondering whether to remove FAQ schema from existing pages, the answer is usually no: keep it where it accurately reflects real questions and answers shown on the page.
What FAQ schema still does
It describes your answers in a form machines can read. FAQPage markup tells any system reading the page "this is a question, and this is its answer", without it having to work that out from the layout. Search engines use structured data to understand pages, and Microsoft has said schema markup helps the large language models behind Copilot understand content.
Imagine two pages answering the same customer question. One buries the answer in general marketing copy with no structure. The other puts the question in a heading, answers it directly underneath and adds FAQPage markup. An AI assistant could cite either, but the second gives search engines and language models a much clearer signal about what the content means.
It helps your structured data be complete and consistent. Organization, Article, Service, BreadcrumbList and FAQPage together give a clear picture of who you are and what each page covers. Structured data is one of the five areas in our AEO score (25% of it), and the check looks at whether markup is present, valid and matches what the page shows. See our methodology for how it’s scored.
What it doesn’t do: it doesn’t guarantee a citation. No AI assistant has said how much weight it gives FAQPage markup, and the published tests of "schema vs AI citations" are small and disagree. Google says its AI Overviews and AI Mode need no special markup at all. Treat FAQ schema as a low-cost way to make good answers easier to read, not as a ranking trick.
The FAQ content matters more than the markup
When someone asks an AI assistant a question, it searches, reads a few pages and writes an answer from them. A page with a heading that matches the buyer’s question, followed by a short, direct answer, is easy to quote. That’s true whether or not the page has FAQ markup.
Take a commercial roofing contractor. A buyer asks ChatGPT: "How long does a commercial flat roof replacement take for a 40,000 square foot warehouse?" A services page that says "We deliver quality roofing solutions on time and on budget" gives the assistant nothing to use. An FAQ that answers "Most 40,000 sq ft flat roof replacements take two to four weeks, depending on the membrane, the weather and whether the old roof is torn off" does. That’s the kind of specific answer an AI assistant can quote, summarize or cite.
How to write FAQs AI assistants can use
- Use the questions buyers actually ask. Take them from sales calls, quote requests, support emails and the questions you’d type into ChatGPT yourself. Skip questions nobody asks ("Why is our company the best choice?").
- Put the question in a heading. Use H2 or H3, worded the way a buyer would ask it.
- Answer in the first sentence. Start with "Yes", "No", a number or a direct statement, then add detail.
- Keep answers to about 40 to 60 words. Long enough to be useful on their own, short enough to quote. Link to a fuller page if there’s more to say.
- Be specific. Industries, locations, timelines, typical ranges, what’s included. Specific facts are what assistants can repeat.
- Answer each question on the page where it belongs. A pricing question goes on the pricing or service page, not on one long site-wide FAQ page.
- Keep answers current. An FAQ that quotes last year’s lead times or a retired product is worse than none.
How to mark it up
Add FAQPage JSON-LD for the questions and answers the page shows. One FAQPage block per page, covering that page’s questions:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does a commercial flat roof replacement take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most 40,000 sq ft flat roof replacements take two to four weeks, depending on the membrane, the weather and whether the old roof is torn off."
}
},
{
"@type": "Question",
"name": "Can you replace a roof while the building is in use?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We work in sections so the building stays open, and schedule noisy work outside business hours where needed."
}
}
]
}
</script>
Rules that still apply:
- Match the page. The questions and answers in the markup must be the ones visible on the page, worded the same. Copy them; don’t paraphrase.
- Only your own Q&A. FAQPage is for questions and answers you wrote. User-submitted questions with several answers (forums, community Q&A) use QAPage instead.
- No advertising in answers. An answer should answer, not sell.
- Generate it from the content if you can. If your CMS builds the JSON-LD from the FAQ section of the page, the markup can’t drift out of sync with the text.
- Validate it with the Schema.org validator (validator.schema.org). Google’s Rich Results Test no longer checks FAQ markup. Our AEO checklist covers validation for all your structured data.
What to do with FAQ markup you already have
| If your FAQ markup... | Then |
|---|---|
| Matches real questions and answers shown on the page | Keep it. It does no harm and still describes the page. |
| Was added only for rich results, with questions nobody asks | Rewrite the FAQ around real buyer questions, or remove both the FAQ and the markup. |
| Is the same block repeated on many pages | Keep it on the one page it belongs to, and write page-specific questions elsewhere. |
| Doesn’t match the visible text, or marks up hidden content | Fix it so it matches, or remove it. |
| Fails the Schema.org validator | Fix the errors. Broken markup tells machines nothing. |
The more important question isn’t whether FAQ schema is on the page. It’s whether the FAQ answers the questions buyers actually ask ChatGPT, Gemini, Perplexity and Google’s AI features. A perfectly marked-up FAQ that answers the wrong questions is unlikely to help. A simple FAQ that answers real buyer questions directly is far more likely to be used.
So check the pages that matter most: do your FAQs answer the questions buyers are asking AI assistants, and are you one of the businesses being recommended when those questions are asked? For the wider set of fixes, see How to get your website cited by ChatGPT, Gemini and Perplexity; for where this fits alongside SEO, see AEO vs SEO.
Frequently asked questions
Did Google remove FAQ rich results?
Yes. Google stopped showing FAQ rich results in Search for all sites on May 7, 2026, after limiting them to authoritative government and health sites in 2023. In June 2026 it also dropped FAQ support from the Rich Results Test and the Search Console reports.
Should I remove FAQ schema from my website?
No, not if it matches real questions and answers shown on the page. Google says the markup causes no problems, and it still describes your content to search engines and AI assistants. Remove it only where the FAQs were written just for rich results or don’t match the visible text.
Does FAQ schema help with AI search?
It can help AI systems read your answers, and Microsoft has said schema helps the models behind Copilot understand content. No assistant guarantees citations for it, though. The visible FAQ content, clear questions with direct answers, matters more than the markup.
Does FAQ schema help with Google AI Overviews?
Not directly. Google says AI Overviews and AI Mode need no special markup; a page needs to be indexed and eligible for a snippet. A clear FAQ on the page can still be quoted, because the content answers the question, with or without the markup.
How do I test FAQ schema now that the Rich Results Test doesn’t support it?
Use the Schema.org validator at validator.schema.org. Paste the URL or the code; it checks FAQPage against the Schema.org vocabulary and shows errors and warnings. Then compare the questions and answers in the markup with the page text by eye.
How many questions should a FAQ section have?
As many as buyers really ask about that page, usually five to ten. Each question should have its own direct answer. A short FAQ with real questions is more useful to buyers and AI assistants than a long one padded with questions nobody asks.
Can I use FAQ schema on every page?
Only on pages that show questions and answers. Don’t repeat the same FAQ block across many pages, and don’t mark up questions that aren’t visible. Write page-specific questions: pricing on the pricing page, timelines on the service page.
What’s the difference between FAQPage and QAPage?
FAQPage is for questions and answers written by the site owner, one answer per question. QAPage is for a page built around one question where users submit answers, such as a forum or community thread. Most business websites need FAQPage.
FAQ rich results are gone, but the reason FAQs work hasn’t changed: buyers have questions, and the businesses that answer them clearly get chosen. Write the questions buyers ask, answer them directly, and mark them up correctly. Then run our free AI visibility checker to see whether AI assistants are naming you, or talk to us about improving it.
Join the discussion
No comments yet.
Leave a Reply