Voice search optimization: getting read out by Siri, Alexa and Gemini
Voice assistants now generate answers with AI models instead of reading out a featured snippet. Here is where each one gets its answers, and six steps to make your page or business the one they use.
The seoscore team 10 min read
On this page
- What voice search optimization means now
- Where Siri, Alexa, Gemini and ChatGPT voice get their answers
- How voice queries differ from typed ones
- Step 1: Let the right crawlers in
- Step 2: Write answers that sound right read aloud
- Step 3: Cover the follow-up questions on one page
- Step 4: Get local listings consistent for "near me" questions
- Step 5: Add structured data that helps, and skip what doesn't
- Step 6: Keep pages fast, mobile-friendly and fresh
- Check your page with seoscore
- How to tell if voice assistants are using your answers
- Voice search myths to drop
- Next steps
Voice search optimization means making your pages and business listings easy for a spoken assistant to find, understand and turn into a short answer. Siri, Alexa and Google's assistant now generate answers with AI models, so most of the work is the same as answer engine optimization: clear answers, open access for crawlers, useful structured data and accurate local listings. A separate voice page or a list of "voice keywords" is not needed.
What voice search optimization means now
Most voice search guides date from around 2018, when the advice was simple: win the featured snippet (the answer box above Google's results) and Google Assistant would read it out. That model has changed. Google has replaced Assistant with Gemini on Android phones, Amazon has rebuilt Alexa as Alexa+, and Siri can hand questions to ChatGPT. These assistants write a fresh answer from what they find, and they may draw on several pages at once.
That makes voice optimization largely AEO, answer engine optimization: making a page easy for AI engines to read, trust and quote. Our guide to answer engine optimization covers the basics. The other half of the job, getting an assistant to name your brand when someone asks for a recommendation, is GEO (generative engine optimization), which the GEO guide explains.
Where Siri, Alexa, Gemini and ChatGPT voice get their answers
None of these companies publishes a full account of how its voice answers are chosen. The table sets out what has been stated publicly and marks the gaps.
| Assistant | Model | Web source | Local data | Names the source aloud? |
|---|---|---|---|---|
| Gemini (Android phones, Google TV, Nest via Gemini for Home) | Gemini | Google Search | Google Business Profile and Google Maps | Not stated by Google |
| Siri with Apple Intelligence | Apple's own models, with an optional handoff to ChatGPT | Applebot's index, plus ChatGPT when the user agrees | Apple Maps, managed through Apple Business Connect | Varies by answer |
| Alexa+ | Amazon's generative AI | Not published in detail | Partners such as Yelp, OpenTable and Tripadvisor | Not stated by Amazon |
| ChatGPT voice mode | OpenAI models | ChatGPT search, built on OAI-SearchBot | Not published in detail | Not stated by OpenAI |
A few notes on the Google row, because it is the one that has moved most this year. Google announced in March 2025 that it was upgrading mobile users from Assistant to Gemini, and Android Headlines reported in September 2026 that the option to switch back to the classic Assistant had been removed on Android. On Nest speakers and displays, Gemini for Home is still rolling out in early access, and reached the UK and much of Europe in April 2026. The Google TV Streamer swapped Assistant for Gemini in late 2025.
When Gemini answers from the web, it grounds the answer in Google Search results. Google's developer documentation on grounding describes the model returning the sources it used. Google has not said whether a spoken answer on a speaker names those sources.
What this means in practice: the crawlers that matter are Googlebot, Applebot, Bingbot and OAI-SearchBot, and the listings that matter are Google Business Profile, Apple Business Connect, Bing Places and Yelp.
How voice queries differ from typed ones
People talk to assistants the way they talk to a person. A typed search might be "boiler service cost Leeds". The spoken version is "How much does a boiler service cost in Leeds?", followed by "Can someone come this week?"
Three differences shape the advice below:
- They are longer and question-shaped. Who, what, how much, how long, is it, can I.
- They are often local. "Near me", "open now" and "closest" questions lean on listings more than web pages.
- There is one answer, not ten links. A typed search shows a page of results the reader can scan. A spoken assistant gives one answer, perhaps with a single source. Being the fourth-best page earns nothing.
Step 1: Let the right crawlers in
An assistant can only quote a page its crawler is allowed to read. Check your robots.txt file (at yourdomain.com/robots.txt) for rules that block these:
User-agent: Googlebot
Allow: /
User-agent: Applebot
Allow: /
User-agent: Bingbot
Allow: /
User-agent: OAI-SearchBot
Allow: /
Two opt-outs cause confusion:
- Applebot-Extended does not crawl anything. According to Apple's Applebot page, it only controls whether content Applebot has already collected can be used to train Apple's models. Blocking Applebot itself is what takes you out of Siri and Spotlight.
- Google-Extended is Google's control for some AI uses of your content. Google's AI features documentation explains how inclusion in Search's AI features works. Now that Gemini is Google's voice assistant, read Google's current description of what Google-Extended covers before blocking it.
OpenAI keeps search and training separate too: OAI-SearchBot feeds ChatGPT search, while GPTBot collects training data. You can block GPTBot and still appear in ChatGPT answers. Our article on allowing AI crawlers in robots.txt has the full list and the firewall issues that block crawlers even when robots.txt allows them.
Step 2: Write answers that sound right read aloud
Put the question people ask in a heading, then answer it in the first sentence or two beneath. Aim for 30 to 50 words: long enough to be complete, short enough to be spoken in about 15 seconds. Then add the detail.
Write that answer so it works without a screen:
- No tables, bullet symbols or "see below" in the key answer.
- Spell out ranges and times: "9am to 5:30pm", not "9–5:30".
- Use units in words where symbols could be misread: "about 20 minutes", not "~20 min".
- Put the answer first, without preamble such as "Great question".
Before, under a heading of "Hours":
Open M–F 9–5:30, Sat 10–4. Closed Sun/BH. See table for Xmas.
After, under a heading of "When are you open?":
We're open Monday to Friday from 9am to 5:30pm, and on Saturdays from 10am to 4pm. We're closed on Sundays and bank holidays. Christmas opening times are listed below.
The second version can be read out word for word, and a model rewording it has nothing to guess at. It also helps text answers: our guide to getting cited in Google AI Overviews uses the same pattern.
Check that your snippet rules aren't working against you. A nosnippet tag or a very low max-snippet value can stop Google using your text in answers; see how snippet rules affect AI answers.
Step 3: Cover the follow-up questions on one page
A spoken conversation rarely stops at one question. Someone who asks how much a service costs will often ask how long it takes, whether you cover their area and how to book. If one page answers all of them, the assistant can keep drawing on it.
Build a section of related questions on the main page for the topic:
- List the questions customers ask you by phone and email. These are the closest thing you have to voice queries.
- Give each one a question heading and a two or three sentence answer.
- Keep each answer self-contained, so it makes sense if it is the only part read out.
- Link to a longer page where an answer needs more depth.
Add FAQPage markup when the questions and answers are visible on the page. Google has shown FAQ rich results only for a small set of authoritative sites since 2023, so don't expect a visual change in search results. The markup still labels each question and answer clearly for any system reading the page.
Step 4: Get local listings consistent for "near me" questions
For "Where's the nearest..." or "Is ... open now?", assistants answer from map and listing data, not your web page. Each platform feeds different assistants, so claim and complete all four:
- Google Business Profile for Gemini, Google Search and Maps.
- Apple Business Connect for Siri and Apple Maps.
- Bing Places for Bing, Copilot and anything that draws on Bing.
- Yelp, which Amazon named among its Alexa+ partners.
On each one:
- Use exactly the same business name, address and phone number. "Ltd" on one and not another, or an old phone number, makes it harder to match the listings as one business.
- Choose the most specific primary category that fits.
- Fill in opening hours, including holiday hours. "Is it open now?" is a common voice question, and a wrong answer costs a visit.
- Add services, a short description and recent photos.
- Ask happy customers for reviews and reply to them.
Google's guide to improving your local ranking says local results depend on relevance, distance and prominence, and that complete, accurate information helps. Finally, add LocalBusiness markup to your site with the same name, address, phone and hours as your listings.
Step 5: Add structured data that helps, and skip what doesn't
Structured data (schema markup) is code that labels what a page is about in a form machines read reliably. For voice, three types are worth the effort:
- Organization on your home page: name, logo, URL and
sameAslinks to your official profiles. It ties your site to your brand as one entity. - LocalBusiness (or a more specific type such as
DentistorPlumber) for businesses customers visit. - FAQPage for the question section from Step 3.
A cut-down LocalBusiness example:
{
"@context": "https://schema.org",
"@type": "Bakery",
"name": "Hill Street Bakery",
"telephone": "+44 113 496 0000",
"address": {
"@type": "PostalAddress",
"streetAddress": "12 Hill Street",
"addressLocality": "Leeds",
"postalCode": "LS1 1AA",
"addressCountry": "GB"
},
"openingHours": ["Mo-Fr 09:00-17:30", "Sa 10:00-16:00"]
}
Speakable markup is the one most voice guides oversell. Google's speakable documentation describes it as a beta feature for news publishers, in US English, for Google Assistant devices. We have seen no statement that Gemini or any other assistant uses it. If you're not a US news publisher, skip it. Our article on schema markup for AI search covers which types matter in more depth.
Step 6: Keep pages fast, mobile-friendly and fresh
Most voice questions start on a phone, and the assistant may hand the user a link to finish the job. A slow, awkward mobile page wastes that visit. Test it with the methods in how to test Core Web Vitals and how to test mobile now.
Make sure your answers are in the HTML the server sends, not loaded later by JavaScript. Several AI crawlers don't run JavaScript, as our test of what AI crawlers see shows. Show a visible "last updated" date on pages where facts change, such as prices and hours, and update it only when you change the content.
Check your page with seoscore
Each step above is something you can check by hand, but it is quicker to check them together. The free AEO and GEO checker runs seoscore's AEO checks on any page without an account: AI crawler access in robots.txt, content without JavaScript, snippet rules, llms.txt, entity markup, freshness, citations, direct answers, FAQ markup and answer blocks. Paste in the page you most want an assistant to answer from, such as your services or opening hours page, and fix what it flags.
To see where those fixes sit in the bigger picture, run an SEO audit. AEO is 15 of the 100 points and Mobile is 12, and every fix is ranked by the points it adds. The methodology page lists every check and weight.
How to tell if voice assistants are using your answers
Google Search Console doesn't separate voice queries from typed ones, and no assistant sends you a report of what it read out. Use these proxies instead:
- Ask the assistants yourself. Once a month, put your ten most common customer questions to Siri, Gemini, Alexa and ChatGPT voice mode. Note whether the answer matches your page or names your business.
- Track question keywords and AI Overviews. Gemini grounds its answers in Google Search, so your Google position for question-shaped keywords is a useful signal. Rank tracking, on Starter and up with a free trial, checks your position weekly or daily and records whether Google showed an AI Overview and cited your site.
- Measure AI answers in text. AI visibility asks ChatGPT, Claude, Gemini and Perplexity the questions your customers ask and scores how often, and how early, they name your site, with the sources they cite. Text answers aren't spoken ones, but they come from the same models. Our guide to tracking brand mentions in ChatGPT covers the method.
Voice search myths to drop
- "50% of searches will be voice." This figure is usually traced to a 2014 prediction, not a measurement. Don't build a plan on it.
- "Speakable schema gets you read out." It is a beta feature for US English news publishers on Google Assistant devices, as above.
- "You need a separate voice page." One well-structured page with clear answers to the main question and its follow-ups serves voice, text AI answers and ordinary search.
- "A featured snippet is the voice answer." That was broadly true for Google Assistant. Google hasn't said how Gemini on speakers chooses what to say, and the other assistants use their own sources. A strong Google position helps, but it isn't a guarantee.
Next steps
- Run your most important page through the free AEO and GEO checker and fix any blocked crawlers first.
- Rewrite the top answer on that page as a 30 to 50 word reply under a question heading.
- Add five follow-up questions with short answers, plus FAQPage markup.
- Make your name, address, phone and hours identical on Google Business Profile, Apple Business Connect, Bing Places and Yelp.
- Read the AEO guide for the page side and the GEO guide for getting your brand named.
Questions people ask
Is voice search still worth the effort for a small business?
Yes, mainly because the work overlaps with things you should do anyway. Clear answers, open crawler access and accurate listings help ordinary search and text AI answers as much as spoken ones. The one voice-specific task, writing answers that read well aloud, takes little time.
Will an assistant read my page out word for word?
Usually not. AI-based assistants tend to rephrase and combine what they find into their own answer. A short, plain answer gives the model less room to get your facts wrong when it rewords them.
Does llms.txt help voice assistants?
No voice assistant has said it reads llms.txt. It is a small file that is cheap to create and may help some AI tools understand your site, but it won't make up for blocked crawlers or unclear answers. Treat it as optional.
Should I write in a conversational tone for voice search?
Write plainly rather than chattily. Use the question as your customers phrase it in the heading, then answer in short, complete sentences. Filler phrases and jokes make an answer longer without making it easier to quote.
Sources
- The Assistant experience on mobile is upgrading to Gemini blog.google
- Gemini Fully Replaces Google Assistant on Android www.androidheadlines.com
- Gemini for Google Home Launches in 16 New Countries www.techadvisor.com
- Google TV Streamer is the latest device to drop Assistant for Gemini www.androidauthority.com
- Gemini API and Google AI Studio now offer Grounding with Google Search - Google Developers Blog developers.googleblog.com
- developers.google.com/search/docs/appearance/ai-features developers.google.com
- platform.openai.com/docs/bots platform.openai.com
- support.google.com/business/answer/7091 support.google.com
- developers.google.com/search/docs/appearance/structured-data/speakable developers.google.com
seoscore
Will AI answer engines quote you?
Run the free AEO checks on any page and see what to fix first.
Check my AEO