Google no longer shows FAQ rich results. In August 2023 it limited them to well-known government and health sites [1], and its updates page now says the feature no longer appears in Google Search results as of May 7, 2026 [2]. FAQPage markup will not give you an expandable result in Google. It can still be worth adding if the page has real questions and answers that readers can see, because it states those pairs in a standard vocabulary at almost no cost.

What Google changed, and when

August 8, 2023. Google announced that FAQ rich results would only be shown for well-known, authoritative government and health websites [1]. It also said sites could keep their FAQ structured data, and that structured data that goes unused does not cause problems for Search but has no visible effect there [1].

May 2026. Google's updates page says the FAQ rich result feature was deprecated on May 8, 2026, and that it no longer appears in Google Search starting May 7, 2026 [2]. The June 2026 documentation update says the FAQ rich result documentation was removed because the feature is no longer shown in Search results [2].

In practice:

  • You cannot expect FAQ rich results in Google from any markup you add.
  • There is no current Google FAQ rich result guideline to follow, because the page was removed.
  • The general structured data rules still apply. They are covered below.

What the general guidelines still say

Two points in Google's general structured data guidelines matter here.

  1. Structured data must follow Google's policies to be eligible for rich results, and Google does not guarantee it will appear in search results even when it is marked up correctly [3].
  2. Markup should be visible to users and representative of the main content of the page [4].

The second point is the one to build your process around. Every question and answer in your JSON-LD should also appear in the page's visible text. Do not put answers in markup that readers cannot see. Do not use markup to say something the page does not say.

Google's older FAQ documentation also said FAQ markup is for official questions and answers. It said not to use it on forums where users can submit alternative answers [1]. That is still a sensible boundary. A page where many people answer the same question is not an FAQ page in the schema.org sense.

What schema.org says

Schema.org defines FAQPage as a type for a page with frequently asked questions and answers [5]. That vocabulary is independent of Google's rich result program. It stays valid whether or not any one search engine renders it.

Google's 2019 documentation noted that FAQ markup could help with snippet generation even when the rich result itself was not shown [6]. That is historical documentation, and the current notes do not confirm it still applies. Do not count on it.

The AI extraction argument, stated carefully

The case for FAQPage now rests on machine readability, not on a Google display feature. JSON-LD lists each question and its accepted answer as separate, labeled items. A parser reading that block does not have to work out where one question ends and the next begins.

What we do not have is vendor documentation saying that a specific AI engine reads FAQPage markup or gives it weight when choosing sources. As far as public documentation goes, that is unconfirmed. Treat it as a low-cost, unproven benefit. It is not a reason to expect citations.

A clear page structure matters whether or not markup exists. If the questions are real headings and the answers are plain text, the content stands on its own. See heading structure for how to set that up.

When to add it

SituationFAQPage markup?
Page has a visible Q&A section written by you, with stable answersReasonable to add
Page has questions in the markup only, not on screenDo not add. It breaks the visible-content rule [4]
Forum or community thread with multiple user answersDo not use FAQPage [1]
Page already has FAQPage markup that matches visible textLeave it. Google said unused markup causes no problems [1]
Page has FAQPage markup whose text no longer matches the pageFix the markup or the page so they agree
You were adding it only to win an expandable result in GoogleThat result is no longer shown [2]

A minimal example

Visible HTML:

<h2>Can I cancel at any time?</h2>
<p>Yes. You can cancel from the billing page, and your plan stays active until the end of the paid period.</p>

<h2>Do you offer refunds?</h2>
<p>Refunds are available within 14 days of the first payment.</p>

Matching JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I cancel at any time?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. You can cancel from the billing page, and your plan stays active until the end of the paid period."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer refunds?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Refunds are available within 14 days of the first payment."
      }
    }
  ]
}
</script>

The question and answer text is identical in both places. That is the property to preserve when someone edits the page later.

Keeping it accurate

  • Generate it from the same source as the page. If the visible FAQ comes from a CMS field or a template, build the JSON-LD from that same data so the two cannot drift apart.
  • Validate syntax. Run the page through the Schema Markup Validator at validator.schema.org to catch malformed JSON and missing properties.
  • Check visible parity. Open the page, then open the markup, and compare them line by line. Do this after every content edit.
  • Keep the list short and real. Use questions customers actually ask, not keyword-shaped filler.

For the wider set of types worth marking up, see Schema.org markup for AI search. To fit this into a broader review, use the technical SEO checklist. If you also publish site-level markup, the Organization schema check covers that separately.

What to do next

  1. List the pages where you have, or plan, markup for a Q&A section.
  2. For each one, confirm every question and answer in the JSON-LD appears in the visible page text.
  3. Remove FAQPage from any page where the answers are not visible or are user-submitted.
  4. For pages that qualify, generate the markup from the same data as the on-page FAQ.
  5. Validate the syntax, then stop. Do not expect a visible change in Google results.