Free structured data tool
FAQ Schema Generator
Add your questions and answers, preview the Schema.org FAQPage JSON-LD, and copy it — as raw JSON-LD or a ready-to-paste script tag. Everything runs in your browser.
// Add at least one complete question and answer to generate FAQPage JSON-LD.
No complete question-and-answer pair yet.
Next step
Paste the markup into the <head> (or body) of the page whose questions and answers these are, then check it with the AI Schema Markup Checker.
FAQPage is a valid Schema.org type, but Google stopped showing FAQ rich results in Search in 2026. Generating this markup does not create a rich result, does not change rankings, and does not guarantee that any AI system will cite or recommend the page. Only mark up questions and answers that are actually visible on the page.
What is FAQ schema?
“FAQ schema” is structured data that uses the Schema.org FAQPage type. Schema.org defines a FAQPage as “a WebPage presenting one or more ‘Frequently asked questions’.” You add it as JSON-LD — a small block of JSON in a script tag — that lists the questions on the page and the answer you give for each one.
It describes content you have already written and published. It does not create content, and it is not a substitute for a real FAQ section that visitors can read.
FAQPage JSON-LD structure
- FAQPage — The top-level type. It marks the page as one that presents a list of frequently asked questions the site itself answers.
- mainEntity — An array of Question objects — one per FAQ, in the order you want them read.
- Question — One entry. `name` holds the question text exactly as it appears on the page.
- acceptedAnswer — The answer to that Question, as a single Answer object (FAQPage expects one accepted answer per question).
- Answer — `text` holds the answer. It may contain limited HTML (for example <p>, <br>, <a>, lists), but it should match the visible answer.
A minimal FAQPage with one question:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your return policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "You can return any item within 30 days for a full refund."
}
}
]
}The Question holds what the user asks; the acceptedAnswer holds your reply. FAQPage expects one accepted answer per question — if a page has many user-submitted answers, that is a QAPage, not a FAQPage.
How and where to add FAQ schema
1Write the Q&A on the page first
The questions and answers must be visible to visitors on that page. Markup for content that isn't on the page is against Google's structured data guidelines.
2Generate the JSON-LD
Enter each question and its answer above. Empty rows and rows missing a question or an answer are left out.
3Copy it as a script tag
Use "Copy <script> tag" to get the JSON-LD already wrapped in a script element with type application/ld+json.
4Paste it into the page's HTML
Put the script tag in the <head>, or anywhere in the <body>, of that specific page. One FAQPage block per page is enough.
5Validate it
Run the page through the AI Schema Markup Checker (or Schema.org's validator) to confirm the JSON parses and the types are right.
FAQPage vs QAPage
FAQPage
“A WebPage presenting one or more ‘Frequently asked questions’.” The site provides both the questions and the answers. There is one accepted answer per question. Use it for a normal FAQ section you wrote.
QAPage
“A WebPage focussed on a specific Question and its Answer(s), e.g. in a question answering site”. Built around a single user-submitted question with user-submitted answers — a forum or community thread where people can post and vote on answers.
The deciding question: can visitors submit their own answers? If no, it is a FAQPage. If yes, it is a QAPage. Using the wrong one misrepresents the page.
Does FAQ schema improve SEO or get a rich result?
Be careful with the older advice on this. The current situation:
- Google's FAQ rich result (the expandable Q&A shown under a search listing) was restricted in 2023 to well-known, authoritative government and health websites.
- In 2026 Google went further and stopped showing the FAQ rich result in Search for everyone, and removed the related Search Console report and Rich Results Test support.
- So adding FAQPage markup today does not produce a Google rich result, and it is not a ranking factor you can rely on.
- FAQPage is still a valid Schema.org type. The markup can stay on a page without causing problems, and it can make the page's Q&A structure explicit for other systems that choose to read it.
- It does not guarantee that ChatGPT or any other AI system will read, cite, or recommend the page.
Add FAQ schema because you have a genuine FAQ and want its structure to be machine- readable — not as a growth tactic. After adding it, confirm it is valid with the AI Schema Markup Checker. To check whether the surrounding page is written so an AI answer engine can extract those answers, analyze your content structure for AI search.
Frequently asked questions
What is FAQ schema?
FAQ schema is FAQPage structured data: a machine-readable list of question-and-answer pairs, written as JSON-LD, that describes Q&A content you have already published on a page. It uses the Schema.org FAQPage type, with a Question for each item and an acceptedAnswer for each Question.
How do I create FAQPage JSON-LD?
List your questions and answers, then wrap them in the FAQPage structure: an @context of https://schema.org, an @type of FAQPage, and a mainEntity array where each entry is a Question with a name and an acceptedAnswer that is an Answer with a text value. This tool builds that structure for you from the fields above.
Where should FAQ schema be added?
On the specific page that shows those questions and answers, inside a script tag with type application/ld+json, in the head or body. Add it only to pages that genuinely contain a list of FAQs, and keep the markup in sync with the visible text.
Does FAQ schema improve SEO?
There is no guarantee that it does. Structured data can help search engines and other systems read your Q&A content in a machine-readable way, but it is not a ranking factor you can rely on, and adding it will not by itself move a page up in results.
Why is my FAQ rich result not showing?
Because Google no longer shows FAQ rich results. Google restricted them to well-known, authoritative government and health sites in 2023, and then stopped showing the FAQ rich result in Search for everyone in 2026, removing the related Search Console report and Rich Results Test support. Valid FAQPage markup will not produce a rich result today.
What is the difference between FAQPage and QAPage?
FAQPage is for a page where the site provides both the questions and the answers — a normal FAQ section you wrote. QAPage is for a page built around a single user-submitted question with one or more user-submitted answers, like a community forum thread where people can post and vote on answers. If visitors cannot submit answers, use FAQPage, not QAPage.
Can FAQ schema help AI systems understand my page?
It can make the Q&A structure of a page explicit rather than something a system has to infer from the layout. Whether any particular AI system reads it, and whether it ever cites or recommends the page, is outside your control and is not something this tool or the markup can guarantee.