Post

Hi @johnmu.com, could I pass along some feedback to the GSC team? Screenshot of compare filter: Branded vs non-branded. There are several cases that are not mutually exclusive, which they should.

0 reposts0 likes

At the bottom of the section when you search for branded or non branded queries you will see this statement: Query classification is powered by AI and may mislabel branded and non-branded queries. Probably get tweaked quite a lot and bound to be mistakes! Interesting though.

Totally get that, but my point is about the fact that a brand term cannot be a non-brand. They should be mutually exclusive, which in most of the cases in that report, they are!

Actually that turns out to be a really good test of what Google thinks are your brand terms - as yours are being muddled perhaps you could focus on strengthening the ones appearing in unbranded that shouldn't be - more signals needed!

that is an interesting idea. I was always under the impression that the brand grouping was done at a GSC level, in a more "analytical" way without it being informed by what search systems consider to be a brand or not. imagine the analytics teams does the grouping without talking to the SEO team

That this can happen is known, and to some extent, expected... different contexts of the same "words entered" can make something branded or non-branded. Eg: [polo], [subway], [patagonia], [visa], etc. Some sites rank both for the branded & non-branded versions, so ideally we'd list them both.

That said, I don't know your particular site and the context of the words you highlighted there. If you find that the selection is totally off (there's no "list of branded queries", so the algorithm is can get things wrong sometimes), please use the feedback mechanism directly in the report. Thanks!

Thank you for your detailed response John! For clarity, I was not arguing the fact of any term being selected. Just that conceptually a brand query shouldn't not be non-brand. I have reported this very same thru the official feedback option in the tool. Hope there's a fix for it! 🤞