糟糕 FAQ 是一堆没人问过的”自夸式”问题。好 FAQ 是转化工具——它提前接住 5 个差点让用户放弃的顾虑。Prompt 必须挖真问题，不能造好看的。
适合哪些场景
写 landing 的 SaaS 创业者、做 PDP 的电商、把工单翻译成公开 FAQ 的客服负责人、提升帮助中心 SEO 的内容人。
什么时候不建议这样写 Prompt
别用来写词汇表或知识库——格式不同。也别用来掩盖坏消息。
Prompt 结构公式
每个 FAQ Prompt 都要带这六个要素：
- 读者：一个具体的人，不是”任何对 X 感兴趣的人”。
- 目标：一个动作——读完 / 点击 / 注册 / 同意 / 分享。
- 语气：品牌或作者语气，用 2-3 个锚定形容词。
- 限制：字数、禁用短语、必含事实。
- 格式：段落、列表、小标题、表格。
- 示例：1-2 条目标语气示例——匹配 voice 的最强杠杆。
这套 Prompt 适合用在哪
- landing FAQ 处理异议
- PDP / 价格页 FAQ
- 新用户 onboarding FAQ
- 工单转公开帮助文章
- FAQPage schema SEO
12 个可直接复制的 Prompt 模板
1. 从工单挖真问题
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.可替换变量： ticketLog
2. 异议处理 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.可替换变量： productName
3. 价格页 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. 按用户路径排序
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. 答案压缩
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 友好 FAQ
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.可替换变量： 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.可替换变量： productName
8. 信任构建 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. 退款 / 注销 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. “对比 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.可替换变量： product, compA, compB
11. 大白话改写
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 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.容易踩的坑
- 编自夸式问题——“你们团队怎么做创新的？”
- 答案前先铺三段铺垫。
- 信任答案模糊——“我们重视安全”。
- 只指向”联系销售”。
- 不按用户路径排序。
- 用第三人称企业腔——用户用第一人称。
- 尴尬就跳过退款 / 注销话题。
优化技巧
- 答案开头先给结论，铺垫放后面。
- 答案 30-50 字以内，再长就开成独立帮助文章。
- 问题用用户原话方式表述。
- 每月看一次工单，刷新 FAQ。
- FAQPage schema 只在 FAQ 真有用之后再上。
- 诚实承认 trade-off，读者反而买账。
- 深度内容用链接外接帮助中心。
实操加深
使用这些 prompt 时，不要只替换一个主题词就直接交付。围绕「FAQ 板块 Prompt：12 个高转化产品 FAQ 模板」先补齐受众、渠道、长度、语气、参考样例、禁止样式和成功标准，再让模型输出 2 个不同版本做横向比较。好的结果应该能被另一个人直接复用，而不是只有顺滑但空泛的表达。
如果输出看起来像通用模板，下一轮要增加一个真实场景、一个反例和一个可检查指标，例如点击率、转化动作、字数、平台限制或品牌禁区。这样改出来的内容才更像可用资产，而不是一次性的灵感草稿。
FAQ
- 多少条算多？: landing 上 8-12 条。再多放帮助中心。
- 按重要性还是按路径排？: landing 按路径，帮助中心按频次。
- FAQPage schema 帮 SEO 吗？: 内容确实有用时能获 rich result，schema 本身不是魔法。
- AI 能挖工单吗？: 能——脱敏后粘进去。
- 负面评价能转 FAQ 吗？: 可以——改成真问题，诚实回答 trade-off。
- 什么时候下线 FAQ？: 工单该问题低于阈值（如月 < 5）时。
相关阅读
标签: #Prompt #写作 #FAQ #Landing Page