FAQ schema is JSON-LD code that labels a page’s questions and answers as FAQPage structured data. Since 7 May 2026 Google no longer turns it into a rich result for any site, so the expandable Q&A dropdown under the blue link is gone. FAQ schema still has a job: it gives AI answer engines and other crawlers clean, machine-readable question-and-answer pairs, and it keeps your on-page Q&A well structured. A free generator adds it in under a minute, no coding required.
Need FAQ and other structured data added across many pages? Our SEO, GEO and technical SEO service handles schema site-wide and checks it in Search Console.
What Is FAQ Schema and Why Add It
FAQ schema uses the FAQPage type from schema.org to mark up a list of questions and their answers in a machine-readable format. Google used to show each question as an expandable dropdown under the search result, but it retired that FAQ rich result for every site on 7 May 2026 (details below). The value now is structure: the markup tells crawlers and AI answer engines exactly which text is a question and which text answers it, so the answer can be quoted accurately, while the visible Q&A section does the work for human visitors.
Beyond classic search, FAQ schema is one of the clearest signals you can give an AI answer engine. A question wrapped in Question and an answer wrapped in acceptedAnswer is exactly the shape ChatGPT, Google’s AI Overviews, and Perplexity look for when deciding what to quote — it’s already split into the question someone asked and the direct answer, with no guesswork required.
How to Add FAQ Schema With a Free Generator
- Open the free Schema Markup Generator and select the FAQ type. Our free Schema Validator checks the same code against schema.org and Google’s required fields in one step. Our schema markup validator guide explains each check in the report.
- Click “Add Question” and type your first question and its answer.
- Repeat for every question you want included — add or remove rows freely.
- The tool builds a complete
FAQPageJSON-LD block as you type. - Copy the code and paste it into your page, ideally right after the visible FAQ section it describes.
The schema must match content that’s actually visible on the page — don’t generate questions the page doesn’t answer.
What FAQ Schema Code Looks Like
A two-question FAQ generates a compact block like this:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQ schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQ schema is JSON-LD markup that labels questions and answers so search engines and AI tools can read them as question-and-answer pairs."
}
}
]
}Each additional question becomes another object inside the mainEntity array — the generator handles that nesting automatically so you never have to count brackets by hand.
FAQ Schema vs. HowTo Schema: Which One Do You Need
The two are easy to mix up because both mark up help content, and Google has retired the rich results for both (How-to in September 2023, FAQ in May 2026). FAQ schema fits a genuine list of separate questions a visitor might ask — “Is this free?”, “Does it work on mobile?” — where each answer stands on its own. HowTo schema fits a single task broken into ordered steps, like assembling furniture or setting up an account, where step 3 only makes sense after step 2. If your content is a numbered list of steps that must happen in order, use HowTo. If it’s a set of independent questions, use FAQ. Some pages legitimately need both — a setup guide followed by a short FAQ about edge cases — and that’s fine, as long as each schema block matches its own visible section.
What Changed: Google Retired FAQ Rich Results in 2026
Google cut FAQ rich results back in two steps. In August 2023 it limited the expandable FAQ dropdown to well-known, authoritative government and health websites. Then it retired the feature for everyone: from 7 May 2026, FAQ rich results stopped appearing in Google Search for all sites, government and health sites included. Google removed the FAQ search appearance, the rich result report and Rich Results Test support in June 2026, deleted the FAQ rich result documentation on 12 June 2026, and gave Search Console API users until August 2026 to adjust (see the Search Central changelog).
In practice, valid FAQ schema no longer earns any visual feature in Google, and the Rich Results Test no longer reports on it. FAQPage is still a valid schema.org type, so existing markup does not cause errors and there is no need to rip it out. It just should not be the reason you add a FAQ section.
The reasons to keep one never depended on the dropdown. Question headings with short, self-contained answers are the format AI answer engines and voice assistants lift into their responses, and FAQ schema mirrors that structure in machine-readable form for any crawler that reads it. The visible Q&A also answers objections for real visitors before they leave. Write the questions for people first, keep the markup identical to the visible text, and treat AI citations, not a Google snippet, as the payoff.
FAQ Schema and Voice Search
Voice assistants answer questions by reading back a single, concise passage. A page whose FAQ content is cleanly split into distinct questions and short, direct answers is far easier for a voice assistant to lift and read aloud than a paragraph where the answer is buried in the middle of a longer explanation. Keeping each answer under 2–3 sentences, in addition to adding the schema, improves your odds of being the source a voice assistant reads from.
Common FAQ Schema Mistakes to Avoid
- Marking up questions that aren’t visible on the page. The questions and answers in your schema must match what a visitor actually sees.
- Writing answers that are too long. Keep each
acceptedAnswerconcise — a few sentences, not a full article. - Using FAQ schema for a single question. It’s built for genuine lists of questions; one question is better served by a direct heading and answer.
- Forgetting to update the schema when the visible FAQ changes. If you edit a question on the page, update the JSON-LD to match, or the two will drift out of sync.
Where to Use FAQ Schema
Good candidates include product pages with a genuine buyer-question section, support and help-center articles, service pages that answer common client questions, and how-to guides that end with a Q&A recap. If you’re also building out a LocalBusiness or Product schema for the same page, FAQ schema can be added alongside it — a single page is allowed to carry more than one schema type as long as each accurately describes real content on that page.
Frequently Asked Questions
Does FAQ schema still show a rich result in Google?
No. Google stopped showing FAQ rich results for all sites, including government and health sites, on 7 May 2026, and removed FAQ support from the Rich Results Test in June 2026. The markup is still valid schema.org, so keep it where it mirrors a real Q&A section; its value now is clean structure for AI answer engines and a better page for visitors.
How many questions should I include?
Include only the questions your page genuinely answers — two to six well-answered questions work better than a padded list of ten thin ones.
Can I use FAQ schema on a product or service page?
Yes, as long as the page has a real, visible Q&A section that matches the schema.
Is FAQ schema free to add?
Yes. The free Schema Markup Generator builds the code with no signup, and pasting it into your page costs nothing.
