Voice Search: How Australians Search Out Loud

Thirteen years in, I still meet Australian owners who have been sold a voice search package and cannot say what changed on their site. The invoice was real. The work, in most cases, was not.

Here is the honest position. You cannot see how often people speak a query in any tool I trust, and much of what circulates online about it is recycled guesswork. What you can do is understand how spoken questions differ from typed ones and make your pages easier to answer from.

This is for the owner or marketing manager who wants to know whether voice search deserves attention and what, concretely, it changes about the words on their pages and the local details they publish. It covers how spoken queries differ, what the Australian evidence actually shows, why the answers come from pages that already rank, what that means for your content and your local information, and the things that are not worth doing at all.

What voice search really is

Spoken queries, typed queries and the difference

Voice search is simply a query that is spoken rather than typed. The difference that matters is not the technology. It is the wording. People speak the way they talk, and they type the way they abbreviate.

Typed search has always leaned towards shorthand, because typing is effort. Speech removes that effort, so a spoken query tends to be a full question in ordinary language.

Why you cannot see voice search numbers anywhere

No tool separates spoken queries from typed ones in a way you can rely on. Search Console does not show them apart, and third party tools cannot measure them properly.

That is why I treat any published voice search figure with caution. Where a number exists, it is usually an estimate, or it is years old. The practical approach is to focus on the behaviour you can act on and ignore the numbers you cannot verify.

How spoken queries differ

Longer, conversational phrasing

A spoken query is longer and more conversational than a typed one. The same need becomes a full sentence with the question words included, rather than two or three keywords pushed together.

For your pages, that means writing for the question rather than the fragment. A heading that reads like the question, followed by a plain answer, matches how the query is actually spoken.

Question words and local intent

Spoken queries often open with the question words: who, what, where, when, how, which. Many of them also carry local intent, because spoken searches happen in places and moments where location matters.

The local questions are the commercially useful ones. Opening hours, whether you cover a particular suburb, what something costs, whether you can come today. Those are the questions people ask out loud, and they are the ones a clear answer on your page helps most.

Why people ask out loud what they never type

Speech removes the friction of typing, so people ask things they would not bother to type. A quick question about a business nearby, asked from a kitchen or a car, is a natural spoken query and an unlikely typed one.

That difference is the whole opportunity. The answers are ordinary, useful pieces of information about your business that many sites never bother to state plainly.

What Australians use voice for

What the Australian data shows

The Australian evidence is older than I would like, and I would rather give you a dated real figure than a current invented one. Per YouGov, "42% of Aussies use voice assistants", reporting the Smart Audio Report by Edison Research and Commercial Radio Australia, published on 13 July 2021.

The scale of that report is worth noting. Per YouGov, "The Smart Audio Report, by Edison Research and Commercial Radio Australia, surveyed 5,000 Australian adults."

Usage elsewhere is not shrinking either. Per the Ahrefs blog, "Google states that 41% of adults and 55% of teens use voice search daily." Treat reach as established and treat any claim about the exact share of searches as unproven.

Devices and where they sit in the home

Voice use is tied to devices, and in Australian homes the phone is still the most common one. Per the Australian Bureau of Statistics, "Similarly, mobile or smart phones are also used by 91% of connected households." That figure comes from the 2016-17 reference period, and the series has since ceased, so it is the most recent ABS figure of its kind rather than a current one.

The practical read is that voice queries happen on phones as much as on speakers. If your pages work well on a phone and answer ordinary questions plainly, the device question largely takes care of itself.

Why the answers come from pages that already rank

Where spoken answers are pulled from

Spoken answers are not drawn from a separate pool of pages. They come from the results that already rank well for the query.

Per the Ahrefs blog, "In fact, almost 91% of voice search results come from the top five pages." That single sentence tells you where the work is. You improve pages you already have, rather than building new ones for a channel nobody can measure.

The role of the answer box

A large share of spoken answers come from the featured snippet, which is the answer box we have covered in its own right. Per the Ahrefs blog, "According to this analysis of 10,000 Google Home search results, 40.7% of voice search answers come from the featured snippet."

So the content work overlaps heavily with winning the answer box: a direct answer, under a question-shaped heading, written plainly enough to be read out.

What this means for your page content

Answer first, then explain

Put the answer before the explanation. A person asking out loud wants the answer, not the context, and a page that answers first is easier to read and easier to lift.

This is the same habit that helps every other part of search. Nothing about it is specific to voice, which is part of why it is worth doing on its own merits.

Plain language a person would say out loud

Write the way a person speaks. If a sentence sounds unnatural when you say it out loud, it will not match a spoken query either.

That does not mean dumbing the content down. It means removing the padding and the jargon that nobody uses in conversation, and saying the thing directly.

Keeping answers short enough to be read aloud

Spoken answers are short. Per the Ahrefs blog, "Google doesn't give a definitive number, but one study found that the average Google Home answer is 29 words."

That is a sensible target for the first sentence or two of an answer. Give the short answer, then continue with the detail for the reader who wants it.

What it means for your local information

Hours, location and phone details

The questions people ask out loud are usually factual and often local. Your opening hours, where you are, which areas you cover, and how to reach you are exactly the details a spoken query wants.

State them clearly and in text on the page. Details that only exist inside an image, a script or a map embed cannot be read and cannot be answered.

Consistency between your site and your listings

Your details should match wherever they appear. If your hours on the site differ from your hours in a directory listing, there is no single correct answer for a spoken response to give.

Pick one set of details, put them everywhere, and update them in the same pass when something changes. Consistency is dull work, and it is the part that most often improves the answer.

What is not worth doing

Pages built for questions nobody asks

Do not build a page for every question a customer might ask. That approach creates thin pages and duplicates the ground you already cover.

Improve the pages you already have, and create a new page only where a question genuinely deserves its own answer. Most questions belong as a section on a page that already exists and already ranks.

Stuffing phrases that no one says

Do not fill a page with question phrasings that nobody would ever speak. A page built to catch awkward variants reads badly to a person and rarely matches a real query.

Use the plain words a customer would use in conversation. If you would not say it to somebody standing in front of you, it does not belong on the page.

A practical voice search checklist

Read your own pages out loud

Open your home page and your contact or location details, and read them out loud. Where a sentence sounds wrong when spoken, fix the sentence. Where the answer to an obvious question is buried, move it up.

Then check the details people ask about most: hours, location, coverage, phone. If any of them is missing, or expressed in a way that would not make sense in a single spoken sentence, that is your next fix.

Where to go from here

Most of this work also helps the ordinary search results, so it is not effort spent on a single channel. If you want the local side done properly, local SEO for the questions people ask out loud covers it, and if you are working on this from Melbourne, that is the market I know best. There are answers to the questions I am asked most already written down, and if you would like a second opinion on your own pages, you can ask me how your pages read out loud.

Frequently asked questions

How many people use voice search?

I will not give you a figure for the share of searches that are spoken, because nobody credible publishes a current one and the widely repeated numbers are years old. What I can tell you is that Australian ownership and use of voice assistants is well established: YouGov's coverage of the Smart Audio Report, which surveyed 5,000 Australian adults, reported that 42% of Australians use voice assistants. Treat reach as real and the exact scale as unmeasurable.

Can I see voice search data in Google Search Console?

No. Search Console does not separate spoken queries from typed ones, and no third party tool can measure it reliably. Anyone who shows you a voice search number is showing you an estimate.

So what should I actually change?

Make your pages easier to answer from. Put a direct answer immediately under a question style heading, use plain words a person would say out loud, keep the answer short enough to be read aloud, and make sure your hours, location and phone number are stated clearly and consistently.

Which queries matter most for voice?

The ones with local intent and a decision attached: opening hours, services offered, whether you cover a particular suburb, how much something costs. These are the questions people ask out loud and the ones where a clear answer on your page helps most.

Should I create a page for every question a customer might ask?

No. That approach creates thin pages and duplicates the ground you already cover. Improve the pages you already have, and only create a new page when a question genuinely deserves its own answer.

Does a fast site matter for voice search?

Page speed matters for search generally, and fast pages correlating with the pages that get read out is a reasonable expectation rather than a separate technique. Do not treat a number as a voice search target. Build a fast site for your customers and let the rest follow.