Answer the questions before they are asked
Launch FAQ builder
Visitors, directory reviewers and search engines ask the same questions: what is it, who is it for, what does it cost, what happens to my data, how do I get help, can I get my money back. Enter the facts once. The builder fills a set of question templates with your own words, you edit the result, and you export it as Markdown, as HTML with proper headings, and as FAQPage structured data.
The questions are fixed templates, not written by AI, and every answer is built only from what you typed. If a fact is missing, the question is left out and listed so you can add it. Everything runs in this page and nothing is sent or stored.
1. Your product facts
The questions are fixed templates filled with your words. Nothing is written for you and nothing is sent anywhere.
How to use it
- Enter the facts. Fill in the product name, what it is, who it is for, the pricing model and details, the free tier, how data is handled, integrations, the support channel and the refund policy. Two optional facts add a getting-started question and a what-it-does-not-do question.
- Propose and edit the questions. Press Propose questions. Each template with its facts filled becomes a question and answer. Edit the wording, remove what does not fit, or add your own question up to a total of twelve.
- Fix anything flagged. Each question must end with a question mark, be a real question and appear once. Each answer must be filled in and no longer than 300 words. Flags show on the item until you fix them.
- Export and publish. Copy the Markdown or the HTML into your page and add the JSON-LD script alongside it. The structure check confirms that the JSON-LD is a FAQPage whose mainEntity is a list of Question items with an acceptedAnswer.
How the questions and the markup are made
There are ten templates: what it is, who it is for, price, free plan or trial, how to get started, data handling, integrations, what it does not do, support and refunds. A template is used only when every fact it needs is filled in, and the answer is your text turned into a sentence: trimmed, capitalised and ended with a full stop if it has no end punctuation. Nothing is added to it. The pricing answer joins a fixed sentence for the model you chose, such as the product having a free plan and paid plans, with your details. The two optional templates are skipped when empty. With the eight main facts filled in you get eight questions, with the optional ones ten, and you may add your own up to twelve.
The checks are simple and strict. A question has to end with a question mark, have at least three words and not repeat another question. An answer has to be non-empty and at most 300 words, counted as runs of non-space characters. Long answers are hard to read in a list and are less likely to be shown in full, so the limit is a writing rule and not a requirement of the schema.
The JSON-LD uses the schema.org types FAQPage, Question and Answer: a FAQPage with a mainEntity array, each item a Question with a name and an acceptedAnswer of type Answer with text. A validator in this page checks exactly that structure, and the tests run it against generated output and against deliberately broken copies. It checks structure, not eligibility. Search engines decide whether to show FAQ results, and they expect the marked-up questions and answers to be visible on the page, so publish the visible HTML or Markdown with the script. In the script tag, the less-than sign is written as a Unicode escape so an answer can never close the tag early. In the HTML, all text is escaped.
Questions
Does this use AI to write the answers?
No. The questions are templates and the answers are your own words with punctuation tidied. That keeps the FAQ true to your facts and lets you check every line.
Why were some questions left out?
A question is only proposed when the facts it needs are filled in. The left-out ones are listed with the missing fact so you can add it and propose again.
How many questions should a FAQ have?
Enough to cover what buyers and reviewers ask, and no more. The builder proposes up to ten from your facts and lets you add your own up to twelve.
Where do I put the JSON-LD?
Paste the script tag into the page that shows the same questions and answers, in the head or the body. The markup should describe content people can see on that page.
Will this make FAQ results appear in search?
It cannot promise that. Search engines choose when to show FAQ results and have limited them over time. Clear questions with direct answers help readers and assistants either way.
What does the 300 word limit protect against?
Answers that turn into pages. Short answers are easier to scan and to quote. The limit is a style rule and you can still publish a longer page elsewhere and link to it.