Does location targeting stop ads showing for other cities' names?

No. Location targeting controls where the searcher is (or shows interest in), not which place names appear in the query. A user physically inside your targeted area can search "plumber Denver" while you serve Chicago, and because they are in-target, your ad is eligible to show. The place name is part of the query text, and query text is governed by keywords and negative keywords, not by the location setting. To stop irrelevant place names you add them as negative keywords; to stop searchers in the wrong place you use location targeting and exclusions. They are two separate controls solving two separate problems, and confusing them is why out-of-area terms keep appearing in the report despite tight targeting.

What is the difference between a location exclusion and a location negative keyword?

A location exclusion removes a geographic area from your targeting — it stops your ad serving to people who are in, or searching about, that place. A location negative keyword blocks a place name as query text — it stops your ad showing when someone types that word, regardless of where they are. If out-of-area city names keep appearing in your search terms report, the fix is usually negative keywords for those city names, because the searchers are inside your target area but typing a different location. Location exclusions do nothing about the query text; they only reshape who is eligible by geography.

Why do city names trigger irrelevant clicks even with exact match?

Because exact match now includes close variants and reordered words with the same apparent intent, and broad match expands far wider. A keyword like [emergency plumber] can match "emergency plumber near downtown" or a reordered, paraphrased variant that pulls in a location modifier you never targeted. Google reads the core intent (plumber) plus a location and considers the ad relevant even when a second modifier changes the intent entirely — for example a job seeker adding their city. The looser match types get, the more geo-modified variants slip through, which is why location-name negatives matter more as match types broaden.

What geographic negative keyword patterns should I add first?

Start with three patterns. First, out-of-area place names: cities, states, or countries you do not serve that keep appearing in the report. Second, intent-flipping geo modifiers — "[service] jobs", "[service] salary", "[service] training", "[service] near me" when near-me is out of range — because people naturally append their city to these. Third, wrong-region qualifiers if you are local: adjacent towns or regions outside your radius. Add out-of-area place names as phrase or exact negatives so you do not accidentally block a legitimate query that merely mentions the area, and review the search terms report to confirm you are catching the real patterns rather than guessing.

Should location negatives go at campaign or account level?

Put genuinely universal geographic negatives — countries or regions you will never serve, and permanent intent-flippers like "jobs" or "salary" if you are not hiring — on an account-level or shared negative list so every campaign inherits them. Keep campaign-specific geography, such as a city one campaign targets but another excludes, at the campaign level so a shared list does not block a term one campaign actually wants. The test is whether the negative is true everywhere in the account: if yes, lift it to a shared list; if it depends on which campaign is serving, scope it to that campaign.

Location-Name Search Terms: Why Targeting Won't Stop Them

Location targeting does not stop your ad from showing for other cities' names, and misunderstanding that is why out-of-area search terms keep draining budget in accounts with supposedly tight geographic settings. Location targeting decides who is eligible to see your ad based on where they are. The place name a person types is query text, and query text is governed entirely by your keywords and negative keywords. Someone standing in your targeted city can search "roofer Miami" while you serve Seattle, and because they are physically in-target, your ad is eligible to serve on a query about a city two thousand miles away.

These are two different controls solving two different problems, and this post is about keeping them straight. We will separate location targeting from location negatives, show why broadening match types make geographic misfires worse, catalogue the query patterns worth negating first, and cover how to structure geographic negatives so a shared list does not block a term one campaign actually wants. The underlying report never changes: as Google's own guidance puts it, the search terms report is where you find the actual queries that triggered your ads and turn them into negative keywords — place names included.

Targeting is not negation: the core confusion

The single most common mistake with geographic waste is assuming location targeting also filters the words in the query. It does not. Location targeting and exclusions reshape the audience by geography — they add or remove people based on where they are or what location they are searching about. Negative keywords act on the text of the query. When a searcher inside your target area types the name of a city you do not serve, they pass the location filter (they are in-target) but fail no keyword filter, because you never told the account that the word for that city is unwanted. The ad serves, you pay, and the term lands in your report looking like a targeting failure when it is really a keyword one.

Google's help center draws the same line between the two tools: you can exclude geographic locations from targeting to control who is eligible, which is a different operation from adding a place name as a negative keyword to control which queries trigger you. If out-of-area city names dominate your irrelevant terms, reach for the negative keyword. If the problem is people in the wrong region entirely, reach for the location exclusion. Using one where you need the other is why the leak persists — you keep adjusting targeting and the query-text problem never moves.

Why broad match and close variants make it worse

Geographic misfires scale with how loose your match types are. Exact match no longer means the literal query; it now includes close variants, plurals, function-word changes, and reordered words judged to share intent. Broad match expands much further, matching on meaning rather than words. A keyword such as [emergency plumber] can pull in a query that appends or embeds a location modifier you never targeted, because Google reads the core service intent and treats the ad as relevant even when a second modifier changes what the searcher actually wants. Add a city name into that mix and the system happily serves.

The intent-flip is the dangerous case. When someone searches "electrician jobs Boston", Google sees the service (electrician) and a location (Boston) and considers your ad a fit, even though the word "jobs" means this person will never be a customer. People naturally attach their own city to job, salary, training, and DIY queries because they want local results, so geo modifiers and intent-flipping modifiers arrive together constantly. This is the same dynamic behind running broad match without a paired negative list: the looser the matching, the more essential the negatives become, and location-name terms are one of the first patterns to slip through when match types widen.

The geographic patterns worth negating first

Start with three families of terms, drawn from your own search terms report rather than a generic list. First, out-of-area place names: the cities, states, or countries that keep appearing but that you do not serve. Second, intent-flipping geo modifiers — "jobs", "salary", "training", "course", "DIY", and "near me" when near-me falls outside your radius — because these are the words people pair with a city when they are not buying. Third, wrong-region qualifiers if you are a local business: adjacent towns just outside your service radius that a broad or close-variant match keeps dragging in.

Match type on the negative matters here. Add out-of-area place names as phrase or exact negatives so you block the city as a term without accidentally killing a legitimate query that merely mentions the area in passing — a single-word broad negative for a common place name can over-block. The intent-flippers like "jobs" are usually safe as broad or phrase negatives because they are rarely part of a buying query. Work from the report, not from imagination: pull the terms, group the geographic ones, and confirm the patterns are real before you commit them, the same way you would with any n-gram search-term analysis. Guessing at city names you think might appear wastes effort; the report tells you which ones actually cost you money.

Structuring geographic negatives across the account

Where a geographic negative lives determines how much work it saves you. Genuinely universal negatives belong on a shared or account-level list so every campaign inherits them: countries and regions you will never serve, and permanent intent-flippers like "jobs" or "salary" if you are not hiring. These are true everywhere in the account, so maintaining them in one place beats copying them into each campaign and forgetting one. This is the same reasoning behind a deliberate negative keyword list structure across account, campaign, and shared levels: universal truths go high, specifics stay low.

Campaign-specific geography must stay at the campaign level, and this is where a careless shared list does damage. If one campaign targets a city that another campaign deliberately excludes, that city name cannot go on a shared negative list — doing so would block the campaign that wants it. Scope it to the campaign that should not serve on it. The test is simple: ask whether the negative is true for every campaign in the account. If yes, lift it to a shared list; if it depends on which campaign is running, keep it local. Getting this wrong creates the mirror-image problem of the one you started with — instead of paying for irrelevant geography, you suppress relevant geography and never see the impressions you wanted.

Cross-check against your targeting settings

Before you negate a wave of place names, confirm your location targeting is set to the right option, because the two controls interact. Google's targeting has settings for whether it matches on a user's presence, their interest in a location, or both. A too-loose setting invites searchers who are merely interested in a far-off place, which then shows up as out-of-area terms. Tightening the location option can remove a chunk of the problem at the source, leaving fewer place names for your negatives to mop up. Do the targeting check first, then negate what remains — otherwise you are patching with negatives a leak that a single setting would have closed.

Then let the two controls do their separate jobs. Location targeting and exclusions handle where the searcher is; negative keywords handle the words they typed. Run both as part of a standing search hygiene audit, and treat a rising count of out-of-area terms in the report as a prompt to check both surfaces rather than to reflexively add more negatives. When the settings are right and the geographic negatives are structured properly, location-name waste stops being a recurring line item and becomes a solved problem you only revisit when the report shows a genuinely new pattern.

For the match-type mechanics behind geo-modifier misfires, see broad match without a paired negative list and negative keyword match types, plurals, and close variants. For structuring the lists themselves, see negative keyword list structure across account, campaign, and shared.