Most accounts try to keep Performance Max off their brand terms with a list of brand negative keywords, and most of those lists leak. The reason is simple: a negative keyword blocks the exact string you typed and whatever its match type covers, so every misspelling, abbreviation, sub-brand, and foreign-script rendering you did not think to add still triggers the ad. Brand exclusions are a different mechanism built to fix exactly that gap. This post is about when each one is the right tool, and why reaching for a negative list when the problem is a brand entity leaves money on the table.
The short version: brand exclusions handle brands, negative keywords handle queries. A brand exclusion is tied to Google’s registry of recognized brands and catches the variants of a brand automatically; a negative keyword blocks a literal string you maintain by hand. They overlap at the point where you are trying to stop PMax serving on a brand name, and at that point the exclusion is almost always the more complete instrument. Everywhere else — junk categories, wrong-intent modifiers, off-topic themes — negatives are still the tool.
Two mechanisms, one overlap
A brand negative keyword works the way every negative works: it blocks the term you list, on the Search and Shopping inventory of Performance Max, subject to its match type. If you add yourbrand as a phrase negative, you block queries containing that literal token and its close variants, and nothing else. That is fine for a term you can spell one way, but a brand is not one string — it is an entity with misspellings, spacing variants, abbreviations, product-line names, and, for anyone selling across markets, foreign-script versions. You cannot enumerate all of them, so a hand-built brand negative list is structurally incomplete.
A brand exclusion starts from the entity instead. Brand exclusions are lists of brands — yours or a competitor’s — that you tell Performance Max not to intercept on the search network; when you activate the exclusion for a brand, PMax stops serving text and Shopping ads for search queries associated with that brand (nine.am on PMax brand exclusions). Because Google maintains a registry of recognized brands, selecting one catches the brand name plus its known misspellings, alternate names, and product-line names without you listing them. That is the whole difference: the exclusion knows what the brand is; the negative only knows what you typed.
Why a brand negative list leaks
The leak is not a mistake in how you built the list — it is a property of literal matching. Say your brand is commonly misspelled two ways, abbreviated one way, and searched in a second script by part of your market. To cover that with negatives you would need to predict and enter every one of those forms, keep the list updated as new misspellings appear, and repeat the exercise for every product line. Miss one and PMax happily serves against it, taking credit for brand demand a cheaper branded Search campaign would have converted. This is the same branded-cannibalization leak that the Performance Max search terms report exists to expose — except here the fix is upstream of the report.
Brand exclusions are built specifically to recognize misspellings, variants, subsidiary brands, and foreign-script versions more completely than a literal negative keyword can (astraloopstudio on brand exclusions). The practical consequence: where a negative list catches the three brand spellings you remembered, the exclusion catches the entity, including the forms you never saw coming. For a brand with any spelling ambiguity or any non-Latin-script audience, that difference is the majority of the leak, not a rounding error.
Competitor brands are the same problem
The identical logic applies to competitor terms. If Performance Max is serving your Shopping ads against a competitor’s brand queries, those clicks usually convert poorly — the searcher is loyal to them, not shopping for you — and the spend is close to pure waste. Advertisers normally attack this with a competitor negative list, which leaks for the same reason a brand list does: you cannot spell every variant of a competitor’s name, and you certainly will not keep up with their new sub-brands.
Because brand exclusions work for any brand in Google’s registry, not just your own, you can exclude a competitor and inherit the same variant coverage — their misspellings, alternate spellings, and product-line names — that you get for yourself. This is the case where the exclusion mechanism most clearly beats the list: competitor names are exactly the terms you are worst at enumerating, and the registry has already done the mapping. Reserve the negative list for competitor-adjacent themes that are not registered brands, such as generic category terms or comparison modifiers.
Where negative keywords are still the right tool
Brand exclusions only help when the thing you want to block is a brand entity. The moment the waste is a category, a modifier, or an intent signal, exclusions have nothing to grab and negatives are the instrument. Free-download seekers, job hunters, DIY and wholesale researchers, and comparison-intent queries are not brands — they are query patterns, and you block them with negative keywords chosen by match type. The bulk of a healthy PMax negative list is still this kind of term, which is why exclusions supplement negatives rather than replace them.
There is also the registry boundary: if a brand is small enough that Google does not recognize it, no exclusion exists for it and you are back to a negative list for that one name. Keep both tools wired into the same structure — manage brand exclusions as an account-level shared list and your query negatives as a shared negative keyword list, so the coverage is consistent across campaigns. The account-versus-shared-versus-campaign trade-offs are the same ones covered in negative keyword list structure.
Setting them up without double-work
Brand exclusions are a native feature you set from the campaign panel in a few clicks, and you can manage them at the account level as shared lists so one definition applies everywhere (Strike Social on PMax updates). The efficient order of operations is: exclude your own brand and your main competitors from the registry first, then remove the now-redundant brand strings from your negative keyword list so you are not maintaining two overlapping controls, and finally point the negative list at the non-brand query waste it is actually good at. That keeps each mechanism doing the job it is built for.
Then verify, because a control you cannot see is a control you cannot trust. After the exclusions are live, re-read the Performance Max search terms report a couple of weeks later and check that brand and competitor queries have dropped out of the served list; if a variant still appears, it may be a brand the registry does not map, in which case add it as a negative. The general workflow for adding and maintaining PMax negatives — limits, match types, and cadence — is in Performance Max negative keywords, and it runs alongside your exclusions rather than competing with them. Exclusions stop the brand leak; negatives stop the query leak; the report confirms both.