Almost every affiliate agreement I've read already bans brand bidding. I still think the clause does almost no work in practice, and I say that as someone who has drafted versions of it myself.
By BrandPatrol · 18 September 2026 · 8 min read
A clause only works if it can sort one ad from the next. Drag the scene or pick a step to see which terms let a bid through, which turn it into a case, and what happens next. The evidence behind each case is described on the features page.
The question starts with what actually rendered on your results page, not with what the advertiser says they meant to target. A case file records the former.
A clause that holds up lists the literal brand string, common misspellings and named near-phonetic variants, rather than a vague reference to the brand's trademarks.
Geography, device and placement are stated plainly, including broad-match and dynamic-search-ads, because that is exactly where an "I didn't bid on it, Google matched it" dispute ends up.
An approved partner doing only what the agreement permits passes straight through. Nothing to enforce, and no case for your team to dismiss.
If the prohibition covers any ad shown against a branded query, however it was matched, the broad-match defense is over in one sentence. The breach is defined by its effect, not the affiliate's stated intent.
First offense, a written warning. A confirmed repeat, commission clawed back on the flagged conversions. Continued behavior, probation with monitoring. Termination sits at the end of the ladder.
Go pull your own affiliate terms right now. There's a good chance a version of this sentence is already in there: affiliates may not bid on the brand's trademarked terms, or close variants, in paid search. It's practically boilerplate at this point, which is exactly the problem. Boilerplate gets written once, gets copied forward into every renewal, and gets checked by nobody.
The clause doesn't fail at the moment it's signed. It fails quietly, every day after, because failing requires someone to actually look at search results and notice a breach, and that's not usually anyone's job description. It's adjacent to several people's jobs (the affiliate manager, whoever owns paid search, sometimes legal) and squarely inside none of them.
And when enforcement does happen, in my experience it's usually luck rather than process: someone's own affiliate manager happened to search the brand name for an unrelated reason, on their own laptop, and noticed something odd. That's not a system. That's a coincidence with a paper trail attached to it after the fact, and building a compliance program around the hope that someone gets lucky periodically is not really a compliance program at all.
Ask yourself what "bidding on our brand term" actually means in your own contract, precisely enough to win an argument about it. Exact match on the literal brand string? A phrase that contains your brand name alongside other words? An obvious misspelling? What about broad match, where the affiliate targeted a generic term and Google's own matching decided, on its own, to show the ad on a branded query the affiliate never explicitly chose? That last one happens more than people expect, and a competent affiliate will absolutely use it as a defense: I didn't bid on your brand name, Google matched it.
I think the honest answer is that the clause should specify all of this up front, in writing, before there's ever a dispute to have. Almost none of the agreements I've seen actually do. So instead, every case becomes its own small negotiation: is one screenshot enough, or do you need a pattern across several days? Does a broad-match impression count the same as an exact-match keyword the affiliate typed in on purpose? I've watched a program spend more energy arguing about what counts as proof than the underlying violation ever cost them.
It plays out roughly like this, in my experience, once you actually flag someone. You say: you were bidding on our brand name, here's the ad, here's the redirect chain, here's the timestamp. They say: we bid on "running shoes near me," not your brand name specifically, broad match decided to show it on that query, and broad match is Google's behavior, not ours.
If your contract just says "affiliates may not bid on our trademarked terms," that argument has real force, and you're now debating intent and platform mechanics instead of the thing you actually care about, which is that your branded search results had an unauthorized ad sitting on them regardless of which keyword nominally triggered it. If your contract instead says the prohibition covers any ad shown against a branded query, however it was matched, the conversation is over in one sentence, because you defined the thing you were trying to prevent by its effect, not by the affiliate's stated intent.
That difference, effect versus intent, is worth the extra paragraph in your contract template. It's also, not coincidentally, exactly the distinction a well-built case file is designed to sidestep: it records what actually rendered on the results page, not what the advertiser claims they meant to target.
It's tempting to blame this entirely on nobody monitoring, and monitoring is genuinely most of it. But even a program that catches a clear violation red-handed often still doesn't act, and the reason isn't technical.
The partner you need to enforce against is frequently your best-performing partner. They're generating real volume through channels that have nothing to do with brand bidding: a comparison page, a loyalty app, an email list that's earned its place. Nobody wants to be the account manager who blew up a relationship worth a meaningful share of the channel's number over one clause, especially when the person who'd have to explain the resulting revenue dip to their own boss is the same person deciding whether to enforce.
I've sat on both sides of that particular conversation, running a program on one side of my career and building the tooling to catch this on the other, and I understand the reluctance even where I don't agree with where it usually ends up. Knowing a violation is happening and choosing not to act on it, at least for a while, is a completely different failure than not knowing. It's just a less comfortable one to admit to.
If I were rewriting one of these from scratch, here's what I'd want it to nail down, in the contract itself, not improvised after the fact:
That fifth point deserves an extra sentence: a program that already produces evidence-grade case files as part of normal detection work has effectively already solved the definition problem, whether it meant to or not. The fields that make a case usable, the affiliate ID, the network, the chain, the timestamp, are a perfectly good answer to "what counts as proof," and you don't need a lawyer to invent a new one when a workable one already exists.
Here's the part I think gets skipped in most conversations about enforcement: removing a big partner has a real cost, and it's larger than the commission you'll save. If they're a genuine top performer, they're probably driving volume through legitimate channels alongside the brand-bidding you caught them on, and losing all of it at once, not just the part you were trying to stop, is the actual tradeoff on the table.
Replacing that volume takes months. The replacement partner might not perform as well; new partners rarely do at first, and some never catch up. So when I say "warn, then withhold commission on the specific conversions you flagged" is usually the more realistic move, I mean it as a genuinely proportionate response, not a soft one: it removes exactly the ill-gotten margin, on exactly the transactions where you can prove it, without torching a relationship over the first pattern you happened to catch.
Termination is still the right tool. It's just the tool for a partner who ignores the warning, not the one you reach for on the first offense. I'll admit reasonable people disagree with me here, and I've come around to this position partly by watching programs handle it the harder way and regret the relationship they burned when a clawback and a direct conversation would have fixed the actual problem just as well.
None of this works, though, without the monitoring underneath it. A remedy ladder with perfectly specified terms is still worthless if nobody's watching for the breach it's supposed to apply to. The clause was never really the weak link. Looking is.
Short answers from the article. For what a violation costs you, see what brand bidding actually costs; to get the evidence side covered, see how monitoring works.
That depends on your affiliate terms. Almost every agreement already bans affiliates from bidding on the brand's trademarked terms, but the clause only works if it defines exactly what is covered. Without that, every flagged ad turns into a negotiation about intent and platform mechanics instead of the breach itself.
It should name the exact terms and variants covered, state geographic, device and placement scope, and address broad match. It should also separate direct linking from brand bidding, define the evidence accepted as proof, and set a remedy ladder rather than a single on-off switch.
Because enforcing it needs someone to look at search results and notice a breach, and that is rarely anyone's job. It also gets awkward when the offender is your best-performing partner. Enforcement then depends on luck rather than process, and the clause quietly does almost no work.
It is a common defense: the affiliate says they bid on a generic term and Google's matching showed the ad on your brand. If your contract prohibits any ad shown against a branded query, however it was matched, that defense disappears, because the breach is defined by effect rather than intent.
Define it in the contract as a standard: a timestamp, the full redirect chain, and a screenshot of both the ad and the landing page. That is roughly the bar a well-built case file already meets, so using that format as your definition of proof saves you inventing one.
Climb a remedy ladder: a written warning first, then commission clawed back on the specific flagged conversions, then probation with active monitoring, and termination last. It removes the margin you can prove was taken without burning a relationship over the first pattern you caught.
Tell us your domain and the keywords that matter. We'll scope the monitoring and quote based on your program size.
Get a quote