What is FAQ schema (FAQPage markup) and does it still help in 2026?

Published

Short answer

FAQ schema is schema.org FAQPage markup, usually JSON-LD, that lists the questions a page answers and the answer to each. It no longer produces anything visible in Google: FAQ rich results stopped appearing on May 7, 2026, and Google has since removed the documentation and the Rich Results Test support. It is still valid, harmless markup that states your questions and answers in machine-readable form, but no search or AI engine documents that it earns citations, so the visible FAQ text matters more than the markup.

For years, FAQ markup was an easy way to make a search result bigger: a few questions unfolded right under your link. That ended in two steps, in 2023 and in 2026. Many guides still describe the old behaviour, and many sites still carry the markup. Here is what FAQ schema is, what Google says about it today, where it can still be useful, and how to write and test it correctly.

On this page
  1. FAQ: what is it, and what is FAQ schema?
  2. What happened to FAQ rich results in Google?
  3. Does FAQ schema still help AI answers?
  4. What properties does FAQPage markup need?
  5. Should I use QAPage or FAQPage?
  6. How do I test FAQ schema?

FAQ: what is it, and what is FAQ schema?

FAQ stands for frequently asked questions: a section or page that lists common questions about a product, service or topic with a short answer to each. FAQ schema is a way of describing that section to machines. It uses the schema.org vocabulary, which defines FAQPage as a web page presenting one or more frequently asked questions. Each question is a Question with a name, and its answer is an Answer with text.

The markup is usually written in JSON-LD, a block of JSON in a script tag that sits next to the visible HTML and does not change how the page looks. The words FAQ schema, FAQ markup and FAQ structured data all mean the same thing.

What happened to FAQ rich results in Google?

Google changed the feature in two steps, and the second removed it entirely.

In 2023 Google also said there was no need to remove FAQ markup, and that structured data which is not used does not cause problems for Search. Nothing in the 2026 notices changed that. So the markup is not harmful, it simply no longer changes how your result looks.

Does FAQ schema still help AI answers?

Be careful with claims here. For Google, the answer is documented: Google says structured data is not required for its generative AI features and that there is no special schema.org markup to add for AI Overviews or AI Mode. OpenAI, Anthropic and Perplexity do not say anything about FAQ markup in their crawler documentation. No source shows that FAQPage markup leads to citations.

What FAQ markup can do is narrower. It pairs each question with its full answer in a format any parser can read without guessing from the layout. If a system does read JSON-LD, that removes ambiguity. Even then, the visible FAQ text is what a reader, and most likely an engine, quotes. A clear question as a heading with a direct answer underneath does the real work; the markup restates it.

The practical rule: if a page already has a visible FAQ section, adding the markup costs little and does no harm. Do not build FAQ sections only to carry markup, and do not expect the markup to fix a page that crawlers cannot reach.

What properties does FAQPage markup need?

Until June 2026, Google's FAQ documentation required mainEntity on the FAQPage with at least one Question; name and acceptedAnswer on each Question, with one answer per question; and text on each Answer, containing the full answer. That matches the schema.org definitions and is still the structure to use. Its content rules remain sensible: use FAQPage only when each question has a single answer written by the site, include the entire question and answer text, do not use it for advertising, and keep all FAQ content visible on the page. Google's general structured data guidelines still say markup must be a true representation of the page and must not describe content that readers cannot see.

A complete example for a page with two questions:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I cancel my plan at any time?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. You can cancel in your account settings, and the plan stays active until the end of the current billing period."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer a free trial?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. There is no time-limited trial: the free plan is the way to try, with one check a day and no card. Paid plans can be cancelled at any time, with a full refund within 14 days of any payment."
      }
    }
  ]
}
</script>

The name and text values should be the same wording as the questions and answers on the page. Put the block in the HTML the server sends rather than injecting it with JavaScript, so any crawler that does not run scripts still sees it.

Should I use QAPage or FAQPage?

They describe different pages. FAQPage is for a list of questions that the site itself answers, one answer each. QAPage is for a page built around a single question where users can submit answers, such as a forum thread or a community support question. Google's Q&A documentation says not to use QAPage for FAQ pages or for pages with several questions, and lists a FAQ page written by the site itself as an example of where QAPage does not apply.

Unlike FAQ, the Q&A rich result is still in Google's structured data gallery and still supported in the Rich Results Test, so for genuine community Q&A pages QAPage is still a supported Google feature.

How do I test FAQ schema?

The Rich Results Test at search.google.com/test/rich-results no longer lists FAQ among the rich result types it supports, so it will not report on FAQPage items. Use the Schema Markup Validator at validator.schema.org instead. Google describes its purpose as checking the syntax of markup and its compliance with schema.org, without checking Google rich result types. Paste the page URL or the code and look for errors in the FAQPage, Question and Answer items.

Then check what a crawler that does not run JavaScript receives:

curl -s https://example.com/faq | grep -c '"@type": *"FAQPage"'

A result of 0 means the markup is missing from the server's HTML, or is added by scripts, or is written with different spacing. Finally, compare each name and text value with the visible page, word for word.

AISeeWhy reports missing FAQ markup as a finding with a fix guide, and its free check shows how much of a page's text arrives without JavaScript, which is where both the visible answers and the markup need to be.

Fixes for this problem

Free tools

Next steps

Frequently asked questions

Should I remove FAQPage markup now that Google no longer shows FAQ rich results?

There is no need. Google said in 2023 that unused structured data does not cause problems for Search, and the 2026 notices did not ask sites to remove it. Remove it only if it no longer matches the visible page.

Can FAQ schema get my site cited by ChatGPT, Perplexity or Claude?

No vendor documents that. Their crawler documentation does not mention FAQ markup. What helps is a page the crawlers can fetch, with questions as headings and direct answers in the visible text. Markup can restate those answers, but it does not replace them.

Does FAQ markup have to match the visible text?

Yes. Google's structured data guidelines say markup must be a true representation of the page and must not cover content that is hidden from readers, and its former FAQ rules required all FAQ content to be visible on the page.

Can I put FAQ schema on every page?

Only on pages that really have a visible list of questions with one site-written answer each. Adding generic questions to every page to carry markup adds clutter for readers and no documented benefit.

Is FAQ schema the same as FAQ markup and FAQ structured data?

Yes. All three names refer to schema.org FAQPage markup with Question and Answer items, usually written in JSON-LD.

Sources

More articles