Of all the disappointing Google Local Services Ads (LSA) leads you will pay for, two types deserve special attention because owners consistently expect credits for them and consistently do not get them: job-type mismatch and geographic mismatch inside your service area. These are not edge cases — together they can account for a large share of unbookable leads. And because Google's machine-learning credit model treats both as valid charges, the real remedy is prevention rather than recovery. This article explains why these leads are non-creditable and what actually reduces them.
Why these two are not credited
The logic is consistent once you see it. LSA promises that you pay for genuine contact from someone seeking your kind of service in an area you serve. In both mismatch types, that promise was technically kept:
- In a job-type mismatch, the caller reached the right kind of business. They wanted a real service in your category or an adjacent one. The contact was legitimate; it simply was not the exact job you wanted or booked.
- In an in-area geo mismatch, the caller is located inside the service area you defined. Google delivered a prospect from a region you explicitly told it you cover. The distance objection is a consequence of your own targeting.
In neither case did the system fail. That is why the ML model, during its roughly 72-hour assessment, leaves these as valid charges. Rating them in the Rate this lead survey will not change the outcome.
Job-type mismatch: the source is your service list
Job-type mismatches usually trace back to the categories and service types you selected. LSA lets you appear for a set of services; if that set is broader than what you actually do — or includes adjacent work you would rather not take — you invite calls you cannot or will not fulfill.
How to reduce it
- Prune your service selections to match the jobs you genuinely want. Removing a rarely-wanted service can cut a stream of mismatched calls.
- Watch adjacent categories. If you are a plumber who does not do drain-only jobs, or an HVAC company that does not do refrigeration, make sure your selections reflect that.
- Review the calls. Recordings tell you which mismatched jobs keep coming, pointing directly at the selection to change.
Geo mismatch: the source is your service-area map
In-area geo mismatch is almost always a symptom of an over-broad service area. Every extra zip or mile you add to your LSA targeting is a place Google can legitimately send you leads — and then decline to credit when the drive is not worth it.
How to reduce it
- Draw the area you actually want to serve, not the largest area you could theoretically reach. Ambition in the map becomes cost in the ledger.
- Work at the zip level. Some zips inside a metro convert far worse than others; excluding chronic underperformers is legitimate and effective.
- Revisit as operations change. A crew reduction, a route change, or a fuel-cost shift can make yesterday's reasonable area today's money pit.
| Mismatch type | Root cause | Preventive fix |
|---|---|---|
| Job-type | Service selections too broad | Prune services to jobs you want |
| In-area geo | Service area too broad | Trim area, exclude weak zips |
The budgeting implication
Because neither mismatch type is creditable, they sit permanently in your net cost. If you assume the ML credit system will refund them, you will systematically overestimate recovery and underestimate your true cost per booked job. Remember that realistic recovery across all creditable leads is only around 6 to 7 percent by third-party estimates — and mismatches are not even in that pool. The money you lose to mismatches is money you must prevent, not reclaim.
Turning mismatch data into optimization
Handled well, mismatch leads become a feedback loop rather than a loss. Every mismatched call is a data point telling you either which service to drop or which zip to exclude. Owners who log these systematically — noting the requested job and the caller's location — accumulate a precise map of where their targeting is too generous. Over a few months, acting on that map does far more for profitability than any dispute ever could, because it removes the bad spend before it happens instead of chasing a refund that will never arrive.
Frequently asked questions
Will Google credit a job-type mismatch lead?
No. In a job-type mismatch the caller still reached the right kind of business seeking a real service, so Google's machine-learning credit model treats it as a valid charge during its roughly 72-hour assessment. Rating it in the Rate this lead survey will not change the outcome. The real fix is prevention: prune your service selections down to the jobs you genuinely want.
Why won't Google credit a lead from inside my own service area?
Because you told Google you cover that area. An in-area geo mismatch is a consequence of your own targeting, so the distance objection is not something Google will refund. Draw the area you actually want to serve rather than the largest area you could reach, work at the zip level, and exclude chronically weak zips.
How much LSA spend can I realistically recover through credits?
Third-party estimates put recoverable spend at only around 6 to 7 percent, and job-type and in-area geo mismatches are not even in that pool. Since manual disputes ended in 2024 and credit is now handled by an automated model, the money lost to mismatches has to be prevented at the source rather than reclaimed after the fact.