Voice search SEO: what still matters now assistants answer in sentences

Voice search still matters for the tasks that already matter to your business. That means being found, open when the assistant says you are, and easy to call or book. It's neither dead nor a separate channel with its own ranking system.

What helps everywhere is accurate business facts, clear answers and customer actions that work on a phone.

Does voice search still matter for Australian businesses?

It's worth making accurate information and useful actions available wherever customers use speech. It's not worth building a separate "voice strategy" around a channel nobody can measure. Prioritise the tasks that already drive enquiries. After all, those are the ones people speak into a phone, a car or a speaker.

The Australian evidence is thinner than the statistics industry would like. The best recent measure is smart speaker ownership. Its source is ACMA's How we use the internet research, published in February 2026.

That's device ownership among Australian adults. It's not households, not daily voice searchers, and not a share of searches. Owning a speaker isn't the same as using the assistant. And using the assistant isn't the same as searching for a business.

Speakers are also only one place people talk to an assistant. Phones and cars carry assistants too. ACMA's figure covers neither.

Keep voice input separate from AI processing. "Hey Google, who does emergency plumbing in Brunswick?" is a spoken request. Where the answer comes from is a processing question. It could be Maps, a web search, an AI generated summary or the assistant's own records. Our guide on what AI changes about search covers the bigger picture.

Two groups make the case for caring without any statistics at all. People who can't type or see well use speech as their main way in. A business an assistant can't describe correctly is closed to them.

And everyone is hands busy sometimes: driving, cooking, holding a child. The customer who asks a car for the nearest open tyre shop at 5pm is not browsing. They are choosing.

How do voice assistants find business information?

Each assistant understands the speech and works out the task and the context. If it needs to, it retrieves information or hands off to a connected service. Then it responds or acts. Some requests never touch the web. A spoken answer doesn't have to repeat the top blue link, and often doesn't.

That's a simplified model, not the published architecture of any assistant. The platforms differ in what they draw on. Those differences decide where your facts need to be right.

The detail behind each row is documented. But the documentation moves. Google's help page on places in Gemini says the feature uses public information from Google Maps. It needs a signed in account with Keep Activity on. And it isn't available in Live chats.

In March 2025, Google said it was upgrading Assistant users on phones to Gemini over the following months. Its Gemini for Home announcement for Australia opened early access on 10 April 2026. Google kept "Hey Google" as the wake phrase.

Apple's Apple Business announcement pitches it for reaching local customers across Apple Maps, Siri and other Apple apps. It replaced Business Connect when it launched on 15 April 2026, carrying existing Business Connect data across. Apple's data isn't the only thing behind Siri, though. With the ChatGPT extension on, Siri can draw on ChatGPT for more detailed answers. Apple's guide to using ChatGPT with Apple Intelligence explains how.

Amazon's Alexa+ announcement for Australia opened early access on 5 August 2026. It names OpenTable for restaurant bookings. So a booking question can end with a partner, not a web page.

OpenAI's ChatGPT Voice help says its Live voice option can use web search. When it does, a spoken question is answered from the pages the assistant finds. That makes it a question of generative engine optimisation (GEO), not of listings. Availability and features change by market. So check each assistant on your own devices.

Cars deserve a line of their own. Google announced its Gemini in Maps navigation update on 5 November 2025. It lets a driver ask hands free for places along the route. They can also ask what parking is like at the destination, or which dishes are popular there.

Google said it would roll out everywhere Gemini is available, without naming Australia. So confirm it on an Australian phone before relying on it. Either way, your Maps facts answer those questions, down to the parking and what you sell.

That's a lot of change in under 18 months, with no single pipeline behind it. The common mistake is to picture one that every assistant shares, where fixing Google fixes everything. It doesn't. When an assistant gets you wrong, find the source behind that answer and correct it there.

Earning a source link inside a Google AI answer, spoken or typed, is a separate job. Our guide on how to get cited in Google AI search covers it.

Which business facts should you fix first?

The ones a customer acts on in the next ten minutes:

• whether you're open

• what you do

• where you are or where you go

• how to reach you

An assistant that reads a wrong opening time sends a customer to a locked door. It will keep doing so until the source is corrected.

Work through the list for an eligible local business:

• Business identity: the real world name, without added keywords, matching the sign on the door. Google's guidelines for representing your business ask for your trading name, as used on your storefront and signage. A harmless abbreviation on one listing isn't the same as a wrong name.

• Location or service area: a genuine office or shopfront, or a service area for a business that travels. A virtual office won't get an online only business a profile, because Google treats that address as ineligible. Useful location pages are fine, but don't create a thin page for every suburb you might visit. Google's spam policies count region or city pages that funnel visitors to one page as doorway abuse. The full location and service area strategy is in our guide to local SEO for small businesses.

• Hours: normal, special and service hours, kept current. Open hours are not appointment capacity. If a clinic is open until 6pm but booked out, the booking link needs to say so.

• Primary category and services: an accurate category describes the core business. The services list should match the website. Google's local ranking guidance explains relevance, distance and prominence without any universal weighting for one field. So set the category accurately and move on.

• Prices or cost factors: where you can support them. "From $X" without conditions creates an answer you will be held to.

• Accessibility facts: step free entry, accessible toilets, parking and dietary arrangements, in precise terms. "Accessible venue" is a label. "Step free entry from Smith Street, accessible toilet on the ground floor" is a fact an assistant can repeat.

• Contact and booking: the published phone number, the tap to call action and the booking route. Test them on a real phone this week.

Those facts live in more than one place. Google's page on how it sources business information lists what it draws on:

• public information such as your website

• licensed data from third parties

• contributions from users

• Google's own interactions with the business

So a wrong fact on a directory can outlive the correction on your profile. Our Google Business Profile guide covers setup and upkeep.

You control the first three directly. The rest you can only claim, correct or answer. So check them for substance rather than identical formatting. "St" on one listing and "Street" on another is harmless. A wrong suburb or an old phone number is not.

Where a material inconsistency exists, see our guide to local citations and directories. It covers which listings still matter and how to correct them. For the broader local picture, Google Maps ranking factors explains how relevance, distance and prominence play out.

The checker's result is a local readiness view. It's not a voice ranking, and not proof that any assistant will choose you. The checker also scores differently from the ten point readiness check in the 30 day plan below. That check is an editorial list. So don't add the two together.

Keep one record of what's true, with an owner and a review date for each fact. That way, a correction made in one place gets made in all of them. Our guide to generative engine optimisation has a business facts record you can copy. For voice, add the customer action you tested against each fact, such as the call or the booking.

Reviews belong here too, because genuine reviews are part of how assistants describe a business. The safe way to gather them is to ask every customer, without incentives or filtering. Our guide to getting more Google reviews legally sets out how. Don't script keywords into review requests. Assistants read what customers wrote, and so does the ACCC.

Then test the actions. Open your profile on a phone, tap call, tap directions, tap book. Business Profile's performance report counts a call as a call button click, not a connected conversation. So pick up the phone during business hours and listen to your own after hours message.

One more reason to answer. In May, Google's I/O 2026 Search updates said Search will call businesses on a person's behalf. The feature covers select categories, such as home repair and pet care. It's rolling out in the US. If that reaches Australia, the business that answers wins the booking.

Where the whole journey fails on a phone, the fix is a mobile one. Our guide to mobile SEO for Australian businesses covers the checks.

Which spoken questions should your pages answer?

The ones customers already ask you by phone and email. Group them by what they want, not by how they phrase it. Spoken questions tend to be longer and more natural than typed ones. Think "who can fix a hot water system today in Geelong" rather than "hot water repair geelong".

But not every spoken query is long. And voice doesn't need a keyword method of its own. Grouping by intent, rather than one keyword per page, serves typed searches just as well.

Collect the questions from real sources:

• sales calls

• support email

• the queries Search Console already shows for your pages

• the terms in your Business Profile performance report

• public research, as a supplement

These reveal language and needs. None of them proves a search was spoken. But you don't need that proof to act.

Then decide which page owns each question. Here is the method applied to an example Australian web design agency:

Related questions stay together. One cost guide owns the cost question, much like our own guide to how much a website costs.

Scope and timing belong to the service page. Our guide to service page SEO covers how to write one that answers them. Proof belongs with the work.

The split is a decision aid, not an instruction to make a page for every question. Start by assuming the answer belongs in a fact or a page you already have. A new page earns its place only when the question needs a different purpose. That page might be a cost guide or a comparison.

Our guide to site architecture for small businesses covers the page ownership logic in full. Start there if grouping questions into pages is new territory.

The needs differ by business, and so does the page that answers. These five rows are examples:

The last row is easy to miss. Stock questions are answered from product feeds and store data, not from a blog. So the feed in Merchant Center and the hours in the profile do the work.

The trade, clinic, firm, venue and retail rows each have a fuller version on our industry pages:

• SEO for tradies

• SEO for healthcare practices

• SEO for professional services

• SEO for hospitality

• SEO for ecommerce

How should you write answers and use structured data?

Answer first, condition second, evidence third, action last. Put all four in the first paragraph under a heading that asks the question. That order serves readers, snippets, spoken answers and AI summaries equally. Google's guide to optimising for generative AI features says you don't need a special writing style. Nor do you need to break content into tiny pieces to appear in those features.

Both passages are examples. The after version answers the question a customer would speak. It keeps the conditions beside the answer and gives the customer something to ask next. It shows clearer information, not a measured voice result.

Leave meaningful qualifications in. A concise answer can sit inside a detailed page. If you cut conditions to make a neat line, an assistant will repeat a neat line that's wrong.

Use sentence case question headings where they help and descriptive headings elsewhere. Google's featured snippet documentation says its systems decide which pages qualify. It also says you can't mark a page up to be a snippet. The formats that get lifted are a separate method. Our guide on how to get featured snippets covers it.

A snippet isn't the same as a spoken answer, either. An assistant may read a snippet, read from Maps data or use its own retrieval. It depends on the question and the device.

Two markup facts matter here. FAQ rich results stopped appearing in Google Search from 7 May 2026, as Google's Search documentation updates record. Helpful FAQ copy on a page still helps readers. Marking it up no longer earns a rich result. Our guide to schema markup for small businesses covers what markup still does.

And the speakable property remains a beta. Google's speakable documentation describes topical news playback on Google Home devices set to English. It's for users in the US, from publishers writing in English.

Ordinary markup still has a job. LocalBusiness, Organization and other relevant types should match the visible page. When they do, they help Google connect your name, address, hours and services to one entity.

Don't add every type to every page. Google's structured data guidelines require markup to be a true representation of the page. Even valid markup isn't guaranteed to show.

Validation proves the markup is well formed, not that the facts are true. Nor does it prove that any assistant will read them aloud. The schema markup generator builds the basic types. Your developer should check them against the published page.

How can you test answers and measure useful outcomes?

Test by speaking. Measure by counting customers, because no report tells you how many searches were spoken. Both halves need a log.

Choose a manageable sample of real customer tasks, five to ten. Run them on the devices and modes your customers use:

• a phone with Google

• Gemini on that phone

• Siri where your audience is on iPhone

• a speaker or Alexa where it's warranted

Record what you said and what the assistant recognised. A wrong answer to a misheard question is one problem. A wrong answer to the right question is another. Repeat under comparable conditions. Save the evidence, including missing answers and missing actions.

Australian names can trip assistants up. Test your business name, your suburb, your acronyms and the phrasing customers use. Use the Australian English setting where the assistant offers one. Add a few representative speakers. Then type the same question.

If the typed version is answered correctly and the spoken one isn't, the problem is recognition, not information. This is a diagnostic, not a claim about any accent's accuracy.

Keep unnecessary personal information out of the log. Use representative speakers with their consent. Treat a successful test as one observation rather than a position.

We've logged spoken checks for clients. In the first round, about 1 in 2 businesses got at least one wrong or missing answer. That count covers answers on hours, phone, location or booking. So expect to find something.

The four evidence sources below each answer a different question. The common mistake is reading one as if it were another.

Search Console gives you the question language. That's useful, even though the tool can't tell spoken from typed. Set a sensible period and consistent country and page filters. Then open Add filter and choose Query. Choose Custom (regex) and Matches regex, then paste the expression below.

Matching is case insensitive and partial by default. So the word boundaries stop "can" matching inside "Canberra". Search Console's filtering documentation explains the regex syntax. Its dimensions documentation lists these dimensions:

• query

• page

• country

• device

• search appearance

• date

There's none for spoken input.

\b(who|what|where|when|why|how|can|does|do|is|are|which)\b

That samples question shaped wording. It misses some conversational queries and includes typed questions. Never call the result a voice segment.

In the client Search Console exports we've reviewed, about 1 in 7 queries with impressions matched that filter. That is question language worth answering, not a count of spoken searches. If the report itself is unfamiliar, our guide on how to read Google Search Console walks through it.

In GA4, measure configured events that mean something. Think of a completed booking, a form that reached the inbox or a verified enquiry. Our guide to GA4 for small business covers what to track and how to read it. A tapped phone link is an intent signal, not a conversation. Voice origin can't be inferred from any of these reports, either.

Keep the AI report separate too. Search Console's Generative AI performance report counts impressions in Google's AI features. It says nothing about whether the question was spoken. That means no voice share or voice return can be calculated from it.

What should you do for voice search in the first 30 days?

Start with the ten point readiness check. That's because it tells you whether the next 30 days are about foundations or about answers. It's an Elev8d editorial checklist for an eligible local business, not a platform score. And a perfect ten guarantees nothing.

Score one point per check passed, where all ten apply. 0 to 3: fix foundations. 4 to 6: close the key gaps. 7 to 9: finish the remaining checks and improve the useful answers. 10: maintain and monitor.

A wrong opening time or a broken contact action takes priority whatever the total. If a check doesn't apply, record it as not applicable. That happens with a profile for a business that isn't eligible for one. Report the passed count out of the applicable count instead of using the bands.

Fifteen minutes is enough for the triage. It's not an audit. The scope of the fixes depends on:

• how many locations you have

• who holds the logins

• how many listings carry errors

• how much content needs rewriting

• whether tracking exists

It's fine if external corrections take longer than the plan.

After the first 30 days, run that cycle monthly. Review listing errors and keep the facts current. Expand content only where a logged question still has no useful answer. This maintenance doesn't compound into rankings. It compounds into fewer customers sent to a locked door.

What we recommend at Elev8d

FAQ

Next steps

Written by Ajay K.Co-founder, Elev8d

Ajay is the co-founder of Elev8d and writes most of what you will read here. Psychology grad turned marketer, which is a fancy way of saying he cares about why people click, not just where things rank. Every guide is written in plain English for Australian businesses, tested on real campaigns before it earns a spot on this site.