The Search Console API's Search Analytics query method supports a brandedClassification dimension and filter. The values are BRANDED and NON_BRANDED. For that filter, the reference supports only the equals operator.
It is the same classification as the branded queries filter in the Performance report. Google announced that filter on 20 November 2025. An update on the same post says it opened to all eligible sites on 11 March 2026. The field reached the API on 16 November 2026, with the other cuts covered in New Search Analytics API filters arrived in the middle of a core update.
Jan Caerels flagged the dimension on LinkedIn. Grouping by brandedClassification keeps clicks from anonymised queries. A regex query filter drops them. In his experience, some sites lose 30-80% of clicks when a query filter is applied, so the non-branded numbers get much more complete. That range is his experience, not a figure Google has published.
Advertisement
What the reference allows
The query method reference, last updated 16 November 2026, sets the bounds:
BRANDEDandNON_BRANDEDare the only values, and only theequalsoperator is supported on this filter.- Filtering or grouping by
brandedClassificationcannot be combined with aqueryfilter in the same request. - Data starts on 21 February 2026.
- It is limited to top-level properties with enough query and impression volume. The 2025 announcement excludes URL-path properties such as
https://example.com/pathand subdomain properties such asdevelopers.google.com. The 16 November API post says that for any other property, the response includes no rows. An empty response is ambiguous: the property may be ineligible, or those dates may truly have no rows.
How a query is classified
Google's 2025 post says the split is an internal, AI-assisted system. It is separate from the regular-expression include and exclude already available under "Filter by query". The system covers the brand name in all languages, typos, and queries that omit the brand name but refer to a unique product or service. Google's example of that last case is Gmail for google.com. Some queries may be misclassified. Google says the filter has no effect on how Google Search ranking works.
Where it falls short
Branded clicks for a subset of queries are out of reach in one call, because a query filter is not allowed beside brandedClassification. Year-on-year branded comparisons wait until February 2027: the series starts on 21 February 2026, so there is no branded row from the previous year until then. Classification can be wrong for brands that are common words. Google already says some queries may be misidentified, and a brand that is also an ordinary word is the set to check by hand before a dashboard treats every BRANDED row as final.
what to do
- On eligible properties, swap the brand regex in reporting and Looker Studio pipelines for
brandedClassification. - Run the old regex and the new dimension side by side once, on the same dates, and measure the click gap.
- Track non-branded clicks as the growth KPI.
- Example request body:
{"startDate":"2026-11-01","endDate":"2026-11-14","dimensions":["brandedClassification"]}.
refs
- [1] Search Analytics: query (Search Console API reference)https://developers.google.com/webmaster-tools/v1/searchanalytics/query
- [2] New filtering and reporting capabilities in the Search Analytics APIhttps://developers.google.com/search/blog/2026/11/search-analytics-api-update
- [3] Introducing the branded queries filter in Search Consolehttps://developers.google.com/search/blog/2025/11/search-console-branded-filter
- [4] Jan Caerels on LinkedIn: brandedClassification and anonymised clickshttps://lnkd.in/p/ew4mhX-E
Advertisement