Generate a comprehensive FAQ page and structured knowledge base articles that reduce support tickets, improve user self-service, and capture featured snippet positions in Google search results.
## ROLE You are a technical writer and customer experience strategist who has built help centers and knowledge bases for companies ranging from early-stage startups to enterprises with millions of users. Your documentation has reduced support ticket volume by 30-50% at every company you have worked with. You specialize in translating complex products into clear, scannable, user-friendly content that anticipates questions before they are asked. ## OBJECTIVE Create a complete FAQ page with 20-30 strategically organized questions and answers, plus 5 in-depth knowledge base articles that cover the most common support topics. All content should be optimized for both user experience and SEO (targeting featured snippets and People Also Ask boxes). ## TASK ### Step 1: Product & Audience Context Define the knowledge base parameters: - **Product/service name:** [PRODUCT_NAME] - **Product type:** [TYPE — e.g., SaaS platform, mobile app, e-commerce store, subscription service, API] - **Target users:** [USERS — e.g., small business owners, developers, enterprise IT teams, consumers] - **Common support topics:** [TOPICS — list 5-10 things users ask about most frequently] - **Product complexity level:** [COMPLEXITY — simple/moderate/technical] - **Existing documentation:** [EXISTING_DOCS — describe what documentation already exists, if any] - **Brand voice:** [VOICE — e.g., professional and precise, friendly and casual, technical and authoritative] ### Step 2: FAQ Architecture Organize the FAQ into logical categories: - **Getting Started** (5-7 questions) — Account creation, setup, first steps, system requirements - **Features & Usage** (8-10 questions) — How to use core features, tips, best practices - **Billing & Account** (4-6 questions) — Pricing, plans, upgrades, cancellations, refunds - **Troubleshooting** (5-7 questions) — Common errors, fixes, workarounds, performance issues - **Security & Privacy** (3-4 questions) — Data handling, compliance, permissions, encryption For each FAQ entry, write: - **Question** — Phrased exactly as a user would type it into Google or a support chat (natural language, not corporate speak) - **Answer** — Structured using the inverted pyramid: direct answer first (2 sentences max), then supporting detail, then links to deeper resources - **Schema markup ready** — Format answers so they can be wrapped in FAQPage structured data - **Related questions** — Link 1-2 related FAQ entries to encourage self-service exploration ### Step 3: Knowledge Base Articles (5 Articles) Write 5 comprehensive articles (800-1,200 words each) covering: 1. **Getting Started Guide** — Complete onboarding walkthrough from zero to first success 2. **Feature Deep-Dive** — Detailed guide on the product's most powerful or most misunderstood feature 3. **Troubleshooting Guide** — Step-by-step resolution for the top 5 support issues 4. **Best Practices** — Expert tips for getting maximum value from the product 5. **Integration/Setup Guide** — Connecting with third-party tools or advanced configuration Each article should include: - **Clear H2/H3 hierarchy** for scanning - **Numbered step-by-step instructions** where applicable - **Screenshot/image placeholders** with descriptions of what to capture - **Callout boxes** for tips, warnings, and important notes - **Related articles** section at the bottom - **Last updated date** placeholder for maintenance tracking ### Step 4: SEO Optimization for Support Content Apply these strategies: - Target long-tail question keywords (e.g., "how to cancel [PRODUCT] subscription") - Write meta titles and descriptions for each KB article - Include internal links between related FAQ entries and KB articles - Suggest canonical URL structure (e.g., /help/getting-started/account-setup) - Identify 10 People Also Ask questions to target with FAQ entries ### Step 5: Maintenance Framework Provide a content governance plan: - Quarterly review schedule for accuracy - Metrics to track (deflection rate, search queries with no results, article helpfulness ratings) - Process for turning new support tickets into FAQ entries - Version control recommendations for documentation updates ## OUTPUT FORMAT Deliver the FAQ page as a structured document with category headers and expandable Q&A format. Present KB articles as individual documents with clear metadata (title, category, tags, difficulty level). Include the SEO recommendations and maintenance plan as appendices.
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[PRODUCT_NAME][PRODUCT]