Pages: FAQ
Guides FAQ page content, structure, and optimization for SEO, conversion, and rich results (PAA, Featured Snippet, GEO, PASF). FAQ content from real user questions and rich-result targeting.
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.
FAQ and Rich Results
| Feature |
Relationship |
Optimization |
| People Also Ask (PAA) |
FAQ schema triggers PAA-style dropdowns; PAA questions = FAQ source |
FAQPage schema; match question phrasing; "how/what/why" format. PAA ~51% of searches. See serp-features |
| Featured Snippet |
Answers extracted for position zero |
40-60 words; answer-first; H2/H3; paragraph (70%), list (19%), table (6%). See featured-snippet |
| GEO / AI Overviews |
AI cites FAQ blocks; FAQ most cited content type (3-7x more citations) |
Self-contained; 40-80 words; entity signals; content in initial HTML. See geo |
| People Also Search For (PASF) |
Appears when user bounces; comprehensive FAQ reduces bounce |
Match intent; cover related questions. PASF shows 6-8 related queries. |
| FAQ rich result |
FAQPage schema; max 2 dropdowns per SERP |
Restricted to government/health in many regions; schema still helps PAA, voice, AI |
PAA vs PASF: PAA = expandable question boxes (same SERP). PASF = related queries after bounce. Both benefit from comprehensive, intent-matching content.
Content Sources
Real user: Support tickets, chat logs, sales objections, surveys, reviews.
Rich-result purpose: PAA (search keyword, extract questions), AnswerThePublic, AlsoAsked, Featured Snippet queries, competitor FAQ, keyword research, GEO citation data.
Reverse flow: Use PAA, Featured Snippet, GSC Search queries to find questions you rank for but don't answer.
Content Structure
| Approach |
When |
Example |
| Page topic |
In-page section |
3-8 questions about that page |
| Theme |
Dedicated page |
Group by Billing, Features, Support, Compliance |
| Logical flow |
Decision funnel |
Awareness -> Consideration -> Purchase -> Support |
| Objection handling |
Conversion |
"Is it worth it?" "Can I cancel?" |
Page-specific: LP (objection handling); pricing (billing, plans, enterprise); alternatives (migration, comparison); category (materials, recommendations); tools (what is X, how calculated). See landing-page-generator, pricing-page-generator, alternatives-page-generator, category-pages, tools-page-generator.
Dedicated FAQ Page vs In-Page FAQ Section
| Dimension |
Dedicated Page |
In-Page Section |
| Placement |
/faq, /help, standalone URL |
Within LP, pricing, blog, product page |
| Count |
5-30 (5-10 optimal) |
3-8 |
| Structure |
Categories, TOC, navigation |
Inline; after main content |
| Schema |
One FAQPage per page |
Same; schema matches visible Q&A |
| When to use |
Many questions; support/help hub; central FAQ |
Objection handling; page-specific long-tail; conversion |
| Related pages |
contact-page, docs-page, website-structure |
landing-page, pricing-page, blog, alternatives, category-pages, tools-page |
Shared rules: Word count, content rules, format, and schema apply to both. Choose placement based on question volume and page purpose.
Accordion: Crawlable?
Yes. Google indexes accordion content fully; hidden content receives full weight.
Requirements: Content in DOM at load (no AJAX on click); use <details>/<summary> or server-rendered HTML; first item expanded. Avoid display: none for primary content. See tab-accordion, rendering-strategies.
Nuance: Some tests suggest visible content outperforms hidden. Use accordion for secondary FAQ; keep primary Q&A visible.
Best Practices
Word Count
| Element |
Range |
Notes |
| Answer |
40-80 words |
Sweet spot for AI; under 40 = incomplete; over 80 = cut off |
| Featured Snippet |
40-60 words |
45 words most common |
| First sentence |
40-50 words |
Answer immediately |
| Sentences |
2-4 |
Standalone, comprehensive |
Content Rules
- Genuine questions: PAA, AnswerThePublic, support; no invented marketing questions
- Standalone answers: Each answer makes sense alone; AI extracts individual pairs
- Content parity: Schema must exactly match visible content; hidden schema = violation
- No duplicates: Each Q&A on one page; choose most authoritative
- Topical focus: FAQs match page topic
- Inverted pyramid: Most important first; data, numbers, actionable advice
- Keywords: 1-2 times naturally; no stuffing
- Quality over quantity: 5-10 excellent beat 50 thin
- Update quarterly: Add questions from emerging trends
Format
- Schema: JSON-LD; one FAQPage per page
- Answer HTML (in schema
text): <a>, <strong>, <em>, <p>, <br>, <ol>; use sparingly
- Structure: H2/H3 per question; semantic HTML; answer-first under heading
- Validation: Google Rich Results Test, Schema.org Validator, GSC
Number of Questions
| Placement |
Count |
Notes |
| In-page section |
3-8 |
Directly related to page |
| Dedicated page |
5-10 optimal |
10-30 if well-crafted; quality over quantity |
| Schema minimum |
2+ |
Single Q&A rarely shown |
| Google display |
Max 2 per result |
See serp-features |
Question and Answer
Question: Match how users ask ("How do I return?" not "Return Policy"); target "how/what/why"; H2/H3; avoid promotional or invented.
Answer: Answer-first in 40-60 words; paragraph, list, or table by content type; scannable (bullets, bold); self-contained; entity signals. See entity-seo.
Organization
Group by topic; clear hierarchy; TOC, accordions, jump links; audit quarterly.
Initial Assessment
Check project context (.cursor/project-context.md or .claude/project-context.md) for objections, product details, customer language.
Identify: (1) Source of questions (2) Conversion focus (3) Placement (dedicated vs in-page).
Why It Matters
- Reduces support load
- Long-tail and voice search
- Category pages: +157% conversion when FAQ used
- 20-30% CTR lift when rich results display
- 3-7x more AI citations with optimized FAQ
Output Format
- Question list (from research)
- Category structure
- Answer format and tone
- Schema (FAQPage)
- SEO metadata
Related Skills
- howto-section-generator: Step-by-step HowTo sections; not FAQ—use HowTo schema, not FAQPage
- tab-accordion: Accordion implementation; details/summary
- serp-features: PAA, Featured Snippet, PASF, FAQ limits
- featured-snippet: Answer length, position zero
- geo: GEO strategy; citable blocks; AI crawlers
- schema-markup: FAQPage implementation
- keyword-research: PAA to FAQ; question keywords
- landing-page-generator, pricing-page-generator, alternatives-page-generator, category-pages, tools-page-generator: In-page FAQ section
- contact-page-generator, docs-page-generator, website-structure: Dedicated FAQ page; FAQ reduces contact form volume
- title-tag, meta-description, page-metadata: Metadata
- entity-seo: Entity signals for GEO
- rendering-strategies: Content in initial HTML
1---
2name: faq-page-generator
3description: When the user wants to create, optimize, or audit FAQ page content. Also use when the user mentions "FAQ page," "frequently asked questions," "help page," "Q&A page," "FAQ schema," "FAQ section," "common questions," "FAQ SEO," "accordion FAQ," "People Also Ask," "PAA," "People Also Search For," "PASF," or "FAQ rich results." For FAQ structured data markup, use schema-markup. For AI search visibility strategy, use generative-engine-optimization.
4metadata:
5 version: 1.2.0
6---
7
8# Pages: FAQ
9
10Guides FAQ page content, structure, and optimization for SEO, conversion, and rich results (PAA, Featured Snippet, GEO, PASF). FAQ content from real user questions and rich-result targeting.
11
12**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.
13
14## FAQ and Rich Results
15
16| Feature | Relationship | Optimization |
17|---------|--------------|---------------|
18| **People Also Ask (PAA)** | FAQ schema triggers PAA-style dropdowns; PAA questions = FAQ source | FAQPage schema; match question phrasing; "how/what/why" format. PAA ~51% of searches. See **serp-features** |
19| **Featured Snippet** | Answers extracted for position zero | 40-60 words; answer-first; H2/H3; paragraph (70%), list (19%), table (6%). See **featured-snippet** |
20| **GEO / AI Overviews** | AI cites FAQ blocks; FAQ most cited content type (3-7x more citations) | Self-contained; 40-80 words; entity signals; content in initial HTML. See **geo** |
21| **People Also Search For (PASF)** | Appears when user bounces; comprehensive FAQ reduces bounce | Match intent; cover related questions. PASF shows 6-8 related queries. |
22| **FAQ rich result** | FAQPage schema; max 2 dropdowns per SERP | Restricted to government/health in many regions; schema still helps PAA, voice, AI |
23
24**PAA vs PASF**: PAA = expandable question boxes (same SERP). PASF = related queries after bounce. Both benefit from comprehensive, intent-matching content.
25
26## Content Sources
27
28**Real user**: Support tickets, chat logs, sales objections, surveys, reviews.
29
30**Rich-result purpose**: PAA (search keyword, extract questions), AnswerThePublic, AlsoAsked, Featured Snippet queries, competitor FAQ, keyword research, GEO citation data.
31
32**Reverse flow**: Use PAA, Featured Snippet, GSC Search queries to find questions you rank for but don't answer.
33
34## Content Structure
35
36| Approach | When | Example |
37|----------|------|---------|
38| **Page topic** | In-page section | 3-8 questions about that page |
39| **Theme** | Dedicated page | Group by Billing, Features, Support, Compliance |
40| **Logical flow** | Decision funnel | Awareness -> Consideration -> Purchase -> Support |
41| **Objection handling** | Conversion | "Is it worth it?" "Can I cancel?" |
42
43**Page-specific**: LP (objection handling); pricing (billing, plans, enterprise); alternatives (migration, comparison); category (materials, recommendations); tools (what is X, how calculated). See **landing-page-generator**, **pricing-page-generator**, **alternatives-page-generator**, **category-pages**, **tools-page-generator**.
44
45## Dedicated FAQ Page vs In-Page FAQ Section
46
47| Dimension | Dedicated Page | In-Page Section |
48|-----------|----------------|-----------------|
49| **Placement** | /faq, /help, standalone URL | Within LP, pricing, blog, product page |
50| **Count** | 5-30 (5-10 optimal) | 3-8 |
51| **Structure** | Categories, TOC, navigation | Inline; after main content |
52| **Schema** | One FAQPage per page | Same; schema matches visible Q&A |
53| **When to use** | Many questions; support/help hub; central FAQ | Objection handling; page-specific long-tail; conversion |
54| **Related pages** | contact-page, docs-page, website-structure | landing-page, pricing-page, blog, alternatives, category-pages, tools-page |
55
56**Shared rules**: Word count, content rules, format, and schema apply to both. Choose placement based on question volume and page purpose.
57
58## Accordion: Crawlable?
59
60**Yes.** Google indexes accordion content fully; hidden content receives full weight.
61
62**Requirements**: Content in DOM at load (no AJAX on click); use `<details>`/`<summary>` or server-rendered HTML; first item expanded. Avoid `display: none` for primary content. See **tab-accordion**, **rendering-strategies**.
63
64**Nuance**: Some tests suggest visible content outperforms hidden. Use accordion for secondary FAQ; keep primary Q&A visible.
65
66## Best Practices
67
68### Word Count
69
70| Element | Range | Notes |
71|---------|-------|------|
72| **Answer** | 40-80 words | Sweet spot for AI; under 40 = incomplete; over 80 = cut off |
73| **Featured Snippet** | 40-60 words | 45 words most common |
74| **First sentence** | 40-50 words | Answer immediately |
75| **Sentences** | 2-4 | Standalone, comprehensive |
76
77### Content Rules
78
79- **Genuine questions**: PAA, AnswerThePublic, support; no invented marketing questions
80- **Standalone answers**: Each answer makes sense alone; AI extracts individual pairs
81- **Content parity**: Schema must exactly match visible content; hidden schema = violation
82- **No duplicates**: Each Q&A on one page; choose most authoritative
83- **Topical focus**: FAQs match page topic
84- **Inverted pyramid**: Most important first; data, numbers, actionable advice
85- **Keywords**: 1-2 times naturally; no stuffing
86- **Quality over quantity**: 5-10 excellent beat 50 thin
87- **Update quarterly**: Add questions from emerging trends
88
89### Format
90
91- **Schema**: JSON-LD; one FAQPage per page
92- **Answer HTML** (in schema `text`): `<a>`, `<strong>`, `<em>`, `<p>`, `<br>`, `<ol>`; use sparingly
93- **Structure**: H2/H3 per question; semantic HTML; answer-first under heading
94- **Validation**: Google Rich Results Test, Schema.org Validator, GSC
95
96### Number of Questions
97
98| Placement | Count | Notes |
99|-----------|-------|------|
100| **In-page section** | 3-8 | Directly related to page |
101| **Dedicated page** | 5-10 optimal | 10-30 if well-crafted; quality over quantity |
102| **Schema minimum** | 2+ | Single Q&A rarely shown |
103| **Google display** | Max 2 per result | See **serp-features** |
104
105### Question and Answer
106
107**Question**: Match how users ask ("How do I return?" not "Return Policy"); target "how/what/why"; H2/H3; avoid promotional or invented.
108
109**Answer**: Answer-first in 40-60 words; paragraph, list, or table by content type; scannable (bullets, bold); self-contained; entity signals. See **entity-seo**.
110
111### Organization
112
113Group by topic; clear hierarchy; TOC, accordions, jump links; audit quarterly.
114
115## Initial Assessment
116
117**Check project context** (`.cursor/project-context.md` or `.claude/project-context.md`) for objections, product details, customer language.
118
119Identify: (1) Source of questions (2) Conversion focus (3) Placement (dedicated vs in-page).
120
121## Why It Matters
122
123- Reduces support load
124- Long-tail and voice search
125- Category pages: +157% conversion when FAQ used
126- 20-30% CTR lift when rich results display
127- 3-7x more AI citations with optimized FAQ
128
129## Output Format
130
131- Question list (from research)
132- Category structure
133- Answer format and tone
134- Schema (FAQPage)
135- SEO metadata
136
137## Related Skills
138
139- **howto-section-generator**: Step-by-step HowTo sections; not FAQ—use HowTo schema, not FAQPage
140- **tab-accordion**: Accordion implementation; details/summary
141- **serp-features**: PAA, Featured Snippet, PASF, FAQ limits
142- **featured-snippet**: Answer length, position zero
143- **geo**: GEO strategy; citable blocks; AI crawlers
144- **schema-markup**: FAQPage implementation
145- **keyword-research**: PAA to FAQ; question keywords
146- **landing-page-generator**, **pricing-page-generator**, **alternatives-page-generator**, **category-pages**, **tools-page-generator**: In-page FAQ section
147- **contact-page-generator**, **docs-page-generator**, **website-structure**: Dedicated FAQ page; FAQ reduces contact form volume
148- **title-tag, meta-description, page-metadata**: Metadata
149- **entity-seo**: Entity signals for GEO
150- **rendering-strategies**: Content in initial HTML
kostja94