Google Adds Branded Query, Multimodal and Multi-Country Filters to Search Analytics API
Google has added branded query, web multimodal and multi-country/multi-device filters to the Search Analytics API, bringing Search Console UI parity to automated reporting workflows.

- Google added three new options to the Search Analytics API: branded query filters, web multimodal data, and multi-country/multi-device filters.
- Setting type to webMultimodal returns performance data from Google Lens, Circle to Search on Android, and image uploads in Google Search.
- Multimodal data will also be available in BigQuery for properties with an active bulk data export.
- Branded query data via brandedClassification is only returned for eligible properties; others get no rows.
- The new filterLists field lets one request filter by several countries or devices at once.
Google has shipped three new filtering and reporting capabilities to the Search Analytics API — branded query classification, web multimodal traffic, and multi-country/multi-device filters — closing a gap that had kept these datasets out of custom reporting and automated pipelines. All three options have lived in the Search Console web interface for some time; the API is only now catching up.
The announcement came from the Search Console team itself: Daniel Waisberg, Nati Yosephian and Karin Gadasi. "Today, we're bringing all three capabilities to the Search Analytics API, following ecosystem requests to make this data available for custom reporting and automated workflows," they wrote. That's a confirmed Google statement, not tool-signal speculation — the features are live now.
What exactly landed in the API?
Google added three "new options to the Search Analytics API":
- Branded queries. Users can group or filter data by
brandedClassificationto compare branded versus non-branded performance directly in the API. There's a catch worth flagging for anyone building pipelines: as in the Search Console interface, this data is only available for eligible properties. For properties that don't qualify, the response simply won't include any rows — so an empty result set may reflect eligibility, not zero traffic. - Web multimodal. Setting
typetowebMultimodalreturns performance data from Google Lens, Circle to Search on Android, and image uploads in Google Search. Google also confirmed this data will flow into BigQuery for properties with an active bulk data export — a meaningful detail for teams that run warehouse-style analysis rather than per-request API calls. - Multi-country and multi-device filters. A new
filterListsfield lets a single request filter by several countries or several devices at once, removing the need to fire off one request per country or per device type and stitch the results together client-side.
Why does this matter for SEO teams?
The practical win is workflow automation. Until now, agencies and in-house teams who wanted branded versus non-branded splits, or Lens and Circle to Search traffic, had to pull that data manually from the Search Console UI or run repeated API calls for multi-country and multi-device views. The new fields push all of it into programmatic reporting — dashboards, scheduled jobs, BigQuery pipelines.
The multimodal addition is the strategically interesting one. Lens and Circle to Search traffic has grown with visual search habits, and until now the API gave no clean way to segment it. With webMultimodal plus bulk export to BigQuery, site owners can finally track how much of their clicks and impressions arrive through image-driven search paths rather than typed queries — relevant for e-commerce, publishing and any vertical where product or editorial imagery drives discovery.
The branded classification matters most for brand-versus-generic analysis. Teams tracking brand strength over time, or measuring how much organic traffic survives when branded demand dips, can now automate that split instead of exporting CSVs from the interface.
What should you watch next?
The immediate move for developers is straightforward: update API calls to use brandedClassification, webMultimodal and filterLists, and verify whether your property is eligible for branded data before assuming empty rows mean missing traffic. Watch for ecosystem reaction on LinkedIn and in the SEO forums, where the announcement is already being discussed, and monitor whether Google extends the same parity pattern to other UI-only Search Console features that still lack API support.
via developers.google.com (Original)
More from James Calloway
Show full bio
Market editor covering money, funding and market shifts around Search rankings and algorithm updates, generative engine optimization at SERP Journal.
231 articles