faq-page-generator
The faq-page-generator skill guides creation and optimization of FAQ pages for SEO performance, conversion, and search rich results like People Also Ask boxes and AI Overviews. Use it when building FAQ content, structuring Q&A sections, targeting featured snippets, or optimizing for AI search visibility through real user questions and schema markup strategies.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/faq-page-generator && cp -r /tmp/faq-page-generator/skills/pages/content/faq ~/.claude/skills/faq-page-generatorSKILL.md
# 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**.
##When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.