Technical SEO for AI Search · Explainer
What is FAQ schema markup? A plain definition for 2026
Part of the guide Technical SEO for AI search: the 2026 checklist, in order
FAQ schema markup is a block of code, usually JSON-LD, that uses the schema.org FAQPage type to label the questions and answers on a web page so machines can read them as pairs. Google used it to show expandable FAQ rich results, but it stopped showing them on 7 May 2026 and removed the documentation in June 2026. The markup is still valid schema.org vocabulary.
FAQ schema in one sentence, and in one example
Schema.org defines the type in one line: "A FAQPage is a WebPage presenting one or more 'Frequently asked questions'." The markup restates the questions and answers that are already visible on your page in a format a crawler can parse without guessing which paragraph answers which heading.
Here is the smallest useful example, for a page with one question:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Do you deliver on Sundays?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Orders placed before 2pm on Saturday arrive on Sunday."
}
}]
}
</script>
The script tag sits anywhere in the page's HTML and is invisible to visitors. It is one of many structured data types; the technical SEO checklist for AI search covers where FAQ markup sits among the others.
The four parts of FAQ markup
Every FAQPage block is built from the same four pieces, nested inside each other.
| Part | What it is | In the example |
|---|---|---|
FAQPage |
The page type: a page made of frequently asked questions | "@type": "FAQPage" |
mainEntity |
The list of questions on the page | The array in square brackets |
Question with name |
One question, with its exact wording | "Do you deliver on Sundays?" |
acceptedAnswer with Answer and text |
The answer to that question | "Yes. Orders placed before 2pm..." |
To add more questions, add more Question objects to the mainEntity array, separated by commas. The answer text can include basic HTML such as links and lists.
What happened to FAQ rich results in Google?
Google no longer shows FAQ rich results for any site. The timeline, from Google's own documentation updates page:
| Date | What Google did |
|---|---|
| August 2023 | Limited FAQ rich results to "well-known, authoritative government and health websites" |
| 8 May 2026 | Added a deprecation notice: the feature "will no longer appear in Google Search starting May 7, 2026" |
| 15 June 2026 | Removed the FAQ rich result documentation; the feature "is no longer shown in Google Search results" |
The old FAQPage documentation URL now redirects to the updates page. So for Google Search specifically, FAQ schema no longer changes how your result looks. Our FAQ schema guide covers what to do with existing markup in more detail.
Is FAQ schema still worth adding?
It is low cost and harmless when it matches your visible FAQ, but do not expect a Google ranking or display benefit from it. Two things from Google's current documentation frame the decision:
- Google does not need it for AI features. The AI features page says: "There's also no special schema.org structured data that you need to add" to appear in AI Overviews or AI Mode. The AI optimization guide lists "overfocusing on structured data" among things you can ignore.
- Structured data in general is still recommended for features that use it. The same guide says to keep using structured data "as part of your overall SEO strategy, as it helps with being eligible for rich results".
What remains is the general value of machine readable structure. FAQPage is still a schema.org type, and other systems that read pages can parse it. No AI search vendor we checked documents using FAQPage markup as a ranking or citation signal, so treat any claim that it gets you cited by ChatGPT or Perplexity as unproven.
Our view: if your site template already generates FAQ markup from a visible FAQ section, keep it. If adding it means manual work on every page, spend that time on the FAQ content itself.
The visible FAQ matters more than the markup
The questions and answers on the page are what readers, search engines and AI systems actually read. A good FAQ section answers real follow-up questions in one to three sentences each, in the same words people use to ask them. That helps whether or not markup is present.
Google's structured data guidelines add a hard rule that applies to every type: "Don't mark up content that is not visible to readers of the page." FAQ markup that lists questions the page does not show, or answers that differ from the visible text, breaks that rule. If you keep FAQ schema, generate it from the visible FAQ so the two cannot drift apart.
FAQPage vs QAPage
Use FAQPage when the site owner writes both the questions and the answers. Schema.org describes QAPage as a page "focussed on a specific Question and its Answer(s)", which fits forums and community sites where users post answers. A product page with an FAQ block written by the business is FAQPage; a support forum thread with several user answers is QAPage.
How to add and check FAQ schema
Most sites add it in one of three ways: a CMS block or plugin that outputs it automatically, a JSON-LD script pasted into the page's code settings, or a template that builds it from the page's FAQ section. Platform steps are in adding FAQ schema in WordPress and adding FAQ schema in Wix and Webflow.
To check the syntax, paste the code or URL into the Schema Markup Validator at validator.schema.org. Because Google no longer offers an FAQ rich result, Google's Rich Results Test is no longer the right tool for this type.
FAQ
What does FAQ schema do?
It labels question and answer pairs on a page so machines can read them as structured data. Google used it for FAQ rich results until 7 May 2026; it no longer displays them.
Does FAQ schema help SEO in 2026?
Not for how your result looks in Google, since FAQ rich results are gone. It does no harm when it matches your visible FAQ, but the FAQ content itself is what helps readers and search.
Do I need FAQ schema for AI Overviews?
No. Google says there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode. A page must be indexed and eligible for a snippet.
Should I remove existing FAQ schema?
There is no need to, as long as it matches the visible questions and answers. Remove it if it lists questions that are not shown on the page, because that breaks Google's structured data guidelines.
Sources
- Schema.org: FAQPage: definition of the FAQPage type, accessed 16 November 2026
- Schema.org: QAPage: definition of the QAPage type, accessed 16 November 2026
- Google Search Central: Documentation updates: FAQ rich result deprecation (8 May 2026) and documentation removal (15 June 2026), accessed 16 November 2026
- Google Search Central blog: Changes to HowTo and FAQ rich results (August 2023): restriction to government and health sites, accessed 16 November 2026
- Google Search Central: AI features and your website: no special structured data needed, accessed 16 November 2026
- Google Search Central: Optimizing for generative AI search: structured data not required for generative AI search but still useful for rich results, accessed 16 November 2026
- Google Search Central: General structured data guidelines: do not mark up content that is not visible, accessed 16 November 2026
Related reading
Last updated: November 16, 2026. Spotted an error? Email support@postbing.com and we will fix it. Editorial policy.
Try Postbing free
Postbing reads your site, plans a month of topics from what your customers search for, writes in your voice and publishes to WordPress, Shopify, Webflow or Ghost. Your first article is free.
Try Postbing freeNo card needed. No link exchanges, ever.