
LSA Geo-Targeting Cleanup: Finding the Zip Codes Eating 30% of Your Budget and Sending 5% of Your Jobs
You already know your Local Services Ads budget is finite. What most contractors don't know is where it's actually going — down to the zip code. Pull the geographic report on almost any LSA or Google Ads account running for a remodeler, builder, or home service pro, and the same pattern shows up: a handful of zip codes are eating 25-30% of total spend while producing a fraction of the booked jobs. The budget isn't being wasted on bad leads. It's being spent on the wrong map.
Geo-targeting cleanup is one of the highest-ROI, lowest-effort moves you can make inside an existing campaign. You're not raising your budget. You're not writing new ad copy. You're just telling Google to stop showing your business to homeowners you can't profitably serve — and redirecting that same spend toward the zip codes that already close for you.
Why your geo-targets drift out of alignment with your actual service area
Most home service accounts get their geo-targeting set up once, at launch, based on a rough service radius or a list of cities pulled from a map. That setup rarely gets revisited. Meanwhile your actual job mix shifts — a crew gets added, a neighborhood goes through a remodeling wave, a competitor starts undercutting you in one submarket. Six months later, the account is still targeting the original radius, but your close rate by zip code looks nothing like it did on day one.
The result is a budget that's technically "working" — leads are coming in, LSA is charging you per lead like it's supposed to — while a disproportionate share of that spend lands in zip codes with long drive times, lower average job values, or homeowners who were never going to hire a contractor from outside their immediate area. The campaign isn't broken. It's just pointed at the wrong map, and nobody's been back to check it since launch.
Finding the zip codes that are quietly draining your budget
You don't need a data analyst for this — you need about 20 minutes and the reports Google already gives you. In LSA, pull the geographic performance breakdown and sort by spend. In standard Google Ads, the same view lives under Locations in the campaign reporting tab. Either way, you're looking for the same thing: zip codes where spend is high but booked jobs are low or zero.
A useful gut-check: list your zip codes by spend, then list them again by closed jobs. Any zip code that shows up near the top of the spend list and near the bottom of the jobs list is a candidate for exclusion. In a typical home service account, 3-5 zip codes account for a wildly outsized share of wasted spend — often 25-30% of the budget for 5% or less of the actual closed business. That's not a rounding error. That's real dollars that could be redeployed into the areas already converting.
Cross-reference against drive time too. A zip code 35 minutes outside your core service area might convert fine on paper — the lead comes in, the call connects — but if your close rate on long-haul jobs is half what it is nearby, you're paying full price per lead for a discounted outcome.
Include, exclude, and the zip-code-level precision most contractors skip
Both LSA and Google Ads let you get far more granular than most accounts ever use. You can include specific zip codes, exclude specific zip codes, or target by city and county — and you can layer exclusions on top of inclusions to carve out the exact footprint you actually want to serve. If three zip codes inside an otherwise strong city are consistently unprofitable, you don't have to pull out of the whole city. You exclude those three and keep the rest running.
This is where most accounts leave money on the table. They set a radius or a city list once and never touch zip-code-level exclusions, even though that's the single most precise lever available. If you've got a 25-mile service radius but your actual profitable jobs cluster inside 12 miles, you're paying for impressions and leads across the other 13 miles of radius you never needed in the first place.
What to do with the budget you just freed up
Cleaning up geo-targeting isn't about spending less — it's about spending the same dollars more precisely. Once you've excluded the zip codes that were quietly eating budget, that spend doesn't have to sit idle. Redirect it toward your highest-converting zip codes by increasing bid adjustments there, or use it to expand into adjacent zip codes that share the same income and housing profile as your best-performing areas.
This is also the point where budget pacing and geo-targeting start working together instead of fighting each other. A weekly budget that looked "too tight" when it was spread across 40 zip codes — half of them unprofitable — can look generous once it's concentrated on the 15 that actually close. You don't need a bigger number. You need the number you already have pointed at the map that works. And if cost per lead has always felt like the wrong number to chase, geo-targeting cleanup is exactly where cost per booked job starts to pull away from cost per lead as the metric that actually matters.
Make this a recurring 20-minute check, not a one-time fix
Geo-targeting cleanup isn't a set-it-and-forget-it project. Your job mix changes, new competitors move into zip codes, and seasonal demand shifts which neighborhoods are actively hiring contractors. The accounts that stay efficient are the ones where someone pulls the geographic report on a recurring basis — monthly is plenty for most home service businesses — and makes small adjustments before a bad zip code has months to quietly drain the budget.
If you're not sure where to start, or you'd rather have someone look at your actual geographic spend data instead of guessing, book a free discovery call and we'll walk through your account together. United Foundry has helped more than 100 home service businesses get their lead systems running almost on autopilot, with 91% client retention and an average 81% increase in conversions once the budget is actually pointed at the zip codes that close.







