FAQ Schema: What Google Supports and What It Doesn't

Why FAQ Schema Became a Restricted Feature

For several years, FAQ schema was one of the most visually rewarding structured data types a publisher could add to a page. It expanded search results with accordion-style questions and answers directly beneath a listing, consuming significantly more space on the results page. Then, in 2023, Google quietly but decisively pulled that feature back. Understanding why that happened reveals something important about how Google thinks about rich results and structured data eligibility more broadly.

FAQ schema did not disappear entirely. It narrowed. Google now limits FAQ rich results to two categories of site: government websites and health websites. Every other publisher can still add FAQ markup to their pages, but Google will not render it as an expanded visual feature in search results. That distinction between "markup Google can read" and "markup Google will reward with a feature" sits at the heart of this lesson.

What FAQ Schema Actually Does

FAQ schema is a structured data format drawn from the Schema.org vocabulary. It signals to search engines that a section of a page contains a list of questions and their corresponding answers. The markup wraps each question-and-answer pair in a standardized format that machines can parse reliably, regardless of how the visible HTML is arranged.

When Google decides to surface a rich result from this markup, the effect is visible: the search listing expands to show two or three questions beneath the main title and URL. Users can click a question to reveal the answer without leaving the results page. This behavior made FAQ schema extremely attractive because it increased the physical footprint of a listing and gave users a reason to engage before clicking.

The markup itself has not changed. What changed is Google's decision about when to use it as the basis for a visual feature.

Why Google Narrowed Eligibility

The restriction reflects a pattern Google has applied to several rich result types over time: when a feature gets widely adopted for reasons that serve publishers rather than searchers, Google reassesses its value.

FAQ schema spread rapidly across commercial websites. Product pages, service pages, blog posts, and landing pages all began carrying FAQ sections, often written specifically to trigger the expanded rich result rather than to answer genuine user questions. The questions were frequently shallow, the answers brief, and the primary motivation was occupying more space on the results page. From a user perspective, the expanded listings added noise without adding proportionate value.

Government and health sites occupy a different position. People searching for information about public services, legal rights, medical conditions, or health guidance have a genuine and often urgent need for accurate answers. The FAQ format maps naturally onto how these institutions communicate: common questions from the public, answered with authoritative, factual responses. The feature serves the searcher in these contexts in a way it often did not on commercial pages.

Google's restriction is therefore a signal about intent alignment. The feature survives where it consistently serves the person searching. It was withdrawn where it had largely become a visibility tactic.

The Difference Between Markup and Features

One of the most important conceptual distinctions in structured data and schema markup is the gap between what you can mark up and what Google will reward with a feature. These are not the same thing, and FAQ schema illustrates that gap clearly.

Schema.org defines hundreds of entity types and properties. Google supports a subset of those for rich results. Even within that supported subset, eligibility is not guaranteed. Google applies its own guidelines about which sites and which contexts qualify for each feature. A publisher can implement technically perfect FAQ markup and receive no visual enhancement in return, either because their site category does not qualify or because Google's systems do not judge the content appropriate for the feature.

This matters because it reframes the purpose of structured data. Markup is not a mechanism for claiming search features. It is a way of communicating clearly with search engines about the nature and structure of content. Features are a downstream decision made by Google based on quality signals, content type, site context, and user benefit. The markup enables the possibility; it does not guarantee the outcome.

What Remains Possible for Non-Eligible Sites

For publishers outside the government and health categories, FAQ markup still has a function, even without the visual rich result. Search engines can use structured data to better understand page content, which may influence how a page is interpreted, indexed, and matched to queries. The absence of a rich result does not mean the markup is ignored entirely.

There is also the question of future eligibility. Google's policies on rich results evolve. A feature restricted today may be extended to new categories later, or a new feature type may emerge that uses similar markup in a different way. Publishers who understand the underlying structure of their content and communicate it clearly through markup are better positioned when those changes occur.

More practically, FAQ content on a page can still contribute to organic visibility through other routes. A well-structured FAQ section with clear questions and substantive answers can appear in featured snippets, People Also Ask boxes, or voice search responses, none of which depend on FAQ schema markup specifically. The content quality and the clarity of the question-answer relationship matter more for those features than the presence of structured data.

How This Fits the Broader Pattern of Rich Result Eligibility

FAQ schema is not an isolated case. Google has adjusted, restricted, or retired several rich result types over the years as usage patterns drifted away from user benefit. Review snippets, breadcrumb displays, and various product markup features have all been subject to eligibility changes.

The underlying logic is consistent. Rich results are a form of editorial curation by Google. They represent a decision to give certain content more prominence in search results. That prominence is justified when it reliably helps the person searching. When it becomes a mechanism for publishers to compete for space rather than to serve users, the justification weakens.

Understanding this pattern changes how it makes sense to think about structured data strategy in general. The question is not "which markup will get me a rich result?" The more durable question is "does my content genuinely serve the user in a way that a rich result would make clearer?" Sites that answer yes to that question are better aligned with where Google's eligibility decisions tend to land over time.

What This Lesson Establishes

FAQ schema still exists, still functions technically, and still has value in specific contexts. But the story of how it became restricted is a precise illustration of how Google thinks about the relationship between structured data, rich results, and user benefit. The feature was not removed because the markup was flawed. It was restricted because the pattern of use had diverged from the purpose the feature was designed to serve.

That understanding shapes how to interpret any structured data type: not as an entitlement to a feature, but as a contribution to a system that rewards content genuinely aligned with what searchers need. The eligibility rules for FAQ schema are a direct expression of that principle.