Google Ads Wrong Location Clicks Start in the Search Terms

Clicks from the wrong location come from two separate gaps in Google Ads. One is a setting: "Presence or interest" lets people outside your area into the auction. The other is the query itself: someone inside your area searches for a city you don't serve, and your ad shows because the user's location matches. Location exclusions check where the user is. They never read the words in the query, so they close neither gap on their own.

A worked example makes this concrete. An Austin plumbing company targets the Austin metro area. The budget is about $4,000 a month, and the average click costs about $10. The owner gets calls from San Antonio and Houston, and excluding those cities hasn't stopped them. Here is why.

Why location targeting lets the wrong people through

Google Ads location targeting looks at two things: where the user is, and what Google thinks the user is interested in. It doesn't check whether the search is about your area. That is the whole problem in one sentence.

When you target "Austin, TX", you aren't telling Google "only show my ad for searches about Austin." You are telling it "show my ad to people Google links to Austin." That link can come from physical location, from regular presence (commuters, people who work there), or from interest. The setting you pick decides which of those count.

Then the keyword match runs. Your keyword emergency plumber on broad or phrase match will happily match "emergency plumber houston". The keyword system doesn't care about the city in the query. The location system doesn't read the query at all. Each system does its job, and an Austin plumber still pays for a Houston query.

So when you see wrong-location clicks, the first question isn't "which locations do I exclude?" The question is "did the user come from the wrong place, or did the query point to the wrong place?" Those have different fixes, and mixing them up is why so many advertisers exclude half of Texas and still get calls from Houston.

"Presence or interest" is the default, and it lets outsiders in

Under "Presence or interest", the default for most campaigns, people outside your area can see your ads if Google decides they're interested in your area. For a local service business, switching to "Presence" is usually the single biggest fix for out-of-area clicks.

You'll find it under campaign settings → Locations → Location options. There are two choices for targeting:

• Presence or interest: people in, regularly in, or who've shown interest in your targeted locations.
• Presence: people in or regularly in your targeted locations.

Under the default, someone in Chicago searching "plumber austin" can see the Austin plumber's ad. Often that's fine. Maybe they own a rental property in Austin. But someone in Chicago who has been reading about Austin and then searches "water heater installation" with no city at all can also be counted as interested. That click is almost never a customer for an Austin plumber.

The cost of switching to Presence

Switching isn't free for every business, and you should know that before you change it. "Presence or interest" exists for good reasons:

• A moving company in Austin wants the Chicago family searching "movers austin" before they relocate.
• A hotel or wedding venue sells almost entirely to people who aren't there yet.
• A property manager works for owners who often live out of state.

If your buyers plan from somewhere else, "Presence" will cut real customers. If your buyers need someone at their door this week, like plumbers, electricians, locksmiths, cleaners or most clinics, "Presence" is almost always the right choice. Our guide to service-business negatives by intent covers the query side of the same distinction.

There's also a middle ground that many advertisers miss. You can keep "Presence or interest" and use negative keywords to block queries for places you don't serve. The setting brings in out-of-area people searching for your area. The negatives keep out people, anywhere, searching for other areas. More on that below.

What exclusions actually do

Location exclusions work on the user, not the query. If you exclude San Antonio, people physically in San Antonio stop seeing your ads. Someone standing in Austin who types "plumber san antonio" still sees them, because by the location rules they're in your targeted area.

This is the mistake behind most "I excluded it and it's still happening" complaints. The advertiser sees "san antonio" in the search terms report, excludes San Antonio in location settings, and next month the same terms show up again. The exclusion worked. It just blocked a different set of people from the ones who searched.

City names in the query are a gap exclusions can't see

Even with "Presence" turned on, people inside your area search for places outside it. Your ad shows because the user's location matches. The only thing that stops it is a negative keyword on the place name.

People type other cities for plenty of reasons. They're looking for a plumber at a parent's house in San Antonio. They're comparing prices for a job in Houston. They work in Austin and live in Waco, and they search from the office. In every case the user is in your targeted area and the query is about somewhere else.

Back to the Austin plumber. Over a month, the search terms report shows:

Round Rock is in the service area, so that row is fine. The other three rows add up to 34 clicks and $340. A location exclusion stops none of them. San Antonio and Houston searchers sitting in Austin are inside the target. "austin mn" (Austin, Minnesota) matches "austin" in the query and comes from users Google ties to Austin, Texas, either by presence or by interest.

$340 out of $4,000 looks small, until you remember that these terms come back every month and that each one teaches your bidding the wrong lessons. The Smart Bidding bad-data article explains that second cost. And most location leaks don't arrive as one big row. They come as dozens of one- and two-click terms: "plumber near pflugerville tx" is fine, "plumber killeen" isn't, "drain cleaning temple tx" isn't. That's the pattern described in low-volume terms add up.

Place names come in more forms than city names

When you scan for location terms, don't stop at city names. Wrong-location queries also show up as:

• State names and abbreviations: "plumber oklahoma", "tx" vs "ok", "austin mn".
• Neighbourhoods and suburbs of other cities: "katy tx plumber" is Houston's metro, not Austin's.
• Zip codes: "plumber 78201" is a San Antonio zip.
• Landmarks and institutions: a university, a military base, an airport in another city.
• Counties: "bexar county plumber".

A good way to spot these fast is to sort search terms by cost and scan only for proper nouns. The 20-minute search terms review has a workflow you can run this inside.

How to find out which gap you have

Use two reports side by side. The user-location report shows where clicks physically came from. The search terms report shows which places people asked about. If clicks come from outside your area, it's the setting. If the queries name outside places, it's the negatives. Most accounts have both.

The user-location report

In the Locations section of your campaign, Google gives you a report of where users actually were, separate from the list of locations you target. Look at it at campaign level for the last 30 to 90 days.

• If you see meaningful spend from cities or states outside your target, the "Presence or interest" option is letting people in. Switching to "Presence" is the fix.
• If almost all spend comes from inside your target and you still get out-of-area calls, the setting isn't the cause. The queries are.

The search terms report

Filter or sort the search terms for place names you don't serve. For Search, Shopping and Performance Max, Google reports search terms in the same place in the API (campaign_search_term_view), so a tool or script can read all three. In the interface, Performance Max terms are less complete than Search, and some terms in every campaign type are hidden for privacy. The hidden search terms article covers what you can still do about the part you can't see.

Reading the two together

The top row is the one to think about. Someone in Chicago searching "plumber austin" is not, by default, waste. For a plumber it often is, since the person doing the searching won't be at the property. For a mover it's the best lead you'll get all week. Decide by looking at conversions, not by rule.

Building location negatives that hold

Use phrase-match negatives on the place name alone: "san antonio", "houston", "austin mn". Put them in a shared list for Search and Shopping. For Performance Max, add them at campaign level. Then check every one against the places you do serve before you save.

Why phrase match on the place name

A negative only blocks what it matches. An exact negative [plumber san antonio] blocks that exact query and nothing else. "san antonio plumber", "24 hour plumber san antonio" and "plumber in san antonio tx" all still get through. A phrase negative "san antonio" blocks any query that contains those two words in that order, which is what you want for a place name.

Avoid broad negatives here. Broad, phrase and exact are the three negative match types, and broad negatives behave unpredictably across match types. For a place name, phrase is precise enough and wide enough.

Also note that negative keywords don't extend to close variants the way positive keywords do. A negative "san antonio" won't catch "sanantonio" or a common misspelling. If you see those in your terms, add them separately. The close variants article explains the asymmetry.

The ambiguous-name trap

This is where location negatives go wrong. Many place names exist in more than one state, or are also a street, a neighbourhood or an ordinary word.

• Georgetown is a city in the Austin metro. It's also a neighbourhood in Washington DC and a city in Kentucky. A negative "georgetown" blocks your own customers. Use "georgetown ky" and "georgetown dc" instead.
• Austin is a city in Minnesota as well as Texas. You can't negate "austin", obviously, but "austin mn" and "austin minnesota" are safe.
• Street names: downtown Austin has a San Antonio Street. A phrase negative "san antonio" would block "plumber san antonio street". That's a rare query, but in a dense city with streets named after other cities, check your own map.
• Ordinary words: a city called "Bastrop" is unambiguous. One called "Liberty", "Temple" or "Victoria" can also be a word, a business name or a surname. "temple tx" is safer than "temple".

Before you add a location list, run each name against your service area, your street names and your brand terms. A negative that blocks your own city is worse than the leak it fixes, and Google won't warn you. Negative keyword conflicts Google won't flag covers how to catch these. If impressions on a core keyword suddenly fall after you add a list, the keyword not showing impressions check is the first place to look.

Where to put the list

• Search and Standard Shopping: both accept shared negative keyword lists. Build one list, something like "Places we don't serve", and attach it to every campaign that targets the same area. If you run campaigns for several areas, keep a list per area, because Houston is a negative for the Austin campaign and a keyword for the Houston one. Account-level vs campaign-level lists goes through that structure.
• Performance Max: a Performance Max campaign doesn't accept shared negative keyword lists. It does accept up to 10,000 campaign-level negative keywords. For location negatives that limit is rarely a problem, but you'll have to add and maintain them per campaign. If your Performance Max negatives seem to be ignored, read why Performance Max negatives don't work before you add more.

Don't block what converts

If "plumber san antonio" converted last month, find out why before you block it. Maybe a customer has a second property. Maybe your team takes jobs on the edge of the area. Maybe the conversion is a spam form fill. A place-name negative is a business decision about where you'll work, not a cleanup task.

What negatives and settings won't fix

Some wrong-location clicks can't be fixed with either tool. Display, Video and App campaigns report no search terms, so there's nothing to negate. Hidden search terms can't be negated one by one. And clicks that are fraudulent or invalid are a separate problem with a separate process.

• Display, Video and App. These campaign types don't report search terms in campaign_search_term_view. If your out-of-area spend sits in a Display campaign, the levers are the location option, location exclusions and placement controls, not negative keywords.
• Performance Max's non-search inventory. Negatives only act on the search part of Performance Max. Out-of-area spend on its Display, YouTube or Gmail placements won't respond to them. See Performance Max placement exclusions, honestly for what you can and can't control there.
• Hidden terms. A slice of your search terms is never shown. If a city leak lives in that slice, you'll see it in the user-location report but not in the terms. Phrase negatives on the place names you do see still apply to hidden queries that contain them, which is one more reason to use phrase rather than exact.
• Bad location data. Users on VPNs, or devices that report a location far from the real one, can show up as out-of-area or in-area wrongly. Neither the setting nor negatives can fix that.
• Invalid clicks. If the "out-of-area" pattern is actually bots or click farms, that's a refund question. What you actually get from invalid-click refunds explains how limited it is.

Where PPCleaner fits, and where it doesn't

PPCleaner handles the query side. Every night it reads the search terms your Search, Shopping and Performance Max campaigns paid for, judges which ones were never going to convert, including those naming places you don't serve, and adds them as negatives. It never changes your location settings. That fix is yours.

What that means in practice:

• It catches the slow leak. The one-click "plumber killeen" and the two-click "drain cleaning 78201" that nobody spots in a monthly review are what a nightly pass is good at.
• It works across all three campaign types. That includes Performance Max, where the negatives go at campaign level because shared lists aren't accepted.
• It never blocks a term that converted in the last 90 days. If "plumber san antonio" brought you a real job last month, it stays live until you decide otherwise. That's on purpose. It also means a converting out-of-area term won't be blocked for you if you want it blocked. Add that one yourself.
• Every block can be undone in one click for 90 days. If a place-name negative turns out to hit a street or suburb you serve, you can reverse it without hunting through lists.

What it won't do: it doesn't touch budgets, bids, ads, keywords or campaign settings. It won't switch you from "Presence or interest" to "Presence", and it can't see search terms that Google doesn't report, so Display, Video and App spend is outside its reach. If the user-location report shows the leak coming from outside your area with no place name in the query, the fix is a setting change in your account, made by you.

The order that works: check the user-location report and decide on the location option first. Then clean the queries. The setting fixes who gets into the auction. The negatives fix what they're allowed to ask for.