Your Google Local Services Ads Paused? Here's How to Fix It in 2026

If your Google Local Services Ads stopped running without warning—or you're getting charged for leads that shouldn't have counted—the process for fixing it has changed significantly since 2024.

Google overhauled how LSAs work behind the scenes over the past 18 months. The manual dispute button is gone. Policy review moved to Policy Manager. And what triggers a pause changed with the July 2025 Terms update that paused thousands of accounts when advertisers didn't see the notification in time. If you're troubleshooting LSAs right now, here's exactly what's happening and how to fix it.

The Most Common Reasons LSAs Pause in 2026

In most cases, a suddenly paused Local Services Ad traces back to one of four things:

• Terms acceptance required. In July 2025, Google updated its Local Services Ads Additional Terms and required all advertisers to accept the new language. Accounts that missed it saw ads pause automatically—often with a red banner at the top of the ads.google.com/localservices dashboard. Per Blazeo's LSA troubleshooting guide, this is the first thing to check. If there's a banner at the top of your dashboard, click through and accept it before doing anything else.
• Background check or license expired. LSAs for home services, healthcare, and legal require ongoing background check status and active license verification. Google's official LSA help documentation lists an expired or failing background check as one of the most common reasons ads stop showing. Adding a new technician, letting your business license renewal lapse, or a background check that didn't complete in time can all trigger a review that pauses your ads.
• Billing issue. A failed payment, an expired card, or a billing threshold mismatch can pause LSAs the same day. Check your Google Ads billing settings—not just your LSA account but the connected Ads account—and verify the payment method is active and current.
• Policy violation on a specific ad. If your ad itself was disapproved rather than your account being paused, the reason appears in Policy Manager inside your LSA account. PrimeLSA's disapproval guide explains that Policy Manager is now the place to go for ad-specific disapprovals—it shows the exact policy issue, not a generic error code.

The Right Order of Operations for Fixing a Paused LSA

Before submitting a review request or contacting support, identify the specific cause. Fixing the wrong thing and requesting review won't work—Google will deny it if the original issue is still active. Work through these steps in order:

1. Log into ads.google.com/localservices. Check for red banners or policy notifications at the top of the dashboard. If there's a Terms banner, accept it first before doing anything else.
2. Check your verification status. Under "Profile & Budget," look at background check status and license verification. Green means current. Yellow or red means action required—follow the prompts to update or re-verify the flagged item.
3. Open Policy Manager. Look for flagged ads or profile content. Read the specific policy reason exactly as stated—don't guess. Fix only what Policy Manager identifies. Changing unrelated fields can trigger a new review and extend your downtime.
4. Verify billing. Confirm your payment method is active, your billing address matches, and no spending threshold was hit that requires you to raise your budget cap.
5. Request review. Once you've addressed the specific cause, request a review from within your LSA account. Standard reviews complete within 2 to 5 business days. Background check disputes can take longer.

Google Removed the Dispute Button: What Replaced It

If you ran LSAs before August 2024, you remember the "Dispute" button that let you flag individual leads for review. That button is gone. Digital Harvest's LSA troubleshooting guide confirms Google replaced manual lead disputes with an automated credit system in August 2024.

How it works now: Google automatically reviews every charged lead within 72 hours of the charge. If the system identifies it as invalid—wrong number, spam call, outside your service area, wrong service category—it issues a credit automatically without you doing anything. You'll see the credit appear in your LSA billing summary.

For leads that don't get auto-credited and that you believe were invalid, your only option is the Lead Feedback Survey inside your LSA dashboard. Find the specific lead, click it, select "Dissatisfied," choose the reason that best fits (wrong number, spam, outside service area, already a customer), and submit. Per Google's official LSA support documentation, feedback is reviewed but does not guarantee a credit. This is advisory rather than a binding dispute mechanism.

What this means practically: you have less recourse on bad leads than you did before August 2024. The automated system catches obvious spam. Edge cases—leads where someone called, you couldn't reach them, the job was outside your area but technically in your zip code—go through the feedback survey and may or may not result in a credit. Budget for some percentage of leads that are invalid and won't get credited; that's the current reality of LSA.

What to Do When Your LSAs Run But Leads Don't Book

A live LSA that isn't producing booked jobs is a different problem than a paused account. If your ads are running but leads aren't converting to appointments, the issue is usually response speed—not the ad itself.

LSA ranking is partly determined by your response rate and speed. Google's documentation states explicitly that businesses that respond to leads quickly rank higher and show more often. Businesses that let calls go to voicemail or let messages sit unanswered for hours see their ranking drop over time, meaning fewer impressions at worse positions.

If your team is in the field during business hours and missing calls, an AI voice receptionist can answer LSA calls, qualify the lead, and book the appointment in real time. That response speed moves your LSA ranking up and your cost per booked job down—the two metrics that matter most in LSA performance.

How to Keep LSAs from Pausing Again

The businesses that maintain consistent LSA uptime do a few specific things differently:

• Set a calendar reminder for background check renewal. Background checks for LSA typically expire on an annual cycle. Set a recurring annual reminder in your calendar for 30 days before the expected renewal date. Letting it lapse is the most common reason accounts go into review during busy seasons when you're too distracted to notice the email notification.
• Give at least two people full LSA account access. If your account is tied to one email address and that person changes roles or leaves, you lose dashboard access. You can't respond to policy issues, update verifications, or accept Terms updates without logging in. Maintain admin access for at least two people.
• Accept Terms updates within 24 hours of notification. Google emails notification when LSA Terms are updated and acceptance is required. These emails are easy to filter or miss. Flag Google's notification sender address so it goes to your primary inbox, not promotions.
• Check your LSA dashboard once per week. Policy issues and verification warnings appear in the dashboard before they cause a pause. Catching them early means fixing them proactively instead of reacting after your ads go down.

If you want help auditing your current LSA setup—verification status, lead quality, response rate, and ranking position—request our free 24-hour audit. We'll tell you exactly what's limiting your LSA performance and what to fix first.

Sources

• Google: Why Aren't My Local Services Ads Running?
• Google: How to Fix a Disapproved Local Services Ad
• Blazeo: Fix Paused Google Local Services Ads — 5-Step Rescue Plan
• PrimeLSA: How to Fix a Disapproved Google Local Services Ad
• Digital Harvest: Google Local Services Ads Not Showing? Fix These 5 Issues