FAQ schema is structured data, using the schema.org FAQPage type, that marks up a list of questions and answers on a page. You can create it in seconds with the QCK FAQ Schema Generator, but know the context first: since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites, so for most sites the markup no longer produces expandable FAQ snippets in search.
What FAQ schema is
FAQPage markup describes a page that contains a list of questions, each with a single accepted answer. In JSON-LD, the structure looks like this:
{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Do you ship internationally?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, we ship to over 30 countries." } } ] }
Each Question has a name (the question) and an acceptedAnswer with text. FAQPage is for questions answered by the site owner. Pages where users submit questions and multiple answers, like forums, use QAPage instead.
What changed in 2023
For several years, FAQ markup could make a search result expand with clickable questions underneath it. Many sites added it to every page to take up more space in results. In August 2023 Google announced that FAQ rich results would be shown only for well-known, authoritative government and health websites. In the same update, HowTo rich results were limited and later removed entirely.
That means most e-commerce and B2B sites will not see FAQ rich results, no matter how valid their markup is. Google has said there is no harm in leaving existing FAQ markup in place.
Is FAQ schema still worth adding?
For most sites, adding FAQ schema is a low-cost, optional step. Reasons to still use it:
- Machine-readable Q&A. The markup states explicitly which text is a question and which is its answer. That clarity can help any system parsing the page, including AI tools, though no major AI provider has documented relying on FAQPage markup specifically.
- Other search engines and platforms. Google's display policy applies to Google. Other consumers of structured data set their own rules.
- Eligibility if you qualify. Government and health sites can still earn FAQ rich results.
The bigger value is the FAQ content itself. Well-written questions and direct answers are exactly what answer engines quote. Write the FAQ for people first, then add the markup as a bonus. The answer engine optimization checklist explains why direct answers matter.
How to use the QCK FAQ schema generator
- Write your questions and answers on the page first. The markup must match visible content.
- Open the FAQ Schema Generator.
- Enter each question and its answer, using the same wording that appears on the page.
- Add, remove or reorder pairs as needed.
- Generate the FAQPage JSON-LD and copy it.
- Paste it into the page inside a
<script type="application/ld+json">tag. - Validate the live page with a schema validator. See the schema validation guide.
How to write FAQs that are worth marking up
Choose real questions
Pull questions from customer support tickets, sales calls, on-site search, product reviews and the "People also ask" boxes for your topic. Real questions use the words your buyers use.
Answer in the first sentence
Start each answer with the direct answer: "Yes", "No", a number or a definition. Then add one or two sentences of context. Short, complete answers are easier to quote.
Keep answers on the page
Answers can sit inside accordions, but the text must be in the page's HTML and available to users. Do not add markup for questions that are not on the page.
Avoid promotional answers
Google's FAQ guidelines exclude advertising content. An answer should inform, not just sell.
Put FAQs where they help
Product pages benefit from questions about sizing, materials, shipping and care. Service pages benefit from questions about process, timelines and fit. A sitewide FAQ page is fine for policy questions, but page-specific FAQs answer the doubts people have at the moment they are deciding, which also supports conversion.
Common FAQ schema mistakes
| Mistake | Fix |
|---|---|
| Markup questions not visible on the page | Show every marked-up question and answer to users |
| Same FAQ block on every page | Use page-specific questions; FAQPage markup belongs on pages whose questions are about that page |
| Two FAQPage blocks from theme and app | Keep one source of markup |
| HTML or quotes breaking the JSON | Escape quotes and keep answer markup to simple, allowed tags such as links and lists |
| Using FAQPage for user Q&A | Use QAPage for forum-style content |
If you are deciding where FAQ content fits in a broader structured data and AI visibility plan, our AI search optimization and SEO services teams can help prioritize the work that moves results.