Local Services Ads

Getting into Local Services Ads starts with qualification, not a campaign build. Google runs a background check on the business and its relevant staff through a screening vendor, verifies license and insurance documentation for regulated categories, and only issues the Google Guaranteed or Google Screened badge once that clears - commonly a process of one to a few weeks depending on category and how fast documents are submitted, and the main setup bottleneck compared with a standard Google Ads account. The account lives in a separate Local Services dashboard, with its own business profile, service area, and job-type list, though it can be linked to a standard Google Ads account for combined billing and reporting visibility.

There's no bid to set. You choose a weekly budget in dollars, and Google's pacing system spends toward it by buying qualified leads - phone calls, messages, or bookings - at a per-lead price set dynamically by category and local competition in that market, which the advertiser doesn't see in advance and can't set directly. A short, low-duration phone call is generally filtered out of billing as unlikely to be a real inquiry, but the exact duration and quality thresholds Google applies aren't fully published, which is part of why the dispute process matters as much as it does.

Where an ad appears in the Local Services placement above organic results is driven by review count and rating, proximity to the searcher, how quickly the business responds to leads, business hours and current availability, and budget - functioning similarly to how Google ranks the local pack rather than like a keyword auction. There's no keyword targeting, no audience targeting, and no device or demographic bid adjustment; service area radius and the list of job types offered are the only targeting inputs.

Disputing bad leads is the primary tool advertisers have over effective cost. Leads outside the set service area, outside the listed job types, spam or bot contacts, and genuine hang-ups or wrong numbers with no real inquiry are all dispute-eligible, and an approved dispute refunds that lead's cost and removes it from the weekly spend total. There's a limited window to file a dispute after the lead comes in, so reviewing new leads - including listening to call recordings and reading message transcripts, both available in the dashboard - promptly rather than in a monthly batch matters for actually recovering the spend.

The most common mistake is approaching it with the mental model of a keyword-based Google Ads campaign: looking for a bid to raise, a keyword to add, or an audience to layer on, none of which exist here. A close second is under-funding the weekly budget relative to local demand, which throttles both impression and lead volume, and reads on the dashboard as low performance when it's really a budget ceiling. A third is neglecting reviews - since they're a direct ranking input, a business that isn't actively asking satisfied customers to leave one is leaving both rank and cost-per-lead efficiency on the table.

Reporting centers on leads received, actual cost per lead (not bid, since there is none), and weekly spend against the budget, with call recordings and message transcripts as the primary quality-review tool rather than any click or impression metric. Because standard PPC vocabulary like CPC, CTR, or keyword-level ROAS doesn't apply here, judging Local Services performance means tracking lead-to-customer conversion rate outside the platform, in whatever CRM or booking system the business runs, and comparing that against the actual post-dispute cost per lead rather than the raw dashboard number.