Why do my Local Services Ads lead disputes keep getting denied?
Most denials trace to three things: the reason chosen does not match what the recording shows, the dispute was filed after the credit window closed, or the note is a judgment about lead quality rather than a policy violation. Google credits leads that fall outside what you signed up to receive, not leads you simply did not like. Write the dispute in the reviewer's language and file it promptly.
Credit categories are narrow on purpose
Lead credit exists to correct mismatches between the lead and the profile you configured: a job type you do not offer, a location outside your service area, a spam or solicitation call, a wrong number. It does not exist to refund leads that were real, in area, on service, and simply did not book. Reviewers read the request against those categories, and a request that argues quality gets read as an argument the categories do not cover.
This is the single most common failure. "Customer was price shopping" describes a genuine business problem, but it is not a defect in the lead. It belongs in your call analysis and your close-rate coaching, not in the credit queue.
The three denial patterns worth separating
When you look at a month of denials, they almost always sort into a small number of shapes.
- Wrong reason code. The call really was out of area, but the request was filed as spam. The reviewer checks for spam signals, does not find them, and denies.
- Filed too late. There is a limited window after the lead is charged. Disputes batched at month end routinely age out of it.
- Unsupported assertion. A one-line note with no specifics gives the reviewer nothing. Quote what the caller asked for, name the city or ZIP, state the job type you are not licensed or configured for.
Make the evidence available before you need it
Disputes get written well when whoever writes them can see the call. If your LSA forwarding destination lands on a tracking number that records and transcribes, the person filing can paste the caller's own words instead of reconstructing them from memory two weeks later. That habit alone changes the tone of a dispute file.
At volume this becomes a workflow rather than an errand. An integration layer can flag calls whose transcript shows an out-of-area address or an unsupported job type and route them to a review queue the same day, while the window is still open.
Track the outcome, not just the request
Keep the reason code, the filing date, the outcome, and the charged amount category for every dispute so you can see which reasons your account actually wins on. Patterns show up fast: an account winning wrong-service disputes and losing out-of-area disputes usually has a service-area configuration problem, not a review problem.
That feedback loop is the useful part. Disputes are a symptom reader. Chronic disputes in one category point at a setting to fix, and fixing the setting is worth more than the credits.
Topics: LSA · lead credits · disputes · operations
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.