FAQ Page From Real Questions

Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.

Build an FAQ page for [PRODUCT/SERVICE/TOPIC].

Real questions people ask me:
"""
[PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.]
"""

Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES]

Do this:
1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicates that differ only in wording, and keep the phrasing closest to how a real person types it, including the awkward ones. Discard nothing as "too basic": the basic questions carry the most volume.
2. **Rank** the clusters by how often they appear and how much they block a purchase or a support resolution.
3. **Write** the top [12-20] as question and answer pairs:
   - The question is a heading, phrased as the reader would say it.
   - The first sentence of the answer IS the answer. Direct, complete, and quotable on its own with no preceding context, because that sentence is what an AI answer engine will lift.
   - Then 1-3 sentences of detail: the exception, the number, the next step.
   - Link out where a full guide exists rather than expanding to 400 words.
4. **Group** the finished questions into 3-5 sections and order them the way a reader progresses: before buying, during setup, after something goes wrong.
5. **Flag** any question where my facts do not contain the answer as [NEEDS ANSWER: question]. Do not write a plausible answer for it.

Rules: answer the question that was asked, not the question you wish had been asked. If the honest answer is unflattering ("no, we do not support that"), say it plainly and say what to do instead. An FAQ that dodges is worse than no FAQ.

How to use

The 'first sentence is the answer' rule is doing double duty: it is what impatient readers need and it is exactly the shape AI search engines and featured snippets extract. Write it so it survives being quoted with no surrounding context. Feed the model raw ticket text rather than your summary of it, since your summary has already lost the phrasings people actually search for. Revisit the [NEEDS ANSWER] list quarterly; it is a map of where your product or policy is genuinely undefined.

Originated fromStan SedberryUpdated
SEO contentbeginner

More writing prompts

Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"].

Target reading level: [e.g. "8th grade" / "as simple as the content allows"].

How to rewrite:
- Lead with what the reader must DO or what happens to them. Background comes af

Plain Language Rewrite

Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.

Writingbeginner
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"].

Options to compare: [LIST 2-8 OPTIONS]
Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE]
My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"]
Facts I can su

Comparison Article

Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.

Writingintermediate
Create the metadata package for this YouTube video.

Video transcript or outline:
"""
[PASTE TRANSCRIPT WITH TIMESTAMPS IF YOU HAVE THEM, OR THE OUTLINE]
"""

Channel and audience: [WHO WATCHES, WHAT THEY EXPECT FROM YOU]
What someone would search to find this: [1-3 PHRASES, OR "you tell me"]

Produce:

1. **Titles**: 8 options under 60 c

YouTube Metadata Pack

Generate ranked title options, a search-optimized description, and accurate timestamp chapters from a transcript or outline.

Writingbeginner

Search prompts

Find a prompt by title, description, tag, or category.