Why Google Ads Is Showing Outside Your Service Area

Google Ads location targeting is not a hard fence. Learn why ads and leads appear outside your service area, what the reports mean, and what to change.

By Gavin Sevastian · Updated August 12, 2026 · 12 min read

An inquiry lands from three towns beyond the edge of your service area. You open Google Ads, see the right cities listed under Locations, and assume the setting failed.

It might have. It also might be doing exactly what it was told to do.

Google Ads location targeting is built from signals, not a line painted around a map. The default includes people who show interest in a place even when they are somewhere else. The reporting can describe either a physical location or a location of interest. And the address where the work is needed comes from the person, not from Google.

Those are three different facts. Until you separate them, every out-of-area inquiry looks like the same problem.

"Outside your service area" can mean three different things

The device or person appeared to be somewhere else

Google estimates where someone is, or is regularly located, from signals that can include an IP address, device location, Wi-Fi, GPS, cell data, settings and past behaviour. It does not promise that any one signal is exact.

A person can therefore click while travelling, at work, on a mobile network whose IP resolves elsewhere, or from a place Google considers part of his regular pattern. That signal describes the person at the time of the ad interaction. It does not tell you where the property is.

Google matched the interaction to a physical place or a place of interest

The Matched locations report is not a clean list of customer addresses. Google's geographic performance documentation says a matched location can be the user's physical location or a location the user showed interest in.

That means a row labelled Toronto does not necessarily mean the person stood in Toronto. It can mean Toronto was the location signal that matched the campaign. The same report can also contain unspecified areas when Google cannot resolve a useful location from the available information.

The job address is outside the territory you will actually serve

This is the business fact that decides whether the inquiry is useful. A homeowner can search from an office downtown for work at a house in another municipality. A landlord can arrange a repair from another province. Someone preparing to move can research contractors before arriving.

The property address may be inside your service area while the click signal looks outside. The reverse can happen too. A person can click from inside your target and ask about a property you will not travel to. Google Ads cannot know your dispatch rules from the campaign map alone.

The default is broader than the locations list suggests

Presence or Interest includes people who are not there

Google's default and recommended positive setting is Presence or Interest. Its advanced location options page says this reaches people likely to be in or regularly in the places you target, plus people who have shown interest in those places.

Interest can come from a current search, an earlier search, a past physical location, a Maps search, or the context of content someone viewed. Google's broader explanation of how location targeting works also says location of interest is not restricted to the person's country or to the Google domain being used.

That breadth makes sense for a hotel, university or real estate listing. The customer can buy while standing somewhere else. A contractor who has to put a crew and a truck at a property has a narrower reality.

Presence narrows the audience, but it does not draw a perfect fence

The alternative positive setting reaches people Google believes are in or regularly in the targeted places. It removes the location-of-interest half of the default. For a local service business that only works inside a fixed territory, that can match the commercial constraint more closely.

It still is not GPS enforcement. Google calls location targeting its best effort and states that 100% accuracy is not guaranteed. It may also show ads in nearby, closely related areas when the exact area has low population, insufficient data or no available target at that level.

So the right expectation is fewer clearly irrelevant out-of-area interactions, not zero. If somebody promises a radius setting will block every person on the wrong side of the circle, he is promising a control Google says it does not provide.

Targeted locations and matched locations are not the same report

Targeted locations tells you what you asked for

The Targeted locations view organizes performance around the places included in the campaign. It answers whether a target you selected produced impressions, clicks, cost and conversions.

That is useful for comparing included markets. It does not prove every person stood inside the selected boundary. Reading it as a physical-location ledger turns a campaign setting into evidence it cannot supply.

Matched locations tells you what Google associated with the interaction

The Matched locations view organizes performance around the location Google used when the ad appeared. Again, that may be physical location or interest. The "Most specific location" column has the same limitation.

This is the better view when an owner says, "I am paying for the wrong towns," because it shows where the platform associated delivery. It still has to be read beside the campaign's advanced location option and the actual job addresses.

One more source of confusion is the Distance report, which requires location assets. Google measures from the location that triggered the ad to the business location, and notes that the reported distance can exceed the campaign radius when the person's location of interest or the business location shown is farther away. A surprising distance is evidence to interpret, not proof the radius was ignored.

Exclusions do a narrower job than their name suggests

Exclusion currently means likely presence

Google's current advanced-options documentation says location exclusions use Presence. In plain language, an excluded city blocks people Google believes are in that city. It does not let you build the inverse of the whole world outside your service area, and it does not turn the included region into a hard border.

That matters because an owner can add a long list of excluded cities and still receive an interaction associated with location interest, an imperfect device signal or a nearby related area. The list did not necessarily malfunction. It may have been asked to solve the wrong kind of leakage.

A single odd inquiry is weak evidence for another exclusion

Exclusions can be useful when a real, repeated pattern comes from a place the business will not serve. They can also remove legitimate demand when they are added from one confusing lead.

Before treating a town as the problem, separate the Google location signal from the customer's property address and the search itself. Somebody searching for a Toronto contractor from Vancouver may be moving to Toronto. Somebody physically in Toronto may want work done in Vancouver. Only one of those is useful to a Toronto contractor, and the city attached to the click does not settle which one.

The shape on the map may not match the shape of the business

Cities, postal codes, regions and radii are different target types

Google supports location types such as countries, provinces, cities, municipalities, postal codes and radii, but availability varies by country. Its location target types page is explicit that not every type is available everywhere and that Google Ads does not determine geographic borders.

A city target follows the geographic entity Google recognizes. A radius draws a circle. Neither understands that your crews travel east along one highway but will not cross a bridge west, or that a profitable replacement job can travel farther than a short repair.

Your service area is an operating decision first. The campaign is a representation of that decision, and the representation gets worse when the business itself has never settled which places it will actually serve.

Local market pages provide context, not targeting instructions

The GTA resource explains the municipalities and market conditions behind work across the region, while the Toronto resource focuses on the city's contractor market. Neither page can tell another business where its crew should drive.

The useful boundary is the one the owner will honour when the phone rings. If the office accepts jobs outside the advertised territory whenever the invoice is large enough, the true service area is conditional. The tracking and the campaign need enough context to reflect that honestly.

An out-of-area lead is not automatically click fraud

Location confusion and invalid traffic are separate diagnoses. Google can validly serve an ad under Presence or Interest to a real person who cannot hire you. The click may be commercially useless and still be a genuine click.

Fraud means the interaction was not the result of genuine user interest, including intentional, automated, accidental or duplicate activity. That needs different evidence. The guide to Google Ads click fraud and invalid clicks explains what Google filters, what it credits later and why a surprising IP or location is not proof by itself.

Bad inquiries sit in a third bucket. A real person may be in the right place and still want the wrong service, a job, a cheap part or something you do not offer. Why Google Ads sends bad or spam leads separates those paths so geography does not absorb every lead-quality problem.

What a useful location review should reconcile

Start with the business promise, not the map

The question is not whether the campaign contains the cities somebody remembers adding. It is whether the account's interpretation of geography matches the business's current promise.

That means the customer-facing service area, the places crews actually accept, the positive targeting option, the locations included and excluded, and the platform's matched-location evidence need to tell one coherent story. When they do not, changing one pin on the map can hide the contradiction without resolving it.

Judge patterns with connected business evidence

Google recommends using geographic performance to refine location targeting. Its refinement guide points advertisers toward performance by location, relevant regional landing pages and exclusions where regions consistently underperform.

For a contractor, performance has to mean more than a conversion marker. An inquiry that Google counted can still be outside the practical territory. A city with fewer leads may produce better jobs. Location settings become useful when paid interactions remain connected to customer addresses and booked work rather than stopping at a form count.

The account also needs reliable measurement before geography can take the blame. Common Google Ads mistakes contractors make covers the broader failures that can make a healthy location report sit beside an unhealthy business result.

What the map can and cannot tell you

Google Ads geo targeting controls eligibility through signals. It does not certify a person's physical position and it does not know the final job address.

For a contractor with a fixed territory, I would question whether the extra reach in Presence or Interest serves the business. Presence is the closer conceptual fit when the business only wants people in or regularly in a defined area, but it remains a best-effort signal rather than a perfect fence. Matched locations then show the locations Google associated with delivery, not a list of properties that asked for work.

Once those meanings are separated, the response becomes calmer. A real setting mismatch gets corrected. A service-area conflict goes back to the business. A bad inquiry goes to the traffic and page diagnosis. Suspicious activity goes to the invalid-click evidence. You stop asking one map to answer four different questions.