You open your Local Services Ads dashboard, glance at the numbers, and stop cold: your LSA cost per lead spiked since last week, sometimes dramatically. The instinct is to assume Google changed something or that the channel is broken. Usually neither is true. A sudden jump in cost per lead almost always has a diagnosable cause — and often it is not even a real price change but a shift in the quality of leads you received. Before you touch a single setting, the goal is to figure out which of a handful of causes actually applies, because the fix for each one is different. This guide walks through them and gives you a confirmation step for each.
First, separate raw cost per lead from effective cost
The single most important distinction is between two numbers that often get blurred together. Raw cost per lead is what Google charged you, divided by the number of charged leads — a straight price. Effective cost per booked job is that figure divided by your booking rate, so it reflects how many of those leads actually became work. These move for completely different reasons.
Here is why it matters: if half your leads booked last month but only a quarter booked this month, your effective cost doubles even if Google's raw price per lead never moved a cent. A large share of raw LSA leads — third-party estimates put it near 45 percent — are unbookable in the first place, so booking rate swings are common and can masquerade as a pricing problem. So the very first check is: did the price Google charges per lead go up, or did your booking rate go down? Answer that and you have already narrowed the field by half.
The diagnosable causes of a spike
Once you know whether you are dealing with a raw or an effective spike, the likely causes fall into a short list.
Auction and competition pressure
If a new competitor enters your area or an existing one raises their bids, the auction gets more expensive and your raw cost per lead rises even with no change on your end. This is one of the most common causes and one you cannot directly control — only respond to.
Seasonal demand surge
Many home-service trades have sharp seasons. When demand spikes — the first heat wave for HVAC, storm season for roofing — more advertisers compete for the same searches and prices climb. Average cost per lead is often cited near $53, but it ranges roughly $12 to $180 by trade and metro, and seasonality moves you within and beyond that band.
A bid or setting change
If you or someone on your team switched to Maximize Leads, raised a Target CPL, or increased a manual Max per lead, you told Google to pursue more or more-competitive leads — and it did. This is the easiest cause to confirm and the easiest to reverse.
Category or service-area change
Adding job categories or expanding your service area changes the mix of auctions you enter. New, higher-priced categories or more competitive zip codes can lift your blended cost per lead without any bid change at all.
A ranking slip
If your ranking drops, you enter fewer of the high-quality, well-matched auctions and end up paying up for the leads you do win. A decline in Google Verified standing, review velocity, or responsiveness can quietly raise cost per lead as a second-order effect.
More unbookable or junk leads
A period heavy with wrong numbers, out-of-area callers, or jobs you do not do will drag down your booking rate and inflate effective cost even when raw price is flat. Checking your credits matters here: Google's ML auto-credit system returns a modest slice of spend, and job-type or geo mismatches are not creditable, so junk-heavy weeks hit twice.
Small-sample volatility
Finally, and most underrated: if you get a handful of leads per week, one expensive lead or one that failed to book swings the average hard. A "spike" over a single low-volume week is frequently just noise, not signal.
A confirmation-and-fix reference
| Likely cause | How to confirm it | What to do |
|---|---|---|
| Auction / competition pressure | Raw cost per lead up across all categories; no setting change on your end | Shore up rank factors (reviews, response speed) rather than only outbidding; monitor before reacting |
| Seasonal surge | Timing lines up with your trade's known peak; volume is also up | Expect it; adjust budget pacing so you do not run dry mid-period |
| Bid / setting change | Spike starts on the exact date a bidding mode, Target CPL, or Max per lead changed | Revert or set a Target CPL / manual cap and watch price and volume together |
| Category or service-area change | Spike aligns with an added category or expanded area | Review the blended mix; segment costs by category to see which is expensive |
| Ranking slip | Dashboard shows lower position or fewer impressions alongside the price rise | Audit reviews, responsiveness, and Verified standing; fix the underlying signal |
| Junk / unbookable leads | Raw price flat but booking rate down; more mismatched or wrong-number leads | Rate leads honestly, pursue eligible credits, tighten categories and geo |
| Small-sample noise | Only one low-volume week is elevated; longer trend is stable | Do nothing yet — wait for more data before changing settings |
A simple diagnostic order
Work the problem in this sequence and you will rarely misdiagnose it:
- Isolate the timeframe. Pin down exactly when the spike started — a precise date narrows the causes fast.
- Check for bid or setting changes. Look at your change history around that date first, because it is the most fixable cause.
- Check the lead mix and booking rate. Determine whether raw price rose or booking simply fell.
- Check credits. See whether creditable leads are being credited and whether junk is the real story.
- Compare to seasonality and volume. Ask whether the timing and your lead count explain the move before blaming Google.
The one thing not to do is overreact to a single week. Cost per lead is inherently noisy at low volumes, and knee-jerk bid cuts can throttle your visibility for weeks in exchange for solving a problem that did not exist.
The takeaway: a spiked LSA cost per lead is a symptom, not a diagnosis. Separate the raw price Google charges from your effective cost per booked job, isolate the date it started, and rule causes in or out one at a time — a bid change, competition, season, category or area shift, a ranking slip, a junk-heavy week, or plain small-sample noise. Because auction dynamics and Google's tools evolve, verify current bidding options and credit behavior in your live dashboard and Google Local Services Ads Help rather than assuming, and give the data a few weeks before you act.
Frequently asked questions
Is a one-week LSA cost per lead spike something to worry about?
Usually not on its own. Cost per lead is volatile at low weekly lead counts, so a single noisy week can move the average without anything actually being wrong. Wait for a few weeks of data or a clear trend before making bid or budget changes, and check whether the spike is really a raw price change or just a drop in your booking rate.
Does switching to Maximize Leads raise my LSA cost per lead?
It can. Maximize Leads tells Google to get as many leads as your budget allows, which can pull in more competitive and higher-priced auctions than a Target CPL or manual Max per lead setting would. If your cost per lead spiked right after a bidding change, that change is a prime suspect. Compare the dates and, if needed, set a Target CPL or manual cap and watch the effect on both price and volume.
What is the difference between raw cost per lead and effective cost per booked job?
Raw cost per lead is simply what Google charges divided by the number of charged leads. Effective cost per booked job is that figure divided by your booking rate, so it reflects how many leads actually turn into jobs. Effective cost can spike even when Google's price per lead has not moved at all, purely because more leads were unbookable that period. Always check the booking rate before assuming Google raised your prices.