A bad FAQ is a wall of corporate questions nobody asked. A good FAQ is a conversion tool — it pre-empts the 5 objections that almost stop the purchase. The Prompt has to mine real questions, not invent flattering ones.
Who this is for
SaaS founders writing landing pages, e-commerce sellers building PDPs, support leads turning tickets into a public FAQ, content marketers improving help-center SEO.
When not to use these prompts
Don’t use these for a glossary or knowledge base — that’s a different format. Don’t use them to bury bad news.
Prompt anatomy / structure formula
Every FAQ-section prompt should carry six elements:
- Audience: one specific reader, not “anyone interested in X”.
- Goal: one outcome — read / click / sign up / agree / share.
- Voice: brand voice or author voice with 2-3 anchor adjectives.
- Constraints: word count, banned phrases, must-include facts.
- Format: paragraph, bulleted, headed sections, table.
- Examples: 1-2 examples of the tone you want — best lever for matching voice.
Best for
- Landing-page FAQ to handle objections
- PDP / pricing FAQ
- Onboarding FAQ for new users
- Support → public help article conversion
- FAQPage schema for SEO
12 copy-ready prompt templates
1. Mine real questions from support tickets
I have these support tickets: {ticketLog}. Cluster into themes and identify the top 8 questions actually asked. For each: (a) the question rephrased to user voice, (b) clearest 2-sentence answer, (c) frequency rank. Skip questions only asked by one person.Variables to swap: ticketLog
2. Objection-handling FAQ
For my product `{productName}`, generate 6 FAQs that handle real purchase objections. For each: (a) the objection in user voice ("Will this work for a team of 2?"), (b) honest 2-3 sentence answer that addresses the objection, (c) optional small reassurance (free trial / refund). No "great question!" filler.Variables to swap: productName
3. Pricing-page FAQ
Generate 8 pricing-page FAQs covering: (1) billing cycle, (2) team seats, (3) annual discount, (4) refund / cancellation, (5) custom plans, (6) tax / invoicing, (7) usage limits, (8) plan downgrade. Each answer ≤ 35 words. No "contact sales" as the only answer.4. Ordering FAQs by user journey
Reorder these FAQs by where they arise in the buyer's journey: awareness → consideration → decision → after-purchase. Output as four grouped sections. If a question fits multiple stages, place it in the earliest one.5. Answer compression
Rewrite each of these FAQ answers in ≤ 30 words. Lead with the answer, then a sentence of context. Cut: "We understand…", "At {brand}, we…", and any apology that delays the answer.6. SEO-aware FAQ for FAQPage schema
Write 6 FAQs that match real search queries for `{topic}`. Use the actual question form ("How do I…", "What is the difference between X and Y…"). Answers ≤ 50 words, factual, no marketing language. These will be wrapped in FAQPage schema.Variables to swap: topic
7. Onboarding FAQ
New users of `{productName}` ask these 6 questions in week 1. Generate questions + answers. Answer style: walk them to the action ("To do X, go to Y → Z"). Include one link per answer.Variables to swap: productName
8. Trust-building FAQ
Write 5 FAQs that address trust concerns: data security, vendor lock-in, who built the company, support hours, change frequency. Answers should be specific (cite SOC2 status, list integrations to export) — vague answers reduce trust.9. Refund / cancellation FAQ
Write the 3 refund / cancellation FAQs we don't want to write: (1) Can I cancel anytime? (2) Will I get a prorated refund? (3) What happens to my data after cancellation? Answer plainly. Don't bury the answer in policy speak.10. “Compared to X” FAQ
Write 3 FAQs comparing `{product}` to known competitors `{compA}`, `{compB}`. Answer honestly — name the trade-off where the competitor is better, then the case for us. Reads as trustworthy, not as sales pitch.Variables to swap: product, compA, compB
11. FAQ rewrite for plain English
Rewrite these FAQs at a 7th-grade reading level. Replace jargon: "leverage" → "use", "robust" → "reliable", "solution" → drop or replace with the actual thing. No corporate hedges.12. FAQ audit
Audit this FAQ section: (1) Which questions answer themselves (drop), (2) Which contradict the product page, (3) Which buries an answer, (4) Which would lose trust if a skeptic read them. Output: keep / rewrite / drop per item.Common mistakes
- Inventing flattering questions (“How does your team innovate?”) nobody asked.
- Burying the answer in 3 paragraphs of context.
- Vague trust answers (“we take security seriously”).
- Pointing to “contact sales” as the only path.
- Not ordering by user journey.
- Writing in third-person corporate voice — users speak first-person.
- Skipping refund / cancellation because it’s uncomfortable.
How to push results further
- Lead each answer with the answer; context after.
- Cap answers at 30-50 words. Anything longer becomes its own help-center article.
- Use the user’s voice in the question — match how they’d phrase it.
- Audit support tickets monthly to refresh FAQ topics.
- For SEO, structure as FAQPage JSON-LD only after the FAQ is genuinely useful.
- Honest about trade-offs — readers reward it.
- Link to deeper help articles for the 10% who need more.
Practical depth notes
Use these prompts as starting points, not final answers. For FAQ Section Prompts: 12 Templates for High-Converting Product FAQs, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How many FAQs is too many?: 8-12 on a landing page. More belongs in a separate help center.
- Should I sort by importance or by journey?: By journey on landing pages, by frequency in help centers.
- Will FAQPage schema help SEO?: It can earn rich-result placement when content is genuinely useful — schema alone isn’t enough.
- Can AI mine my tickets?: Yes — paste a sanitised export. Strip PII before pasting.
- Should I include negative reviews as FAQs?: Sometimes. Reframe as a real question, answer the trade-off honestly.
- When should I retire FAQs?: When ticket volume on that question drops below a threshold (e.g., < 5 / month).
Related
- FAQ writing prompts
- Landing page copy prompts
- Sales copy prompts
- CTA prompts
- Writing & Copywriting Prompts hub
Tags: #Prompt #Writing #FAQ #Landing page