faq-page-generator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pages: FAQ

页面：FAQ

Guides FAQ page content, structure, and optimization for SEO and conversion.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

为SEO和转化提升提供FAQ页面的内容、结构和优化指导。

调用规则：首次使用时，如果有帮助，可以先用1-2句话介绍本技能覆盖的内容及其价值，再提供主输出。后续使用或用户要求跳过介绍时，直接给出主输出即可。

Initial Assessment

初步评估

Check for product marketing context first: If

.claude/product-marketing-context.md

.cursor/product-marketing-context.md

exists, read it for objections, product details, and customer language.

Identify:

Source of questions: Support tickets, sales, chat, surveys
Conversion focus: Objection-handling, decision-support
Placement: Dedicated page, in-page sections, or both

首先检查产品营销上下文：如果存在

.claude/product-marketing-context.md

或

.cursor/product-marketing-context.md

文件，请阅读获取用户异议、产品详情和客户常用表述。

确认以下信息：

问题来源：支持工单、销售记录、聊天记录、调研
转化重点：异议处理、决策支持
展示位置：独立页面、页面内板块，或两者兼有

Best Practices

最佳实践

Word Count & Answer Length

字数与回答长度

Context	Recommended	Notes
Featured Snippet (paragraph)	40–60 words	45 words most common; ~70% of snippets are paragraphs; see featured-snippet
First sentence	40–50 words	Answer immediately; Google pulls from first lines
Full answer	40–100 words	GEO: keep under 100 words per answer for AI citation
Complex questions	Flexible	Prioritize clarity over rigid count; some need more

Principle: Start with direct answer in 40–60 words; add brief context. Quality and completeness matter more than strict length.

场景	推荐值	说明
精选片段（段落形式）	40–60 词	最常见为45词；约70%的精选片段为段落形式，参考 featured-snippet
首句	40–50 词	直接给出答案；Google会从首行内容提取信息
完整回答	40–100 词	GEO要求：单条回答控制在100词以内，便于AI引用
复杂问题	灵活调整	优先保证清晰度而非严格遵守字数要求，部分问题需要更多篇幅解释

原则：开头用40-60词直接给出答案，再补充简短上下文。质量和完整性比严格的长度要求更重要。

Number of Questions

问题数量

Placement	Count	Notes
FAQ section (in-page)	3–8	Small set; directly related to page topic; catches long-tail
Dedicated FAQ page	5–30	10–30 genuine questions; group by category
Schema minimum	2+	Single Q&A technically valid but rarely shown
Schema per page	5–8 optimal	Balance value vs. dilution; quality over quantity
Google display	Max 2 per result	Google shows max 2 FAQ dropdowns per SERP snippet (since 2021); see serp-features

Note: FAQ rich results are now restricted to well-known government/health sites in many regions. Schema still helps AI Overviews, PAA, and voice search.

展示位置	数量	说明
页面内FAQ板块	3–8	数量少，与页面主题直接相关，覆盖长尾搜索需求
独立FAQ页面	5–30	10-30条真实问题，按类别分组
Schema最低要求	2条及以上	单个问答技术上合规，但很少被展示
单页Schema数量	最优5–8条	平衡价值与权重稀释，质量优先于数量
谷歌展示规则	单条结果最多2条	自2021年起，谷歌在SERP片段中最多展示2个FAQ下拉项，参考 serp-features

注意：目前很多地区仅知名政府、健康类网站可获得FAQ富媒体结果。但Schema仍然对AI概览、相关问题（PAA）和语音搜索有帮助。

Question Best Practices

问题编写最佳实践

Source: Support tickets, chat logs, sales objections, PAA, AnswerThePublic, Semrush
Phrasing: Match how users ask—"How do I return an item?" not "Return Policy"
Intent: Target "how," "what," "why" queries; align with search intent
Structure: Use H2/H3 for each question; helps extraction
Avoid: Promotional, irrelevant, or invented questions
Conversion: Address objections; move toward purchase or next step

来源：支持工单、聊天记录、销售异议、PAA、AnswerThePublic、Semrush
表述：匹配用户的真实提问方式，比如“我如何退货？”而非“退货政策”
意图：覆盖“how”、“what”、“why”类查询，匹配搜索意图
结构：每个问题使用H2/H3标签，便于内容提取
避免：推广类、无关的或凭空编造的问题
转化：解决用户异议，引导用户完成购买或进入下一步

Answer Best Practices

回答编写最佳实践

Answer-first: Place direct answer in first 1–2 sentences (40–60 words)
Format: Paragraph (70%), list (19%), table (6%)—choose by content type
Scannable: Bullets, numbered lists, bold for key terms
Self-contained: Each answer readable alone (GEO: AI cites discrete blocks)
Conversational: Human-friendly; no jargon
Complete: No need for follow-up to understand
Entity signals: Clear brand/product names for GEO citation

答案前置：在前1-2句（40-60词）中直接给出答案
格式：段落（70%）、列表（19%）、表格（6%），根据内容类型选择
易扫描：使用项目符号、有序列表、加粗标注关键术语
自包含：每条回答独立可读（GEO要求：AI会引用独立的内容块）
口语化：友好易懂，无行业黑话
完整性：无需额外追问即可理解内容
实体信号：标注清晰的品牌/产品名称，便于GEO引用

Organization

内容组织

Categories: Group by topic (Billing, Features, Support, Compliance)
Hierarchy: Clear sections, logical order
Navigation: Table of contents, accordions, jump links, search bar; see tab-accordion for accordion SEO and implementation
Maintenance: Audit quarterly; rewrite underperforming answers

分类：按主题分组（账单、功能、支持、合规）
层级：板块清晰，逻辑排序
导航：目录、手风琴组件、锚点链接、搜索栏；手风琴的SEO和实现参考 tab-accordion
维护：每季度审核，重写效果不佳的回答

SEO & GEO

SEO与GEO优化

Keywords: Natural inclusion in Q&A
Title/meta: Optimized for FAQ queries
Schema: FAQPage JSON-LD; validate with Rich Results Test
Schema = visible: Markup must match on-page content exactly
GEO: Atomic answer blocks; definitions, lists, stats; under 100 words per answer

关键词：在问答中自然植入关键词
标题/元描述：针对FAQ类查询优化
Schema：使用FAQPage JSON-LD格式，通过富媒体结果测试工具验证
Schema与可见内容一致：标记内容必须与页面展示内容完全匹配
GEO要求：原子化回答块，包含定义、列表、统计数据；单条回答不超过100词

Why It Matters

价值说明

Reduces support load
Targets long-tail and voice search
Can convert 2×+ higher than standard content
Builds trust; creates featured snippet opportunities; see featured-snippet, serp-features
FAQ schema supports AI Overviews, PAA, voice search even when rich results don't display (20–30% CTR lift when they do)

降低支持负载
覆盖长尾搜索和语音搜索需求
转化率可比标准内容高2倍以上
建立用户信任，获得精选片段展示机会，参考 featured-snippet、serp-features
即使不展示富媒体结果，FAQ schema也对AI概览、PAA、语音搜索有帮助（展示时可提升20-30%的点击率）

Output Format

输出格式

Question list (from research)
Category structure
Answer format and tone
Schema (FAQPage)
SEO metadata

问题列表（基于调研）
分类结构
回答格式与语气
Schema（FAQPage）
SEO元数据