Check website

FAQ schema: is FAQPage markup still worth adding?

·4 min read

FAQ schema no longer gets you anything visible in Google. Google stopped showing FAQ rich results for every site on May 7, 2026, so FAQPage markup is worth adding only to a page that already has a real FAQ, and only because it costs little and breaks nothing. Never build an FAQ section just to carry the markup.

That is the whole verdict. The rest of this post covers why, what correct markup looks like, and what to do with the FAQ schema you already have.

What happened to FAQ rich results?

They are gone for everyone. Google limited FAQ rich results to well-known government and health sites in August 2023, then dropped them for all sites on May 7, 2026. The Search Central changelog records the deprecation, and on June 15, 2026 Google removed the FAQ structured data documentation altogether.

So there is no longer an official Google page listing FAQPage requirements. The type still exists on schema.org, and validators still parse it. Google simply has no search feature that uses it.

Is FAQPage schema still worth adding?

Yes on a page with a genuine, visible FAQ. No anywhere else. Here is how I would decide.

Situation What to do
Support or pricing page with real customer questions Keep or add FAQPage markup
Blog post with a "FAQ" section bolted on for snippets Remove the section and the markup
Product page with questions and answers written by shoppers Use QAPage, not FAQPage
Existing valid FAQ markup on a real FAQ Leave it alone

The case for keeping it is modest. Valid markup labels each question and answer for any parser that reads JSON-LD. It does no harm, and removing it is work with no return.

The case against adding it everywhere is stronger. Google's AI optimization guide says structured data isn't required for generative AI search. I have found no primary documentation from Google, OpenAI, Perplexity or Microsoft saying their AI answers use FAQPage markup. Blog posts claiming FAQ schema triples AI citations cite their own small samples. Treat that as a guess.

What does help is the visible FAQ itself. A question in a heading followed by a short, direct answer is easy for any engine to quote, with or without markup. If the markup were deleted tomorrow, the content would still do the work. Our AEO checklist covers that writing pattern.

FAQPage schema example in JSON-LD

FAQPage markup is one FAQPage node whose mainEntity holds a list of Question nodes, each with an acceptedAnswer. Put it in the page's HTML inside a script tag.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I change plans mid-month?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Upgrades apply right away and we prorate the difference. Downgrades start at your next billing date."
      }
    },
    {
      "@type": "Question",
      "name": "Do you ship outside the US?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We ship to Canada, the UK and the EU. Duties are shown at checkout."
      }
    }
  ]
}
</script>

The question text goes in name, not text. The answer goes in acceptedAnswer.text. Keep it plain text and escape any double quotes inside it, or the whole block stops being valid JSON. If JSON-LD itself is new to you, start with what JSON-LD is.

FAQ schema rules that still apply

The FAQ-specific documentation is gone, but Google's general structured data guidelines still cover this markup. Follow these rules.

  1. Mark up only visible content. Google's guidelines say not to mark up content readers can't see. Every question and answer in the JSON-LD must appear on the page, word for word or very close.
  2. Match the page. The guidelines say structured data must be a true representation of the page content. Markup describing questions from another page fails that test.
  3. One FAQPage per question set. Put all of a page's questions in a single FAQPage node. Don't split them across several nodes, and don't paste the same block onto every page of the site.
  4. Use FAQPage only for questions you answer. If visitors post questions and others reply, that is a QAPage.

Spammy structured data can earn a manual action, which removes rich result eligibility. With no FAQ rich result left to lose, the real cost of fake FAQ markup is a page padded with filler.

What to do with FAQ schema you already have

Audit it once and stop worrying. Run each page with FAQPage markup through a validator and sort it into two groups.

  • The FAQ is real and the markup is valid. Leave both.
  • The FAQ exists only for the markup. Delete the section and the JSON-LD together, or rewrite the content into normal sections with question headings.

The Rich Results Test explains what Google's own tester still shows, and our schema markup guide lists which types still earn rich results so you can spend your markup effort there.

Build FAQPage JSON-LD for a real FAQ

Our FAQ Schema Builder turns your questions and answers into FAQPage JSON-LD. Paste them one per line as Question | Answer, and add a page name and URL if you want them in the markup. Nothing is fetched from your site.

It checks the output against the same validator rules as our Schema Markup Checker and notes that Google no longer shows FAQ rich results. A run costs 3 credits. Paste the result into the page that shows those questions, then check the live page with the Schema Markup Checker.

Keep reading