FAQ Schema in 2026: Does It Still Help SEO?

What is FAQ schema?

FAQ schema is code that labels the question and answer pairs on a page so search engines and AI tools can read them clearly. It is usually written as JSON-LD, a small block of structured data that sits inside a <script> tag in your page. It does not change anything a visitor sees. It just tells machines, in plain terms, "this is a question, and this is its answer."

It is one type of schema among many. If you want the full picture of how structured data works, read our guide to schema markup. FAQ schema is just the slice that handles question and answer content. It uses the FAQPage type from Schema.org, and inside it you list each Question with its acceptedAnswer.

Think of it as a label, not a billboard. It works behind the scenes. A good FAQ section on the page is what people read. The schema is the machine-readable copy of that same content. The two should always match. For where this fits in the bigger on-page picture, our on-page SEO checklist walks through the rest.

What changed with FAQ rich results?

Here is the honest core. FAQ schema used to earn a visible FAQ dropdown in Google Search, then Google took that reward away in two steps. The code still works. The Google bonus does not.

Before 2023, almost any page could add FAQ schema and win an expandable FAQ block under its search result. It got over-used fast. People stuffed marketing copy into fake "questions" to grab more space on the page. So in August 2023, Google limited FAQ rich results to well known government and health sites. The effect was instant and large. A Portent study of 31,316 keywords found the share of SERPs showing FAQs dropped from 53.94% to 17.04% between February and August 2023.

Then came the final step. Google fully deprecated FAQ rich results, and they stopped appearing in Google Search for everyone from 7 May 2026. Even the gov and health exception is gone. The FAQPage type is still a valid Schema.org type, and Google confirms that unused structured data does not cause problems for Search. So nothing breaks if you keep it. You just will not see a dropdown.

If you want to track how your pages actually show up over time, our Search Console guide shows you where to look. Just do not expect a FAQ rich result line in there anymore.

Is FAQ schema still worth adding?

Honest verdict: not for a Google rich result, because that is gone, but yes for a few quieter reasons. FAQ schema is no longer a quick win. It is now a clarity and future-proofing choice.

The first reason is plain structure. Marking up your questions and answers forces you to write real, clean Q&A content. That is good for readers, and good for machines that parse your page. The second reason is AI and answer visibility. More search journeys end inside an answer box, not on your site. Google searches ended without a click 68.01% of the time in a recent US study, and AI Overviews now appear on more than 20% of Google searches. We cannot promise FAQ schema lifts your AI visibility by any exact amount, and you should be wary of anyone who claims a number. But structured, machine-readable answers give your content a cleaner shape for tools that lift and reuse text.

The third reason is other engines and the future. Not every search tool follows Google's choices. Valid FAQPage markup stays readable elsewhere, and it costs you almost nothing to keep. If your SEO setup already adds it, leave it. If you are building a strategy from scratch, our SEO service can help you decide where structured data actually earns its place.

How to add FAQ schema the right way

FAQ schema is simple to add if you do it in the right order. Start with the content, not the code.

First, write real questions and answers that visitors can see on the page. The schema must describe content that is actually there. Do not invent hidden questions just to fill the markup. Second, add a JSON-LD FAQPage block inside a <script type="application/ld+json"> tag. Inside it, each entry has a Question with a "name" and an acceptedAnswer with "text". The answer text in the code must match the visible answer word for word.

Third, follow the rules. Use FAQPage only on genuine FAQ pages. Google says FAQPage markup should never be used for advertising or promotional content. Do not stuff keywords. Do not turn sales copy into fake questions. Fourth, check your JSON syntax is valid, with balanced braces and quotes. Note that Google is removing FAQ support from the Rich Results Test, so a generic JSON-LD validator is the safer tool now.

Most modern content systems and SEO plugins can add this for you automatically when you build a real FAQ section. If yours does, you usually do not need to touch raw code at all. You just write the Q&A, and the tool wraps it in valid markup.

When FAQ schema is worth it (and when to skip it)

FAQ schema is worth it when you have a genuine FAQ page, you care about being quoted in AI answers, and your CMS can add the markup with little effort. In those cases it is a small, low-risk improvement to how machines read your content.

Skip the stress in two cases. One, do not add FAQ schema hoping to win back the old Google dropdown. It is gone, and no markup brings it back. Two, do not expect FAQ schema to lift your rankings on its own. It is a labelling tool, not a ranking signal. If your pages are not showing up, the fix is usually content, links, and the basics, not schema.

And please do not rip out FAQ schema you already have. It does no harm. Google ignores unused structured data, so leaving it costs you nothing and keeps your content tidy for the next engine that does read it. Spend the time you saved on writing better answers instead. If you want a second pair of eyes on your whole setup, get in touch with us and we will tell you what is worth doing and what is not.