Google Local Services Ads leads usually feel “low quality” for one of four different reasons:
- The contact is invalid, spam, or a solicitation.
- The person is real, but the requested service or location does not fit.
- The lead fits, but the business fails to respond or convert it.
- The reporting definition labels every unbooked lead as bad.
Those problems look identical in a dashboard—no booked job—but require different fixes. Before changing budget, service areas, or bidding, review a sample of actual conversations and identify which problem you have.
First, define lead quality without circular logic
A useful definition is:
A qualified LSA lead is a real prospective customer requesting an offered service in a serviceable location, within any legitimate business-specific acceptance rules.
“Booked” is a later outcome. A qualified lead can fail to book because the requested time is unavailable, the price is rejected, or the intake person never offers a next step. For a clean status model, see what counts as a booked job in LSA.
Run a 50-lead audit
Export or review the most recent 50 charged leads for one account and date range. Fifty is not statistically magical; it is a manageable sample large enough to expose repeated patterns. Review the recording, transcript, or message—not just the employee note.
Assign exactly one primary outcome:
| Outcome | Definition | Owner of the next fix |
|---|---|---|
| Invalid | Spam, solicitation, duplicate, or no genuine service intent | Lead feedback and monitoring |
| Wrong service | Real request for a job the business does not perform | Profile job types |
| Wrong location | Real request outside the practical service area | Service-area settings |
| Qualified, mishandled | Fit lead missed, abandoned, or poorly handled | Intake and routing |
| Qualified, not booked | Fit lead handled but no appointment agreed | Offer, price, availability, follow-up |
| Booked | Specific next step confirmed | Show rate and sales process |
| Existing customer | Service or support request from a current customer | Reporting policy and routing |
| Unclear | Evidence is insufficient | Tracking or QA gap |
Then calculate the share in each bucket. Do not start by averaging every account or location together; one broken phone route can disappear inside a portfolio average.
Diagnose the pattern you find
Pattern 1: spam, robocalls, and solicitations
Separate obvious non-customer traffic from real prospects who simply did not buy. For every invalid contact, record:
- Lead ID and timestamp
- Call or message channel
- Caller identity pattern, if available
- First meaningful statement in the conversation
- Duplicate account or location, if relevant
- Google charge and credit status
Look for concentration by hour, location, service category, or repeated caller. A pattern is actionable; “LSA is all spam” is not.
Use Google’s lead feedback control accurately and monitor whether the lead is not charged, in review, charged, or credited. The current process is explained in our guide to Google LSA lead credits. Do not promise that every spam label will result in a refund.
Pattern 2: wrong-service inquiries
Compare the caller’s words with the job types enabled in the exact LSA profile. Common mistakes include enabling an adjacent service for volume even though the business rarely accepts it, or leaving an old service active after staffing changes.
Google recommends selecting the job types you perform. That can expand reach, but it also means the profile must reflect what the team will genuinely fulfill. Remove misleading options; do not expect intake staff to repair a targeting promise after the phone rings.
Pattern 3: out-of-area leads
Confirm whether the request was truly outside the configured area or merely outside the dispatcher’s preferred route that day. If the profile advertises the location, the lead may be working as configured.
Google’s performance guidance encourages broad service areas. If a lead falls outside the business’s service area, GEO_MISMATCH remains a valid dissatisfied-lead feedback reason in the Google Ads API. However, Google’s separate automated-credit policy says “geo not serviced” is not supported for credits. Submit accurate feedback, but do not present that reason as a guaranteed—or currently supported—path to a credit.
The practical targeting compromise is to advertise the broadest area the business can reliably serve—not the broadest map it can select.
Pattern 4: missed calls and slow responses
Google explicitly includes responsiveness in the LSA auction and notes that missed calls may negatively affect it. Its ad ranking documentation also includes average response time in profile quality.
For each missed opportunity, check:
- Did the call reach a person?
- Did a forwarding or IVR system fail?
- Was the lead received inside advertised hours?
- How long until the first meaningful response?
- Did the responder confirm service, location, and next step?
If half the “bad leads” are unanswered, narrowing targeting will not solve the main loss.
Pattern 5: fit leads that do not book
Listen for the moment the conversation breaks:
- No appointment or consultation was offered
- The available time did not fit
- The prospect asked for a price and received no useful next step
- Intake could not explain the process
- The business did not follow up
- The prospect was comparison shopping
These are conversion reasons, not invalid-lead reasons. Report them to the sales or operations owner with examples.
Use a scorecard that produces a decision
A complicated 100-point score can create false precision. For most LSA accounts, four yes/no gates are easier to audit:
| Gate | Question |
|---|---|
| Real demand | Is this a genuine prospective customer rather than spam or a vendor? |
| Service fit | Does the request match a service the business accepts? |
| Location fit | Can the business serve the location under its stated rules? |
| Commercial fit | Does the lead meet legitimate business acceptance criteria, such as case type? |
If all required gates pass, call the lead qualified. Track urgency, budget, or booking readiness as secondary attributes rather than changing the definition after seeing whether the sale closed.
A 30-day correction plan
Week 1: establish the baseline
- Review 50 recent leads.
- Agree on reason-code definitions.
- Calculate qualified rate, booking rate from qualified leads, and net cost per qualified lead.
- Save five representative conversation examples.
Week 2: fix the largest upstream mismatch
- Correct job types or service areas if they drive the largest bucket.
- Repair phone routing and notification ownership if missed leads dominate.
- Keep a dated change log.
Week 3: improve the conversation
- Require intake to confirm service and location early.
- Define the next step for price questions, unavailable slots, and after-hours inquiries.
- Review five qualified-but-unbooked conversations with the team.
Week 4: compare the same metrics
- Use the same definitions and a fresh sample.
- Compare reason shares, not only total lead volume.
- Keep changes that improved qualified-lead cost without damaging booked-job volume.
Avoid making multiple account, staffing, and script changes on the same day. You will not know what caused the result.
What Google can and cannot tell you
Google’s LSA reports show lead volume, charges, channels, credits, and bookings. They do not know all of your internal acceptance rules or whether a rep handled a viable call well.
Google says feedback in the Lead Feedback Survey helps it understand advertiser preferences. Treat that as useful input, not a promise that rating leads directly controls future ranking or guarantees a specific lead mix.
How LeadUp supports the audit
LeadUp connects to Google LSA accounts and brings supported call transcripts, summaries, consistent qualification, ratings, credits, and cost-per-qualified-lead reporting into one place. The same built-in qualification framework applies across every client. Agencies can review and submit eligible ratings themselves or enable complete automation so LeadUp submits them automatically.
The tool reduces review time and removes account-by-account variation by applying one qualification framework. Your team can keep control of rating review and submission or choose the fully automated workflow.
Bottom line
Do not solve “low-quality leads” as one problem. Audit the conversations and separate invalid traffic, targeting mismatch, intake failure, and sales loss.
Once every no-booking outcome has a reason and an owner, the next action becomes obvious: correct the profile, fix routing, improve intake, submit accurate feedback, or change the offer. That is far more useful than simply lowering the lead-quality score.