Google Search Analytics API Updates: Nov 16, 2026
Google added branded query filtering, multi-country and multi-device filterLists, and webMultimodal performance reporting to the Search Analytics API on November 16, 2026.
Google added three new capabilities to the Search Analytics API on November 16, 2026: branded query filtering, web multimodal search reporting, and multi-country and multi-device filtering. These additions bring features previously requested by developers directly into custom reporting and automated workflows.1
Branded query segmentation with brandedClassification

The Search Analytics API now includes a brandedQueries option that lets developers group or filter data by brandedClassification. This allows teams to automatically segment branded from non-branded traffic directly in their dashboards.12
As in Search Console, branded query data in the API is only available for eligible properties, and the response will not include any rows for properties that are not eligible.1
Querying regions and devices with filterLists
Developers can now use the new filterLists field to filter by several countries or devices in a single API request. This consolidates request logic for regional groups such as EMEA, LATAM, or DACH, as well as device combinations, into one API call. Teams already tracking multi-select device filters in Search Console can now mirror that segmentation in automated pipelines.13
Tracking webMultimodal performance and BigQuery exports
To pull web multimodal performance data, developers must set the API type parameter to webMultimodal. This unlocks metrics from Google Lens, Circle to Search on Android, and image uploads in Google Search. Users can pipe these search metrics directly into dashboards and monitoring workflows to track multimodal performance alongside standard Google Search results.1
For broader storage, web multimodal performance data is also available in BigQuery for properties that have an active bulk data export enabled. Teams investigating November 2026 Search Console click spikes can use this pipeline to separate visual search traffic from standard web results.1