FAQ Page Writer

Generate comprehensive FAQ pages that reduce support tickets and improve SEO with rich snippets.

**Product/Service:** [NAME AND DESCRIPTION]
**Industry:** [SAAS / ECOMMERCE / HEALTHCARE / FINANCE / EDUCATION / TRAVEL]
**Target Audience:** [BEGINNER USERS / ENTERPRISE CLIENTS / GENERAL CONSUMERS]

**Required Structure:**
- CATEGORIZED FAQ SECTIONS (group by topic, not random):
  * Getting Started / Account Setup
  * Features & Functionality
  * Pricing & Billing
  * Technical Support / Troubleshooting
  * Security & Privacy
  * Integrations & Compatibility
  * Refunds & Policies

**For each FAQ item:**
- QUESTION: Written in natural language people actually search for (use question phrasing)
- ANSWER: Clear, concise response (2-5 sentences) with:
  * Direct answer first, then elaboration if needed
  * Step-by-step instructions where applicable
  * Links to relevant help articles or documentation
  * Screenshots or visual aid descriptions
  * Common follow-up questions addressed proactively

**SEO Requirements:**
- Schema markup recommendations (FAQPage structured data)
- Question phrasing optimized for "people also ask" queries
- Internal linking strategy to related pages
- Character count optimization for snippet display (~155 characters for meta descriptions)

**Additional Sections:**
- "Still have questions?" CTA with contact form link or chat widget prompt
- Search bar suggestion for the FAQ page
- Feedback mechanism (Was this helpful? Yes/No)

How to Customize It

Replace each bracketed placeholder with your own details before running the prompt. The more specific you are, the better the output — vague inputs produce generic results.

• [NAME AND DESCRIPTION]Swap in your name and description.
• [SAAS / ECOMMERCE / HEALTHCARE / FINANCE / EDUCATION / TRAVEL]Swap in your saas or ecommerce or healthcare or finance or education or travel.
• [BEGINNER USERS / ENTERPRISE CLIENTS / GENERAL CONSUMERS]Swap in your beginner users or enterprise clients or general consumers.

When to Use It

• Launching a product page where the FAQ section handles the objections your sales calls keep hearing.
• Reducing support ticket volume by publishing answers to the questions your inbox already proves people ask.
• Capturing long-tail search traffic — question-format pages are disproportionately eligible for featured snippets.

Tips for Better Results

• 1Seed it with real questions from support tickets, sales calls, and reviews; invented questions produce an FAQ that answers nothing anyone asks.
• 2Ask for FAQPage schema markup (JSON-LD) alongside the copy if you're publishing on the web — it's what makes rich snippets possible.
• 3Keep answers to 2–3 sentences with a link to deeper docs; FAQ answers that run to paragraphs belong in documentation.