faq

Name: faq
Author: kostja94

753stars109forks

How to install faq?

kostja94/marketing-skills/faq

$npx -y skills add kostja94/marketing-skills --skill faq

Installs into the current project.

Summary

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 Al

Files · 1

View on GitHub

SKILL.md

1	# Pages: FAQ
2
3	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.
4
5	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.
6
7	## FAQ and Rich Results
8
9	\| Feature \| Relationship \| Optimization \|
10	\|---------\|--------------\|---------------\|
11	\| 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 \|
12	\| Featured Snippet \| Answers extracted for position zero \| 40-60 words; answer-first; H2/H3; paragraph (70%), list (19%), table (6%). See featured-snippet \|
13	\| 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 \|
14	\| People Also Search For (PASF) \| Appears when user bounces; comprehensive FAQ reduces bounce \| Match intent; cover related questions. PASF shows 6-8 related queries. \|
15	\| FAQ rich result \| FAQPage schema; max 2 dropdowns per SERP \| Restricted to government/health in many regions; schema still helps PAA, voice, AI \|
16
17	PAA vs PASF: PAA = expandable question boxes (same SERP). PASF = related queries after bounce. Both benefit from comprehensive, intent-matching content.
18
19	## Content Sources
20
21	Real user: Support tickets, chat logs, sales objections, surveys, reviews.
22
23	Rich-result purpose: PAA (search keyword, extract questions), AnswerThePublic, AlsoAsked, Featured Snippet queries, competitor FAQ, keyword research, GEO citation data.
24
25	Reverse flow: Use PAA, Featured Snippet, GSC Search queries to find questions you rank for but don't answer.
26
27	## Content Structure
28
29	\| Approach \| When \| Example \|
30	\|----------\|------\|---------\|
31	\| Page topic \| In-page section \| 3-8 questions about that page \|
32	\| Theme \| Dedicated page \| Group by Billing, Features, Support, Compliance \|
33	\| Logical flow \| Decision funnel \| Awareness -> Consideration -> Purchase -> Support \|
34	\| Objection handling \| Conversion \| "Is it worth it?" "Can I cancel?" \|
35
36	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.
37
38	## Dedicated FAQ Page vs In-Page FAQ Section
39
40	\| Dimension \| Dedicated Page \| In-Page Section \|
41	\|-----------\|----------------\|-----------------\|
42	\| Placement \| /faq, /help, standalone URL \| Within LP, pricing, blog, product page \|
43	\| Count \| 5-30 (5-10 optimal) \| 3-8 \|
44	\| Structure \| Categories, TOC, navigation \| Inline; after main content \|
45	\| Schema \| One FAQPage per page \| Same; schema matches visible Q&A \|
46	\| When to use \| Many questions; support/help hub; central FAQ \| Objection handling; page-specific long-tail; conversion \|
47	\| Related pages \| contact-page, docs-page, website-structure \| landing-page, pricing-page, blog, alternatives, category-pages, tools-page \|
48
49	Shared rules: Word count, content rules, format, and schema apply to both. Choose placement based on question volume and page purpose.
50
51	## Accordion: Crawlable?
52
53	Yes. Google indexes accordion content fully; hidden content receives full weight.
54
55	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.
56
57	Nuance: Some tests suggest visible content outperforms hidden. Use accordion for secondary FAQ; keep primary Q&A visible.
58
59	## Best Practices
60
61	### Word Count
62
63	\| Element \| Range \| Notes \|
64	\|---------\|-------\|------\|
65	\| Answer \| 40-80 words \| Sweet spot for AI; under 40 = incomplete; over 80 = cut off \|
66	\| Featured Snippet \| 40-60 words \| 45 words most common \|
67	\| First sentence \| 40-50 words \| Answer immediately \|
68	\| Sentences \| 2-4 \| Standalone, comprehensive \|
69
70	### Content Rules
71
72	- Genuine questions: PAA, AnswerThePublic, support; no invented marketing questi

People who liked this also viewed

6 picks

Type

faq

753stars109forks

View on GitHub

How to install faq?

kostja94/marketing-skills/faq

$npx -y skills add kostja94/marketing-skills --skill faq

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Pages: FAQ
2
3	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.
4
5	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.
6
7	## FAQ and Rich Results
8
9	\| Feature \| Relationship \| Optimization \|
10	\|---------\|--------------\|---------------\|
11	\| 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 \|
12	\| Featured Snippet \| Answers extracted for position zero \| 40-60 words; answer-first; H2/H3; paragraph (70%), list (19%), table (6%). See featured-snippet \|
13	\| 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 \|
14	\| People Also Search For (PASF) \| Appears when user bounces; comprehensive FAQ reduces bounce \| Match intent; cover related questions. PASF shows 6-8 related queries. \|
15	\| FAQ rich result \| FAQPage schema; max 2 dropdowns per SERP \| Restricted to government/health in many regions; schema still helps PAA, voice, AI \|
16
17	PAA vs PASF: PAA = expandable question boxes (same SERP). PASF = related queries after bounce. Both benefit from comprehensive, intent-matching content.
18
19	## Content Sources
20
21	Real user: Support tickets, chat logs, sales objections, surveys, reviews.
22
23	Rich-result purpose: PAA (search keyword, extract questions), AnswerThePublic, AlsoAsked, Featured Snippet queries, competitor FAQ, keyword research, GEO citation data.
24
25	Reverse flow: Use PAA, Featured Snippet, GSC Search queries to find questions you rank for but don't answer.
26
27	## Content Structure
28
29	\| Approach \| When \| Example \|
30	\|----------\|------\|---------\|
31	\| Page topic \| In-page section \| 3-8 questions about that page \|
32	\| Theme \| Dedicated page \| Group by Billing, Features, Support, Compliance \|
33	\| Logical flow \| Decision funnel \| Awareness -> Consideration -> Purchase -> Support \|
34	\| Objection handling \| Conversion \| "Is it worth it?" "Can I cancel?" \|
35
36	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.
37
38	## Dedicated FAQ Page vs In-Page FAQ Section
39
40	\| Dimension \| Dedicated Page \| In-Page Section \|
41	\|-----------\|----------------\|-----------------\|
42	\| Placement \| /faq, /help, standalone URL \| Within LP, pricing, blog, product page \|
43	\| Count \| 5-30 (5-10 optimal) \| 3-8 \|
44	\| Structure \| Categories, TOC, navigation \| Inline; after main content \|
45	\| Schema \| One FAQPage per page \| Same; schema matches visible Q&A \|
46	\| When to use \| Many questions; support/help hub; central FAQ \| Objection handling; page-specific long-tail; conversion \|
47	\| Related pages \| contact-page, docs-page, website-structure \| landing-page, pricing-page, blog, alternatives, category-pages, tools-page \|
48
49	Shared rules: Word count, content rules, format, and schema apply to both. Choose placement based on question volume and page purpose.
50
51	## Accordion: Crawlable?
52
53	Yes. Google indexes accordion content fully; hidden content receives full weight.
54
55	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.
56
57	Nuance: Some tests suggest visible content outperforms hidden. Use accordion for secondary FAQ; keep primary Q&A visible.
58
59	## Best Practices
60
61	### Word Count
62
63	\| Element \| Range \| Notes \|
64	\|---------\|-------\|------\|
65	\| Answer \| 40-80 words \| Sweet spot for AI; under 40 = incomplete; over 80 = cut off \|
66	\| Featured Snippet \| 40-60 words \| 45 words most common \|
67	\| First sentence \| 40-50 words \| Answer immediately \|
68	\| Sentences \| 2-4 \| Standalone, comprehensive \|
69
70	### Content Rules
71
72	- Genuine questions: PAA, AnswerThePublic, support; no invented marketing questi

People who liked this also viewed

6 picks

Type