The negative-keyword match-type mistake that silently blocks profitable traffic

A negative keyword is a word or phrase you tell Google Ads (or another ad platform) not to show your ad for, even if the search would otherwise match your regular keywords. You add negatives to stop your budget from going toward searches that will never convert, like someone searching for a free version of a product you sell, or a job title that happens to share a word with your product name.

What a lot of advertisers don't realize is that negative keywords carry the same three match types as regular keywords: broad, phrase, and exact. Broad match is the loosest (matches the most searches), phrase match is more contained, and exact match is the tightest. In most account setups, typing a negative keyword into the standard add-negative box and hitting save applies broad match by default, because it's the fastest thing to type and requires no extra syntax. That default is exactly the problem.

A broad match negative keyword blocks any search that contains all the words in that negative, in any order, mixed in with other words. This is documented, standard platform behavior, not a bug. So if you add "running shoes" as a broad negative, you block any search containing both "running" and "shoes" somewhere in it: "best shoes for running," "running shoes size 10," "waterproof running shoes reviews." All of it gets excluded, not just the literal phrase.

That breadth is fine when every plausible combination of those words really is something you want to exclude. It becomes a liability the moment a search containing all those words is actually a real, convertible query you wanted to catch. And because a broad negative doesn't require the words to sit next to each other, or even to appear in the order you typed them, it can suppress searches that look nothing like the phrase you originally had in mind.

Picture a hypothetical business selling a premium, higher-priced product, say, a $400 espresso machine. To keep the ad budget away from obvious bargain-hunters, someone adds "cheap" as a broad match negative keyword. On the surface this looks like smart budget discipline: stop paying for clicks from people who were never going to buy a $400 machine anyway.

But a broad negative for the single word "cheap" blocks every search containing that word, not just searches for cheap alternatives. A search like "cheap ways to descale an espresso machine" contains the word "cheap", so it gets excluded, even though someone searching that could easily already own a premium machine and be a strong candidate for accessories, maintenance products, or a service plan. The negative doesn't know the difference between "cheap alternative to [this product]" and "cheap way to maintain [this exact product]"; it just sees the word and blocks the search. The same risk exists for any single common word used as a broad negative: it doesn't just filter out the scenario you had in mind, it filters out every scenario where that word shows up alongside other words, including ones that are relevant, high-intent, and unrelated to the low-intent behavior you were actually trying to exclude.

Wasted ad spend is visible. If a keyword is getting clicks but no conversions, that shows up as a line item: spend without return, sitting right there in the report waiting to be noticed and fixed.

An over-broad negative keyword does the opposite. It prevents your ad from being shown in the first place, which means the search never becomes a click, an impression you can query, or any kind of measurable event tied to your account. There's no report for "searches you were eligible to win but never got the chance to see," because the platform has no reason to log a search it decided not to show you against. The absence is structural, not a reporting gap you can turn on. That's exactly why an overly broad negative can sit in an account for months or years, quietly suppressing legitimate demand, without a single dashboard metric ever flagging it as a problem.

Default to the most specific negative match type that actually solves the problem you're trying to solve. If you only want to exclude the literal phrase "free version," an exact match negative for that phrase blocks just that search, not every search containing the words "free" and "version" in any order. Phrase match negatives sit in between: they block searches containing that exact sequence of words, with other words potentially before or after, but don't scatter-match on individual words the way broad does. Reach for broad match negatives only when you deliberately want that wide a net, and treat single common words as broad negatives with particular caution, since a single word is the case most likely to collide with searches you didn't intend to block.

The second half of the fix is a habit, not a one-time setting change: periodically audit your existing negative keyword list, not just add new negatives to it. Most accounts treat negatives as something you only add to, never review. Instead, pull the platform's search terms report (the log of the actual queries that triggered, or in some cases were blocked from triggering, your ads) and cross-check it against your negative list. Look specifically for cases where a broad negative might be suppressing a search pattern that, on reflection, looks like it would have converted. This is slower than just adding negatives reactively, but it's the only way to catch a mistake that, by design, never shows up in your normal performance metrics.