FAQ schema generator
Generate FAQPage markup from your visible questions and answers, or check an existing JSON object.
Your generated markup
1 question ready
1 complete pair. Markup is ready to copy.
FAQPage JSON-LD
Using the tool
Paste one FAQPage JSON object without script tags. This checker does not support arrays, @graph or custom contexts. It checks up to 20 pairs.
Each question allows 1,000 characters and each answer 10,000. Your entries stay in this browser page and are cleared when you reload.
This check is separate from the generator. Pasted JSON does not replace your questions or the output.
Copy includes the script tags. The download is an HTML snippet with the same markup. You can also select the output and copy it yourself.
The output uses your exact question and answer text. Confirm that it matches the destination page before adding it.
From visible answers to JSON-LD
FAQ schema describes the questions and answers on a page in a machine-readable format. JSON-LD means JavaScript Object Notation for Linked Data.
In the example, “Can I return it?” becomes the Question’s name. “Read our returns policy.” becomes the acceptedAnswer’s text, inside an Answer object. The FAQPage holds that pair in its mainEntity array.
The generator adds the field names and structure from Schema.org’s FAQPage definition. It preserves what you enter, including line breaks and quotation marks. It does not invent a return window or turn the answer into a promise that every item is returnable.
Copy the visible answer text, including any conditions. HTML entered in an answer stays text in the output preview. Less-than signs are escaped in the JSON so a script-closing string cannot end the surrounding script element.
FAQ schema checker and validator
The FAQ schema checker checks JSON syntax and a defined set of FAQ fields. A syntax error means the pasted text cannot be parsed as JSON. A missing answer means a question has no usable acceptedAnswer text.
Duplicate detection is an editing rule used here. Questions that differ only in letter case or spacing count as the same question. Resolve repeated questions before exporting. Schema.org does not set this duplicate rule.
This validator accepts one FAQPage object with a Schema.org URL as its context, a mainEntity array and one Answer per Question. Arrays of objects, @graph documents and custom contexts are outside these checks. Additional properties are not validated.
A passing result covers those fields only. It does not inspect your published page, resolve linked data or certify eligibility for a search feature. Fix any reported field, then compare the completed output with the visible page.
Where the markup belongs
Add the generated script to the HTML of the page that displays those questions and answers. The markup and visible content must agree. When you change an answer, update both versions.
Google no longer shows FAQ rich results in Search, as recorded in its Search documentation updates. Generating FAQPage markup does not promise rankings or citations in AI answers.
Write the visible content first with the guide to building an FAQ page. If the same answers also support a shopping agent, keep their source policies in an AI knowledge base.
Use your site’s HTML or structured-data editor for the snippet. If a plugin already publishes FAQPage data for that page, update that existing entry instead of adding a second copy.
Compare FAQPage output with livekod
Livekod.com describes its free FAQ schema generator as a tool with no signup. Its published workflow is to enter the visible questions and answers, then copy the generated JSON-LD to the same page.
This generator is a separate tool. Use the same example in either generator: “Can I return it?” with the answer “Read our returns policy.” Compare the resulting question and answer text before adding any markup.
Here, the result is a FAQPage object with a mainEntity array. Its Question has name set to “Can I return it?” and one acceptedAnswer of type Answer. That Answer’s text is “Read our returns policy.”
Indentation and property order can differ without changing these values. A Unicode escape such as \u003c decodes to a less-than sign. Quotation marks and line breaks need valid JSON escapes. An unescaped closing script tag can end an HTML snippet early.
To test an exported snippet, copy the JSON between its script tags into the checker above. A missing answer produces a field error here, and a repeated question produces a duplicate error. These messages describe this checker’s rules.
This page’s Copy markup button and HTML download contain the same script-wrapped JSON-LD. Compare decoded values, then confirm every exported answer still matches the visible page. Different button labels or file names do not change the FAQPage data.