FAQ schema is structured data, usually written in JSON-LD, that labels the questions and answers on a page so machines can read them as a list of question-and-answer pairs. If a landscaping company's service page has a section answering "How often should I aerate my lawn?", FAQ schema marks that question and its answer using the schema.org FAQPage type.
For businesses, the most important thing to know is that FAQ schema no longer produces special results in Google. Google limited FAQ rich results to a small group of government and health sites in 2023, and stopped showing them in Google Search entirely on May 7, 2026. The markup is still valid, and other systems may still read it, but it is no longer a way to win extra space on Google's results page.
What is FAQ schema?
FAQ schema is a type of schema markup based on the FAQPage type from schema.org, the shared vocabulary that search engines use for structured data. It wraps a page's frequently asked questions in a standard format. Each item is a Question with a name, the question text, and an acceptedAnswer containing the answer text.
Most sites add it as JSON-LD, a block of code in the page that visitors don't see. The questions and answers in the markup should match the FAQ content that is visible on the page. Every entry in this glossary, for example, includes FAQPage markup that mirrors the questions at the bottom of the page.
FAQ schema is meant for pages where the site itself writes both the questions and the answers. Pages where users submit answers, such as forums, are a different case.
Why FAQ schema matters
Its role in Google has changed completely. For several years, FAQ schema could make a page eligible for an FAQ rich result: expandable questions shown below a listing in search results. That made it a popular SEO tactic. In August 2023, Google announced that FAQ rich results would be shown only for well-known, authoritative government and health websites. Most business sites lost them at that point.
Google has now ended FAQ rich results for everyone. Google's documentation says FAQ rich results no longer appear in Google Search starting May 7, 2026. Google said it would drop the FAQ search appearance, the rich result report in Google Search Console and Rich Results Test support in June 2026, and end Search Console API support in August 2026. Google published no blog post explaining the change.
The markup isn't harmful. Search Engine Journal reported that Google's documentation says FAQ structured data can stay on pages without causing problems, though it won't produce visible FAQ results. FAQPage remains a valid schema.org type.
The AI angle is unproven, not zero. Microsoft's Fabrice Canel confirmed at SMX Munich that Bing uses schema markup to help its large language models understand content. There is no public evidence that FAQ schema specifically makes AI tools more likely to cite a page. What clearly helps is the visible content itself: direct questions with clear, self-contained answers.
How FAQ schema works
The structure
FAQ schema uses three schema.org types. FAQPage describes the page. Inside it, mainEntity holds a list of Question items. Each Question has a name (the question) and an acceptedAnswer of type Answer, which has a text property (the answer).
How search engines read it
Search engines and other systems parse the markup when they crawl the page. Because the format is standard, they can tell exactly which text is a question and which is the answer without guessing from the page layout.
What changed in display
Reading markup and displaying a special result are separate things. Google no longer displays FAQ rich results, but it hasn't said whether it uses the markup for anything else. Treat any benefit outside Google's results page as possible but unconfirmed.
How to use FAQ schema today
- Write the visible FAQ first. The questions and answers on the page are what people, search engines and AI tools actually read. Base them on real customer questions.
- Keep answers short and complete. Answer each question directly in two or three sentences that make sense on their own.
- Match markup to the page. If you add FAQ schema, make sure every question and answer in the markup matches the visible text exactly.
- Don't rebuild just for schema. If FAQ markup is already on your site, Google's documentation doesn't require removing it. If it isn't, adding it is low priority compared with other work.
- Prioritize schema that still drives features. Types like Product schema, LocalBusiness schema and Organization schema still support search features and entity understanding.
- Update reports and tracking. If you used Search Console's FAQ report or API fields, remove them from dashboards so missing data isn't mistaken for a traffic drop.
Common mistakes and misconceptions
- "FAQ schema will get us extra space in Google." Not anymore. Google stopped showing FAQ rich results on May 7, 2026.
- "We need to remove all our FAQ schema." Search Engine Journal reported that Google's documentation says the markup can stay without causing problems. Removing it is optional.
- "FAQ schema guarantees AI citations." No public evidence supports this. Clear, useful answers on the page matter more than the markup.
- "Any page can be stuffed with FAQs." Adding unrelated or repetitive questions to many pages creates thin, duplicated content. Use FAQs where real questions exist.
- "FAQ markup can differ from the page." Google's general structured data guidelines say not to mark up content that readers can't see. Markup that doesn't match the page misleads the systems that read it.
FAQ schema vs. an FAQ section
An FAQ section is visible content: questions and answers that people read on the page. FAQ schema is hidden code that labels that content for machines. The section can exist without the schema, and it still helps visitors, search engines and AI tools. The schema without a matching section is pointless. Today, the visible section does most of the work, and features like People Also Ask and featured snippets don't require FAQ markup at all.
How Butter approaches FAQ schema
At Butter, we follow Google's current documentation, so we no longer recommend FAQ schema as a way to win rich results. We focus on writing strong FAQ sections based on the questions a client's customers actually ask, with direct answers that work for readers and are easy for AI tools to quote.
Our schema markup guidance prioritizes types that still support search features and help systems understand a business, such as Organization, LocalBusiness and Product. Where FAQ markup already exists and matches the page, we usually leave it in place. Where it doesn't match, we recommend fixing or removing it.
Frequently asked questions
Does Google still show FAQ rich results?
No. Google's documentation says FAQ rich results no longer appear in Google Search starting May 7, 2026. Before that, from 2023, they were limited to well-known, authoritative government and health websites.
Should I remove FAQ schema from my site?
You don't have to. Google's documentation says the markup can stay without causing problems, and FAQPage is still a valid schema.org type. Just make sure it matches the visible content.
Does FAQ schema help with AI search?
It's unproven. Microsoft has said Bing uses schema to help its models understand content, but there's no public evidence that FAQ markup itself increases AI citations. Clear answers on the page matter most.
Is it still worth writing FAQ sections?
Yes. A good FAQ section answers real customer questions in plain language. That helps visitors and gives search engines and AI tools clear, quotable answers.