FAQ Schema Generator
Turn a list of questions and answers into valid FAQPage JSON-LD, ready to paste.
Nothing you type here is uploaded, stored or sent anywhere. It all runs in your browser.
Before you paste this
- The Q&As must be visible on the page. Markup describing content a visitor cannot see is a structured data violation, and it is the most common way sites lose rich results.
- FAQ rich results are limited now. Since 2023 Google shows them mainly for government and health sites. The markup still helps machines understand the page — just do not expect the SERP real estate.
- One FAQPage per page. Do not mark up the same question twice.
- Answers can contain basic HTML — links, lists, bold. Plain text is safer.
Questions people ask
If Google barely shows FAQ rich results any more, why add the markup?
Because the rich result was never the main point and is now the least of it. The markup states plainly which text on the page is a question and which is its answer, which is what every answer engine reading your page is trying to work out. The cost is a few lines in the head. Just size the expectation correctly: this is machine readability, not SERP real estate.
Can I mark up questions that are hidden inside an accordion?
Yes, as long as the answer is in the HTML when the page loads and the click only expands it. That is the normal accordion and it is explicitly fine. What is not fine is fetching the answer over the network when the user clicks — then the markup describes text the page did not serve.
FAQPage or QAPage?
FAQPage is for questions you wrote and answered yourself. QAPage is for a single user-submitted question with answers from other people, which is a forum, not a support page. Using FAQPage on community content, or QAPage on your own, is the most common type mismatch in this area.
Can the same FAQ block go on every page of the site?
You can, and it buys nothing. Repeating five identical questions across two hundred pages tells Google two hundred pages are about the same five things. Put the block where the questions belong — the service page, the pricing page — and write different ones for each.
Is there a length limit on an answer?
Google allows a lot of characters and the practical limit is different: an answer under about thirty words usually means the question was not worth asking. Write the answer you would give on a call, then trim the throat-clearing at the start.
Guides for this tool
Related tools
Structured data done, still not ranking?
Schema helps machines read a page. Links are what make it compete.