The brand cannibalization check most accounts skip

A client asks why brand spend keeps climbing when the brand name is not exactly new anymore. The honest answer, more often than specialists want to admit, is that nobody has checked whether the organic listing for that same query already wins the click -- because the two data sources that would settle it live in different products, Google Ads and Search Console, and neither pulls the other in by default.

Why a campaign name is not proof

Most accounts settle this with a naming convention: a campaign called "Brand" is treated as brand traffic, and a campaign called anything else is treated as non-brand. That convention is a guess dressed up as a category. Campaigns get renamed, cloned, and repurposed over the life of an account, and a name chosen eighteen months ago by someone who has since left the agency is not evidence of what a campaign actually targets today.

The two-signal check

The check that actually settles it uses two independent sources instead of one label. Search Console shows, per query, where the organic listing ranks and what click-through rate it earns at that position. Google Ads shows, per campaign, what is actually being targeted and bid on. When both agree that a query is brand-dominated -- organic already winning the click at a strong rate, and the campaign's own targeting confirming it is a brand play -- that agreement is the real evidence, not the campaign's name.

A worked example

Take an illustrative case: a campaign named "Brand -- NL" spends steadily every month. Search Console shows the account's own company name ranking position 1, with a click-through rate clearly above what that position normally earns -- organic is winning the click on its own. The campaign's targeting independently confirms it is bidding almost exclusively on brand and near-brand terms. Both signals point the same way, and that alignment is what turns "this looks like brand spend" into "this is confirmed brand spend competing with an organic listing that does not need the help."

Now the more interesting, equally illustrative case: same strong organic position, but the spend sits in a broader, non-brand campaign that happens to be picking up that query through close variant matching. The two signals disagree. That disagreement is not noise to average away -- it is the actual finding, and it points at a targeting or exclusion-list question, not a budget decision to make on the spot.

When the two signals disagree

A disagreement between what Search Console shows and what the campaign's own targeting says is not a tie-breaker situation. It means the campaign structure and the organic reality have drifted apart, and the next step is to look at match types, negative keyword lists, and campaign scope -- not to shift budget based on a hunch about which signal to trust more.

Why the check needs a volume floor

A single click can swing a click-through rate from unremarkable to spectacular and back within a week, which is exactly why this check needs a minimum amount of Search Console traffic on the query before it means anything. Below that floor, the honest answer is that there is not enough data yet -- not a confident-sounding conclusion built on three clicks that happened to land well.

The payoff for doing this properly is not a one-time cleanup. Brand campaigns drift over time as an account grows, gets renamed, or gets handed to a new specialist -- which makes this a check worth repeating on a cadence, not a box to tick once and forget.