Skip to content
Join the waitlist

Classic Search

FAQ Schema

FAQ schema is FAQPage structured data from schema.org that labels the questions and answers on a page. Google stopped showing FAQ rich results in Search on 7 May 2026, so the markup no longer earns that appearance there. It still describes the page’s questions and answers in a form machines can read.

  • Industry term

By QueryRev ResearchPublished Updated5 min read

Why it matters.

The markup was built for a result Google no longer shows. In August 2023 Google said FAQ rich results would be shown only for well-known, authoritative government and health sites, and not regularly for any other site[1]. In May 2026 it added a deprecation notice to its documentation: the feature no longer appears in Google Search from 7 May 2026, and in June it removed the documentation[2].

Dropping it is optional. When it reduced the result in 2023, Google said there was no need to remove the structured data proactively, because markup that is not used does not cause problems for Search and has no visible effect there[1]. Keeping it costs nothing in Search, and neither does leaving it out.

The vocabulary itself has not changed. Schema.org defines an FAQPage as a web page presenting one or more frequently asked questions[3], and the Question type as a specific question, such as one collected in a frequently asked questions document, with an acceptedAnswer property for the answer[4]. Any system that reads schema.org can read it.

What lasts is the question-and-answer content on the page. Microsoft’s guidance on AI search answers says that direct questions with clear answers mirror the way people search, that assistants can often lift such pairs word for word into AI-generated responses, and that schema can label content as an FAQ so machines can interpret it[5]. Google says there is no special schema.org structured data to add for its AI features, and that structured data should match the visible text on the page[6]. Markup is one of several statements a site can make to a machine. In QueryRev’s study, 164 of the 5,637 robots.txt files read, 2.9%, carry a Content-Signal line stating preferences for search, AI input and AI training[7]. Each says something to a program, and neither replaces a page that answers the question.

How it is measured.

Count the pages that carry FAQPage markup, and check on each that every marked question and answer is visible in the page’s text, word for word. Structured data that does not match the visible text is the one failure that matters, whatever the markup earns.

Measure what the questions earn now. Record, for the questions the page answers, whether the page holds a featured snippet or a place in People Also Ask, and whether an AI answer quotes or cites the passage. These are the results a clear question and answer can still win, and they are counted with the AEO measures, not as rich results.

Check that the answers can be read. Microsoft advises against hiding important answers in tabs or expandable menus, because AI systems may not render hidden content[5]. An accordion that needs a click is a risk for the answer, whatever the markup says.

Measured by

  • Pages with FAQ markup
  • Markup that matches the text
  • Answers lifted

A worked example.

Sample data: an invented site, to show the method.

A sample health information site, of the well-known kind that Google still showed FAQ rich results for after August 2023, has a guide to home blood pressure checks with three questions and FAQPage markup that labels them. Before 7 May 2026 the markup could earn an FAQ rich result in Google Search. After that day no site is shown one. The questions, the answers and the markup are the same in both versions, and what has changed is what the markup earns.

The site leaves the visible questions in place, because readers use them, and checks once that the markup matches them word for word. It stops adding FAQ markup to new pages as a way to earn a result, and it measures the three questions by whether an answer lifts them, not by a rich result that cannot appear.

The same markup, before and after May 2026

What to do, step by step.

  1. Crawl the site for FAQPage markup and list the pages that carry it.

  2. On each page, compare the marked questions and answers with the visible text. Correct the markup, or remove it, where they differ.

  3. Keep the visible questions where they help readers. Write each question as a heading and give the answer in the first sentence.

  4. Stop adding FAQPage markup to new pages to earn a rich result, and add it only where a template produces it at no cost.

  5. Show answers in the page text, not behind a tab or a click that a machine may not open.

  6. Measure the questions by featured snippets, People Also Ask places and AI answers that quote them, over several snapshots.

Mistakes to avoid.

  • Marking up questions that are not on the page. Structured data has to match the visible text. Markup for questions a reader cannot see breaks that rule, so fix it or remove it.

  • Expecting a rich result. Google no longer shows the FAQ rich result, and a report that still counts it as a win counts something that cannot happen.

  • Removing the questions with the markup. Google’s change was to a result, not to the value of a clear question and answer. Assistants can lift such pairs from the text of the page.

  • Hiding answers in an accordion. Microsoft says AI systems may not render hidden content. Put the answers that matter where a crawler reads them without a click.

How QueryRev treats it.

QueryRev treats FAQ markup as a change to a page like any other. A proposed fix shows the markup before and after, checked against the visible questions and answers, and a person approves it under policy before it is applied and written to the Change Ledger. The question-and-answer content is judged by whether answers use it, not by a rich result. See Governed Execution, the guide to answer engine optimization and the GEO audit checklist.

Questions people ask.

Should I remove FAQ schema from my site?

There is no need to. When Google reduced the result in 2023 it said markup that is not used causes no problems for Search and has no visible effect. Keep it where it matches the visible questions and answers, and remove it where it is costly to maintain.

Is FAQ schema the same as an FAQ section?

No. An FAQ section is the questions and answers a reader sees. FAQ schema is the markup that labels them for machines. The section keeps its value for readers whether or not the markup is there.

Does FAQ schema help AI answers?

Google says no special schema.org markup is needed for its AI features. Microsoft says clear question and answer pairs are easy for assistants to lift and that schema can label content as an FAQ. The pairs on the page matter more than the label.

Sources and citation.

Primary sources only: the search engines, the AI vendors, standards bodies and QueryRev’s own research. Each is cited in the text by its number.

  1. Changes to HowTo and FAQ rich resultsGoogle Search Central Blog ·

  2. Latest documentation updatesGoogle Search Central ·

  3. FAQPageSchema.org ·

  4. QuestionSchema.org ·

  5. Optimizing your content for inclusion in AI search answersMicrosoft Advertising ·

  6. AI features and your websiteGoogle Search Central ·

  7. State of AI crawler access, October 2026QueryRev Research ·

Cite this definition

A suggested citation. Its link goes to the definition, whose anchor does not change.

QueryRev Research. “FAQ Schema.” QueryRev AI glossary, 23 October 2026. https://queryrev.com/glossary/faq-schema#definition

Related terms