FAQ schema is structured data (a type of schema.org markup) that labels a page's question-and-answer content so search engines can read it unambiguously. Its headline benefit, FAQ rich results in Google, is being retired: Google announced in 2026 that FAQ rich results would no longer show in Search. FAQ schema is still worth adding because it helps search engines and AI systems parse your content, other engines still process it, and it costs almost nothing to implement. But it is no longer a rich-result tactic. This guide covers what changed, whether to keep it, and how to implement it correctly.
What Is FAQ Schema?
FAQ schema (FAQPage structured data) is markup you add to a page that contains a list of frequently asked questions and their answers. It tells a search engine, explicitly, "this block is a question, and this block is its answer," rather than leaving the engine to infer it from your HTML.
It is written in JSON-LD, a small block of code that sits in the page's source. You do not see it on the page. Search engines and AI systems read it directly.
What Changed: Google Retired FAQ Rich Results
For years, the payoff for FAQ schema was the FAQ rich result, your questions appearing as an expandable accordion directly in the search listing. That payoff is gone.
Google announced in 2026 that FAQ rich results would no longer appear in Search. The FAQ search appearance, the rich result report in Search Console, and Rich Results Test support are being removed through mid-2026, with API support ending in August 2026.
Google's own guidance on what to do is relaxed: "You can remove the FAQ structured data from your code, if you want but you can also leave it." There is no penalty for keeping it. Other search engines may still process it.
Google's official position (May 2026): Google's AI optimization guide states structured data "isn't required for generative AI search, and there's no special schema.org markup you need to add." My take: that is true for AI features specifically, but schema still earns rich results in traditional Search where they still exist, helps every current and future search engine understand your entities, takes seconds to generate now with ChatGPT, Claude, or Gemini, and ships built into most modern CMS platforms. It costs almost nothing and still does real work. For FAQ schema specifically, the rich result is gone, so treat it as low-cost content-clarity insurance, not a visibility tactic.
Should You Still Use FAQ Schema?
Yes, with adjusted expectations. The reasons to keep or add it in 2026:
- It clarifies your content for machines. Search engines and AI systems both parse structured data. Even without a rich result, labelled Q&A content is easier for them to extract accurately.
- Other engines still use it. Google retiring the FAQ rich result does not bind Bing or other engines.
- It is effectively free. Modern CMS platforms and SEO plugins generate it automatically. An AI tool can write the JSON-LD in seconds. There is no real cost to keeping it.
- It does no harm. Google has confirmed there is no penalty for leaving valid FAQ markup in place.
What changed is the framing. Do not add FAQ schema expecting a visibility boost. Add it, or keep it, as a small content-hygiene measure.
FAQ Schema vs Q&A Schema
Two question-based schema types exist, and they are not interchangeable:
- FAQPage schema is for pages where you, the site owner, publish a fixed set of questions and their answers. A support page or a guide's FAQ section.
- QAPage schema is for community-driven pages where users post a question and others submit competing answers. A forum thread.
Use FAQPage for your own published Q&A. Use QAPage only for genuine user-generated question pages. Mislabelling them is a common error.
Google's FAQ Schema Guidelines
| Aspect | Guideline |
|---|---|
| When to use | Only when the page genuinely lists questions with site-authored answers. |
| Valid use | Your own FAQ pages, product support pages with predefined Q&A. |
| Invalid use | Forum pages with user-submitted answers, or using it purely for advertising. |
| Content match | The question and answer in the schema must match the visible content on the page exactly. |
How to Add FAQ Schema (4 Steps)
- Generate the schema. Use JSON-LD, which Google prefers over Microdata. An SEO plugin, a CMS feature, or an AI assistant can produce the FAQPage JSON-LD from your visible Q&A in seconds.
- Validate it. Run it through the Schema Markup Validator at schema.org. (Google's Rich Results Test no longer reports FAQ results, since the rich result is retired.) Confirm the JSON-LD is syntactically valid and the question and answer text matches the page.
- Add it to the page. Place the JSON-LD block in the page source. Most CMS platforms and SEO plugins handle this automatically once you mark up the FAQ section.
- Let it get crawled. Submit the page in Google Search Console if you want it re-crawled sooner. There is no rich result to wait for now, but the structured data still gets read.
Best Practices for FAQ Schema
- One clear answer per question. If a question needs a multi-step process, that is HowTo content, not an FAQ.
- No duplicate FAQs across pages. Repeating the same Q&A block site-wide is poor for users and adds nothing for engines.
- Match schema to visible content. The markup must reflect what a user actually sees on the page. Hidden or mismatched FAQ content violates Google's guidelines.
- Write the answers for humans first. The schema is a label on good content. It cannot rescue thin or evasive answers.
FAQ
Does FAQ schema still work in 2026?
FAQ schema still functions as structured data that search engines and AI systems read, but its rich result in Google Search has been retired. It no longer produces the expandable accordion in search listings. It remains useful for content clarity and is still processed by other engines.
Should I remove FAQ schema from my site?
No need to. Google has confirmed there is no penalty for leaving valid FAQ markup in place, and other search engines still process it. Removing it is optional and low priority.
Does FAQ schema help with AI search citation?
Not directly. Google states structured data is not required for generative AI search. Clear, well-written FAQ content can be cited by AI engines, but the schema label itself is not the lever.
What is the difference between FAQ schema and HowTo schema?
FAQ schema is for questions with a single direct answer. HowTo schema is for step-by-step processes. If your answer is a sequence of steps, use HowTo.
Is JSON-LD or Microdata better for FAQ schema?
JSON-LD. Google explicitly prefers it, it is easier to maintain because it sits in one block rather than being woven through your HTML, and most tools generate it by default.
Related Reading
- Structured Data for AI Search Engines
- How to Earn Google Featured Snippets
- Header Tags for SEO: H1-H6 Best Practices
- On-Page SEO: A Beginner's Guide
Sources & Further Reading
Soaring Above Search
Weekly AI search insights from the front line. One newsletter. Six sections. Everything that actually moved this week, with a practitioner's take.
Chief of Staff at StudioHawk, Australia's largest dedicated SEO agency. Specialising in AI search visibility, technical SEO, and organic growth strategy. Leading a team of 120+ across Melbourne, Sydney, London, and the US. Book a free consultation →