Confirm the symptom
Confirm what changed before assigning a cause.
Google LSA problem diagnosis
Google LSA Leads Suddenly Stopped?
Trace when LSA leads dropped, then check visibility, demand, and contact handling before changing several settings at once.
This page gives a public diagnostic path. It does not expose PrimeLSA scoring, thresholds, or detection logic.
Lead-flow timeline
Trace when calls and messages changed before editing settings.
Lead-flow timeline
Recent baselineCalls and messages had a visible pattern.
Lead flow slowedContact volume dropped compared with that baseline.
Next reviewCheck visibility, demand, calls, and replies before editing settings.
Account changes to inspect
Visibility declinedLead volume often follows visibility trends, even when the account still looks active.
Demand shiftedDemand can change by season, market, category, or service area.
Response gaps appearedMissed calls or slow replies can turn available demand into lost opportunities.
Start with a focused diagnostic path
Treat the page as a triage path: confirm what the symptom looks like, check account details, avoid premature edits, then decide the next review.
Find the last normal contact
Mark the last period when calls or messages followed the expected account pattern.
Do not change everything
Hold broad account edits until the evidence supports one change.
Audit events around the break
Compare account, profile, verification, staffing, routing, demand, weather, and competitor events around that date.
Direct answer
What to check when Google LSA leads suddenly stop
A sudden stop in Google LSA leads can begin with visibility, eligibility, customer demand, call handling, message response, reviews, lead quality, or local competition. Build a timeline before changing several account settings.
Compare the lead drop with impressions, phone calls, messages, booked outcomes, and recent market events. If the account still receives calls or missed calls, inspect Google LSA call analysis before assuming demand disappeared.
A focused review should answer whether the account stopped being visible, stopped attracting the right customers, or stopped converting the contacts it still received. Advantage keeps the next action tied to the account record.
If the symptom overlaps with another issue, return to the Google LSA problems hub, compare nearby problem paths, and review response workflows such as Google LSA auto reply. Many LSA changes look similar in the dashboard. Confirm which metric changed first, then check adjacent problems before editing budget, service areas, categories, or profile fields. This keeps owner and agency reporting tied to a visible symptom, a recent baseline, and one measurable next action.
Confirm the timeline
Compare the drop with the recent lead baseline, not only the current dashboard status.
Inspect account evidence
Compare visibility, calls, messages, reviews, lead quality, and account-health changes.
Protect the signal
Avoid changing budget, categories, hours, and service areas at the same time.
Symptom evidence
Common signs your LSA leads have stopped
Use these signs to determine whether your LSA leads have stopped. Compare the account's dated records with its recent baseline before editing budget, categories, territory, or profile details.
LSA leads depend on visibility, customer demand, response behavior, and account health.
Lead flow drops
Calls or messages fall sharply compared with the recent baseline.
Active but quiet
The account appears active but customers are not contacting the business.
No clear cause
The team cannot tie the change to a specific edit.
Why the dashboard feels unclear
A zero-lead day can begin in visibility, demand, or intake
Customer demand and ad visibility come before lead volume. Calls and messages then depend on how the team handles each contact. A quiet period can begin at any stage, so the diagnosis needs a timeline across the full sequence.
Short date ranges can exaggerate normal variation, while long date ranges can hide the day the pattern changed. Start with the last normal interval and narrow toward the first sustained break in impressions or contacts.
Demand changed first
Search activity fell while account coverage and response remained stable.
Visibility changed first
Impressions weakened before calls and messages slowed.
Contact handling changed first
Demand and visibility remained, but calls, replies, or booking outcomes broke downstream.
Do not make several rescue edits on the first quiet day
Simultaneous changes to budget, hours, categories, service area, profile details, and routing erase the original timeline. The team then cannot tell whether lead flow returned because of an edit, normal demand, or a market shift.
- Do not compare a partial current day with a completed prior day.
- Do not assume zero contacts means zero impressions.
- Do not increase budget before checking whether recent calls or messages were missed or mishandled.
Public-facing categories
Likely Causes
The causes below are public-facing categories, not proprietary PrimeLSA detection logic.
Visibility declined
Lead volume often follows visibility trends, even when the account still looks active.
Demand shifted
Demand can change by season, market, category, or service area.
Response gaps appeared
Missed calls or slow replies can turn available demand into lost opportunities.
Account record
LSA leads depend on demand, visibility, and contact handling
LSA leads depend on visibility, customer demand, response behavior, and account health.
Review map
Keep the public explanation useful without publishing scoring, thresholds, formulas, or internal diagnostic rules.
Visibility
Where the account appears and where it does not.
Response
How calls, messages, and follow-up changed.
Market
What moved around demand, reviews, and competition.
How to diagnose this issue
Build a before-and-after timeline. Put impressions, calls, messages, missed contacts, and booked outcomes on the same dates. Add account edits, verification events, profile changes, staffing gaps, routing changes, holidays, severe weather, and changes in visible competitors beneath the chart.
The first metric or event to move becomes the working hypothesis. If impressions fall first, review visibility and demand. If contacts remain but bookings fall, review answer coverage, lead fit, and follow-up. Keep the conclusion provisional until another comparable period confirms it.
Baseline window
Choose recent comparable days or weeks with normal contact flow.
Break window
Identify the first sustained change. Ignore a single isolated low point.
Event ledger
Place account, staffing, routing, market, and seasonal events on the same timeline.
Where Advantage fits
How Advantage organizes the evidence when your LSA leads have stopped
Advantage aligns account changes and contact handling around the break point. The user can compare the sequence and decide whether to inspect visibility, response, lead quality, or account health.
Anchor the analysis to a date
Start from the last normal and first quiet periods. An undated account snapshot hides the sequence.
Connect upstream and downstream
Read visibility trends beside calls, replies, lead feedback, and booked outcomes.
Preserve the test
Document the next check and avoid mixing it with unrelated edits.
References
Use Local Services Ads impressions and lead records, call and message timestamps, missed-call routing, booking records, account history, verification status, and staffing notes.
Keep the before-and-after ranges comparable. Annotate holidays, storms, closures, or other local events that changed either demand or the team's ability to answer.
Related LSA issues
Similar symptoms can overlap. Switch paths before assuming the account has only one cause.
LSA active but not showingReview why an active LSA account may not appear in the market.LSA impressions droppedReview visibility drops before changing budget.LSA cost per lead increasedReview CPL movement without guessing at the cause.Visibility varies by cityReview uneven visibility across cities and service areas.Performance changed without editsReview account movement when no obvious edits were made.
FAQ: Google LSA Leads Suddenly Stopped?
Clear answers about service fit, account review, and the next step to take.
Leads may stop because visibility changed, demand dropped, eligibility moved, calls were missed, or the account conditions shifted.
Continue the LSA diagnosis
Continue with related Local Services Ads guides, tools, and account-review resources.
LSA active but not showingReview why an active LSA account may not appear in the market.LSA impressions droppedReview visibility drops before changing budget.LSA cost per lead increasedReview CPL movement without guessing at the cause.Visibility varies by cityReview uneven visibility across cities and service areas.All Google LSA problemsReview the full problem library.Advantage by PrimeLSAConnect the symptom with the account record.How to pay for Google LSAsSeparate payment method, weekly budget, charged leads, and credits before changing spend.How LSA bidding worksCompare bid modes, budget support, Target CPL, and Max per lead before changing bids.How to view LSA reportsCheck the native report for charged leads, spend, credits, and lead type before changing settings.LSA ROI calculatorEstimate spend, booked jobs, revenue, ROAS, and break-even before scaling.Google LSA call analysisReview missed calls, spam, booking gaps, and call quality before changing account settings.
See why your LSA leads suddenly stopped.
Use Advantage to connect the public symptom with account data, calls, replies, reviews, lead quality, and market changes.