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.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
| 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.
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.
| 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.
| 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.
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.
| 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 |
text): <a>, <strong>, <em>, <p>, <br>, <ol>; use sparingly| 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: 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.
Group by topic; clear hierarchy; TOC, accordions, jump links; audit quarterly.
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).
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
The English summary is being prepared. Showing the original description.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
The English summary is being prepared. Showing the original description.