The gap between a typed query and a spoken one is bigger than most FAQ content accounts for: people ask a phone assistant in full sentences, not fragments. This prompt writes questions the way they’d actually be spoken and answers that front-load the direct answer, since a voice assistant reads one extracted sentence with no surrounding page context.
SEO
Write a voice-search-optimized FAQ section
A prompt for drafting FAQ answers phrased the way people actually speak to a voice assistant, structured to be extractable as a single spoken answer.
Works with Claude / GPT1,480 uses★ 4.3
The prompt
seo-voice-search-faq
[yourdomain.com] runs a local bakery and wants an FAQ section on its "[custom
birthday cakes]" page optimized for voice queries like "how far in advance do I need
to order a custom cake" and "how much does a custom birthday cake cost," the kind of
thing someone asks a phone assistant while planning a party, not typing into a
search box.
PAGE TOPIC: [custom birthday cakes, local bakery]
KNOWN CUSTOMER QUESTIONS (from staff/calls, paste any real ones): [paste here]
ACTUAL BUSINESS DETAILS (lead time, pricing range, size options): [paste here]
Write these the way someone optimizing for a spoken answer, not a scanned page,
would:
1. Phrase each question the way a person would actually say it out loud to a voice
assistant ("how far ahead do I need to order a cake") rather than how they'd type
it into Google ("custom cake order lead time"), since spoken queries are longer
and more conversational than typed ones.
2. Write each answer as a single self-contained sentence or two that would make
sense read aloud with zero visual context, no "see the chart below" or "as
mentioned above," since a voice assistant reads one extracted answer with nothing
else from the page.
3. Lead each answer with the direct answer in the first few words (e.g. "Order at
least 5 business days ahead for a custom cake" not "Great question! There are a
few factors that go into..."), since assistants tend to truncate or extract only
the opening of a long answer.
4. Use the real business details provided, don't invent a lead time or price range
if none was given, say which questions can't be answered yet and need real
numbers from the business before publishing.
5. Add FAQPage schema for these Q&As, matching the visible text exactly, and note
that voice assistants often source spoken answers from the same structured data
and featured snippets Google surfaces on desktop, so this content should also be
checked against what currently appears in a featured snippet for these queries,
if one exists.