Google extended its Search Analytics API on Monday, November 16, with three features borrowed from the Search Console Performance report: branded query classification, web multimodal reporting, and country and device filters that accept lists. The Search Console team announced the change on the Google Search Central Blog, citing ecosystem requests for the data in custom reports and automated workflows.

All three features already existed in the Search Console interface. What changes is access. Anyone who built dashboards on the API had to settle for the narrower dataset or export numbers by hand from the web UI.

The branded query option works through a field called brandedClassification. Developers can group or filter on it to set branded traffic against everything else. Google states the data is limited to eligible properties, the same restriction that applies in Search Console. For any other property, the response returns no rows, so an empty result is not a bug in your query.

Web multimodal is exposed by setting the type parameter to webMultimodal. It returns performance data covering Google Lens, the Android feature Circle to Search, and image uploads made in Google Search. Sites that already run a bulk export to BigQuery will find the same data there. Google’s post does not say how much traffic these surfaces send, so the reporting gives teams a way to measure it rather than a number to rely on.

The third addition is a filterLists field, which lets one request filter by several countries or several devices at once. Google’s examples are regional country groups: EMEA, LATAM, and DACH. Before this, covering a region meant sending separate requests per country and stitching the results together, or maintaining long keyword patterns to approximate a brand segment.

Because the filters combine, a team can ask narrower questions in one call. Google gives two examples: tracking brand growth across particular regional hubs, and identifying the pages that lead in multimodal results for important markets and devices. Search Engine Roundtable, which covered the announcement, noted the features have been available in the web interface for some time.

For practitioners, the practical gain is cleaner automation. A branded versus non-branded split is one of the first cuts used to judge whether a traffic change reflects demand for the company or real ranking movement. Automating it removes a manual step from weekly reporting and a source of inconsistency between analysts who each define “branded” differently. The classification here is Google’s, so teams should compare it with any internal keyword lists before swapping one for the other.

The announcement carries limits worth noting. Google did not publish eligibility criteria in the post itself beyond linking to its documentation, and it gave no usage figures for multimodal queries. Teams should read the Search Analytics API documentation for the supported values and combinations before changing production pipelines.

Agencies and in-house teams that maintain regional dashboards should schedule a test pull of the new fields this week. Confirm which of your properties are eligible for branded data, and start logging multimodal clicks now so you have a baseline when the volume question comes up.

Google Search Central Blog, Search Console team, November 16, 2026, with additional reporting from Search Engine Roundtable.