Section 1
What the voice hype got wrong, and what it accidentally got right
The 2018 prediction was that half of searches would be voice and every business needed a 'voice strategy.' That specific future fizzled: smart speakers became kitchen timers, and dedicated voice SEO never produced a distinct discipline. But the underlying bet, that natural language would replace keyword-ese as the way people ask for things, came true through large language models instead. Today's assistants accept a spoken sentence, a photo, a screenshot, or all three, and respond in kind. Stanford HAI's AI Index documents the steep capability gains in language and multimodal systems that made this practical. The lesson for operators is about how queries changed shape: 'plumber tampa' became 'who can fix a tankless water heater in South Tampa this week and what should it cost.' Longer, situational, spoken-style questions are now the input your content competes to answer. For the step that usually comes next, see [The Future of Storytelling in Business: Trends to Watch](/blog/the-future-of-storytelling-in-business-trends-to-watch).
Section 2
The three query modes and what each demands from your site
It clarifies planning to treat voice, visual, and conversational text as distinct modes that converge on the same backend: an assistant reading the open web and choosing what to repeat. The table below maps each mode to design implications, with priority ratings for a typical 5-7 figure service firm. Notice what is absent: no exotic 'voice markup' tricks. Google deprecated most speakable-specific experiments, and its current guidance for AI features is that standard fundamentals, crawlability, useful content, structured data where applicable, carry the load. The leverage sits in unglamorous places: a services page that answers cost questions in plain sentences, a Google Business Profile that agrees with your website, image alt text and captions that say what the photo shows, and pages that load fast on the mobile networks where spoken queries happen.
Section 3
Local service businesses have the most to win, and lose
Spoken and assistant-mediated queries skew heavily local and transactional: near me, open now, how much, who is best. When an assistant answers those, it typically names one to three providers, not ten. That compression is brutal for whoever ranks fourth and golden for whoever is cited. The inputs assistants weigh are mostly verifiable entity data: consistent name, address, and service details across your website and Google Business Profile, genuine reviews, service-area pages that say plainly where you work, and Organization or LocalBusiness structured data binding it together. None of this is glamorous, which is exactly why most local competitors have not done it properly; in our site audits, inconsistent or machine-illegible business data remains the most common failure. Being boringly, verifiably consistent everywhere machines look is currently the highest-ROI 'voice strategy' a local service business can execute. A useful companion to this piece is [The Minimum Viable Website Stack for a Service Business](/blog/minimum-viable-website-stack-service-business).
Section 4
What to do this quarter, in order
First, collect your real spoken-style queries: pull the exact questions from sales calls, intake forms, and chat transcripts; these are what buyers ask assistants. Second, build or rewrite Q&A content so each question gets a direct, complete answer in the first two sentences, with specifics an assistant can repeat accurately. Third, audit entity consistency: website, Google Business Profile, directories, and schema markup must agree on name, services, areas, and hours. Fourth, fix mobile speed; multimodal queries happen overwhelmingly on phones, and web.dev's Core Web Vitals data shows roughly 40% of sites still fail the loading threshold, which is a quiet competitive opening. Fifth, test monthly: ask the major assistants your top ten buyer questions and log who gets named. If your firm never appears, that finding is the agenda for a strategy call. If you are turning this into practice, [Attention Is Not a Lead: Why Service Businesses Confuse Audience With Pipeline](/blog/attention-is-not-a-lead-why-service-businesses-confuse-audience-with-pipeline) maps the adjacent system.