Skip to main content
SEO

Search Console API adds branded query and multimodal filters

Google has added branded query classification, multimodal search data and multi-country and multi-device filters to the Search Console Search Analytics API, so the splits that Google added to the Performance report over the past year can now be pulled into automated reports.

The Search Console team announced the change on Monday 16 November 2026. The post, from Daniel Waisberg, Nati Yosephian and Karin Gadasi, says the three options arrive "following ecosystem requests to make this data available for custom reporting and automated workflows".

For an Australian business that reads Search Console through a dashboard instead of the web interface, the practical change is that brand versus non-brand traffic no longer has to be rebuilt from a regex list of brand spellings, and a group of markets can be filtered in one request.

Performance report filters are now available through the API

Google says it introduced the branded queries filter, web multimodal search reporting and multi-country and multi-device filtering to the Search Console Performance report over the past year. Until now each of them lived in the web interface only. Anyone pulling data through the API had to work around them.

The API now has three new options:

  • A brandedClassification dimension, which groups or filters rows as BRANDED or NON_BRANDED.
  • A new type value, webMultimodal, which covers visual searches: Google Lens, Android's Circle to Search and images uploaded to Google Search.
  • A filterLists field, which filters by several countries or several device types in a single request.

Google's own examples of what the combination allows are monitoring brand growth across regional hubs and seeing which pages perform best in multimodal search across chosen markets and devices. The filters work together, so a single call can ask for non-branded, mobile-only traffic from a list of countries, or multimodal traffic for chosen markets and devices.

Small properties get no brandedClassification rows

The caveat Google puts on the branded split is the same one that applies in the Search Console interface: the data is only available for eligible properties. For any other property, the API response contains no rows at all.

The API reference spells out the eligibility. Branded classification data starts on 21 February 2026 and is only available for top-level properties with sufficient query and impression volume. The reference does not give a number.

Two other limits matter for anyone building a report. The brandedClassification filter supports only the equals operator, and it cannot be combined with a query filter in the same request. So a report that wants non-branded queries containing a particular product term has to be built as two calls, or by grouping the non-branded set by query and filtering afterwards.

For a small site with low impression volume, an empty response is a likely result. That is worth knowing before a dashboard goes blank and someone assumes the integration broke. A script should treat an empty branded response as "property not eligible" and fall back to the old regex method.

Where the property is eligible, the split answers a question most owners ask their agency every month: how much of the organic traffic came from people who already knew the name, and how much came from ranking for the things they sell. The same split is becoming a live issue on the paid side, where Google's Performance Max help page now says the campaign may filter out brand searches so a dedicated brand Search campaign serves them.

Google Lens traffic needs its own API request

Setting type to webMultimodal returns the performance data for visual searches: someone pointing Google Lens at a product, circling something on an Android screen, or uploading an image into Google Search. Google adds that this data will also appear in BigQuery for properties with an active bulk data export.

The type field defaults to web, which is the combined "All" tab in Google Search and excludes Discover and Google News. The other values in the reference are discover, googleNews, news, image and video. webMultimodal sits alongside them as its own result type, so a dashboard that reports organic search from the default web type is unlikely to be counting it unless someone adds a second request.

Google has not said how large multimodal traffic is for a typical site. For a retailer, a tradie with photographed jobs on the site, or anyone whose pages carry product images, it is the kind of segment worth plotting for a few months before deciding whether it needs attention.

One request covers Australia and New Zealand

The existing filters array in the API matches a single value per entry. The new filterLists array accepts a list of exact-match values for one dimension, and a row matches if its value equals any of them. Google's post gives EMEA, LATAM and DACH as the kind of groupings it had in mind.

Two dimensions are supported in filterLists: country, using three-letter ISO 3166-1 alpha-3 codes (AUS for Australia, NZL for New Zealand), and device, using DESKTOP, MOBILE and TABLET. Each dimension can only be filtered one way per request, so country cannot appear in filters and filterLists together.

For an exporter, or a business serving Australia and New Zealand, that turns a trans-Tasman view into one call. The same applies to a mobile plus tablet slice, which previously meant two requests or pulling everything and filtering locally.

Elsewhere in the API reference, date ranges are still expressed in Pacific time, so an Australian day does not line up with an API day. Rows are sorted by clicks descending, rowLimit runs from 1 to 25,000 with a default of 1,000, and Google still says the API is bounded by Search Console's internal limits and returns the top rows without guaranteeing every row. Anyone comparing API totals with the interface, or with analytics, should expect small gaps, a theme that also runs through Google's recent guide to finding Search traffic in analytics.

Search Console connectors need the new fields

Most businesses do not call the API directly. They use a connector inside a dashboard tool, a rank-tracking platform or an agency's reporting stack, and each of those has to add the new fields before a report can use them. The first job is to find out whether yours has.

  • Ask your agency or tool vendor whether their Search Console integration supports brandedClassification, the webMultimodal type and filterLists, and when it will.
  • Run one test request grouped by brandedClassification for the last 28 days. If rows come back, the property is eligible and a brand versus non-brand chart can go into the monthly report. If nothing comes back, keep the regex-based brand filter and note that the property is either below Google's volume threshold or not a top-level property.
  • Add a second request with type set to webMultimodal and plot it on its own line. The API lists webMultimodal as a separate type from the default web type, and the Search Console interface shows it as its own search type, so a dashboard that only pulls the default web type is unlikely to include it. Keep it on its own line rather than adding it to the main organic figure.
  • If you report on more than one country, replace any stitched country requests with a single filterLists call and confirm the totals match the old method.
  • If you use the BigQuery bulk export, check whether webMultimodal rows have appeared in the export tables.

Google started the November 2026 core update rollout on 10 November, and the useful before-and-after comparison comes once it finishes. Having the brand split in place by then means a ranking change can be read on the non-brand line, where brand searches do not mask it.

If you run your own reporting, the full list of supported values and combinations is in Google's Search Analytics API reference, and a single test request against your property will tell you within a minute whether the branded data exists for you yet.

Filed under
search analytics apisearch console api branded queriessearch console branded filterwebMultimodal search consolesearch console api filterListssearch console reporting automation