What is FAQPage schema, and should you use it?
Markup that labels a genuine FAQ section so machines can read the questions and answers as questions and answers, rather than as an undifferentiated block of text. Useful when you have a real FAQ, and actively risky when you pretend you do.
What it actually is
A page can look obviously like an FAQ to a person — bold question, answer underneath, repeat — and be completely ambiguous to a machine, which sees only a sequence of headings and paragraphs. FAQPage markup makes the relationship explicit: this text is a question, that text is its answer, and the same business wrote both.
Why it matters
Question-and-answer content is the single most quotable shape on the web for AI assistants, because it matches what a user asked. When your answer is already labelled as the answer to a specific question, an assistant can lift it with confidence and attribute it to you. Unlabelled, that same answer competes with every other paragraph on the page for the assistant's attention.
What good looks like
Markup that appears on pages with a real FAQ — several genuine questions, each with your own substantive answer — and matches what a visitor can actually see on the page. The questions in the markup should be the questions on the page, and the answers should be the answers. It belongs on pages that have an FAQ, not on every page of the site.
Being honest about it
Google narrowed the rich result this markup earns, so the visible search payoff is much smaller than it was a few years ago and anyone selling it on rich snippets alone is behind. The reason it still matters is AI readability, not decoration in the results page. And it genuinely does not apply to most pages — a glossary, a service page or a blog post does not need it, and we do not treat its absence there as a problem.
Where most sites go wrong
The dominant failure is markup describing an FAQ the page does not have, usually inherited from a template or an SEO plugin applied site-wide. That is a mismatch between what you claim and what you show, which is the category of problem search engines treat most harshly. A near relation is marking up questions the site answers elsewhere, or not at all, leaving an assistant holding a question with an empty answer attached to your name.
On the web
State of the Web · November 2026In November 2026, 46% of the sites where it applies (19% of the sites we could read) passed the “FAQ / Q&A schema” check.
WordPress sites pass it most often, at 51%. Webflow sites pass it least often, at 41%.
On the sites scanned in both September 2026 and October 2026, it went from 44% to 51%.
The month-by-month line counts the sites scanned in each calendar month, so it can differ from the figure above, which uses each site’s latest scan from the last three months.
Goes with
-
Sites that pass this are 2.5 times as likely to pass the “A machine-readable published / updated date” check too. 17% of the sites that pass the first check pass this one, against 7% of the sites that do not.
-
Sites that pass this are 2.5 times as likely to pass the “Images are optimised” check too. 23% of the sites that pass the first check pass this one, against 9% of the sites that do not.
-
Sites that pass this are twice as likely to pass the “Buttons, links and fields have names” check too. 48% of the sites that pass the first check pass this one, against 23% of the sites that do not.
Not enough history yet.
Based on the sites Bot Appétit has scanned. Most of these sites come from lists we scan for research. Not a random sample of the web.
Not sure where yours stands?
A free scan checks this and everything else in about 20 seconds — no signup. Or if it's already flagged and you'd rather it were simply handled, we do that too.
Flagged for this one? We handle it. No pitch, just a plain-English chat.
Book a call