Does Google still show FAQ rich results?

No. Google deprecated the feature on 7 May 2026 and FAQ rich results no longer appear for any site. The Search Console report and Rich Results Test support were removed in June 2026, and Search Console API support in August 2026. From August 2023 until then, only authoritative government and health sites qualified.

Should I remove FAQ schema from my site?

There's no need. Google has said existing FAQPage markup can stay in place and won't cause problems, and removing it gains nothing in Search. Keep it if it is generated automatically from your visible FAQ content; just don't spend extra effort hand-maintaining markup purely for Google.

Does FAQ schema help with AI Overviews or ChatGPT?

There's no evidence it gives an edge in Google's AI features — Google says no special markup is needed to appear in AI Overviews or AI Mode. Microsoft has said schema markup helps its LLMs understand content for Bing and Copilot. The visible questions and answers matter far more than the markup around them.

How do I add FAQ schema to a page?

Add a script tag with type application/ld+json containing one FAQPage object whose mainEntity array lists each Question with its acceptedAnswer. Every question and answer must also be visible on the page. WordPress SEO plugins such as Yoast and Rank Math generate the markup from their FAQ blocks.

What is the difference between FAQPage and QAPage schema?

FAQPage is for questions that each have one answer written by the site owner, like a help or product page. QAPage is for a single question where users submit answers, like a forum thread or community Q&A. Using FAQPage for user-submitted answers misdescribes the content.

FAQ Schema: JSON-LD Template and Google's 2026 Change

The short answer

FAQ schema is FAQPage structured data: a block of JSON-LD that labels the questions and answers on a page so machines can read them as Q&A pairs. You add it by pasting a <script type="application/ld+json"> block into the page that lists every visible question and its answer. What changed is the payoff. Google stopped showing FAQ rich results for every site on 7 May 2026, after spending almost three years restricting them. The markup is still valid and harmless, but it no longer produces the expandable question list under your Google result.

What changed, in order

2019: Google launches FAQ rich results. Any page with valid FAQPage markup can show expandable questions beneath its listing, and the markup spreads across almost every template.
August 2023: Google announces FAQ rich results will only be shown for "well-known, authoritative government and health websites". For nearly everyone else the feature disappears.
7 May 2026: Google deprecates the feature entirely. FAQ rich results stop appearing in Search for all sites, including the government and health sites that still had them.
June 2026: the FAQ search appearance filter, the FAQ rich result report in Search Console, and FAQ support in the Rich Results Test are removed, along with Google's FAQ structured data documentation.
August 2026: FAQ rich result data is removed from the Search Console API.

Google didn't publish a reason. Its deprecation notice did confirm the practical point: existing markup can stay in place and won't cause problems.

Is FAQ schema still worth adding?

For Google Search, it no longer earns anything you can see. Google's guidance on AI Overviews and AI Mode is also explicit that there are no additional technical requirements or special markup needed to appear in them, so don't add FAQPage expecting an AI-feature boost from Google.

Outside Google the picture is less settled. Microsoft's Fabrice Canel said publicly in March 2025 that schema markup helps Microsoft's LLMs understand content for Bing and Copilot, and schema.org is a shared vocabulary any crawler can parse. That is a reasonable, low-cost reason to keep generating it — not a measured ranking effect.

A sensible rule for 2026:

Already have FAQ markup? Leave it

Removing it gains nothing and costs a deploy. It won't trigger errors or penalties, and it keeps your Q&A machine-readable for any system that does use it.

Building new pages? Generate it, don't hand-maintain it

If your FAQ section is rendered from data — a CMS field, a JSON file, an array in code — output the schema from that same data. It stays in sync for free. If adding it means maintaining a second copy of every answer by hand, skip it.

Spend the effort on the visible FAQ instead

The questions and answers people can read are what gets quoted, whether by a featured snippet, an AI answer or a human skimming the page. Real questions from support tickets and search data, answered in the first sentence, do far more than the markup around them.

CheckSEO's FAQ Schema Generator turns a list of questions and answers into valid, ready-to-paste FAQPage JSON-LD — no hand-escaped quotes, no missing commas. Free and no signup.

Generate FAQPage JSON-LD

The JSON-LD template

Every FAQ block has the same shape: one FAQPage with a mainEntity array, and inside it one Question per item, each holding an acceptedAnswer of type Answer. The question text goes in name; the full answer goes in text.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does delivery take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Orders ship within one business day."
      }
    },
    {
      "@type": "Question",
      "name": "Can I return an item?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, unused items within 30 days."
      }
    }
  ]
}
</script>

The script can go in the <head> or anywhere in the <body>; parsers read it wherever it sits. Use one FAQPage block per page containing all of that page's questions, rather than a separate block for each one.

How to add it on common platforms

WordPress: Yoast SEO's FAQ block and Rank Math's FAQ block both output FAQPage markup for the questions you add in the editor, so the visible text and the schema come from the same place.
Shopify and other hosted builders: paste the generated script into the page's HTML or custom-code section, or use a theme app that renders it from your FAQ content.
Next.js and React: build the object from the same array that renders your FAQ list and output it as a script tag. Escape < so an answer can never close the tag early — the pattern the Next.js docs recommend:

// app/help/page.tsx
const faqSchema = {
  "@context": "https://schema.org",
  "@type": "FAQPage",
  mainEntity: faqs.map((f) => ({
    "@type": "Question",
    name: f.question,
    acceptedAnswer: { "@type": "Answer", text: f.answer },
  })),
};

<script
  type="application/ld+json"
  dangerouslySetInnerHTML={{
    __html: JSON.stringify(faqSchema).replace(/</g, "\u003c"),
  }}
/>

The rules that still apply

Google's FAQ guidelines went away with its documentation, but they described good structured data practice rather than anything Google-specific, and they are still the right standard:

Mark up only what is visible. Every question and answer in the schema must appear on the page. An answer inside a collapsed accordion counts, as long as a visitor can open it.
One answer per question, written by you. If users submit answers — a forum thread, a community Q&A — the correct type is QAPage, not FAQPage.
No advertising copy. The FAQ should answer real questions, not repeat sales messages in question form.
Full text, not teasers. Each text value holds the complete answer, not "click to find out".

How to check FAQ schema now

With FAQ support gone from Google's Rich Results Test, validate with the Schema Markup Validator at validator.schema.org, which checks any schema.org type against the vocabulary itself. It confirms the JSON parses and the properties are recognised. It can't tell you anything about search appearance, because there is none left to report. For how FAQPage fits alongside the types Google still rewards — Product, Article, Breadcrumb, Review — see the schema markup guide.

Generate your FAQ schema

CheckSEO's FAQ Schema Generator builds a clean FAQPage block from the questions and answers you enter, ready to paste into any page — the quickest way to keep your Q&A machine-readable without writing JSON by hand.

FAQ Schema: How to Add It, What Google Changed, and Whether It Still Helps