FAQ schema used to be one of the easiest wins in SEO. Add a few lines of markup, and your search result grew a set of expandable questions that pushed competitors down the page. That is over. Google stopped showing FAQ rich results entirely in May 2026.
So is FAQ schema still worth adding? Sometimes, for different reasons than before. This guide covers what changed, what the markup still does, when to bother with it, and how to write the FAQ content itself, which now matters far more than the code around it.
What is FAQ schema?
FAQ schema is structured data, usually written in JSON-LD, that labels a list of questions and answers on a page. It uses the schema.org FAQPage type, with each pair marked as a Question and its acceptedAnswer. It tells machines "this is a question, and this is its answer", rather than leaving them to work it out from the layout.
What happened to FAQ rich results?
Google wound the feature down in two steps.
| When | What changed |
|---|---|
| 2023 | Google limited FAQ rich results to well-known, authoritative government and health websites. Everyone else lost them |
| May 7, 2026 | FAQ rich results stopped appearing in Google Search altogether, for every site |
| June 2026 | Google removed the FAQ search appearance report, Rich Results Test support and the documentation |
If you added FAQ markup to win a bigger search listing, that reason no longer exists. If an SEO tool or plugin still flags missing FAQ schema as a problem, it is working from an outdated rulebook.
Does FAQ schema still do anything?
Less than it used to, but it is not dead code. Here is what is known, and what is only claimed.
- Bing: Microsoft's Fabrice Canel said in March 2025 that Bing uses schema markup to help its large language models understand content. That covers Bing search and Microsoft Copilot
- Google: FAQPage is still valid schema.org markup, and Google has said there is no need to remove it. It no longer produces a visible result, and Google has not said it uses it for AI Overviews
- ChatGPT, Perplexity and Gemini: there is no public confirmation either way. Anyone telling you FAQ schema gets you cited by ChatGPT is guessing
What is clear is that the questions and answers themselves, the visible text on the page, are what AI tools quote. A page with a well-written FAQ section and no markup is more useful than a page with perfect markup wrapped around vague answers.
Should you remove FAQ schema you already have?
No. It does no harm, it costs nothing to keep, and it may still help Bing and Copilot read the page. Remove it only where it is wrong: where the marked-up questions do not appear on the page, or where the same FAQ block is repeated across dozens of pages.
When is FAQ schema worth adding?
| Worth adding | Not worth it |
|---|---|
| The page has a real FAQ section answering questions customers ask | The questions exist only to fit keywords in |
| Each answer is specific to that page | The same five questions appear on every page of the site |
| Your CMS or plugin generates it from the visible FAQ automatically | Someone has to hand-code and maintain it separately |
| The answers are factual and stable | The answers are sales copy |
The pattern is simple. If maintaining the markup takes real effort, put that effort into the answers instead.
How do you add FAQ schema correctly?
If you do add it, the rules that applied before still describe good practice.
- Mark up only questions and answers that are visible on the page, word for word
- Use one FAQPage block per page, listing every question in it
- Keep advertising out of the answers
- Generate the markup from the same source as the visible FAQ, so the two cannot drift apart
- Validate it with the Schema Markup Validator at validator.schema.org, since Google's Rich Results Test no longer checks FAQ markup
The structure is short. Each entry in the mainEntity list is a Question with a name, which is the question text, and an acceptedAnswer, which is an Answer with a text property holding the answer.
How do you write FAQ answers that get quoted?
This is the part that still pays off, in Google's featured snippets, in AI answers and with readers.
- Answer in the first sentence. "Yes, usually within two weeks" beats a paragraph of context
- Make each answer stand alone, so it still makes sense when lifted out of the page
- Keep most answers between 40 and 80 words
- Use the question as customers phrase it, taken from calls, emails and the People Also Ask box
- Include one specific detail, a number, a time frame or a condition, that a generic answer would not have
The same principles drive featured snippet optimization, and they are a large part of why AEO, SEO and GEO overlap more than the acronyms suggest.
Where do you find questions worth answering?
Not from a keyword tool alone. The best FAQ questions come from people who have already tried to buy from you.
- Phone calls and emails: write down every question a customer asks twice
- Search Console: in the Performance report, filter queries containing words like how, what, why, can and does to see the questions you already appear for
- The People Also Ask box in Google for your main service keywords
- Sales objections: the reasons people give for not going ahead
- Your competitors' reviews, where customers say what they wish they had known
Five real questions answered well beat twenty invented ones. Each answer should tell a reader something they could not have guessed.
Which pages should have an FAQ section?
| Page type | Good FAQ topics |
|---|---|
| Service pages | Cost, timing, what is included, who it suits |
| Pricing page | What changes the price, contracts, cancellation |
| Product pages | Sizing, compatibility, shipping, returns |
| Guides and articles | Follow-up questions the article raises but does not cover in depth |
| Location pages | Questions specific to that area, not the same ones as every other location |
Keep each FAQ specific to its page. Repeating one block sitewide adds the same text to dozens of URLs, which helps nobody and makes it harder for search engines and AI tools to tell your pages apart.
Which schema matters more now than FAQ schema?
With FAQ rich results gone, structured data earns its keep by describing who you are and what you offer, consistently. For most businesses that means Organization or LocalBusiness markup with your name, address, phone, logo and profiles on other sites, Service or Product markup on the pages that sell, and Article markup with accurate publish and update dates on content. These help search engines and AI tools connect your pages to one clear business, which is a bigger lever for AI visibility than any FAQ block.
The short version
FAQ schema no longer changes how you look in Google. Keep it where it is accurate, add it where it is automatic, and spend the effort on answers worth quoting. The questions at the end of this article are marked up exactly that way, generated from the same text you are reading. For help structuring your own pages, see our answer engine optimization services.
