Google has opened three Search Console reporting features to developers through the Search Analytics API. The Google Search Central Blog announced the change on November 16, 2026, in a post by Daniel Waisberg, Nati Yosephian and Karin Gadasi of the Search Console team. The API now supports branded-query classification, a web multimodal search type, and filters that match several countries or devices in a single request.
The first addition is branded-query classification. Requests can now group or filter results using a brandedClassification dimension, splitting queries into branded and non-branded traffic without a hand-built list of brand terms. Google introduced its own branded-query classification in the Search Console interface in November 2025, so the API access arrives almost a year later. Branded data is available from February 21, 2026, and only for top-level properties with enough query and impression volume.
The second addition is a seventh search type, webMultimodal. Setting the type parameter to webMultimodal returns performance data from Google Lens, Circle to Search on Android, and image uploads in Google Search. Multimodal reporting reached the Search Console interface in September 2026, and the API now exposes the same data. The third addition is a new filterLists field inside dimensionFilterGroups, which matches one dimension against several exact values at once, so a single request can cover a region such as DACH or a pair of devices.
The announcement is useful, but the limits matter as much as the features. Branded classification is restricted to eligible properties, and Google says requests for ineligible properties return no rows, so an empty result on its own does not prove a site has no branded traffic. The branded dimension also cannot be combined with a query filter in the same request, which means the two most obvious cuts of the data cannot be pulled together in one call.
The multimodal type has its own quirks. Queries are generally not available for image-led searches, because those searches rely primarily on images rather than text, so the multimodal rows will show which pages earned visibility without saying which words drove it. And the API reference places filterLists inside dimensionFilterGroups and limits it to country or device values, with a cap of 1,000 values per filter list that appears in the formal specification but not in the human-readable reference.
The multimodal addition did not arrive without a stumble. In a test on November 11, five days before the announcement, Aymar at Ayrank reported that requesting the API search type MULTIMODAL returned an HTTP 400 error, while the API reference listed Discover, Google News, News, Image, Video and Web, but not Multimodal. The Search Console interface already offered a Web: multimodal filter at that point, so the interface report could not then be reproduced through the API. The November 16 announcement, with the reference page updated the same day, closes that gap.
The episode is a reminder that the API and the interface do not always move together. Features appear in the interface first, and the API catches up later, sometimes after developers have already hit errors trying to use a value the interface implies should work. Teams that build dashboards on the API should treat a 400 on a new value as a sign the feature has not landed yet, not as a bug in their own code.
For agencies and SEO software companies, the practical gain is fewer requests and cleaner dashboards. One call can now do what used to take hand-built brand lists or a separate request per market. A branded versus non-branded split is the basic cut for judging whether a link-building campaign is growing discovery traffic or just riding brand demand, and having Google's own classification in the API makes that cut consistent across every client report.
The multimodal type matters for a different reason: it is the first API window into visual search. Lens and Circle to Search traffic is small for most sites today, but it is the traffic most likely to grow as image-led search becomes normal, and pages with strong product or visual content will want to know whether that surface is sending them anything. The data will reach BigQuery too, for properties with an active bulk data export, so the multimodal numbers can sit next to every other Search Console cut.
Watch whether Google extends the branded classification to more properties, or loosens the restriction that blocks combining it with a query filter. Both limits are the kind of thing that gets relaxed once a feature has been in the API for a while. And watch the multimodal numbers themselves: the first sites to report real Lens and Circle to Search traffic through the API will show whether visual search is a rounding error or a real channel, and which kinds of pages it favors.
Sources: Google Search Central Blog, November 16, 2026; PPC Land, November 16, 2026.
Related reading on this site: Search Console's Generative AI Report Had a Data Bug During the Core Update, November Search Console Click Spikes May Be Bots, SEJ Reports, Google Explains How to Find Search Traffic in Analytics and Server Logs, SEJ Pulse: Core Update, ChatGPT Business Hub and AI Mode's New Model, November Core Update Collides With Black Friday, and a Clean Read Will Not Come Until December, and AI Overview Citations: What 15 Studies Agree On, and Don't.
Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.
Start free trial