# Turn launch comments into an FAQ

> Group the questions people asked on launch day and turn them into an FAQ on the pages where they come up.

Canonical: https://abacklaunch.com/prompts/comments-to-faq
Last updated: 2026-10-26

Version 1.0.

Launch comments, replies and support emails about the production site are the best list of questions real people have. Turn them into an FAQ: grouped, answered plainly, and placed on the pages where each question comes up, so the next visitor gets the answer before they ask.

Site: not given. Find the production URL in the project config, or ask me.

## Ground rules

1. Read before you write. Explore the parts of the codebase this job touches and tell me what is already in place.
2. Plan, then stop. Give me a numbered plan: what you will change, in which files, and why. Wait for my approval before editing anything.
3. Fix things at their source (the shared layout, the config, the generator), not with one-off patches page by page.
4. Keep the project's conventions: its framework APIs, file layout, naming and code style. Add no new dependency without asking.
5. Where something is already done well, say so and leave it alone.

## You will not

- Edit `.env` files, secrets or API keys, or print their values.
- Deploy, push, merge or publish anything.
- Delete data, or run migrations or scripts against a production database.
- Add tracking, third-party scripts or links to any site I did not ask for.
- Change copy, design or behaviour that this job does not need.
- Publish answers I have not approved.
- Include commenters' names or personal details.

## Your stack

- Framework: Work out the framework, router and build output from the project files (package.json, lockfiles, framework config) before planning, and say which you found.
- Host: Work out where the site is hosted from the config files (vercel.json, netlify.toml, wrangler config, Dockerfile, fly.toml) and say which you found.

## Steps

### 1. Collect the questions

Ask me to paste the launch comments, replies and support messages, or point you at an export. Pull out every question and objection, merge duplicates, and count how often each came up. Leave out names and anything personal.

### 2. Group and answer

Group questions by topic (pricing, privacy, integrations, how it compares, limits). Draft an answer for each that starts with the answer, names the product, and uses only facts from the code, docs or my earlier replies. Show me the list with drafts before building.

### 3. Place them

Put each group where the question comes up: pricing questions on the pricing page, security on a security or privacy section, the top five on the homepage. Store FAQs as data so one answer can appear in several places without being copied.

### 4. Mark them up

Add `FAQPage` JSON-LD that matches the visible questions and answers on each page, using the existing structured data helper.

## Done means

- [ ] Every question from the launch is collected, merged and counted, without personal details.
- [ ] Each has an answer I approved, based on real facts.
- [ ] FAQs are stored as data and shown on the pages where they come up.
- [ ] FAQPage JSON-LD matches the visible FAQ on each page.

## Report back

When you finish, give me:

- what you changed, file by file;
- anything you skipped, and why;
- anything I must do by hand (DNS records, dashboards, accounts, deploys);
- how to check each change on the live site.

## Related

- [Triage launch feedback into issues](https://abacklaunch.com/prompts/feedback-triage)
- [Definition and FAQ blocks that answer engines can quote](https://abacklaunch.com/prompts/answer-ready-content)
- [A testimonial wall from real reviews](https://abacklaunch.com/prompts/testimonial-wall)