FAQ Content and FAQPage Schema: A Practical Guide

FAQ content is worth building. FAQPage schema is worth adding. But if you’re doing either one because you expect it to produce a rich result in Google Search, that reason no longer holds. This guide covers what still makes FAQ content valuable, what FAQPage schema actually does today, and where each fits into a real content strategy.

The rich result is gone. Here’s the actual timeline.

Google has been walking back the FAQ rich result for several years, and as of 2026 it’s fully discontinued for every site.

• August 2023: Google restricted the FAQ rich result to a narrow set of “well-known, authoritative government and health websites.” For essentially every commercial or business site, the expandable-question dropdown had already stopped appearing at this point, regardless of markup quality.
• May 7, 2026: Google discontinued the FAQ rich result entirely, for all sites, including the government and health sites that had kept it. It no longer shows in Google Search for anyone.
• June 2026: Google removed the FAQ search-appearance filter and rich result report from Search Console, and dropped FAQ support from the Rich Results Test.
• August 2026: Support for the FAQ rich result type in the Search Console API is scheduled to be removed.

Google’s own documentation update log confirms the May 7, 2026 discontinuation date and the phased removal of Search Console tooling, and Search Engine Land’s coverage reports the same dates from an independent source. If you still see FAQPage schema documentation floating around the web with a screenshot of an expandable dropdown, that screenshot is describing a feature that no longer exists.

Two practical notes if you already have FAQPage markup on your site:

1. You don’t need to rip it out. Google representatives, including John Mueller in public statements, have said structured data that doesn’t match any currently active rich-result feature is simply not used, it doesn’t cause errors or penalties on its own. This isn’t laid out in a single canonical Google document the way the May 7, 2026 discontinuation date above is, so treat it as a well-established public position rather than a citable spec line.
2. You also don’t need to add it expecting a visual payoff in Google. There isn’t one anymore.

So why bother with FAQ content at all?

Because the rich result was never the only reason FAQ content worked, it was just the most visible one. Three reasons still apply.

Page understanding. A tightly written Q&A block gives Google (and any other crawler) an unambiguous signal about what specific questions a page answers. This doesn’t require schema, it comes from the content itself, but well-structured FAQ content, in prose or in schema, makes that signal cleaner and easier for a crawler to parse.

Intent-matching for question queries. People still type or speak questions into search boxes and voice assistants. A page that directly answers “how long does an FAQPage schema take to get removed from a rich result” (to pick an example that’s now relevant) has a real shot at matching that query, independent of whether Google renders a dropdown for it.

Visibility as an answer surface for AI-generated answers. This is the part of the pitch that’s actually changed, not disappeared. Google’s AI Overviews, AI Mode, and other LLM-based answer engines pull from indexed web content to construct direct answers, and a clearly stated question followed by a clean, complete answer is exactly the kind of content unit these systems can extract and cite. Nobody outside Google publishes a verified mechanism for how a given FAQ block gets selected for an AI-generated answer, so don’t treat this as a guaranteed outcome or attach a false statistic to it. Treat it as a real, currently-relevant reason to structure content this way: clear question, complete self-contained answer, no fluff between them.

None of these three benefits depend on FAQPage schema being present. They depend on the FAQ content itself being genuinely good.

What FAQPage schema still does

Schema was never a ranking factor on its own, and that hasn’t changed. What it does is help a machine parse structured content unambiguously. With the rich result gone, FAQPage schema’s remaining job is machine-readability: it labels a group of questions and answers explicitly, which can make it easier for any system reading your page (search crawlers, AI answer engines, or anything else parsing the page) to identify the Q&A pairs without having to infer them from HTML structure. Without schema, a crawler sees a block of bolded questions in a <div> and has to infer which text is the question and which is the answer. With FAQPage JSON-LD, the same content is explicitly tagged as Question and acceptedAnswer pairs, no inference required.

That’s a real but modest benefit. It’s not nothing, but it’s also not a reason to force FAQ content onto a page that doesn’t need it, and it’s not a substitute for actually writing a good answer.

If you want the JSON-LD implementation mechanics (exact syntax, required properties, how markup attaches to a page), that’s covered in this site’s general schema markup guide rather than repeated here. This post stays focused on FAQ content strategy and the FAQ-specific parts of schema decision-making.

Content standards for FAQ that’s actually worth writing

Because the rich result incentive is gone, there’s no reason left to pad out FAQ sections with invented questions just to have “more” schema entries. What’s left is the actual bar for good FAQ content:

• Answer real questions. Pull from support tickets, sales call objections, Search Console query data, and “People Also Ask” boxes for the topic, not from a brainstorm of what sounds plausible.
• Give a complete answer. The point of an FAQ answer is that the reader doesn’t have to keep searching after reading it. A vague or partial answer that exists mainly to house a keyword defeats the purpose.
• Match depth to the question. A yes/no or single-fact question needs a short, direct answer. A “how do I…” question needs enough steps to actually be usable. Padding a simple answer to hit a word count, or truncating a complex one to keep things tidy, both make the content worse.
• Don’t duplicate answers already covered elsewhere on the page. If the body copy already fully answers a question, restating it verbatim in an FAQ block at the bottom adds length without adding information.

Where FAQ content belongs on a page

Three placement patterns are common, and they serve different purposes:

Placement	Best for	Risk if overused
Inline within body content	Answering a specific objection or clarifying a point right where the reader hits it	Breaks up reading flow if overused
End-of-page FAQ block	Catching secondary questions that don't fit the main content flow	Becomes a dumping ground for low-value, thin Q&A pairs
Dedicated FAQ page	Consolidating many related questions about one topic area (product, service, policy)	Thin, disconnected pages that don't rank for anything on their own

The right choice depends on how many genuine questions you have and how directly they relate to the surrounding content. A page with three or four questions closely tied to the topic works better as an inline or end-of-page block. A topic with fifteen or more genuinely distinct questions can justify a dedicated page, but only if each question is actually different, not a rephrasing of the same question five ways to inflate a schema count.

FAQPage vs QAPage

Google’s schema.org documentation distinguishes two related types. FAQPage is for content where a single entity (you, the site) writes and controls both the questions and the answers. QAPage is for user-generated Q&A content, like a forum or community platform, where multiple users can submit answers and one gets marked accepted. Most business sites writing their own FAQ content should use FAQPage; QAPage only applies if you’re running something closer to a public Q&A forum.

The bottom line

FAQ content is still a legitimate, useful content format. FAQPage schema is still worth adding if you already have genuine FAQ content, because it costs little and gives machines a cleaner read on the content’s structure. What’s no longer true, and shouldn’t appear in any FAQ strategy going forward, is the idea that adding FAQPage schema will earn you a visible spot in Google’s search results. That mechanism is gone as of May 7, 2026, for every site, permanently as far as anyone can currently tell. Build FAQ content because it answers real questions well, not because of what Google used to show for it. Start by pulling your last twenty support tickets or sales-call objections on the topic before writing a single FAQ answer, that’s where the real questions actually are.