FAQ Schema Markup: Is It Still Worth Adding?

For a few years, FAQ schema markup was the easiest rich result in SEO. Add a few questions in JSON-LD, and your search listing grew expandable dropdowns that pushed competitors further down the page. Then Google changed the rules, and a lot of sites were left with markup that no longer produces anything visible.

This guide covers what FAQ schema is, the current Google limits, how to implement it correctly, and our view on when it is still worth the effort.

What FAQ Schema Markup Is

FAQ schema is structured data using the schema.org FAQPage type. It tells search engines that a page contains a list of questions, each with a single answer provided by the site itself.

It is not the same as QAPage, which is for pages where users submit questions and multiple answers (forums, community Q&A). If visitors can post their own answers, FAQPage is the wrong type.

What Changed in 2023

In August 2023, Google announced it would limit FAQ rich results: they are now shown only for well-known, authoritative government and health websites. For everyone else, the FAQ dropdowns no longer appear in Google Search, even with valid markup. At the same time, Google reduced and then deprecated HowTo rich results.

Two things did not change:

• FAQPage is still valid schema.org markup, and Google still documents it. Valid markup does not cause problems.
• The Rich Results Test still validates the markup, so “valid” in the tool does not mean “eligible for display” for your site.

The most common misunderstanding we see: site owners validate their FAQ markup, see no errors, and assume the missing dropdowns are a bug. They are not. Unless the site is a recognized government or health authority, Google will not show them.

Is FAQ Schema Still Worth Adding?

Our position: yes, where the FAQ genuinely belongs on the page, and no as a ranking or CTR tactic.

Reasons it can still be worth it:

1. It is cheap when generated from content you already show. If a page has a real FAQ section, emitting matching JSON-LD from the same source costs nothing to maintain.
2. Other consumers read structured data. Search engines other than Google and various tools that parse pages can use explicit question-and-answer structure. How much any specific AI system relies on it is not publicly documented, so treat this as a modest, unproven upside rather than a reason on its own.
3. It forces a clean content structure. Writing distinct questions with self-contained answers improves the section for readers, and self-contained answers are exactly what tends to get quoted in featured snippets and AI summaries.

Reasons not to bother:

• Adding a fake FAQ block to every page purely to carry markup. It clutters pages and no longer earns a visual reward.
• Maintaining markup by hand, separately from the visible content. It drifts, and mismatched structured data is a guidelines problem.

Google’s Rules for FAQPage Markup

From Google’s structured data guidelines for FAQ content, the essentials are:

• The questions and answers must be visible on the page. Do not mark up content hidden from users.
• Use FAQPage only where the site provides both question and answer.
• Do not use it for advertising content.
• Each question should include the full question text, and each answer the full answer text.
• If the same FAQ appears on several pages, mark it up only once on the site.

A JSON-LD Example

Here is a minimal, valid implementation for a page with two questions:

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How long does a technical SEO audit take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "A crawl of a small site finishes in minutes. Analysis and a prioritized report usually take one to three days, depending on site size and how many data sources are reviewed."
        }
      },
      {
        "@type": "Question",
        "name": "Do I need to fix every issue an audit tool reports?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "No. Prioritize issues that block crawling or indexing of important pages, then work down by impact. Many low-severity warnings never affect rankings."
        }
      }
    ]
  }
</script>

Notes:

• Answer text can contain limited HTML such as links, lists and bold text. Keep it simple.
• Put the script in the <head> or <body>; either works.
• If the page already has other structured data (an Article, a Product), you can combine types with an @graph array rather than separate scripts. Both approaches are valid.

Combining with Article markup

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "headline": "How to Run a Technical SEO Audit",
      "datePublished": "2026-10-12"
    },
    {
      "@type": "FAQPage",
      "mainEntity": []
    }
  ]
}

Generate It From the Content, Not by Hand

The most robust pattern is to generate FAQ markup from the same source that renders the visible FAQ. A few ways to do that:

• CMS fields: a repeatable “FAQ” field group (question, answer) that renders both the HTML section and the JSON-LD.
• Markdown conventions: treat a specific heading, such as ## Frequently asked questions, as the FAQ section and build JSON-LD from the H3 questions beneath it at build time. This is what we do on this blog: every FAQ you see at the end of an article produces matching markup automatically, so the two can never drift.
• WordPress plugins: Yoast SEO and Rank Math both offer FAQ blocks for the block editor that output the markup alongside the visible content.

How to Validate FAQ Schema

1. Rich Results Test (Google): paste the URL or code. It confirms the FAQ markup parses. Remember that “eligible” here does not guarantee display.
2. Schema Markup Validator (schema.org): checks the markup against the schema.org vocabulary, independent of Google features.
3. Search Console enhancement reports: if Google detects FAQ markup on your site, it may show a report with valid items and errors. Watch it after template changes.
4. Spot-check the rendered page, not just the source, if your FAQ is injected with JavaScript. The markup must be present after rendering.

You can draft markup with a schema markup generator and then validate it with the tools above. For broader structured data strategy, see our schema markup guide; for business-specific types, see the local schema markup guide.

Common FAQ Schema Mistakes

1. Markup without visible content. The FAQ exists only in JSON-LD. This violates the guidelines.
2. Same FAQ on every page. A sitewide FAQ block (shipping, returns) marked up on thousands of product pages. Mark it up once, on the FAQ page.
3. Answers that do not answer. “Contact us to learn more” is not an answer and makes the section useless for readers.
4. Marketing questions. “Why is our product the best?” is an advert, not a frequently asked question.
5. Stale answers. Prices, policies and dates in FAQ answers go out of date quickly. If the markup is generated from content, fixing the visible text fixes the markup too.

Frequently asked questions

Does FAQ schema still work in 2026?

FAQ schema is still valid structured data, but since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. Most sites will not see FAQ dropdowns in Google even with valid markup.

Does FAQ schema help SEO rankings?

There is no evidence that FAQ markup is a ranking factor. Its historical benefit was a larger search listing. Today the main benefits are clean content structure and machine-readable question-and-answer pairs.

What is the difference between FAQPage and QAPage schema?

FAQPage is for questions and answers written by the site itself. QAPage is for pages where users ask a question and other users submit answers, such as forums and community Q&A pages.

Can FAQ schema be added to every page?

Only to pages that actually show a relevant FAQ to visitors. Adding the same FAQ block and markup to every page is against Google’s guidelines and adds clutter without benefit.

How do I test FAQ schema markup?

Use Google’s Rich Results Test to check that the markup parses, the Schema Markup Validator for vocabulary checks, and Search Console’s enhancement reports to monitor errors across the site.