Google adds branded queries, multimodal search data and multi-country filters to the Search Console API
On November 16, 2026, Google brought three Performance report features into the Search Analytics API. Developers can now split branded from non-branded queries (for eligible properties), pull data from multimodal searches such as Lens and Circle to Search, and narrow one request to a group of countries or devices.
Three report features reach the API
According to a post on Google's Search Central Blog dated November 16, 2026, the Search Console team is now offering three capabilities, added to the Performance report over the past year, in the Search Analytics API as well: filtering by branded queries, reporting on web multimodal search, and filtering across multiple countries and devices.
The team says the reason is requests from the ecosystem for custom reporting and automated workflows. The idea is that site owners, businesses working across borders and makers of third-party tools can pull this data into their own systems instead of reading it off a screen.
What each field does
Branded queries. With the new brandedClassification option you can group or filter data and compare branded against non-branded performance. Google says that, as in Search Console, the data exists only for eligible properties, and other properties get a response with no rows. Search Engine Journal reports that the values are BRANDED and NON_BRANDED, that data begins on February 21, 2026, and that it works for top-level properties only. The same outlet adds that only the equals operator is accepted and that the field cannot be used in requests that carry a query filter.
Web multimodal search. Setting type to webMultimodal returns performance figures for searches made with Google Lens, with Circle to Search on Android devices, and with images uploaded to Google Search. Google writes that the same data will later show up in BigQuery for sites that have bulk data export switched on. Search Engine Journal says no date is given for that, and that as of November 16 the export table reference listed six search types with no multimodal value.
Multi-country and multi-device filters. A new filterLists field lets a single call narrow results to a set of countries or a set of devices. Google offers regional groupings such as EMEA, LATAM and DACH as examples. Search Engine Journal adds that the field covers only the country and device dimensions with exact matching, and that one dimension cannot appear in both filters and filterLists.
Google says the filters can be combined. Its examples include following brand growth across regional hubs and seeing which pages do well in multimodal search in important markets and on particular devices. For supported values and combination rules, Google points readers to the Search Analytics API documentation.
Fewer regex lists, says Google, but there are caveats
In Google's own framing, teams no longer need to stitch several requests together or keep complicated keyword lists: a group of countries can be queried in one call, and branded traffic can be segmented automatically in dashboards. Multimodal data can then sit next to other Google Search results.
Search Engine Journal raises a few cautions. The branded classification is AI-assisted, so some queries may be labeled wrongly, and the author suggests running the API split next to your existing brand regex to spot differences. As of November 16, the API reference also does not say whether web results already include webMultimodal data, so before adding the two totals you should compare against the Performance report to rule out double counting. The same article notes that Google has not said how far back webMultimodal data goes.
What it means for businesses in Türkiye
This section is our reading, not a fact from the sources. The change is an API option, not a new screen, so the main benefit goes to agencies, e-commerce teams and tool builders who feed Search Console data into dashboards or scheduled reports. Branded data also depends on the property being eligible.
A Turkish business that sells abroad could track target markets as groups such as EMEA or DACH in one query. The branded split may give teams that read ad spend and organic brand searches together a new measurement input, and a separate multimodal row is a starting point for measuring how much traffic image-based search brings to a site. That is our suggestion, and it is best started with the double-counting caution above in mind.
The UNALSOFT view
Connecting search data to automated reports narrows the gap between a site simply being live and knowing how it is found. We read this news as a reminder that measurement and reporting should be planned while a site is being built. In our web design work we treat site structure and measurement setup together. The news imposes no requirement; it widens the options for teams already using Search Console reports.
Shall we review how you measure your site's search performance?
A short conversation is enough to define your measurement and reporting setup.