FAQ schema in 2026: what changed, what still works, five mistakes

FAQ schema no longer produces anything visible in Google. Google restricted FAQ rich results to well-known government and health sites in August 2023 and stopped showing them entirely on May 7, 2026, removing the related Search Console report and Rich Results Test support afterward. The FAQPage type is still valid Schema.org, and Google has said that structured data it is not using "does not cause problems for Search." No AI engine has documented that it uses FAQ markup to choose sources, and Google says no special schema is needed for AI Overviews. A well-written FAQ section on the page still earns its keep; the markup on its own no longer does much.

How we got here

For most sites, the 2026 change was a formality. The visible accordion of questions under a search result disappeared for anyone who was not a government or health authority nearly three years earlier. What changed in 2026 is that the last reason to treat FAQ markup as a search-appearance tactic went away.

Does FAQ schema help with AI search?

There is no published evidence that it does, and no vendor has said so. Google's guidance on AI Overviews and AI Mode is explicit that you do not need "new machine readable files, AI text files, or markup" and that there is "no special schema.org structured data that you need to add." OpenAI, Anthropic, and Perplexity document their crawlers, but none of them says FAQ markup influences which sources they cite.

An earlier version of this article claimed that language models "ingest FAQ schema as a high-confidence Q-and-A structure." We could not find a source for that, so it is gone. The reasonable position is narrower: structured data helps a crawler understand what a page is about, and a question-and-answer format on the visible page is easy for any system to read. The visible format is doing the work; the markup describes it.

Where a FAQ section still earns its place

A good FAQ section answers real questions directly, one per heading, in passages that stand on their own. That is exactly the shape answer engines quote, as our guide to citable passages explains. The best FAQ sections share four traits:

• The questions come from customers, not from marketing: sales calls, support tickets, reviews, and the People Also Ask results for your topic.
• Each answer starts with the answer, in one sentence, and then adds the detail a careful buyer would want.
• The answers are specific: prices, timelines, requirements, and exceptions, with sources where a figure needs one.
• The section is in the server-rendered HTML, not inside an accordion that loads its content with JavaScript, so AI crawlers can read it.

A worked example

Here is one FAQ entry from a typical home-services page, before and after. The "before" is what most FAQ sections look like; the "after" is what an engine can quote.

How much does it cost? Every home is different, so pricing depends on your needs. Contact us today for a free, no-obligation quote from our friendly team!

Before: no answer, nothing to quote

How much does a whole-house water filter cost to install? Most installations cost between $1,500 and $3,000, including the unit and labor. The main variables are the filter type, the length of pipe that has to be rerouted, and whether a permit is required in your county. We confirm the price in writing before any work starts.

After: answers, explains the range, names the variables

The figures in the example are illustrative. On your own page they must be true, current, and consistent with your pricing page, because an engine that quotes an outdated price is quoting you.

One more judgment call: a FAQ is not always the right format. If a question deserves more than a few paragraphs, such as a full cost breakdown or a comparison of options, give it its own page and link to it from the FAQ. A FAQ that tries to hold a guide's worth of content becomes a wall of text that answers nothing quickly.

Five mistakes that make FAQ content worthless

1. Marking up questions that are not on the page

Google's structured data guidelines are blunt: "Don't mark up content that is not visible to readers of the page." FAQ markup that describes hidden or absent questions violates that rule, and it was the most common way FAQ markup went wrong when rich results still existed.

2. Sales copy dressed as questions

"Why is our platform the best choice?" is not a question anyone asks. A section full of these teaches readers to skip it and gives engines nothing quotable. If the answer would not survive being shown without your logo next to it, cut the question.

3. The same FAQ on every page

Copying one FAQ block across every service or location page creates duplicate passages that compete with each other. Each page's questions should be specific to that page's topic.

4. Answers that do not answer

"It depends on your needs, contact us to learn more" is the most common FAQ answer on the web and the least useful. Say what it depends on, give the typical range, and then invite contact.

5. Broken or mismatched markup

If you keep FAQPage markup, keep it correct: a FAQPage with a mainEntity list of Question items, each with an acceptedAnswer whose text matches what is on the page. Markup that drifts from the visible content after an edit is worse than none, because it tells machines something the page does not say.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does a whole-house water filter cost to install?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most installations cost between $1,500 and $3,000, including the unit and labor. The main variables are the filter type, the length of pipe that has to be rerouted, and whether a permit is required in your county. We confirm the price in writing before any work starts."
      }
    }
  ]
}

Should you remove existing FAQ markup?

Not urgently. When Google first restricted FAQ results in 2023 it said there was "no need to proactively remove" the markup, because structured data it does not use "does not cause problems for Search, but also has no visible effects." Other search engines and tools may still read it. Remove it if it is invalid, if it describes questions that are no longer on the page, or if maintaining it is slowing down content edits. Spend the time you save on the visible answers instead.

How SEO for AI Agents measures this

We do not reward FAQ markup for its own sake, since no engine has said it matters for citation. The JSON-LD validity check does flag FAQPage blocks that are malformed, and the schema completeness check focuses on the types that describe your business and content, such as Organization, WebSite, Article, and the right LocalBusiness subtype for your vertical.

The visible FAQ content is what we measure closely. The passage extractability check shows, answer by answer, which FAQ entries are self-contained and quotable and which are too thin to stand alone, with the word count and heading behind each one. For background on the markup itself, see the glossary entries on structured data and rich results.