How to add FAQ schema, and whether it is still worth it
Google stopped showing FAQ rich results in May 2026. How to add valid FAQPage markup anyway, when it still makes sense, and when to leave it out.
By Sohail Hussain17 November 20265 min read
To add FAQ schema, write the questions and answers visibly on the page, generate a FAQPage JSON-LD block from the same text, add it to that page once, and validate it. That takes ten minutes. The more important fact is what it no longer does: as of May 7, 2026, Google does not show FAQ rich results for any site, so the markup will not change how your page looks in Google Search.
That changes the advice. FAQ schema used to be one of the cheapest ways to take up more space in search results. Now it is optional markup with no visible effect in Google. This post covers what changed, when the markup is still reasonable to add, how to do it correctly, and what to do with markup you already have. It is one item in our technical SEO checklist, and a small one. When we review structured data as part of technical SEO and performance work, FAQ markup is now the type we spend the least time on.
What happened to FAQ rich results?
The feature was removed in two stages.
| Date | Change |
|---|---|
| August 2023 | FAQ rich results limited to well-known, authoritative government and health websites. All other sites stopped seeing them. |
| May 7, 2026 | FAQ rich results no longer appear in Google Search for any site. |
| June 2026 | Google drops the FAQ search appearance filter, the FAQ report in Search Console and FAQ support in the Rich Results Test. Documentation removed on June 15. |
| August 2026 | FAQ support removed from the Search Console API. |
The source for each step is Google's own Search Central changelog and its August 2023 post on changes to HowTo and FAQ rich results. HowTo rich results went first: Google stopped showing them on mobile in August 2023 and on desktop in September 2023.
If you remember FAQ dropdowns under your listings, most business sites lost them in August 2023. The May 2026 change mainly affected government and health sites.
Is FAQ schema still worth adding?
For Google rich results, no. There is nothing left to win.
There are still reasons it can be reasonable to have:
- Your CMS adds it for free. Many themes and SEO plugins output FAQPage markup automatically for FAQ blocks. If it is accurate, leaving it costs nothing. This blog does the same: the questions at the end of this post are marked up from the same source that renders them.
- Other consumers of schema.org. Schema.org is a shared vocabulary, and other search engines and tools that read it may use the markup. Check their own documentation before relying on that.
- It describes the page correctly. Google says it uses structured data to understand pages in general, not only to display rich results.
And reasons not to spend money or time on it:
- Do not pay anyone to add FAQ schema across a site. The work no longer produces a visible result in Google.
- Do not add FAQ sections to pages only to hold markup. A list of thin questions under every service page makes the page worse to read.
- Do not add it for AI Overviews or AI Mode. Google's guidance on AI features says there is no special schema.org markup needed to appear in them.
The part that still matters is the visible FAQ. Answering the questions customers ask you, in plain words on the page, helps readers and gives Google text that matches what people search for. Write the answers well whether or not you mark them up.
How do you add FAQPage markup correctly?
If you do add it, do it properly. The steps:
- Write the questions and answers on the page. They must be visible to readers without a login. Collapsed accordions are fine; content that exists only in the markup is not.
- Generate the JSON-LD from the same text. One
Questionper question, each with anacceptedAnswer. Our FAQ schema generator builds the block from pasted pairs. - Add the script to the page once. In the
heador thebody, as a singlescripttag of typeapplication/ld+json. - Validate it. Use the Schema Markup Validator, run by schema.org. Google said it would drop FAQ support from its Rich Results Test in June 2026, so that tool will not report on FAQ markup.
- Keep it in sync. If someone edits an answer on the page, the markup must change too. Generating both from one source is the only reliable way.
A complete, valid block for a page with two questions:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What are your opening hours?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We are open Monday to Saturday, 9:00 to 18:00, and closed on public holidays."
}
},
{
"@type": "Question",
"name": "Do you offer home visits?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, within the city limits, for an extra fee that we confirm when you book."
}
}
]
}
</script>
Keep the answer text plain and identical to the answer on the page. If the JSON is generated in code, escape quotes and line breaks, or the whole block fails to parse.
Which mistakes should you avoid?
- Marking up hidden content. Google's structured data guidelines forbid markup for content readers cannot see. A FAQPage block with questions that appear nowhere on the page is misleading markup.
- The same FAQ on every page. A site-wide FAQ block in the footer, marked up on 200 URLs, describes none of them.
- Two FAQPage blocks on one page. Usually a theme and a plugin both adding one. Keep one.
- Using FAQPage for user answers. Forum threads and community Q&A use QAPage, a different type with its own rules.
- Advertising inside answers. Answers stuffed with offers and keywords read badly and break the rule that markup must describe the content honestly.
- Answers that drift. The page says delivery takes five days; the markup still says three. Fix the source, not just the page.
What should you do with FAQ markup you already have?
Audit it once, then stop thinking about it.
- Accurate, visible and generated automatically: leave it. Google's 2023 post said unused structured data does not cause problems for Search.
- Hidden, duplicated or out of date: remove it or fix it. Inaccurate markup is the only version that carries risk.
- Added by a paid plugin you keep only for FAQ schema: cancel the plugin and remove the markup. Fewer plugins means fewer updates and fewer conflicts.
Do not expect any change in Google traffic either way. The rich result is gone for everyone, so removing or keeping the markup moves nothing you can measure. The structured data that still earns visible results for a business site, such as Organization, Breadcrumb and Product, is covered in structured data: which types matter. Spend the time there instead.
Was this guide useful?