Learn how to optimise your website content for voice search with plain-English fixes, real examples and a checklist. Chat to Sage Writers when you're ready.
The voice search problem most sites ignore
Eight in ten homepages we audit read like a Scrabble tile rack — keyword-stuffed, comma-splice-heavy, and physically impossible to say out loud without running out of breath. That’s fine when your customer is typing into Google on a laptop. It’s a disaster the moment they’re driving, cooking, or asking Alexa on the kitchen counter.
Because here’s the thing about voice search. Alexa, Siri and Google Assistant don’t read ten blue links. They read one answer, out loud, in a friendly voice. If that answer isn’t yours, you’re not on page two — you don’t exist at all.
So this is a teardown, not a schema jargon dump. Six moves, plain English, the same approach we use at Sage Writers with clients who want to be the answer instead of a footnote.
How voice search actually works
Typed queries are stubby. “Teeth whitening cost.” “Best B&B Cotswolds.” Voice queries are longer, chattier, and shaped like actual sentences a human would speak. “How much does teeth whitening cost near me?” “What’s a good B&B near Bourton-on-the-Water for a couple?” Assistants parse those queries, pull from the top-ranking pages, and read a single passage aloud — usually the featured snippet or a People Also Ask box. Google explains the mechanics in its own Search Central documentation.
How is voice search different from typed search?
Voice queries run 20-30% longer than typed ones and lean on natural, conversational phrasing — full questions instead of stubby keywords. Intent is usually immediate: the user wants one answer, right now, not a list to browse. The assistant reads a single passage aloud, so pages that structure content into short, standalone answers win. Pages built for scrolling and scanning don’t get a look-in.
Quick tip — if your answer can’t be read aloud in about 30 seconds, it won’t be. Assistants cut off long-winded pages before your best sentence lands.
Write the way people actually ask
The single biggest win here is boring and free: rewrite your headings as full questions. Who, what, where, why, when, how, is, can, does. Then answer each one in a rhythm a human would actually use — contractions, short clauses, one idea per sentence.
Here’s what that looks like in practice.
| Keyboard phrasing | Voice phrasing |
|---|---|
| Teeth whitening cost Birmingham | How much does teeth whitening cost in Birmingham? |
| Late invoice chase email | What’s the best way to chase a late invoice? |
| Best coffee shop Digbeth open now | Where’s a good coffee shop in Digbeth open right now? |
The read-aloud test — if you can’t say the sentence in one breath, cut it. Full stop. This is the single rule that fixes 80% of voice-hostile copy.
Structure content for the 40-60 word answer
Voice assistants love a specific shape of paragraph. Direct, standalone, 40-60 words, sitting near the top of a section so the crawler doesn’t have to dig for it. That’s the featured-snippet sweet spot, and it’s also what gets read aloud.
We teach clients a four-step pattern:
- Restate the question in the answer’s first clause so it stands alone.
- Give the answer in one clean sentence.
- Qualify briefly — one caveat, one example, one number.
- Stop. No throat-clearing, no “hope this helps”.
What word count works best for a voice search answer?
Aim for 40-60 words. That’s roughly 25-30 seconds of natural speech — long enough to answer properly, short enough that an assistant will read it in full. Anything over 80 words gets truncated mid-sentence. Anything under 30 sounds thin and rarely wins the snippet slot. Write the answer first, then edit for rhythm, not the other way round.
Place the answer near the top of the section, not buried three paragraphs down. If you want a deeper primer on writing for search, our take on small-business SEO copywriting covers the mechanics without the jargon.
Three real rewrites (anonymised)
Three client rewrites from the last twelve months. Names changed, structure identical.
Example 1 — A Birmingham dental practice
Before (keyboard):
Teeth whitening cost varies depending on a number of factors including the type of whitening treatment selected, the severity of staining, and additional consultation fees which may apply.
After (voice):
How much does teeth whitening cost in Birmingham? At our practice, professional whitening costs £295 for the full in-chair treatment, including a consultation and a top-up kit. Home whitening trays are £195. Prices haven’t changed since 2024.
The rewrite is shorter, opens with the question, and gives a real number. Alexa can read it. The old version can’t.
Example 2 — A Cotswolds B&B
Before: Three paragraphs of moody prose about “nestled countryside charm” before mentioning the town. After: “Where’s a good B&B near Bourton-on-the-Water? We’re a six-room guesthouse in Lower Slaughter, twelve minutes’ walk from Bourton, with off-street parking and a full Cotswold breakfast. Rooms from £120 a night, dogs welcome in two of them.”
Example 3 — A SaaS invoicing tool
Before: A pillar page on “accounts receivable optimisation” that never used the phrase “late invoice”. After: The H2 became “How do I chase a late invoice without annoying the client?”, and the 55-word answer sat directly underneath. Impressions on that page tripled inside a quarter.
In every case: shorter, more specific, sounds like it came out of a mouth.
The technical bits that actually matter
We’re going to be honest — the technical layer is smaller than most SEO blogs pretend. Three things carry real weight.
- Schema markup. FAQPage and HowTo, kept short. Mark up genuine Q&As, not every paragraph. Schema.org has the full vocabulary.
- Page speed. Assistants time out on slow pages. Core Web Vitals — especially LCP and INP — need to be green.
- Local signals. NAP consistency across your site, Google Business Profile, and directories decides who wins “near me” queries.
Do I need FAQ schema for voice search?
Not strictly, but it helps. FAQ schema doesn’t give you a magic voice-search boost on its own — Google confirmed that years ago. What it does is make your Q&A content easier for crawlers to parse, which improves your odds of being picked as the snippet an assistant reads aloud. Use it on pages with genuine, distinct questions. Don’t paste it onto pages that don’t have them.
A warning: schema is a hint, not a hack. Marking up content that isn’t really a Q&A gets you a manual action, not a ranking.
Why Sage Writers writes for voice by default
Most agencies bolt “voice search” on as an upsell. We don’t, because writing for a real human mouth is what we do anyway. Every draft goes through a read-aloud pass before it leaves the studio — one senior UK writer, no AI-mills, no offshore rewrites.
You get a fixed-price brief, a first draft in five working days, and two rounds of revisions included. No hidden hourly creep. Our website content writing services cover homepage, service pages and long-form together, and our approach to search engine optimisation content writing bakes in the voice-shaped structure from the outline stage — not as a last-minute polish.
Small studio, real humans, work you can actually read out loud.
What to ship today
You don’t need to commission a full rewrite this afternoon. Thirty minutes and one page will get you 80% of the way there.
- Pick your highest-intent page (usually a service or product page).
- List five real questions customers ask you on the phone.
- Rewrite the first H2 as one of those questions.
- Draft a 50-word answer using the four-step pattern above.
- Read it aloud. If you stumble or run out of breath, cut it.
- Publish. Come back next week and do the next question.
Read it aloud, or don’t publish it. That’s the whole methodology, honestly.
If you’d like a second pair of eyes on what’s live now — or a hand rewriting the top three pages so they earn their place in the assistant’s mouth — Get a free quote and we’ll send one over within a working day.