There is no separate optimization track for voice search apart from ordinary local SEO. Voice assistants such as Google Assistant, the newer Gemini assistant, Siri, and Alexa answer local questions from the same sources as regular Google search, mainly the Google Business Profile and the structured data on a business website. A contractor who keeps those two fundamentals current is already covering the voice search share of local search, without building out a separate channel for it.
How often people actually search by voice
Reliable numbers on voice assistant adoption exist, though they vary by source and definition, and almost none of them isolate home services specifically. eMarketer’s forecasts put US voice assistant users at roughly 153.4 million in 2025 and 157.9 million in 2026, with Google Assistant leading at an estimated 91.9 million users, ahead of Siri at 86.5 million and Alexa at 77.2 million. Those are platform adoption figures, not search-behavior studies.
What is missing is a current, well-documented study that quantifies how often US consumers specifically use voice search to find a plumber, electrician, or roofer. Widely repeated claims, such as the figure that a fixed share of all voice searches are “near me” queries, cannot be traced back to a verifiable, dated primary study and should not be treated as a reliable benchmark. The realistic takeaway: a meaningful share of the population uses voice assistants regularly, but voice search is not a separately measurable lead channel for contractors the way paid search or Google Business Profile views are. The two situations where it plausibly matters most are the same ones that already drive mobile local search generally: searching from the car for a nearby business, and an urgent search at home when both hands are busy with a leak or a breaker panel.
A practical example
An HVAC company with a complete Google Business Profile, accurate hours, and an emergency service page with a click-to-call number shows up in a voice query like “emergency HVAC repair near me” through the same local pack data that surfaces without a voice assistant involved. If the service area is missing from the profile, or the phone number on the website does not match the one in the profile, the assistant may either skip the business entirely or read out an outdated number. The gap is not a missing voice-search optimization step, it is the same data inconsistency that already weakens ordinary local search results.
The Google Assistant to Gemini switch does not change the underlying picture
Starting September 4, 2026, Google began gradually replacing Google Assistant with Gemini, first on Android smartphones, tablets, Wear OS devices, headphones, and Android Auto. The rollout runs over several weeks and does not initially touch smart speakers already in people’s homes. For a home service business, the practical impact is small: Gemini answers local questions using the same Google Business Profile and website data Assistant already relied on, not a new, separate dataset. The switch is a reasonable moment to double-check an existing profile, not a reason to invest in new voice-specific tooling.
Where the answer actually comes from
When someone asks a voice assistant to find a plumber nearby or check a business’s hours, the answer draws on the same data that powers the regular local pack in Google search: name, address, phone number, hours, and category from the Google Business Profile, combined with structured data from the business website. Inconsistent business information across the profile, website, and directory listings hurts voice answers exactly as much as it hurts regular local search, as covered in the piece on local SEO for contractors. There is no separate optimization path reserved for voice queries.
Why speakable schema is not worth building for a home service site
Speakable is a schema.org property meant to tell Google which text sections are suitable for the Assistant to read aloud. It shows up often in voice-SEO checklists, which makes it tempting to add. For a home service business, the effort is not worthwhile: Google’s documentation scopes the feature specifically to news content, articles the Assistant can read out as a topical news update on a smart speaker, not general business or service pages. That restriction applies regardless of language, so a plumbing company’s service page or blog post falls outside the intended use case even before considering the feature’s US-only, English-only rollout and its multi-year beta status with no announced expansion.
FAQ content remains the actual lever, with or without a rich result
Google removed FAQ rich results from search on May 7, 2026, a change covered in more detail in the article on local business schema markup. That change affects only the expandable visual snippet in search results, not the underlying value of a well-written question-and-answer section. Voice assistants and AI answer engines still read the visible page content directly, regardless of whether a rich snippet displays for it. An FAQ section that answers real customer questions in short, natural sentences remains one of the few investments that pays off for both regular search and voice queries at once.
What actually moves the needle for voice search, and what does not
| Action | Effect on voice search | Effort |
|---|---|---|
| Complete, accurate Google Business Profile | High | Low |
| Consistent business information across website, profile, and directories | High | Medium |
| FAQ sections written in natural question-and-answer form | Medium | Low |
| Click-to-call phone number | High, calling is often the next step after a local voice search | Low |
| Building out speakable schema | No effect for a typical service business site | High |
| Hiring a dedicated “voice SEO” specialist | Usually no benefit beyond ordinary local SEO | High |
A click-to-call number deserves particular attention, since calling is often the most direct next step after someone asks a voice assistant to find a local business. The article on click-to-call buttons covers the technical setup in more detail.
Practical checklist
- Review the Google Business Profile for completeness: category, hours, service area, phone number.
- Cross-check business information across the website, profile, and key directories, no mismatched spellings or outdated phone numbers.
- Add an FAQ section built from real customer questions written in full, natural sentences, not just keyword fragments.
- Make the phone number clickable on every device, especially on the homepage and any emergency service page.
- Skip dedicated budget for speakable schema or a specialized voice SEO vendor until the basics above are solid.
Next step
Voice search turns out to be less of a new project and more of an additional check on work that already needs doing: a complete Business Profile, accurate structured data, and a maintained FAQ section. Mr.Site runs managed website service for several hundred business websites and keeps profile data, business information, and contact paths current on an ongoing basis, instead of setting them once at launch and letting them drift.