What we measured ·
What Google shows for "faq schema" right now
Method: Live Google results (United States, desktop, English) for "faq schema" retrieved through DataForSEO's SERP API on 2026-10-22. Page types are our own classification of each ranking URL.
The top 8 organic results for "faq schema" were 3 guides or explainers, 2 product or service pages, 2 official search-engine docs pages, 1 video. The first three were schema.org, developers.google.com, neilpatel.com.
Google showed an AI Overview for this query, citing 6 source domains including schema.org, neilpatel.com, www.schemaapp.com, susodigital.com. Pages that state the answer directly and early are the ones an Overview can quote.
People Also Ask listed: "Is FAQ schema still relevant?"; "Can you provide an example of FAQ schema?"; "What does FAQ stand for?"; "How to structure a FAQ page?". The sections below answer the ones within this page's scope.
| Position | Domain | Page type |
|---|---|---|
| 1 | schema.org | Product or service page |
| 2 | developers.google.com | Official search-engine documentation |
| 3 | neilpatel.com | Guide or explainer |
| 4 | www.schemaapp.com | Guide or explainer |
| 5 | rankmath.com | Guide or explainer |
| 6 | www.youtube.com | Video |
What changed in 2023
In August 2023 Google announced it would show FAQ rich results only for well-known, authoritative government and health websites, and would stop showing them for other sites. At the same time it limited HowTo rich results to desktop, and later removed them. The FAQPage structured data itself remains part of Schema.org and can still be validated; Google simply does not display the rich result for most sites. Check Google's current structured data documentation, as eligibility can change again.
When FAQ markup is still worth adding
Add it when a page genuinely contains a list of questions and answers written by the site, because it describes the content accurately at little cost. Other search engines and tools may read it, and structured data helps machines understand page structure. On serionflow.com, every growth page that shows FAQs includes matching FAQPage JSON-LD, and our build check fails if a page shows FAQs without the markup, or carries the markup without visible FAQs. Do not add FAQs to a page just to carry the markup; FAQs should answer real follow-up questions.
Correct JSON-LD structure
The structure has three levels.
| Property | Value | Notes |
|---|---|---|
| @context | https://schema.org | Required |
| @type | FAQPage | One per page |
| mainEntity | Array of Question items | Each visible question |
| Question.name | The question text | Must match the visible question |
| Question.acceptedAnswer | An Answer item | One per question |
| Answer.text | The full answer text | Must match the visible answer; limited HTML allowed |
Mistakes to avoid
Marking up questions that are not visible on the page, or answers that differ from the visible text. Using FAQPage for content where users submit answers, which should use QAPage. Adding FAQ markup to every page with promotional questions such as 'Why is our product the best?'. Repeating the same FAQ block across many pages. Placing answers in collapsed sections that load only on click, which can hide them from crawlers; keep answers in the HTML even if collapsed visually.
Validating the markup
Test with Google's Rich Results Test, which reports whether the FAQPage markup is valid even though most sites will not get the rich result, and with the Schema.org validator. Check that the JSON-LD is in the server-rendered HTML. Our free schema builder and validator generates FAQPage JSON-LD from your questions and checks existing markup on a live page. SerionFlow is the wrong tool for adding FAQ markup to your existing pages; it adds matching markup only to the pages it publishes.
Clear answers
Frequently asked questions
Is FAQ schema still relevant?
+
For Google rich results, only for authoritative government and health sites since 2023. As accurate structured data describing a real FAQ section, it remains valid and harmless.
What is the difference between FAQPage and QAPage?
+
FAQPage is for questions and answers written by the site. QAPage is for pages where a single question has answers submitted by users, such as forums.
About the author
Shadrack Kumi · Founder, SerionFlow
Shadrack builds SerionFlow's site research, page generation, and Search Console tooling, and runs the free tools these guides pair with. Search Console figures cited on these pages come from serionflow.com's own property.
Continue exploring
Related SerionFlow resources
- Schema Builder and Validator
- AEO checklist: what to check on every page and across the site
- JavaScript SEO: how rendering works and what breaks
- Entity SEO: making search engines and AI understand who you are
- Internal linking strategy: how to plan links that help pages rank
- Single-page website SEO: what one page can rank for
More in Guides
- How to do a free SEO competitor analysis, step by step
- GEO audit checklist: what to check before expecting AI citations
- GEO services for SaaS: what to buy, from whom, and what to expect
- How to check a sitemap for errors
- How to fix keyword cannibalization
- How to get cited by ChatGPT, Perplexity, and Google AI Overviews
- Meta description length and best practices
- Programmatic SEO on Next.js and Vercel
Make the next move obvious
Let SerionFlow turn your market evidence into momentum.
Confirm the market, rank the opportunities that matter, create brand matched pages on your domain, and keep moving with controlled weekly intelligence.