Short answer: Start from the questions customers really ask before they buy: price, who it is for, what is included, how it compares, how to cancel. Write each answer so the first sentence is the answer, with specifics (numbers, names, limits) and no marketing wrap. Put each question in a real heading or <summary>, keep the text in the HTML, and mark the page up with FAQPage structured data that matches it exactly. Unvibe lists the questions buyers ask in your market and checks which ones your site answers.
Why FAQ pages work for AI
An assistant answering “Does it work with my tools?” or “How much does it cost?” wants a passage that answers that exact question. A question followed by a direct answer is the shape of text it can lift without rewriting. A page of marketing paragraphs makes it do the work of finding the answer, and it may find someone else’s instead.
1. Use questions people really ask
Do not invent questions to fit keywords. Go to the places the real ones live: emails to your team, support tickets, comments, and the questions you answer on calls. Typical ones for almost every business:
- How much does it cost, and what is not included?
- Who is it for, and who is it not for?
- How is it different from [the obvious alternative]?
- How do I get started, and how long does it take?
- What happens if I want to cancel or get a refund?
Then add the ones specific to your field, such as insurance for a clinic or integrations for software. We explain how to find them in the questions customers ask AI before they choose you.
2. Answer in the first sentence
| Weak | Strong |
|---|---|
| “Great question! Pricing is something we have thought hard about, and we want to make it work for everyone.” | “Plans start at $19 a month. Yearly billing costs about 20% less.” |
| “We offer a range of integrations.” | “It connects to Slack, Google Sheets and Zapier. It does not connect to Salesforce yet.” |
The example numbers are made up. Use your own, and include the limits and the “no”. An honest “not yet” is more useful, and more believable, than an answer that avoids the question.
3. Keep each answer standalone
Name the thing in the answer instead of saying “it” or “as above”. An assistant may quote one answer on its own, and it should still make sense.
4. Use real headings and put the text in the HTML
A question in an <h3>, or in a <summary> inside a <details> block, with the answer in the HTML next to it. Collapsible answers are fine if the text is in the page source. Answers loaded by JavaScript when you click may never reach a crawler that does not run scripts. Check with view source.
5. Add FAQPage markup, and keep it identical
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "How much does it cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Plans start at $19 a month. Yearly billing costs about 20% less."
}
}]
}
The questions and answers must match what is on the page. If someone edits one and forgets the other, the two disagree. More on this in Structured data for AI.
6. Keep it current
An FAQ with last year’s prices is worse than none, because the assistant repeats it with confidence. Put a review in your calendar, and update the answer and the markup together.
Where Unvibe fits
The hard part is knowing which questions matter in your market, and which ones your site does not yet answer.
The questions buyers ask, and what your site answers
- Questions for your market: the checkup works out your niche from your pages and lists the questions people ask before choosing a business like yours.
- Answered, partly or missing: each question is marked, with the sentence from your site that answers it, quoted as proof.
- Ready-to-paste fix: for each gap, a heading and a place to write the answer, built from your own facts.
- Confirmed on the live site: run another checkup after you publish and it re-checks the same questions.
How the questions are chosen and checked is described in the checkup docs.
Questions
How many questions should an FAQ page have?
As many as real customers ask, usually between 8 and 20. Ten honest answers beat fifty padded ones.
Should I put the FAQ on its own page or on each product page?
Both can work. A dedicated page gives assistants one place to look. Questions about a specific product also belong on that product’s page.
Does FAQPage markup guarantee my answers are quoted?
No. It makes the questions and answers unambiguous for anything that reads them. Whether an assistant uses them is its decision.