The Rundown
- FAQ schema is structured data that identifies FAQ content for search engines and helps classify question-and-answer content on a page.
- Google FAQ rich results stopped appearing in Google Search as of May 7, 2026, so FAQ schema should no longer be treated as a way to earn expandable FAQ dropdowns in search results.
- FAQ content can still help users and search visibility by answering common questions, reducing uncertainty, improving page usefulness, and making content easier for AI systems to understand and extract.
- Site owners, SEOs, developers, and content teams should audit existing FAQ schema instead of automatically removing it, keeping it where the content is visible, accurate, useful, and aligned with the page.
Due to a May 2026 update, Google FAQ rich results are no longer appearing in Google Search1. Google also says it will drop the FAQ search appearance, rich result report, and support in the Rich Results Test in June 2026, with Search Console API support for FAQ rich results removed in August 2026. However, that doesn’t mean FAQ schema is something you automatically need to remove or ignore in your marketing strategy. FAQPage remains a valid Schema.org type2, and structured data is still a standardized way to help classify page content, even if this specific Google rich result is no longer a visible search feature.
Table of Contents
What Happened to FAQ Schema in Google Search?
A schema markup is essentially standardized code in the form of structured data. It helps Google understand the meaning of your page, its elements, and how to categorize it for use.
Structured data is an integral part of rich results. By feeding information to Google in a standardized format, you make it easy for the search engine to understand the information on your page and serve it when relevant.
FAQ schema is a specific type of schema markup that tells search engines it’s crawling an FAQ page or FAQ section. FAQs, if you’re not familiar with the term, refer to frequently asked questions. These are standard additions to all kinds of websites, offering users quick answers to common questions.
FAQs can be pages in their own right or simply sections on relevant product and service pages, making it easy for customers to resolve their queries.
Previously, structuring FAQ information in schema format gave pages a chance to appear in Google’s FAQ rich results. These were enhanced search listings displayed in a question-and-answer format, often with multiple expandable questions under a standard search result.
That changed in stages. In August 2023, Google reduced FAQ rich result visibility3 and limited it to well-known, authoritative government and health websites. In May 2026, Google went further and updated its documentation to say FAQ rich results are no longer appearing in Google Search.
This means FAQ schema should no longer be positioned as an easy way to get a larger Google result, more SERP real estate, or a quick organic traffic lift through FAQ dropdowns. That part of the strategy is outdated. The markup can still exist on your site, but it no longer earns visible FAQ rich results in Google Search.
Who Should Care and Why?
Site owners, SEOs, content teams, and developers should care if they have been using FAQ schema as a search visibility tactic, tracking FAQ rich results in Search Console, or relying on FAQ dropdowns as part of their organic CTR strategy.
There are still good reasons to use FAQs on your pages. They help users get quick answers, support clearer page structure, and can address common objections or informational gaps before users leave the page. In the right cases, FAQ structured data can also help classify the content in a consistent format.
The main consideration here is still website speed. You may need to use JavaScript or a plugin to enable this function, which may contribute to slower page load speed. Also, adding FAQs to a page that doesn’t need them may affect user experience.
The bigger change is that FAQ schema is no longer a shortcut to enhanced Google Search visibility. Older benefits like “improve website visibility,” “enhanced search result,” and “more SERP real estate” need to be reframed. They were valid when FAQ rich results were commonly shown, but they are not reliable benefits in May 2026.
FAQ content can still support SEO when the questions are useful, relevant, and aligned with what users actually need to know. It can also support AI search and answer extraction when the content is clear, specific, and easy to parse. But the value now comes from the usefulness and structure of the content, not from a guaranteed Google FAQ rich result.
Need help adapting your SEO strategy?
What Should You Do Now?
Do not automatically remove FAQ schema just because Google FAQ rich results are gone. Google previously stated that unused structured data does not cause problems for Search, but also has no visible effects in Google Search. FAQPage markup is still a valid Schema.org type.
Instead, audit where FAQ schema exists and decide whether it still serves a purpose. Keep it where the FAQ content is visible, useful, and accurate. Remove or simplify it where FAQs were added only to chase rich results, where the questions are thin, or where plugins are adding performance overhead without a real user benefit.
You should also update reporting. If your dashboards, Search Console reviews, or API pulls include FAQ rich result performance, those references need to be phased out. Google says the FAQ search appearance, FAQ rich result report, and Rich Results Test support will be dropped in June 2026, while Search Console API support will be removed in August 2026.
How to Implement FAQ Schema
You can hand code FAQ schema data (it’s fairly easy), or you can use a plugin or a CMS with built-in schema functionality. If you want to add it manually, you can do it using JSON-LD or Microdata.
JSON-LD is a lightweight format that helps you encode linked data. It’s easy to use, scalable, and lets you define or borrow custom schemas. Microdata lets you add extra information to HTML tags. It helps identify the type of data being used and how to handle it.
For reference, Google recommends JSON-LD for structured data where possible, given its ease of implementation. You can simply code it into the header of your content. If you need help coding, you can always enlist the help of SEO schema tools, such as TechnicalSEO’s Schema Markup Generator4.
The Microdata option also offers you a host of free tools to generate your own schema code. Whether you choose JSON-LD or Microdata, it’s a good idea to stick with it throughout the webpage for consistency.
Follow Google’s FAQ Schema Guidelines
It’s worth consulting Google’s list of guidelines for implementing FAQ structured data to ensure your use case is valid. Here is an abbreviated list:
- You cannot add information via structured data that isn’t visible to users on the web page itself.
- You can’t implement FAQ schema on forum pages reserved for eliciting answers to a single question.
- You also can’t implement it on any interactive response pages where users can contribute answers.
- FAQ sections can’t be used for advertising purposes.
- If your FAQ content is repetitive across your site, mark up only one instance of that FAQ for your entire site.
In general, you want to make sure your FAQ content conforms to Google’s content guidelines and Google Search Essentials.
Validate Your FAQ Schema
You can still test structured data to see whether it is valid, but the validation workflow is changing. Google says support for FAQ rich results in the Rich Results Test will be dropped in June 2026. After that, use Schema.org’s validator5 and general structured data checks to confirm that your markup is technically valid, even though it will not produce FAQ rich results in Google Search.
Your data should still be accurate, visible on the page, and consistent with the page content. Invalid or misleading structured data can create quality problems, even if FAQ rich results are no longer the goal.
Include the Right Questions in Your FAQs
There are a number of different use cases for FAQs. However, you’re likely to derive the most benefits when your questions are relevant and add genuine value for the user. There are a few ways to come up with good FAQ questions:
- Keyword Research
Keywords often yield very interesting insights about your target audience. Sometimes, the keywords are structured as outright questions. Performing deep keyword research across your industry can offer up a lot of ideas to use in FAQ sections.
- Google’s People Also Ask Section
Check Google result pages for relevant keywords and you’ll often notice a section where Google lists other questions asked by users with a similar query. This can give you inspiration to craft questions for your web page.
- Customer Surveys
You can never go wrong with customer surveys and interviews. Open-ended questions can often elicit questions in return about your brand or your policies. If these questions turn up often, consider including them in your FAQs.
- Online Forums
Online forums like Quora, Reddit, and Yelp are excellent places to understand more about your users. Even outright complaints can help you craft useful questions that can resolve users’ problems before they lead to dissatisfaction.
Frequently Asked Questions
Need More Traffic? We Can Help!
Despite how daunting it may seem, growing organic traffic is practically guaranteed with a systematic, data-driven approach. Coalition Technologies is one of the nation’s leading SEO companies. We generate 687% more revenue than the average digital agency and our efforts have been widely recognized by clients and peers alike. From implementing structured data where it still makes sense to running multiple service lines for your site, we do everything we can to get you the results you need.
Reach out to us for a free site audit and to schedule a personalized consultation for your business.
Sources:
- https://developers.google.com/search/docs/appearance/structured-data/faqpage ↩︎
- https://schema.org/FAQPage ↩︎
- https://developers.google.com/search/blog/2023/08/howto-faq-changes ↩︎
- https://technicalseo.com/tools/schema-markup-generator/ ↩︎
- https://validator.schema.org/ ↩︎