voice-search

Voice Search Optimization Audit — Phase 18

Executive Summary

Voice search in 2025–2026 is no longer just smart speakers — it's the entire AI conversational interface layer. Google's voice-driven AI Mode, iOS 18 Siri with deep web integration, and AI Overview voice results on mobile collectively account for 27% of mobile searches (Google internal data, 2024). "Near me" searches have grown 200%+ over 5 years. Optimizing for voice = optimizing for AI answer extraction. Local businesses missing voice optimization lose 20–30% of mobile intent queries to competitors.

Tools for This Phase

| Tool | Purpose | Cost | |------|---------|------| | Google PageSpeed Insights | Mobile speed — voice results require > 70 mobile score | Free | | Google Rich Results Test | FAQPage, HowTo, Speakable schema validation | Free | | Google Search | Test "near me" + conversational queries — does AIO appear? | Free | | ChatGPT | Test voice-style queries — is client mentioned? | Free/Paid | | Perplexity | AI search visibility test for local queries | Free | | Google Maps / GBP | Confirm GBP completeness for voice data extraction | Free | | AlsoAsked.com | Question clusters for FAQ + voice query mapping | Freemium | | AnswerThePublic | Conversational query patterns per service topic | Freemium | | BrightLocal | Citation consistency check — NAP for voice accuracy | Paid |

Step 1: Read Project Context

Read {AUDIT_DIR}/intake-data.md — business name, URL, location, services. Read {AUDIT_DIR}/local-findings.md — GBP completeness (critical for local voice queries). Read {AUDIT_DIR}/speed-findings.md — mobile speed score (voice requirement: > 70/100 PSI).

2025–2026 Voice Search Context

Where voice queries originate: | Platform | Query Type | Local Business Impact | |----------|-----------|----------------------| | Google Assistant (Android + mobile) | "Near me", "Open now", hours, directions | Critical — highest local volume | | Siri (iOS 18+) | Business info, hours, services | High — uses Apple Maps + web | | Google AI Mode | Conversational follow-up queries | Critical — replacing traditional SERP | | AI Overviews (voice trigger) | "How to", "What is", "Best [service] in" | High — appears for 20–35% local queries | | Alexa / Google Home | "Find a [service] near me", business hours | Medium — smart home user base | | ChatGPT / Perplexity voice | "Best [service] in [city]" recommendations | Growing — AI-first searchers |

2025 voice search stats:

• 27% of mobile searches are voice-based (Google, 2024)
• Voice search results come from pages with mobile PSI score > 70 at 97% rate (Backlinko, 2024)
• "Near me" searches grew 200%+ in 5 years
• Featured snippets are read aloud for 80%+ of voice answers (SEMrush, 2024)
• GBP is the primary data source for 90%+ of local voice responses

Step 2: GBP Voice Readiness (Critical for All Local Voice Queries)

Voice assistants extract local business data directly from GBP. Missing or inaccurate GBP = wrong voice answers.

GBP voice readiness checklist:

| Check | Status | Fix | Effort | |-------|--------|-----|--------| | Business name 100% accurate (no keyword stuffing) | ✅/❌ | Edit GBP | 5 min | | Full address including suite/unit | ✅/❌ | Edit GBP | 5 min | | Phone number (primary click-to-call) | ✅/❌ | Edit GBP | 5 min | | Hours: all 7 days + holidays + special hours | ✅/❌ | Edit GBP | 15 min | | "Describe your business" (1,000 char description) | ✅/❌ | Write + edit GBP | 30 min | | All services listed with accurate names | ✅/❌ | Add services | 30 min | | Booking link configured (for "book a [service]" queries) | ✅/❌ | Add booking URL | 15 min | | Q&A section with 5+ common questions answered | ✅/❌ | Add Q&As | 30–45 min | | GBP verified and no pending flags | ✅/❌ | Verify via phone/video | 1–3 days |

Voice query simulation via GBP:

• "Hey Google, what time does [Business Name] close?" → reads Hours
• "Hey Google, call [Business Name]" → reads Phone
• "Hey Google, get directions to [Business Name]" → reads Address
• "Hey Google, does [Business Name] do [service]?" → reads Services + Description

Step 3: Voice Query Types for Local Businesses

Map target voice queries across 4 intent categories:

"Near Me" Queries (Highest Volume)

• "[service] near me"
• "best [service] near me"
• "[service] open now near me"
• "[service] in [neighborhood]"

Ranking factors for "near me" voice results:

1. GBP proximity + verified address ← #1 signal
2. GBP primary category match ← #2 signal
3. GBP review count + rating ≥ 4.0 ← #3 signal
4. Website local relevance (city mentioned in content) ← #4 signal
5. NAP citation consistency across directories ← #5 signal

Business-Specific Queries

• "What time does [Business Name] close?"
• "Is [Business Name] open on Sunday?"
• "Phone number for [Business Name]"
• "How much does [service] cost at [Business Name]?"

Informational/Conversational Queries

• "How do I [service-related question]?"
• "What is the best [service] for [problem]?"
• "How long does [service] take?"
• "What causes [problem that service fixes]?"

Action-Intent Queries

• "Book a [service] appointment"
• "Call [Business Name]"
• "Get directions to [Business Name]"
• "Schedule [service] online"

Step 4: Content Optimization for Conversational Queries

FAQ Content (Primary AIO + Voice Citation Source)

FAQ quality checklist: | Check | Standard | Status | |-------|---------|--------| | FAQ exists (standalone page or per service) | Required | ✅/❌ | | Questions in natural conversational language | Required | ✅/❌ | | Questions mirror actual voice query phrasing | Required | ✅/❌ | | Answers ≤ 40–50 words (ideal for TTS reading) | Target | ✅/❌ | | FAQPage + Question + Answer schema implemented | Required | ✅/❌ | | Answers start with direct response (no preamble) | Required | ✅/❌ |

Optimal FAQ answer format for voice:

Q: How much does [service] cost in [City]?
A: [Service] in [City] typically costs $X–$Y. [1-sentence context].
   Call [Business] for a free quote: [phone].

(Under 50 words → voice-readable, AIO-citable, featured snippet-optimized)

Featured Snippet Optimization (Voice Reads Snippets 80%+ of Time)

For each target voice query:

• [ ] Concise answer in first 40–50 words of the page (no "as mentioned above...")?
• [ ] Answer follows H2/H3 question header directly?
• [ ] Single clean paragraph or numbered list (2–4 steps)?
• [ ] No qualifiers or conditional language in first sentence?

Speakable Schema

SpeakableSpecification marks sections optimal for TTS reading:

{
  "@type": "SpeakableSpecification",
  "cssSelector": [".faq-answer", "h2 + p", ".direct-answer"]
}

Apply on: Homepage summary paragraph, all FAQ answers, key service descriptions.

Step 5: Technical Voice SEO Requirements

Voice results have strict technical requirements:

| Requirement | Threshold | Check Method | |-------------|-----------|-------------| | Mobile PageSpeed | ≥ 70 PSI score | PageSpeed Insights → Mobile | | LCP | < 2.5s | PageSpeed Insights → LCP | | TTFB | < 800ms | WebPageTest | | HTTPS | All pages | curl -I https://[domain] | | Mobile-responsive | Full responsiveness at 375px | Chrome DevTools → Device toolbar | | Tap targets | ≥ 44px (voice → tap follow-up) | Lighthouse → Tap Targets |

Schema for voice ranking: | Schema Type | Voice Use Case | Priority | |------------|---------------|---------| | LocalBusiness (complete) | Hours, phone, address, directions | Critical | | FAQPage | Q&A voice answers | Critical | | HowTo | Process/instructional queries | High | | Speakable | Marks voice-optimal content sections | Medium | | OpeningHoursSpecification | Hours queries | Critical | | ContactPoint | Phone/contact queries | High | | GeoCoordinates | "Near me" precision | High |

Step 6: AI Assistant Visibility Test

Test across all major AI platforms using voice-