Why add an FAQ at all
A short FAQ answers the objections that stop people from acting: what it costs, who it’s for, how long it takes, what happens if it doesn’t work. Each answer is also a small, self-contained passage that a search engine or an AI assistant can quote when someone asks that exact question. That only works if the questions are ones people really ask and the answers are specific.
How the generator works
Describe the page in a few sentences, with the facts you want covered. We ask an open model (Llama 3.3 70B on Cloudflare Workers AI) for questions a reader would type into Google or ask an assistant, each with a direct answer of one to three sentences. It’s told to use only facts from your summary and to stay general where you didn’t give one. We then clean the output: questions end with a question mark, answers are trimmed at a sentence boundary, duplicates are dropped, and you get five you can edit in place. The FAQPage JSON-LD updates as you edit. Nothing is saved.
Making the FAQ good
- Replace generic questions with real ones. The best FAQs come from support tickets, sales calls and reviews. Use the generated list as a prompt for your own memory.
- Answer in the first sentence. “Yes, up to three clients free” before any explanation.
- Add the specifics only you know. Prices, limits, timelines, integrations. The model doesn’t know them unless you wrote them in the summary.
- Keep it short. Five good questions beat fifteen padded ones.
Adding it to your page
- Put the questions and answers visibly on the page, usually near the end.
- Paste the JSON-LD into the same page’s HTML. Markup must match what readers can see.
- Test the live URL with Google’s Rich Results Test or the Schema Markup Validator.
Already have your questions? Use the FAQ schema generator instead. To see which H2s could become questions, run the page through the heading checker.