WritingCollectible prompt
FAQ page that answers questions before people ask
Act as a customer-focused web writer. Write the FAQ page for {{business_name}}, a {{business_type}} whose customers are mostly {{target_audience}}. Facts, policies and details you can use: {{business_details}}
Write 15 to 20 questions:
- Phrased the way customers actually ask, including the awkward ones about price, cancellations, refunds and delays
- Grouped under three to five headings, such as Booking, Pricing and payment, Before your visit, and Policies, with the most-asked first in each
- Each answer gives the direct answer in its first sentence, then adds detail in 80 words or fewer
- Each answer links to the page where people can act, such as booking or contact
- Warm and plain, with no legal-sounding hedging
Use only the facts I've given. When an answer needs a detail I haven't provided, write it with a clear note saying what to confirm.
Also return a two-line intro for the top of the page, a contact line for anything not covered, and a title and meta description. Lay the page out with each question as a real heading and jump links at the top, and write for people rather than for FAQ markup, which now earns rich results for very few sites.
Ask me which questions I hear most often if you need more to go on.
Writingnvoka.com/library/nvoka-faq-page-for-your-websiteScan to open
Writing
FAQ page that answers questions before people ask
Write an FAQ page in your customers' words, with direct answers grouped so people find them fast.
Curated by Nvoka
ChatGPTClaudeGemini
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 4 filledYour prompt
Act as a customer-focused web writer. Write the FAQ page for {{business_name}}, a {{business_type}} whose customers are mostly {{target_audience}}. Facts, policies and details you can use: {{business_details}}
Write 15 to 20 questions:
- Phrased the way customers actually ask, including the awkward ones about price, cancellations, refunds and delays
- Grouped under three to five headings, such as Booking, Pricing and payment, Before your visit, and Policies, with the most-asked first in each
- Each answer gives the direct answer in its first sentence, then adds detail in 80 words or fewer
- Each answer links to the page where people can act, such as booking or contact
- Warm and plain, with no legal-sounding hedging
Use only the facts I've given. When an answer needs a detail I haven't provided, write it with a clear note saying what to confirm.
Also return a two-line intro for the top of the page, a contact line for anything not covered, and a title and meta description. Lay the page out with each question as a real heading and jump links at the top, and write for people rather than for FAQ markup, which now earns rich results for very few sites.
Ask me which questions I hear most often if you need more to go on.