Branded vs non-branded search share
Branded vs non-branded search share is the proportion of search clicks or impressions from queries that contain your brand name versus those that do not. It separates demand you already earned (people searching your name) from discovery (people finding you for a topic). The split is usually built by filtering Search Console queries, and it is limited by query redaction and by the fuzzy boundary of what counts as 'branded'.
What this means
A branded query contains your brand or product name; a non-branded (or generic) query does not. The share is the proportion of search clicks or impressions in each bucket, typically produced by applying a brand-term filter to Google Search Console's query data. It distinguishes captured demand (someone already looking for you) from discovery demand (someone looking for a topic you happen to serve).
Why the split is imperfect
Two limits matter. First, classification is fuzzy: brand misspellings, brand-plus-topic queries, and ambiguous names make the branded/non-branded boundary a judgment call, so two analysts can split the same data differently. Second, Search Console withholds (anonymizes) queries that are too rare to show without risking user privacy, so a portion of clicks and impressions has no query attached and cannot be classified at all. The share is therefore an estimate over the queries you can see, not a complete census of search demand.
- Built by filtering Search Console queries for brand terms
- Brand-plus-topic and misspellings blur the boundary
- Redacted (anonymized) queries are missing from the split
How it appears in analytics and logs
The split shows how much search interest comes from your name versus generic topics. A rising non-branded share suggests growing discovery; but redacted queries mean the totals are incomplete, so read it as directional.
Diagnostic use case
Use the branded vs non-branded split to separate existing brand demand from topical discovery, while accounting for redacted queries that are missing from the data.
What WebmasterID can help detect
WebmasterID complements search-query analysis with first-party on-site behavior, so you can see what branded and non-branded arrivals do after they land without third-party cookies.
Common mistakes
- Treating the brand filter as unambiguous.
- Ignoring redacted queries when totalling the split.
- Comparing branded shares built with different brand-term lists.
Privacy and accuracy notes
The split is built from aggregated, anonymized search-query data; individual queries that are too rare are withheld by the search engine to protect users. No personal identifiers are involved.
Related pages
- Organic vs paid traffic share
Organic vs paid traffic share is the proportion of sessions classified into organic channels (unpaid search, referral, social) versus paid channels (search/display/social ads). It comes from channel-grouping rules that read the referrer and campaign parameters. The split is only as accurate as that classification: untagged paid links can land in organic, and stripped referrers fall into direct, so the share reflects tagging as much as reality.
- Click-through rate (CTR)
Click-through rate is clicks divided by impressions, expressed as a percentage. The catch is what counts as an impression: Google Search Console counts a result appearing in search, while ad platforms count an ad being served or viewed. Because the denominator differs by platform, CTR figures are only comparable within the same system — and a low CTR can mean wrong audience or simply low intent.
- Impressions and the viewability problem
An impression counts a piece of content being shown — a search result, an ad, a social post. The trap is that 'shown' has no single definition: Search Console counts a listing appearing in results, ad servers count an ad being delivered, and the IAB/MRC viewable-impression standard requires a portion of pixels visible for a minimum time before it counts. Impressions are only comparable within one definition.
- Web analytics
Pair search-query splits with first-party behavior.
Sources and verification notes
- Google — Search Console: Performance report and query data
- Google — Why some Search Console data is anonymizedExplains query redaction for rare/anonymized queries.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.