On 16 November 2026, Google added branded query classification, web multimodal reporting and multi-country or multi-device filtering to the Search Analytics API. These options were already available in the Search Console interface; the change brings them to programmatic reporting. It does not alter how Google crawls, indexes or ranks pages. The Search Console team announced the API expansion for site owners and developers building custom reports.
The practical question is not whether every site needs a new dashboard. It is whether the new fields answer a reporting question that an existing export could not handle efficiently, and whether the property is eligible to return the requested data.
What changed in the Search Analytics API
Branded queries: a classification with eligibility limits
Reports can now group or filter by brandedClassification, using BRANDED and NON_BRANDED. Google limits this data to eligible top-level properties with sufficient query and impression volume. The API reference says the classification data starts on 21 February 2026. A request using this classification returns no rows for an ineligible property, even if its ordinary Search performance report has data.
There are two implementation restrictions worth checking: the classification filter supports the equals operator, and filtering or grouping by brandedClassification cannot be combined with a query filter in the same request. The distinction between brand demand and non-brand discovery is covered separately in MOCOBIN’s branded versus non-branded keywords guide. The API change automates one way of measuring that distinction; it does not redefine search intent.
Web multimodal: access through a separate search type
Setting type to webMultimodal retrieves performance data for searches involving Google Lens, Circle to Search on Android and images uploaded to Google Search. Google introduced multimodal reporting in the Search Console interface in September 2026, so this is new API access rather than a newly launched search feature.
Google says multimodal data will also be available in BigQuery for properties with an active bulk data export. This is a Search performance breakdown, not an automatic measure of sessions, conversions or AI-generated answer citations. Compare it with the relevant report before adding figures together.
Several countries or devices in one request
The new filterLists field, within the API’s dimension filter groups, lets a request match several countries or device types. That is useful for a regional report covering more than one market or comparing mobile and desktop performance without assembling a separate request for each selection. Country filters use three-letter ISO 3166-1 codes; the documented device values are DESKTOP, MOBILE and TABLET.
Fewer separate requests can simplify a reporting workflow, but Google has not promised that every implementation will consume less API quota. Check supported combinations and request limits in the Search Analytics query reference before changing production code.
Google Search Analytics API Adds Three Reporting Features
- Confirm the property and time period. Test a basic performance request first, then test branded classification on the same property and a supported date range. An empty response can reflect eligibility, a restrictive filter or simply no matching data. It is not evidence of an indexing penalty.
- Keep search types separate. Request
webMultimodalexplicitly and compare equivalent dates and dimensions. Do not assume it represents additional visits that can be added to ordinary Web totals or to generative AI impressions. - Validate country and device values. Use the exact codes and combinations supported by the API. If you change filters between periods, the resulting trend may no longer be comparable.
- Check completeness before drawing conclusions. The Search Analytics API returns grouped rows subject to Search Console’s data limits, rather than guaranteeing every individual query row. Treat small or missing segments as an investigation prompt, not a ranking diagnosis.
What the release changes for SEO reporting
For a multi-market site, the strongest use case is a more repeatable reporting process: compare eligible branded and non-branded performance, inspect pages receiving multimodal search exposure, and view the relevant countries or devices without stitching together as many requests. MOCOBIN’s Google Search Console guide explains the underlying reports and how to interpret indexing and performance data.
This API update should not be confused with Google’s separate generative AI performance reports. The two reporting developments answer different questions. Neither explains why Google selected a page or proves that an SEO edit caused a traffic change. The useful next step is to test whether the requested segment exists for your property, record the query settings, and compare like-for-like data before making a decision.









