FAQ Schema Generator — build valid FAQPage JSON-LD
Paste your questions and answers. We'll generate the schema.org FAQPage JSON-LD you can drop into the <head> of your page. Free, no signup, no quota.
Your questions
Add the question-and-answer pairs that should appear in your FAQ. We'll build the JSON-LD as you type.
Question 1
Question 2
Output
2 valid questions
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your return policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We accept returns within 30 days of purchase for a full refund. Items must be unused and in their original packaging."
}
},
{
"@type": "Question",
"name": "How long does shipping take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Standard shipping arrives in 3-5 business days within the US. Express shipping is 1-2 business days."
}
}
]
}
</script>Paste the <script> block into the <head> of the page whose visible FAQ matches these questions. Google requires the schema content to match what users see.
Want this to stay fresh automatically?
faqlogic re-orders your FAQ by what visitors actually click and keeps the schema in sync as questions change. The first scan is free.
Try faqlogic freeWhat FAQ schema actually does for you
FAQ schema (formally schema.org's FAQPage type) tells search engines your page contains a structured list of questions and answers. You write it as a JSON-LD script tag in the <head> of your page. Google, Bing, and the assistant systems built on them parse it to understand your content faster and more accurately than they can from your HTML alone.
In 2023, Google narrowed the conditions under which FAQ rich results appear in the blue links — they're now reserved mostly for well-known authoritative sites. That led some people to declare FAQ schema dead. It isn't. The schema still feeds People Also Ask, AI Overviews, voice assistant answers, other search engines, and gives Google a clean structural signal even when no rich snippet shows. It's low effort, high upside, and the bar for "correctly formed" is publicly documented.
The hard part isn't the JSON — it's keeping the schema in sync with your visible FAQ as your content changes. Google explicitly requires that the schema content match what users see on the page. If you add a question on the page but forget to update the schema, you stop earning the signal. If you change wording in the schema but not the page, you risk a manual action.
How to use this tool
- Add each question and its answer in the form above. The output updates live as you type.
- Copy the <script> block (or just the JSON) using the button on the right.
- Paste it into the <head> of the page that has the matching visible FAQ.
- Validate with Google's Rich Results Test — or paste the URL into our FAQ Schema Validator to check the live page.
Frequently asked questions
What is FAQ schema (FAQPage JSON-LD)?
FAQ schema is a small block of structured data — written in JSON-LD format and based on schema.org's FAQPage type — that tells search engines your page contains a list of questions and answers. It lets Google understand the Q&A structure rather than guessing from your HTML.
Does FAQ schema still show as a Google rich result?
Google scaled back FAQ rich results in 2023 — they now mostly appear for well-known authoritative sites. But FAQ schema is still widely used for AI Overviews, People Also Ask, voice assistants, and is read by other search engines. It also helps Google understand your page's content even when no rich snippet is shown.
Where do I paste the generated code?
Inside the <head> of the page whose visible FAQ matches these questions. The schema content must match what users actually see on the page — Google explicitly requires this and may penalize mismatches.
Can I include HTML formatting in answers?
Yes — the acceptedAnswer.text field accepts a limited set of HTML (paragraphs, lists, basic formatting). For the simplest, safest output, plain text works everywhere and won't trip schema validators.
How many questions should I include?
There's no hard limit, but practical sweet spot is 5-15. Below that, you don't cover enough intent; above that, the page becomes a wall of text and the most important answers get diluted. Order by what your visitors actually need first.
Will this schema match the rich-results test?
The output follows schema.org and Google's documented requirements: FAQPage type, mainEntity array, Question + acceptedAnswer.text on each entry. Paste the result into Google's Rich Results Test to confirm.
Stop hand-updating your FAQ schema every time content changes
faqlogic keeps the schema in sync with your live FAQ, re-orders questions by what visitors actually click, and shows you what people are searching for that you don't yet answer. The first scan is free.