The essentials
- Definition: voice search means putting a query out loud, through an assistant (Google Assistant, Siri, Alexa, Gemini, ChatGPT in voice mode), which reads out or displays an answer.
- Real uses: local queries ("pharmacy open near me"), quick questions, commands; above all on mobile and in the car.
- What it changes: queries in natural language, a single answer read out, the importance of the Google listing and of featured snippets.
- Useful optimisations: a complete Google listing, a FAQ in spoken language, short answers, mobile speed, structured data.
Enhanced measurement Voice search is querying an engine or an assistant by voice. Announced as dominant back in 2016 ("50% of searches by 2020"), it hasn't become so, but it holds a real place on mobile, in the car and at home, and it now blends into conversational AI assistants. This article takes stock of the measured uses, of what changes for SEO, and of the optimisations with a demonstrable effect, particularly in local.
The real uses in 2026
| Context | Typical queries | Expected answer |
|---|---|---|
| Mobile, on the move | "Bakery open near me", "directions to…", "call Martin's garage" | A Google listing, a call, directions |
| In the car | "Nearest petrol station", "opening hours of the duty pharmacy" | An answer read out, immediate action |
| At home, a speaker | "How long to boil an egg", "the weather", "what is GEO" | A sentence read out, taken from a featured snippet or generated by AI |
| An AI assistant in voice mode | Complex questions, conversation, comparisons | A synthesised answer with sources, as in text |
Usage studies (Statista, Comscore, Google) indicate that around one adult in four uses voice at least weekly to search, mostly on a smartphone, and that most voice queries are local or practical. Voice search isn't a separate channel: it is a way of phrasing queries that the engines handle like any other, with two particularities, natural-language phrasing and a single answer.
What voice changes for SEO
- Long, interrogative queries: "when is the best time to trim a hedge" rather than "hedge trimming season". Pages answering naturally phrased questions are favoured.
- A single answer: the assistant reads one result, generally the featured snippet (see position zero) or an AI synthesis. There is no second place.
- Local first: "near me" and "open now" queries draw on the Google Business Profile listing: hours, category, address, phone. An incomplete listing is invisible to voice.
- Actions: call, book, order, get directions: voice favours listings and sites with clickable actions.
- Speed: the pages cited in a voice answer load fast; voice is almost always mobile.
The optimisations that have an effect
| Optimisation | Why | Where to go deeper |
|---|---|---|
| A complete Google Business Profile listing: category, hours (including exceptional ones), phone, attributes | It is the source of local voice answers | Optimising your listing |
| A FAQ written in customers' spoken words | The spoken question matches the subheading, the short answer is read out | What content to create locally |
| 30- to 50-word answers under each question | The length of the extracts assistants read | Position zero |
| LocalBusiness, FAQPage and Speakable structured data | Helps assistants identify hours, address, answers | local Schema.org |
| Mobile speed and HTTPS | Slow pages aren't chosen to be read out | Complete SEO audit |
| A clickable number and online booking | Voice leads to action | |
| Conversational content for AI assistants | Voice AI assistants cite the same sources as in text | Optimising for conversational intent |
What serves no purpose
- Creating "voice search" pages or content dedicated to voice: the engines don't distinguish the query's source.
- Stuffing texts with "OK Google" or "Hey Siri" phrasings.
- Targeting separate "voice" keywords: keyword tools don't isolate them, and long spoken queries attach to the existing short ones.
- Buying "voice optimisation" as a separate service: it is local SEO and well-structured content, nothing else.
Measure
No tool isolates voice queries: Google doesn't supply the modality in Search Console. The indirect clues are the share of long interrogative queries in Search Console, calls and directions from the Google listing (the listing's statistics), and the featured snippets held on questions. General tracking is described in the local SEO KPIs. In practice, a local business that is clearly visible in the local pack and holds a few snippets is properly positioned for voice, with no specific measurement.
How GreenRed helps
Rather than juggling several tools, GreenRed's Google Business Profile module brings these metrics together in a single dashboard, compares them over time and tells you which actions come first. You can try it free, with no card, from the Pricing.
Frequently asked questions
Does voice search really account for a large share of searches?
A real but minority share: around one adult in four uses it weekly, mostly on mobile for local and practical queries. The prediction of "50% of searches by voice" didn't come true. Its importance depends on your business: high for a local shop or service, low for a B2B site.
Do you need specific content for voice search?
No. Assistants draw on the same pages and the same listings as text search. What helps voice also helps text: questions as subheadings, short answers, a complete Google listing, structured data, mobile speed.
How do you appear in Siri, Alexa or Google Assistant answers for a local search?
Siri and Google Assistant draw on Apple Maps and Google Maps; Alexa on Yelp and Bing. Claim and complete your Google Business Profile listing, your Apple Business Connect listing and your Bing Places listing, with the same hours, address and phone. Reviews and the category determine which business is offered.
Is Speakable markup useful?
Speakable (Schema.org) marks the passages of a page suited to being read aloud. Google limited it to news publishers and its use remains marginal. For a business, LocalBusiness and FAQPage have more effect.