When someone in their truck says 'Hey Siri, find a plumber near me,' the assistant returns one or two businesses — not a page of results. Voice is the most winner-take-all surface in local search. But here's what most advice gets wrong: there is no single 'voice search.' Siri, Alexa, and Google Assistant each pull from different data providers, so optimizing for one does almost nothing for the others. You have to optimize by assistant.
Voice queries are longer, conversational, and almost always local
People type 'plumber Ashtabula' but they speak 'who's the best emergency plumber near me that's open right now.' Spoken queries are longer, phrased as full questions, and carry strong local and urgency intent. That has two implications: your content needs to answer real spoken questions in natural language, and your profile data — hours, service area, services — needs to be complete and accurate, because that's what the assistant reads from when it answers.
Diagnose by assistant — never by 'voice search' generically
Each assistant has a different data brain. Google Assistant pulls primarily from your Google Business Profile. Siri and Apple Maps pull from Apple Business Connect and lean on Yelp for reviews. Alexa pulls heavily from Bing Places and Yelp. If you're invisible on Siri but fine on Google Assistant, the problem isn't 'voice' — it's that you've never claimed Apple Business Connect. Always trace the specific assistant back to its specific data provider, then fix that provider.
Claim the profiles that feed each assistant
This is the foundational work and most contractors have only done a third of it. Claim and fully complete your Google Business Profile (Google Assistant), Apple Business Connect (Siri and Apple Maps), Bing Places (Alexa and Bing), and Yelp (feeds both Siri and Alexa for reviews). Each profile needs an identical name, address, and phone number, correct hours, and an accurate service area. An unclaimed or half-finished profile is a dead end for the assistant that depends on it.
NAP consistency is non-negotiable for voice
An assistant won't read out a business it isn't confident about. If your phone number is formatted three different ways across Google, Yelp, and your website, or your address uses 'Street' in one place and 'St.' in another, you're introducing the exact ambiguity that makes an assistant skip you in favor of a competitor whose data is clean. Pick one canonical version of your name, address, and phone and make every profile and your website match it character for character.
Answer-first content and FAQ schema are what get read aloud
When an assistant answers a question from a website rather than a profile, it overwhelmingly pulls from short, direct answers — the kind a well-structured FAQ section provides. Write FAQ entries around the actual questions customers ask out loud, keep each answer to roughly 30 to 50 words so it's speakable, and mark them up with FAQPage schema so the assistant understands the structure. Adding SpeakableSpecification schema to your highest-value answer tells voice systems exactly which sentence to read.
How to test whether you show up on voice
Pick up your phone and ask. Use Siri, then Google Assistant, then an Alexa device if you have one, and run the spoken queries a customer would: 'find a [trade] near me,' 'who's open now for [service],' '[trade] with good reviews near [city].' Note which assistant names you and which doesn't. The gaps map directly to the profile you haven't claimed or completed. Re-test after every fix.
