FAQ Schema: The Markup, Google's Changes and When It Is Still Worth Adding
FAQ schema is FAQPage structured data: a list of questions, each with one answer, written in JSON-LD. For years it earned expandable questions under a result in Google. Since August 2023 Google has shown that rich result only for well-known government and health sites, and on May 7, 2026 it stopped showing it for every site. The markup itself is still valid Schema.org, and it can still be worth keeping. Here is what changed, what the markup looks like and when to use it.
What FAQ Schema Is
FAQ schema uses three Schema.org types. FAQPage describes a page of frequently asked questions. Its mainEntity holds a list of Question items. Each Question has a name, the full question, and an acceptedAnswer, an Answer whose text is the full answer.
It is meant for a page where the site itself wrote both the questions and the answers: a support page, a returns policy, a product FAQ. Where users post questions and other users answer them, the right type is QAPage, not FAQPage.
What Google Changed, and When
The short version: since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites, and since May 7, 2026 it shows them for no site at all. The dates, from Google's own August 2023 announcement and the Search Central changelog:
| Date | What changed | Who sees FAQ results |
|---|---|---|
| Before Aug 2023 | Rich result open to all sites | Any eligible site |
| Aug 8, 2023 | Limited to authoritative sites | Government and health only |
| May 7, 2026 | Rich result retired | No site |
| Jun 15, 2026 | Documentation removed | No site |
Google gave the reason in 2023: a cleaner, more consistent results page. The old documentation URL, /structured-data/faqpage, now redirects to the changelog entry. Nothing in either notice asks sites to remove the markup, and Google's general rule still holds: structured data that is not used for a feature does no harm.
If your traffic reports show a drop in clicks on FAQ pages around August 2023 or May 2026, this is a likely reason. The pages did not lose rankings; they lost the extra lines under the result.
FAQPage Properties at a Glance
The properties Google listed as required until its FAQ documentation was removed in June 2026. Google never listed any recommended ones. Schema.org allows many more, but these are the ones every consumer expects.
| Type | Property | Google status | Expects |
|---|---|---|---|
| FAQPage | mainEntity | Required | One or more Question |
| Question | name | Required | Full question text |
| Question | acceptedAnswer | Required | One Answer |
| Answer | text | Required | Full answer, simple HTML |
| FAQPage | Recommended properties | 0 listed | None |
The answer text could carry a short list of HTML tags: h1 to h6, br, ol, ul, li, a, p, div, b, strong, i and em. Other tags were ignored. One FAQPage per page was the rule.
A Valid FAQ Schema JSON-LD Example
Put the block anywhere in the HTML, usually in the head. Each question and answer must also be visible on the page, word for word or close to it.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does a refund take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Refunds reach your card within <b>5 to 10 business days</b> after we receive the item."
}
},
{
"@type": "Question",
"name": "Can I return an item without the box?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Pack it safely and include the order number. See our <a href=\"https://www.example.com/returns\">returns page</a>."
}
}
]
}
</script>
Notes on the example:
- One
acceptedAnswerper question. Several answers to one question means the page is a QAPage. - HTML inside
textis escaped JSON, so quotes inside attributes need a backslash. - Raw line breaks inside a JSON string break the block. Use
<br>or a space.
Validate it with the Schema Markup Validator. Google's Rich Results Test no longer has an FAQ result to show. The schema markup validator guide explains the difference between the two tools.
Why FAQ Schema Can Still Be Worth It
The rich result is gone. The reasons to keep the markup are about everything else that reads a page:
- It is still valid Schema.org. FAQPage was never removed from the vocabulary. Validators accept it, and it carries no penalty.
- Machines read questions as questions. The markup states, in a format any parser understands, which text is a question and which is its answer. That is useful to any search engine, assistant or AI system that reads structured data, even where none promises a visible feature for it.
- It keeps the page honest. Writing the markup forces each answer to be complete and to sit next to its question.
- It costs almost nothing. A few hundred bytes, usually generated by the same template that prints the FAQ.
SEO ProCheck goes through the evidence in FAQ schema: why you still keep FAQPage markup, including when it is worth adding to a new page. Our rule of thumb:
| Your situation | Keep or add | Why |
|---|---|---|
| Real FAQ, already marked up | ✓ | Valid, costs nothing |
| Real FAQ, no markup yet | ◐ | Add with the template |
| Questions invented for markup | – | Remove the fake questions |
| User answers on one question | – | Use QAPage instead |
| Markup without visible FAQ | – | Against Google guidelines |
We follow that rule ourselves. Every guide on neova.app with a Questions section, this one included, prints FAQPage JSON-LD from the same list of questions that renders on the page, so the markup and the visible answers cannot differ.
What the markup will not do any more is change how a result looks in Google. Do not expect a click gain from adding it.
Rules That Still Apply
Google's general structured data guidelines cover every type, FAQPage included:
- Visible content only. Every question and answer in the markup must be on the page. An answer inside a click to expand section counts as visible.
- No advertising. An FAQ written as a sales pitch was against the FAQ guidelines, and markup that misleads is against the general ones.
- Complete text. The full question in
name, the full answer intext. No teasers. - One answer per question, written by the site. User answers belong in QAPage.
- Same markup on one page only. An FAQ block repeated on every page of a section describes none of them well.
Common FAQ Schema Mistakes
| Mistake | Effect | Fix |
|---|---|---|
| Raw line break in a string | Block does not parse | Escape or remove it |
| Markup differs from page | Misleading markup | Print both from one source |
| Several FAQPage blocks | Unclear which is main | Merge into one |
| FAQ on a forum thread | Wrong type | Use QAPage |
| Same FAQ on every page | Duplicate signals | One page per FAQ |
| Questions nobody asks | Thin, written for markup | Use real support questions |
The first one is the most common, and it is invisible in the browser. One broken character can make the whole block unreadable, and with it every other type the same script holds.
Check FAQ Schema Across a Site With Neova
Neova's Structured Data category reads JSON-LD, microdata and RDFa from every HTML page of a crawl, lists the types in a Schema Types column and gives each type on a URL a verdict. For FAQ markup, these checks matter most:
- Structured Data Has Syntax Errors, for JSON-LD that does not parse, has a raw newline or tab in a string, or lacks @context or @type
- FAQ Section Lacks Real Questions or Differs From Its FAQPage Markup, read by the AI reader on pages with FAQPage markup or 3 or more visible questions
- QAPage or Forum Posting Markup Does Not Match the HTML Page, for the cases where QAPage was the right choice
- FAQ Review Is Unrecorded, Undated or Past the Review Cycle, a written review of your FAQ against real questions, every 365 days unless set otherwise
- HTML Page Has No Structured Data, for indexable pages with no markup at all
The AI reader checks run with AI on your own computer. The Free plan crawls up to 1,000 URLs with every check, on Mac, Windows and Linux. See Features or download Neova.
Questions
Does FAQ schema still work in 2026?
The markup is still valid Schema.org, but Google stopped showing the FAQ rich result for every site on May 7, 2026. From August 2023 until then, it showed it only for well-known government and health sites.
Should I remove FAQ schema from my pages?
No, if the FAQ is real and visible. Google never asked anyone to remove it, and unused structured data does no harm. Remove it only where the questions were invented for the markup or are not on the page.
What are the required properties of FAQPage?
Google's last published list: mainEntity on FAQPage, name and acceptedAnswer on each Question, and text on each Answer. It listed no recommended properties.
What is the difference between FAQPage and QAPage?
FAQPage is for questions the site asks and answers itself, one answer each. QAPage is for one question with answers posted by users, such as a forum or support community thread.
Why did Google limit FAQ rich results in 2023?
Google said it wanted a cleaner and more consistent results page, and kept the feature only for well-known, authoritative government and health sites, where it judged the answers most useful.