FAQ schema: how and when to use it
FAQ schema had a rough couple of years. Google pulled back the rich results that once made it a rankings favorite, and plenty of people wrote it off entirely. That was a mistake. Used in the right spots, FAQ schema still helps machines understand your page, and machines are doing far more of the reading now.
FAQ schema is structured data that labels a list of questions and answers on a page so search engines and AI assistants can read them without guessing. Use it when a page genuinely answers common questions, keep the visible text matching the markup exactly, and avoid it on pages that only bolt on questions to chase a rich result.
What FAQ schema is
FAQ schema is a small block of JSON-LD code that tells search engines a page contains a list of questions and their answers. It uses the FAQPage type, and inside it each entry is a Question with an acceptedAnswer. You place it in the page head or body, and it describes content the visitor can already see. It does not change how your page looks to humans. It changes how clearly a crawler, or an AI assistant, can pull the question and answer apart. This is one of the simpler pieces of the wider structured data toolkit.
When FAQ schema still helps
FAQ schema still helps most on pages that already answer real, recurring questions. Even though Google now shows FAQ rich results mainly for government and health sites, the markup keeps working behind the scenes. It gives answer engines a clean, labeled question and answer pair to quote, which matters for answer engine optimization and for getting cited by ChatGPT, Gemini and Perplexity. A clearly structured answer is easier for any system to lift, whether that system is a snippet box or a chatbot.
When to skip FAQ schema
Skip FAQ schema when the questions are filler. If you are inventing questions nobody asks just to add markup, Google may see it as manipulative and ignore it, or worse. Do not repeat the same FAQ block across dozens of pages, and do not mark up content that is not actually visible on the page, which breaks Google's guidelines. On a thin page, the fix is better content, not more schema. Adding People Also Ask answers the right way beats padding a weak page with fake questions.
How to write the markup
Write the markup as JSON-LD and keep it honest. Each entry needs a Question with a name field holding the exact question text, and an acceptedAnswer with a text field holding the answer. The answer text should match what a reader sees on the page, word for word where possible. Keep answers to a few clear sentences. Once the code is in place, run it through Google's Rich Results Test to confirm it parses. If you are on WordPress, most SEO plugins can generate valid FAQ blocks for you, so you rarely need to hand-write it.
A quick word on where the questions come from. The best FAQ blocks answer the questions people genuinely search, not the ones a marketing team wishes they would ask. Pull them from your support inbox, sales calls, and the People Also Ask box for your topic. That way the markup reflects real demand, the answers stay useful to visitors, and the same block does double duty by helping you rank for those questions in normal search as well.
FAQ schema and AI answers
FAQ schema earns most of its keep now by feeding AI answers. When an assistant builds a response, it looks for content it can trust and quote quickly, and a labeled question and answer pair is close to ideal. The same block can support Google AI Overviews and voice results at the same time. Think of the markup as insurance: it costs almost nothing, and it makes your best answers legible to every system that reads the web. Our free AEO and GEO checklist covers where schema fits into the bigger picture.
Common mistakes to avoid
The most common mistake is mismatched content, where the markup says one thing and the page shows another. The second is overuse, spraying FAQ schema on pages that do not warrant it. The third is neglect, leaving old answers in the markup after you have changed the visible page. Fix these and FAQ schema quietly does its job. You can pressure test your setup with a free audit to catch mismatches before they cost you.
FAQ schema is not the ranking cheat code it once looked like, and that is fine. Its real value today is clarity. Mark up questions people truly ask, keep the code and the page in sync, and you hand every search and answer engine a clean answer to quote.
Frequently asked questions
Does FAQ schema still help SEO in 2026?
Yes, though its role has changed. Google now shows FAQ rich results mainly for health and government sites, so the visible star ratings are gone for most. The markup still helps search engines and AI assistants read your questions cleanly, which supports answer engine and AI-citation visibility.
Where should I put FAQ schema on my page?
Add the JSON-LD to the page that actually contains the questions and answers, either in the head or body. The markup must describe content a visitor can see. Never mark up hidden or invented questions, since that breaks Google's guidelines and can get the structured data ignored or penalized.
Can I use FAQ schema on every page?
You can, but you should not. Only use FAQ schema where a page genuinely answers common questions, and avoid repeating the same block across many pages. Forcing questions onto pages just to add markup looks manipulative. If a page has no real FAQs, better content serves you more than extra schema.
How do I test if my FAQ schema works?
Paste the page URL or code into Google's Rich Results Test, which confirms whether the FAQPage markup is valid and readable. Fix any errors it flags, then recheck. Also confirm the questions and answers in the markup match the visible text on the page word for word.
Does FAQ schema help with AI search and ChatGPT?
It can. A clearly labeled question and answer pair is easy for any assistant to quote, so FAQ schema supports getting picked up in AI Overviews and cited by chatbots. It is not required, but it removes ambiguity about what your answers are, which helps machines use them.
Want this done for your site?
Run a free audit and see exactly what to fix for Google and AI search.