GOOGLE ADS
Performance Max Exclusions: Negative Keywords, Brands and URLs
Updated: 9/19/26
Why one exclusion list is not enough
Performance Max can reach users across multiple Google properties and use feed, page, audience, and conversion signals together. A single negative-keyword list cannot correct every mismatch. Advertisers often block queries when the real issue is a weak product feed, an overbroad final URL, or an unavailable offer.
Choose the control that matches the problem
| Control | Best use | Main risk |
|---|---|---|
| Negative keyword | Consistently irrelevant query meaning | Blocking valuable variants |
| Brand exclusion | Separating brand demand or excluding selected brands | Removing useful branded discovery |
| Final URL control | Keeping traffic within approved landing pages | Reducing automation’s ability to match intent |
| Listing group or feed rule | Controlling products, margins, stock, or eligibility | Hiding feed-quality issues |
Start with the business objective
Decide whether the campaign is meant to acquire new customers, defend branded demand, grow a product category, clear inventory, or maximize profit. The same query may be desirable in one campaign and harmful in another. Document the intended boundary before adding exclusions.
Use negative keywords carefully
Add negatives when the meaning is clearly incompatible with the offer, policy, geography, or economics. Review the query theme rather than reacting to a single expensive click. Exact, phrase, and broad negative behavior is not identical to positive keyword matching, so validate examples before applying a large list.
Avoid reflexive overblocking
Queries that appear informational can assist a purchase, especially for complex products. Compare conversion quality and path behavior before removing a whole research theme.
Use brand exclusions for structure
Brand exclusions can help separate branded and non-branded demand or prevent the system from serving against selected brand terms. They are useful when leadership needs clean acquisition reporting, but they do not prove incrementality. Continue comparing new-customer rate, assisted conversions, and controlled lift.
Control URLs and feeds upstream
If ads repeatedly land on weak pages, fix page feeds, Merchant Center data, final URL expansion settings, or site structure. If low-margin items dominate spend, pass better product economics or build listing groups. Query exclusions should not become a substitute for merchandising governance.
Run a monthly exclusion audit
Review every exclusion with its original reason, owner, date, and affected scope. Remove temporary blocks when promotions, inventory, geography, or strategy changes. Compare excluded themes with organic site search and CRM language to detect demand you may be suppressing.
Use an exclusion decision log
For every new exclusion, record the observed query or destination, the evidence of mismatch, the control selected, campaign scope, owner, and review date. Add a reason code such as policy, geography, low margin, unsupported product, existing customer, or irrelevant intent. This makes it possible to distinguish strategic boundaries from temporary fixes. During review, sample both blocked demand and the remaining traffic to confirm the exclusion solved the original problem without creating a new coverage gap.
Frequently asked questions
Should brand traffic be excluded from Performance Max?
Only when separate reporting, acquisition strategy, or budget governance requires it. Evaluate the full customer journey before deciding.
Can negatives fix poor product matching?
Sometimes, but feed titles, categories, landing pages, and product economics often need correction first.
How often should exclusions be reviewed?
Review high-spend campaigns monthly and after major product, site, or strategy changes.