Technical SEO for AI Search · How to

FAQ schema in 2026: Google dropped the rich result, now what?

Part of the guide Technical SEO for AI search: the 2026 checklist, in order

FAQ schema is FAQPage structured data in JSON-LD that marks up the questions and answers on a page. Google stopped showing FAQ rich results in Search from May 7, 2026 and removed the documentation on June 15, 2026, so the markup no longer earns expandable answers under your listing. It is still valid schema.org, costs little if generated automatically, and the visible FAQ it describes remains useful.

What happened to FAQ rich results?

Google retired them in two steps. On 8 May 2026 Google added a deprecation notice saying the feature "will no longer appear in Google Search starting May 7, 2026". On 15 June 2026 it removed the documentation, noting "The FAQ rich result feature is no longer shown in Google Search results". The old FAQPage guide URL now redirects to the Search Central updates page.

For where structured data fits among the other technical jobs, see the technical SEO for AI search checklist.

This was the end of a long decline. Since August 2023 Google had shown FAQ rich results only for "well-known, authoritative government and health websites", so most business sites had already lost them. If a tutorial written before May 2026 promises extra SERP space from FAQ schema, it is out of date.

Date Change Source
August 2023 FAQ rich results limited to authoritative government and health sites Google Search Central blog
7 May 2026 FAQ rich results stop appearing in Google Search Google documentation updates, entry of 8 May 2026
15 June 2026 FAQ rich result documentation removed Google documentation updates

Should you still add FAQPage markup?

Keep it if your CMS or template generates it from the visible FAQ for free; do not spend hours adding it by hand for Google. That is the honest answer for November 2026.

What FAQPage still does:

  • It is valid schema.org. Schema.org defines FAQPage as "a WebPage presenting one or more 'Frequently asked questions'". Any parser that reads schema.org can use it to understand the page's question and answer pairs.
  • It costs nothing when automated. If the markup is generated from the FAQ section on publish, it can never drift from the visible text.

What it does not do:

  • No Google rich result. That feature is gone.
  • No special AI Overviews boost. Google's AI features page says "There's also no special schema.org structured data that you need to add" to appear in AI Overviews or AI Mode, and its AI optimization guide says structured data "isn't required for generative AI search".
  • No documented effect in ChatGPT, Claude or Perplexity. None of their crawler pages we read on 16 November 2026 mention structured data.

The part that does matter is the visible FAQ. Answer engines rewrite one prompt into several short searches, and many of them are literal questions. A "### question" with a direct one to three sentence answer underneath is a paragraph that can be quoted as is. Write the FAQ for readers first; the markup is a by-product. Our guide to answer first content covers the writing side.

What does valid FAQPage JSON-LD look like?

A FAQPage has a mainEntity array of Question items, each with a name and an acceptedAnswer of type Answer with a text. Put it in a script tag in the page HTML:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you deliver on Sundays?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, between 10am and 4pm in Leeds and Bradford. Orders placed before 8pm on Saturday arrive on Sunday."
      }
    },
    {
      "@type": "Question",
      "name": "Can I change my delivery address after ordering?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, until the order is packed. Reply to your confirmation email with the new address."
      }
    }
  ]
}
</script>

Rules that keep it honest and useful, whether or not anyone shows a rich result:

  1. Match the visible text. Every question and answer in the markup must appear on the page, word for word. Markup for content users cannot see is misleading.
  2. One FAQPage per page. Put all question and answer pairs in one block.
  3. Real questions only. Questions customers ask, not keyword variations dressed as questions.
  4. Not for question and answer threads. For a page focused on one question with answers from users, schema.org points to QAPage instead.
  5. Server side. Put the JSON-LD in the HTML your server sends. Crawlers that do not run JavaScript will not see markup a tag manager injects; see how AI crawlers handle JavaScript.

How do you generate FAQ schema automatically?

Generate it from the content so the two never disagree. If your articles are markdown with a ## FAQ section and ### questions, this Python script prints a ready script tag. We tested it on 16 November 2026 against the markdown source of our OAI-SearchBot guide.

import json, re, sys

text = open(sys.argv[1], encoding="utf-8").read()
faq = text.split("\n## FAQ", 1)[1].split("\n## ", 1)[0]
pairs = re.findall(r"^### (.+?)\n+(.+?)(?=\n### |\Z)", faq, re.S | re.M)

data = {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
        {"@type": "Question", "name": q.strip(),
         "acceptedAnswer": {"@type": "Answer", "text": a.strip()}}
        for q, a in pairs
    ],
}
print('<script type="application/ld+json">')
print(json.dumps(data, indent=2, ensure_ascii=False))
print("</script>")

Run python3 faq_jsonld.py article.md. Answers are copied as plain text, so strip markdown links or formatting first if your answers contain them. On WordPress, if an SEO plugin's FAQ block writes the markup for you, view the page source once to confirm the JSON-LD is in the HTML and matches the visible answers.

How do you validate it now?

Use the Schema Markup Validator at validator.schema.org. Google's Rich Results Test checks markup for features Google shows, and FAQ is no longer one of them, so a syntax and vocabulary check is what you need. Paste the URL or the code and confirm a single FAQPage with the right number of Question items and no errors.

Then check the live page with curl to confirm the markup reaches crawlers:

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

A result of 1 means one FAQPage block is in the server HTML.

How Postbing handles FAQ schema

Every article Postbing writes includes an FAQ section and FAQ schema, alongside Article schema and meta tags. We kept it after Google dropped the rich result because it is generated, not hand written, and because the visible FAQ is useful to readers and answer engines. We do not claim it brings rich results or AI citations. You can see what each plan includes on the pricing page.

For the markup that still has a documented Google use, read the Article schema guide and the breadcrumb schema guide. The technical SEO for AI search checklist shows where structured data sits in the order of work: after access and rendering, not before.

FAQ

Does Google still show FAQ rich results?

No. Google's documentation updates say FAQ rich results stopped appearing in Google Search from May 7, 2026, and the documentation was removed on June 15, 2026.

Is FAQ schema bad for SEO now?

No. Google has not said FAQPage markup harms a page. It simply no longer produces a rich result, so its value is limited to valid, machine readable structure.

Does FAQ schema help with AI Overviews?

Google says no special schema.org structured data is needed to appear in AI Overviews or AI Mode. A clear visible FAQ can still be quoted because the answer sits right under the question.

What is the difference between FAQPage and QAPage?

FAQPage is for a list of frequently asked questions with answers written by the site. QAPage is for a page focused on one question and its answers, such as a thread on a question and answer site.

How do I test FAQ schema now?

Use the Schema Markup Validator at validator.schema.org for syntax, then fetch the page with curl to confirm the JSON-LD is in the server HTML.

Sources

Last updated: November 16, 2026. Spotted an error? Email support@postbing.com and we will fix it. Editorial policy.

Try Postbing free

Postbing reads your site, plans a month of topics from what your customers search for, writes in your voice and publishes to WordPress, Shopify, Webflow or Ghost. Your first article is free.

Try Postbing free

No card needed. No link exchanges, ever.