Voice Search Analytics

Analyze likely voice queries from Google Search Console data and prioritize optimization work

Business+ Feature

Voice Search Analytics requires a Business+ tier license and a connected Google Search Console property.

Real Data Only

The module uses only stored analysis data built from Google Search Console queries. If you see empty results, the site is not connected, no property is selected, or no qualifying query data exists yet.

How Detection Works

Google does not explicitly label voice queries. ProRank classifies likely voice queries using rule-based linguistic patterns and a score threshold.

// Simplified scoring model
score = 0

if (startsWithQuestionWord) score += 3
if (hasConversationalPattern) score += 2
if (hasLocalIntentPattern) score += 2
if (wordCount > 4) score += 1
if (hasNaturalLanguageVerbPattern) score += 1

isVoiceLike = score >= 3

Query type buckets are classified as question, conversational, local, or general.

Analysis Timing

Voice analysis is scheduled weekly. You can also trigger recommendation analysis from the Voice Search UI.

Condition	Result
GSC disconnected	Status is skipped with connection message
No selected property	Status is skipped with property selection message
No query rows	Status is no_data
Valid query data available	Status is ready with metrics, queries, pages, and insights

Dashboard Tabs

Overview: voice query count, voice share, voice CTR, average position. Also includes an AI Insights section for recommendation generation.
Voice Queries: query list with score and type labels.
Optimization: recommendations and FAQ opportunity actions.
Settings: tracking toggle, Track Conversational Queries, alert threshold, email alerts, export format.

Settings Keys

{
  "enableTracking": true,
  "track_ai_rankings": true,   // UI label: "Track Conversational Queries"
  "alertThreshold": 20,
  "emailAlerts": false,
  "exportFormat": "csv"
}

REST API Endpoints

# Main analytics payload
GET /wp-json/prorank/v1/analytics/voice-search

# Optional content optimization helper
POST /wp-json/prorank/v1/analytics/voice-search/optimize

# Settings
GET /wp-json/prorank/v1/analytics/voice-search/settings
PUT /wp-json/prorank/v1/analytics/voice-search/settings

# Recommendation + assistant endpoints
GET  /wp-json/prorank-seo/v1/voice-search/ai-recommendations
POST /wp-json/prorank-seo/v1/voice-search/analyze
GET  /wp-json/prorank-seo/v1/voice-search/pages-needing-faq
POST /wp-json/prorank-seo/v1/voice-search/generate-faqs
POST /wp-json/prorank-seo/v1/voice-search/simulate

FAQ

Why are all metrics zero?

Usually because GSC is not connected, no property is selected, or there is no query data yet for the analyzed window.

Is this exact voice traffic?

No. It is a best-effort classification from query language patterns because Google does not provide an explicit voice-search flag.

What tier is required?

Business+

(Business, Agency, or Enterprise).