---
name: faq-section-builder
description: "Writes a website FAQ that answers the questions buyers actually hesitate on, grouped by topic, in a set tone, with optional HTML and JSON-LD markup ready to publish. Use when a product or service page needs an FAQ section that resolves buyer doubts about price, setup, security, or returns, optionally with HTML and JSON-LD markup. Do not use for internal support macros, or a help centre with step-by-step troubleshooting articles. Related topics: marketing, copywriting, business."
---

# FAQ Section Builder

Writes a website FAQ that answers the questions buyers actually hesitate on, grouped by topic, in a set tone, with optional HTML and JSON-LD markup ready to publish.

## When to use

Use this skill when a product or service page needs an FAQ section that resolves buyer doubts about price, setup, security, or returns, optionally with HTML and JSON-LD markup. Do not use it for internal support macros, or a help centre with step-by-step troubleshooting articles.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Draft the questions in the visitor's own words and order them by the stage of the buying decision, from what it is to what happens when things go wrong.
3. Spread the questions across the selected focus areas, dropping any area the product description cannot support.
4. Answer each in two to four sentences with the direct answer first, the exception second, and a next step where one belongs, in the chosen tone.
5. Mark every answer that depends on an unsupplied fact with CONFIRM so the owner verifies it before publishing.
6. Append the HTML details elements and the JSON-LD FAQPage block when markup is requested, matching the questions exactly.

## Inputs

- **Product or service name** (free text, e.g. "Name")
- **What it is and how it works** (longer free text)
- **Target audience** (choose one: Tech-savvy users, General consumers, Enterprise B2B, Beginners)
- **Focus areas to cover** (choose any: Pricing and Billing, Account Setup, Troubleshooting, Security and Privacy, Shipping and Returns, Compatibility)
- **Number of FAQs** (number from 3 to 15)
- **Tone of answers** (choose one: Helpful and Friendly, Formal and Legal, Short and Direct)
- **Also output HTML and JSON-LD markup** (choose one: Yes, No)

## Output

Question and answer pairs grouped under focus-area headings in buying-decision order, then optional HTML and JSON-LD blocks, with CONFIRM on any answer that needs a fact from the owner.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### FAQ Section

Write an FAQ section for the product below that a visitor can use to answer their own question in under a minute, and that removes the doubts that stop a purchase or sign-up.

### Product
- Product or service name: {{Product or service name}}
- What it is and how it works: {{What it is and how it works}}
- Target audience: {{Target audience}}

### FAQ parameters
- Focus areas to cover: {{Focus areas to cover}}
- Number of FAQs: {{Number of FAQs}}
- Tone of answers: {{Tone of answers}}
- Also output HTML and JSON-LD markup: {{Also output HTML and JSON-LD markup}}

Write the questions as the visitor would type them, in first person where natural ("Can I cancel any time?"), and order them by the stage of the buying decision: what it is, who it is for, price, setup, security, what happens when things go wrong. Spread the questions across the selected focus areas and skip any area the product description does not support. Answer each in two to four sentences: the direct answer in the first sentence, the condition or exception in the second, and a next step or link placeholder where one belongs. Match the tone chosen for the audience, with no marketing language in a legal tone and no legalese in a friendly one. Mark any answer that depends on a fact not supplied (a refund window, a data location) with the word CONFIRM so the site owner checks it before publishing. When markup is requested, append the same FAQs as HTML details elements and as a JSON-LD FAQPage block.

### Output
A markdown list of question and answer pairs in buying-decision order, grouped under the focus area headings, followed by the HTML and JSON-LD blocks when requested, with CONFIRM on any answer that needs a fact from the owner.

## Pitfalls

- Inventing a refund window or data residency to make an answer sound complete, which becomes a published promise.
- Writing questions nobody asks ('Why is our product the best?'), which reads as marketing and gets skipped.
- Letting the JSON-LD text drift from the visible FAQ, which search engines treat as spam markup.
