Faq Page Generator
Draft and optimize FAQ page copy structured for rich results, PAA, featured snippets, and AI-search citations.
Overview
FAQ Page Generator is an agent skill most often used in Launch (also Grow content and Validate landing) that creates and optimizes FAQ page content for SEO rich results, PAA, and GEO visibility.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill faq-page-generatorWhat is this skill?
- Maps FAQ content to PAA, Featured Snippet, GEO/AI Overviews, and PASF opportunities
- Rich-results guidance: answer-first 40–60 words, H2/H3 structure, snippet format mix
- Sources questions from real user queries; separates content from schema-markup skill
- Cross-references serp-features and featured-snippet skills for deeper SERP tactics
- Versioned protocol (1.2.0) with optional first-use intro then direct output on repeat runs
- PAA appears in roughly 51% of searches per skill SERP table reference
- Featured snippet format mix cited: paragraph ~70%, list ~19%, table ~6%
- Answer-first FAQ answers targeted at 40–60 words for snippet eligibility
Adoption & trust: 795 installs on skills.sh; 586 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have scattered support answers but no FAQ page structured to win snippets, PAA coverage, or AI citations from real customer questions.
Who is it for?
Solo builders launching or refreshing a product site who need SEO-ready FAQ copy tied to SERP and AI overview opportunities.
Skip if: Teams that only need JSON-LD without page copy (use schema-markup) or sites skipping organic discovery entirely.
When should I use this skill?
User mentions FAQ page, frequently asked questions, FAQ schema context, PAA, PASF, accordion FAQ, FAQ SEO, or FAQ rich results.
What do I get? / Deliverables
You get an optimized FAQ content plan and copy patterns with clear handoffs to schema-markup for markup and generative-engine-optimization for AI-search strategy.
- Structured FAQ content outline with question phrasing aligned to PAA/snippet patterns
- Optimized answer blocks (paragraph/list/table guidance per question)
- Audit or improvement notes for existing FAQ pages
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
FAQ pages are primarily a launch and organic visibility asset that targets SERP features and conversion on help content. The skill ties FAQ structure to SEO rich results (PAA, snippets, GEO)—canonical shelf is launch/seo rather than generic copywriting.
Where it fits
Build a pricing-and-product FAQ that targets PAA questions competitors already trigger.
Add a pre-launch FAQ section on a landing page to handle objections before waitlist signup.
Expand support macros into a searchable FAQ hub optimized for snippet formats.
How it compares
Content-and-structure skill for FAQ pages—not a substitute for dedicated schema markup or full GEO strategy skills.
Common Questions / FAQ
Who is faq-page-generator for?
Indie founders and marketers writing help, pricing, and product FAQ pages who care about SEO, rich results, and AI-search citations without an agency copy deck.
When should I use faq-page-generator?
At Launch/seo for FAQ SEO and rich results; at Validate/landing for pre-launch objection handling; at Grow/content when expanding help hubs from support tickets and PAA research.
Is faq-page-generator safe to install?
It outputs marketing copy guidance only; review the Security Audits panel on this Prism page before installing and validate factual claims in answers before publishing.
Workflow Chain
Then invoke: schema markup, generative engine optimization
SKILL.md
READMESKILL.md - Faq Page Generator
# 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 a