FAQ schema is one of the simplest types of structured data you can add to a webpage. You write your questions and answers in JSON-LD format, paste the code into your HTML, and search engines can read them directly.
But there is an important caveat. In August 2023, Google significantly reduced FAQ rich results visibility. If you are still following advice from 2022 or earlier, you are working with outdated information.
This guide covers what FAQ schema is, what changed, why it still has value, and how to add it correctly. You will also get copy-paste code you can use right away.
What Is FAQ Schema?
FAQ schema (also called FAQPage schema) is a type of structured data that tells search engines "this page contains a list of questions and answers." It uses the FAQPage and Question types from Schema.org.
The most common way to implement it is with JSON-LD, a block of JavaScript notation you place in your page's <head> or <body>. Google, Bing, and other search engines parse it to understand the content without relying on visual layout alone.
Before the 2023 changes, FAQ schema could generate expandable rich results directly in Google Search. A page with five FAQ items could take up a large portion of the SERP, pushing competitors down. That made it extremely popular, and, inevitably, heavily abused.
How it differs from HowTo and Q&A schema
- FAQPage: One page with multiple questions and answers, all written by the site owner.
- QAPage: A single question with community-submitted answers (think Stack Overflow).
- HowTo: Step-by-step instructions to complete a task.
If your page has a list of common questions that your team wrote answers to, FAQPage is the correct type. If users are submitting answers, use QAPage instead.
The 2023 Google Change (and What It Means Now)
In August 2023, Google announced that FAQ rich results would only be shown for "well-known, authoritative government and health websites." You can find the current requirements in Google's FAQ structured data documentation. For everyone else, FAQ schema stopped generating the expandable dropdown in search results.
This was a big deal. Entire SEO strategies had been built around FAQ rich results. Sites were adding FAQ schema to every page, sometimes with questions that barely related to the content, just to grab extra SERP real estate.
Let's be honest: FAQ schema is not as powerful for SERP real estate as it was in 2022, but it still matters for AI engines. Here is why that distinction is important.
If you are adding FAQ schema purely to get rich results in Google, you will likely be disappointed. The rich results are gone for most sites. But that is only one reason to use structured data.
Why FAQ Schema Still Matters in 2026
Even without the visual SERP benefit, FAQ schema serves several practical purposes.
1. AI search engines use structured data
ChatGPT, Perplexity, Google's AI Overviews, and other AI-powered search tools pull from structured data when generating answers. FAQ schema makes your questions and answers machine-readable, which increases the chance of being cited in AI-generated responses. If you are serious about GEO optimization, structured data is part of the foundation.
2. It clarifies content intent for crawlers
Structured data removes ambiguity. When a crawler hits your page, it does not have to guess whether a block of text is a question-and-answer pair or just regular content. The schema makes the relationship explicit. This is especially useful for pages where the FAQ section sits below the main content and might otherwise be treated as secondary.
3. Bing still shows FAQ rich results
While Google restricted FAQ rich results, Bing did not follow suit across the board. Bing users represent a meaningful audience segment, especially in enterprise and desktop environments. Your FAQ schema can still earn visual treatment there.
4. Voice assistants pull from FAQ data
When someone asks a voice assistant a question that matches your FAQ, the structured data makes it easier for the assistant to find and read your answer. This is a small but growing channel, and it costs nothing extra to support it.
The takeaway: structured data is not just about rich results. It is about making your content understandable by machines, and that is increasingly how people find information. For a deeper look at how to optimize your site for ChatGPT and Perplexity, see our dedicated guide.
How to Add FAQ Schema: Step-by-Step
Here is the process to add FAQ schema to any page. The approach works whether you are editing raw HTML, using a CMS, or working with a static site generator.
Step 1: Identify your questions and answers
Only mark up questions and answers that are actually visible on the page. Google's guidelines are clear: the content in your schema must match the content users can see. Do not create "hidden" FAQs that only exist in the structured data.
Good FAQ candidates include:
- Questions customers actually ask your support team.
- Questions you see in Google's "People Also Ask" boxes.
- Questions from keyword research tools that match the page topic.
Step 2: Write the JSON-LD code
Here is a complete, copy-paste template. Replace the questions and answers with your own content.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQ schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQ schema is structured data markup that identifies question-and-answer content on a webpage. It uses the FAQPage type from Schema.org and is typically implemented in JSON-LD format."
}
},
{
"@type": "Question",
"name": "How do I add FAQ schema to my site?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add a script tag with type application/ld+json to your page's head or body. Inside it, define a FAQPage object with a mainEntity array containing your Question and Answer objects."
}
},
{
"@type": "Question",
"name": "Does FAQ schema still work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQ schema still works for helping search engines and AI tools understand your content. However, Google reduced FAQ rich results visibility in August 2023, limiting the expandable dropdown to authoritative government and health sites."
}
}
]
}
</script>Step 3: Place the code on your page
Paste the <script> block anywhere in your HTML. The recommended locations are:
- In the
<head>: Cleanest approach, keeps structured data separate from visible content. - At the end of
<body>: Works equally well, sometimes easier to manage in CMS environments.
Both locations are valid. Google processes them identically.
Step 4: Match the visible content
This step is critical. Every question and answer in your JSON-LD must appear on the page in a format users can read. The wording does not have to be identical, but the substance must match. If your schema says "Our product costs $50" but the page says "$75," that is a problem.
Use an AI SEO audit tool to verify that your structured data matches your visible content. OwnVector checks for structured data mismatches automatically across all 87 audit checks.
Common Mistakes That Waste Your Effort
FAQ schema is simple to implement, which means the mistakes tend to be strategic rather than technical.
Marking up non-FAQ content
The most common mistake is using FAQ schema on content that is not actually a set of frequently asked questions. Product descriptions, marketing copy, and feature lists are not FAQs. If you are turning "Why choose our product?" into a "question," you are doing it wrong.
Adding FAQ schema to every page
Not every page needs FAQ schema. Your homepage, your contact page, your about page. They probably do not have genuine FAQs. Add the markup only where it makes sense, and only where you have real questions with substantive answers.
Duplicate questions across pages
If the same FAQ appears on five different pages with the same schema, you are creating confusion for search engines. Pick the best page for each question and mark it up there. This is the same principle behind choosing the right structured data type for each page.
Thin answers
An answer that says "Yes" or "Contact us for details" provides no value. Your FAQ answers should actually answer the question in enough detail that a reader (or an AI) finds it useful. Two to four sentences is usually the right range.
Using deprecated markup formats
Microdata and RDFa still technically work, but JSON-LD is Google's recommended format and the standard that all major search engines and AI tools prefer. If you are still using microdata for FAQs, switch to JSON-LD.
Testing and Validating Your FAQ Markup
After adding FAQ schema to your page, test it before publishing. Here are the tools to use.
Google Rich Results Test
Go to search.google.com/test/rich-results and enter your URL (or paste your code). The tool will tell you whether your FAQ markup is valid and eligible for rich results. Remember, "eligible" does not mean "will show" for most sites post-2023.
Schema Markup Validator
The Schema.org validator checks your markup against the full Schema.org specification, not just Google's subset. This is useful for catching issues that might affect Bing, AI search tools, or other consumers of your structured data.
Google Search Console
After your page is indexed, check the "Enhancements" section in Search Console. If Google detects FAQ markup, it will appear here along with any errors or warnings.
Run an automated audit
Manual testing works for individual pages, but if you are managing FAQ schema across a larger site, automated audits save significant time. OwnVector scans for structured data issues as part of its 87-point audit, flagging invalid markup, missing required fields, and mismatches between schema and visible content.
FAQ
Does FAQ schema still work after the 2023 Google update?
Yes, but with reduced visibility. Google now only shows FAQ rich results for well-known government and health authority websites. For most sites, FAQ schema no longer triggers the expandable dropdown in search results. However, the structured data still helps Google understand your content, and AI search engines like ChatGPT and Perplexity use it to extract answers.
Can FAQ schema hurt my SEO?
FAQ schema itself will not hurt your SEO, but misusing it can. If you mark up content that is not actually in a question-and-answer format, or if you use it for promotional text instead of genuine FAQs, Google may issue a manual action. The key rule: only mark up real questions and answers that are visible on the page.
How many FAQ items should I add per page?
Google does not set an official limit, but 3 to 10 FAQ items per page is a practical range. Too few and you are not providing enough value. Too many and you risk diluting the page focus. Pick the questions your users actually ask, not questions you invented to stuff keywords.
