Paste your questions and answers as plain text and get valid FAQPage JSON-LD to add to the page. The generator reads Q: and A: lines, or any line ending in a question mark, removes duplicates, and flags questions with no answer.
Start each question with Q: and each answer with A:. A line ending in a question mark also counts as a question.
What FAQ schema is, and what it no longer does
FAQPage schema marks up a list of questions and answers so a machine can read each pair without working out where one ends and the next begins.
Be clear about what to expect. For years the reason to add it was the expandable questions that appeared under a result in Google. In August 2023 Google restricted those rich results to well known, authoritative government and health websites. A business site adding FAQ schema today will almost certainly not get them, and any guide that promises otherwise is out of date.
Why it is still worth adding
The markup has a second job that did not go away. It states, unambiguously, “this is a question and this is its complete answer”. A question and answer pair is close to the ideal unit for an assistant to quote: self-contained, specific and already phrased the way a person asks. Marking the pairs up removes any doubt about where each answer starts and stops.
We cannot show you a number for how much this helps, and nobody else can either. It is a small, cheap step that makes your content easier to parse. Treat it as tidy housekeeping, not a growth tactic.
Rules that keep the markup valid
| Rule | Why |
|---|---|
| The questions and answers must be visible on the page | Markup for hidden content breaks Google’s structured data guidelines. Content inside an accordion that a visitor can open is fine |
| The text must match what is on the page | The schema describes the page. It is not a second place to put different wording |
| One FAQPage block per page | Put every pair in a single block |
| The same question should not be marked up on several pages | Pick the one page where it belongs |
| Use it for questions with one answer from you | Where users submit answers, the right type is QAPage, not FAQPage |
Writing questions worth marking up
- Use the questions buyers really ask. Your sales inbox and call notes are the best source.
- Answer in the first sentence, then add detail. “Two weeks for most sites” before the explanation.
- Keep each answer under about 100 words. The tool warns above 300.
- Name the subject in the answer. “An audit takes two weeks”, not “It takes two weeks”, so the answer still makes sense when quoted without the question.
- Leave out questions written only to hold a keyword. They help nobody.
Where to put the output
Paste the block into the HTML of the page that shows the questions, in the head or anywhere in the body. In WordPress, use a Custom HTML block or your SEO plugin’s schema field. If your SEO plugin has its own FAQ block, use that instead, since it outputs the visible questions and the markup together and they cannot drift apart. Then test the page in Google’s Rich Results Test.
What this tool cannot tell you
It turns text into valid markup. It cannot check that the same text is visible on your page, which is the rule that matters most, and it cannot tell you whether a question is one anybody asks.
Frequently asked questions
How many questions should a page have?
As many as are useful, which is usually three to eight. A list of thirty suggests the page is doing the job of several.
Can I put links in the answers?
Yes. Google accepts a small set of HTML tags in answer text, including links, lists and paragraphs. Add them to the output by hand if you need them.
Will this get me into AI answers?
Not by itself. It makes well written answers easier to extract. The writing has to be worth extracting first.
Related
- JSON-LD schema for AI search
- Schema validators and testing tools: which one answers which question
- Organization Schema Builder
- All free SEO tools