Leads From Outside Your Service Area: 5 Causes

If your phone is ringing with jobs you cannot drive to, you are not looking at one broken setting. You are looking at five channels with five different causes, four of which are working exactly as designed.

The short answer: Google Ads ships on a default that deliberately includes people who are not in your area, Meta removed the control that would have fixed it, Local Services Ads stopped refunding out-of-area leads entirely, and organic and AI search have no location setting to get wrong. Which one is hurting you determines the fix, and they are not interchangeable. Find out which channel is leaking before you touch a setting.

Diagnose before you change a single setting

Take your last 60 days of inquiries and build one table with two columns: lead source, and the postal code of the job rather than of the person. Then count out-of-area leads by source.

Almost every owner who does this is wrong about the culprit. They have spent weeks tightening a Google Ads radius while the actual leak was a service area page ranking in a city two hours away, or a Meta ad set with an expansion checkbox nobody knew existed. If you cannot see out-of-area volume broken out by source, every change you make is a guess, and you will not be able to tell afterward whether it worked. This is why lead source belongs on the record at intake, not in a spreadsheet someone updates on Fridays: a lead system that captures source and job address on the same form makes this a two-minute filter.

Cause 1: Google Ads defaults to including people who are not there

This is the most common cause, the easiest to fix, and Google is completely open about it.

When you set a location in Google Ads there is a collapsed section beneath it called Location options. The default is "Presence or Interest," which Google's help page describes as broad geo targeting that reaches "people who not only exist in your targeted locations, but have shown an interest in your targeted locations." Someone in another state who read an article about your city last week qualifies. They will never call you, and you pay for the click.

Google does not hide its reasoning. The same page carries this tip: "Advertisers who switched location targeting from 'Presence' to 'Presence or Interest' in the Travel, Real Estate, and Education verticals view +5% more conversions on Search campaigns," sourced to Google internal data from 21 May to 1 June 2022. Read the verticals again. Travel, real estate and education are three categories where wanting to be somewhere else is the entire purchase. A homeowner in Kentucky researching your city is a live prospect for a realtor and a dead one for a garage door company.

The fix takes under two minutes. Go to the campaign, Settings, Locations, expand Location options, and switch Target from "Presence or interest" to "Presence." Do it in every campaign individually, because it is not an account-level setting.

Two caveats. "Presence" still means people who are in or regularly in your area, and Google has never published what "regularly" means. And Google states plainly that location targeting runs on signals from "users' settings, devices, and behavior on our platform" and that "100% accuracy is not guaranteed in every situation." There is no setting that reaches only people standing in your service area right now. Note too that Google does not permit radius targeting under 1 km, so a very tight circle around your shop has a floor.

Cause 2: Meta removed the control that would have fixed this

Meta advertisers get told to check their radius. The radius is usually not the problem, and the control they actually need was taken away.

There used to be four ways to define a targeted location: living in it, recently in it, traveling in it, and living in or recently in. As Jon Loomer documented in his March 2025 breakdown of location targeting, Meta collapsed all four into one. The only survivor is "living in or recently in." You can no longer tell Meta to reach only residents of your city, which for a service business is the single setting you would want.

Then the radius. The default when you target a city is plus 25 miles and the tightest you can set is plus 10 miles. For a Denver business, Loomer notes, plus 25 miles pulls in Boulder, an hour from other points inside the same circle.

Then the checkbox. In the ad set under Audiences, Locations sits an option worded "Reach more people likely to respond to your ads. Also show ads to people who are interested in or near this location." It is frequently checked by default. A window cleaning operator posting on r/WindowCleaning in early 2026 described exactly this: a Denver service area at plus 17 miles, leads arriving from Arkansas, Florida and Kentucky. A commenter, 6133mj6133, walked them to that checkbox and noted it means "people who ever search for Denver will see your ads too. It's useless for window cleaning ads."

Even with all of that off, Meta's documentation concedes that "because these signals vary, complete accuracy cannot be guaranteed. You may occasionally see a small number of ad impressions, or even receive a message or lead, from outside of your location settings." A small number. If you are getting a flood, one of the three causes above is still live.

Cause 3: Local Services Ads stopped crediting out-of-area leads

This is the change most contractors have not caught up with, and the most expensive one on the list.

Google's Local Services documentation on automated lead credits contains one sentence that changes the economics of the channel: "Google no longer supports credits for 'job type not serviced' and 'geo not serviced' leads." The manual dispute where you flagged a wrong-city lead and got your money back is gone for exactly that reason code.

What replaced it is automatic and narrower. Models assess leads at first contact, and leads judged invalid or low quality are not charged. Charged leads get reassessed and may be credited later, applied to your account balance in most cases within 30 days, though "the original lead charge will still appear on your invoice." Credits are unavailable entirely for health care verticals, tax specialists and advertisers in EMEA.

Google's own guidance here is unambiguous and slightly bleak: "If you're receiving unwanted leads, revisit your service areas, job types, and categories," while warning that tightening those settings "could reduce the number of leads you receive." That is the deal. On LSA, geography is a pre-purchase decision now, not a post-purchase dispute. If you have been running loose service areas assuming you could dispute the bad ones, price that assumption out of your budget. Our breakdown of Local Services Ads for contractors covers where the channel still earns its keep.

Leave lead feedback anyway, even though it no longer refunds geo mismatches: the rating survey is the input the matching models use to decide what to send you next.

Cause 4: Organic and AI search have no location setting at all

Here is the part no one tells contractors, and it is why this problem got noticeably worse in 2026.

Whitespark's Local Search Ranking Factors survey asks 47 local search experts to score 187 factors across a two-hour survey. The 2026 edition added a new scoring dimension for AI search visibility alongside the map pack, local organic and conversion dimensions. Comparing how one factor scores across those dimensions tells you something no ad setting will:

Read the first row. In the map pack, physical distance between you and the searcher is the second strongest factor of 187. In an AI answer it drops to 52nd. The proximity governor that has always quietly protected local businesses from irrelevant demand does not apply when an assistant is doing the answering.

Now the second row. What takes its place is the geographic wording of your content, which climbs to 2nd in local organic and 6th in AI search. Your service area pages are not a description of your targeting. In those two channels they are your targeting. If you published a page naming eighteen towns because someone said it was good for SEO, that page is doing exactly what you built it to do, for people two hours away, and there is no radius control anywhere to walk it back.

That gives you a shortcut. If distant leads survive after you have ruled out paid, look at your city pages before anything else. And note the flip side: because proximity is the number two map pack factor, the map pack is almost never the source of a distant lead, so you can eliminate it early. If your problem is the opposite one, ranking near home, how to rank in the Google map pack is the other half of this.

Cause 5: The lead sellers use their radius, not yours

If some of your out-of-area leads arrive through Angi, Thumbtack, Networx or a similar marketplace, none of the fixes above touch them, because you are not the one doing the targeting. Thumbtack's own community carries recurring threads titled "Getting leads outside my area" and "Why am I getting charged for leads outside of my service area," where the standard answer is to submit a refund request for each one. That is the structural issue in a sentence: on a marketplace you do not prevent bad leads, you appeal them, one at a time, after being billed, on the platform's timeline and against its judgment. If you are reducing that dependency, how to stop paying for shared leads covers the exit sequence.

The real problem: platforms target people, your job is at a property

Step back from the settings and the reason this keeps happening is structural.

Every platform on that list targets a person's location, inferred from device signals, IP address, profile data and behavior. Your business is not defined by where a person is. It is defined by where the property is. A homeowner can research a roof replacement from an airport lounge and the job is still on your street. A landlord in Toronto can own the duplex three blocks from your shop. In both cases the platform's location signal is correct and completely irrelevant to whether you can do the work.

No ad platform has a field for the job address, because none of them knows it. So the targeting layer can never fully solve this. The decision about whether a lead is serviceable can only be made where the job address first appears, which is your form.

The form fix that works on every channel at once

Make the job postal code a required field, and make it the first one. It is the only intervention here that works identically across paid search, paid social, organic, AI search and marketplace leads, because it runs after the lead arrives and before it reaches your phone. Four rules:

1. Ask for the job address, never the person's address. Label it explicitly: "Where is the work being done?" You are qualifying a property, not a customer.
2. Put it first, above name and phone. A required field near the top costs almost no completion rate and screens the whole submission. Buried at the bottom it just annoys people who already typed everything else.
3. Route on it automatically. In-area leads go to whoever books. Out-of-area leads go to a separate queue with a polite decline template.
4. Keep the out-of-area ones. That queue is your evidence file, and it is what tells you next month whether your Presence fix actually worked.

This beats blocking by IP or detected location because it does not throw away good jobs, and blocking does. Rule 4 is the one most people skip, and it is what turns a filter into a feedback loop. If your leads currently land as raw email notifications none of this is possible, because there is no structured field to route on. That is the same failure described in why a website gets traffic but no calls: the intake does no work, so the owner does all of it.

Which out-of-area leads are actually worth keeping

Not all of them are junk, and treating them as one category costs real money. Before you decline, check for four patterns:

• The absentee owner. Lives elsewhere, owns property in your area. The person is out of area, the job never is. These convert well because there is no second opinion in the driveway.
• The adult child. Arranging work on a parent's house from another city. Often urgent, often pays fast, property is local.
• The relocation. A buyer closing in six weeks who wants work booked for move-in. Long lead time, high intent, usually comparing nobody.
• The just-outside job with the right ticket. A 50-minute drive is a bad service call and a perfectly good install.

For that last one the test is drive time against ticket size, using your own numbers: round-trip hours times what a productive hour is worth to you, plus fuel, against the gross profit on that job type. This is why operators disagree so loudly. On the same r/WindowCleaning thread one commenter argued for hyperlocal 3 to 5 mile circles while another said they run a 52 mile service area profitably. Both can be right, because route density matters enormously for a $300 recurring job and barely at all for a $12,000 install.

The 20-minute audit

In this order, cheapest and most certain first.

1. Build the source and job postal code table for the last 60 days. It tells you which of the remaining steps matter.
2. In every Google Ads campaign, expand Location options and switch Target to "Presence." Per campaign, not per account.
3. Pull the matched locations report, filter for clicks with zero conversions over 30 days, exclude anything outside your area.
4. In every Meta ad set, open Audiences, Locations, and uncheck "Reach more people likely to respond to your ads."
5. Reduce Meta radii toward plus 10 miles, or replace one wide circle with several tight ones on the routes you want.
6. In Local Services Ads, tighten service areas and job types, and accept the volume drop. There is no refund path for geo mismatches now.
7. Open every service area page and delete any city you would decline. Those pages are your organic and AI targeting.
8. Add the required job postal code field above name and phone, and set up the two routes.
9. Re-run the table in 30 days against the same window length. Out-of-area count by source is your scoreboard.

Steps 2 and 4 take about ten minutes combined and usually account for most of the volume. Step 7 fixes the leads nobody can otherwise explain.

The bottom line

Out-of-area leads feel like a targeting failure. Mostly they are a default-settings failure plus a structural mismatch nobody can configure away. Google Ads ships you interest-based traffic on purpose, Meta removed the setting that would have stopped it, Local Services Ads will not refund a geo mismatch anymore, and organic and AI search never had a radius at all.

Two moves survive all of that: fix the defaults once, then qualify on the job's postal code forever. The first stops you paying for people who were never going to call. The second means it stops mattering where the person was sitting when they filled out your form.