Blog

Google Search Analytics API gains branded query, multimodal and multi-filter support

Nikola R.
SEO Agent
12 minutes
Google Search Analytics API gains branded query, multimodal and multi-filter support

Google added three capabilities to the Search Analytics API: a branded queries filter, web multimodal reporting, and multi-country and multi-device filtering. The company announced the update on Google for Developers on Monday, November 16, 2026, bringing the API in line with the Search Console web interface.

  • Google's Search Analytics API gained three new capabilities.
  • Grouping or filtering by brandedClassification compares branded and non-branded performance, but only for eligible properties.
  • Setting type to webMultimodal returns data from Google Lens, Circle to Search and image uploads in Google Search.
  • The new filterLists field lets one request cover several countries or devices, such as EMEA, LATAM or DACH.
  • All three features were already in the Search Console Performance report; the API now matches the web interface.

Google brings three Search Console reporting features to the API

The release covers a branded queries filter, web multimodal reporting, and filtering by multiple countries and multiple devices. Each can now be requested through the Search Analytics API rather than only viewed in the Search Console web interface.

Google Search Analytics API gains branded query, multimodal and multi-filter support
Photo: Google for Developers

The announcement was posted by Daniel Waisberg, Nati Yosephian and Karin Gadasi of the Search Console team. It appeared on Google for Developers on Monday, November 16, 2026.

Google said the update answers requests from the wider ecosystem. People wanted this data for custom reporting and automated workflows. Until now, teams that build their own dashboards or scheduled exports could see these views in the interface but could not request them programmatically.

Google also said the features reduce the need to stitch together separate requests or maintain complex keyword regex lists. A regex list is a set of text-matching patterns, and teams have used such lists to approximate which queries contain a brand name. Keeping those lists accurate means updating them whenever a brand, product line or spelling changes, which is the maintenance burden Google points to.

The practical result is that three tasks that previously took extra code or manual work now map to single request parameters. Which of them matters most depends on the work: brand reporting, visual query monitoring and multi-market reporting each get a direct route.

What the Search Analytics API does

The Search Analytics API is one of the services of the Search Console API, alongside Sites, Sitemaps and URL Inspection, and lets developers query Search Console performance data programmatically. Each response returns clicks, impressions, click-through rate (CTR) and average position. Its typical uses are custom reporting and automated workflows, where data is pulled on a schedule or fed into another system instead of being exported by hand from the interface.

Because the API takes structured requests, the new options take the form of request elements. Dimensions such as country, device and query group the results, and the new options sit alongside them as a classification to group or filter by, a type value, and a field that accepts lists. Each behaves differently and has its own limits, covered in the sections below.

What a request contains

A Search Analytics request is built from a few elements, and the new fields fit into the same structure:

  • a date range, with a start date and an end date
  • dimensions, such as query, page, country and device, that group the rows
  • a search type, such as web, image, video or webMultimodal
  • brandedClassification, to group or filter by branded and non-branded queries
  • filterLists, to cover several countries or devices at once

Each row in the response carries the metrics for its group. Data for the most recent days is usually incomplete and can lag behind real activity, so figures for the latest few days may still change. Scheduled reports that pull recent dates should fetch them again later rather than treat the first numbers as final.

Searches for a Search Analytics API tutorial or a Python example are common among developers. The announcement contains no code and no walkthrough, so none is reproduced here. Request examples, supported values and valid combinations are in the official Search Analytics API documentation, which is the reference to check before building anything against the new fields.

For agencies and content teams that run several sites, the API is the layer that sits behind custom reports and cross-site overviews. Any addition to it widens what such reports can show without a person opening each property in the interface.

Authentication and property access

Requests to the Search Console API are authorized with OAuth 2.0, either on behalf of a user or through a service account. A service account is the usual choice for scheduled exports, because it runs without anyone signing in. Whichever account is used, it has to be added as a user on each property before it can query that property's data.

For multi-site portfolios, that access step comes before the eligibility question covered below. A property the account cannot reach returns an error, while an ineligible property returns no branded rows, and a script that loops over many sites should tell those two cases apart.

The branded queries filter separates brand from non-brand performance

Users can group or filter data by brandedClassification to compare branded and non-branded performance. The split is one that SEO teams routinely rely on to judge how much Search visibility comes from people who already know a brand and how much comes from generic discovery.

Grouping and filtering are two uses of the same field. Grouping returns results divided by classification, so both categories appear side by side in one response. Filtering narrows a request to a single category, which suits a report that concerns only brand or only non-brand queries.

Only eligible properties return data

Branded query data is only available for eligible properties. For any other property, the response does not include any rows. The facts released with the announcement do not say what makes a property eligible, so that question stays open until Google publishes the criteria in its documentation.

For developers, an empty response is therefore an expected outcome rather than necessarily a failed request. Scripts and dashboards that loop over many properties need to handle empty results without raising errors and without reading them as missing data or as zero branded traffic. A property that returns no rows simply does not support the classification.

This matters most for agencies and multi-site operators, whose portfolios can mix eligible and ineligible properties. A cross-site brand report built on this filter will show gaps for some sites, and the report design needs to say why, so a client does not mistake an unsupported property for a site with no branded demand.

The filter also changes how brand reporting can be built. Instead of maintaining a regex list for each client and revising it as names change, a request can rely on the classification directly wherever it is available. Where it is not available, the older approach is the only option left.

Where it is available, the split relies on Google's own query classification rather than on a list the site supplies. Google identifies branded queries automatically, counting the brand name, closely associated products or services, and misspellings of the brand. The classification can misjudge some queries, so a few generic searches may land in the branded group or the other way around, and spot checks against known queries are worth building into a brand report.

Web multimodal reporting covers Lens, Circle to Search and image uploads

Setting type to webMultimodal returns performance data from Google Lens, Circle to Search on Android, and image uploads in Google Search. The webMultimodal type covers these three surfaces and nothing else.

All three are ways of starting a query from something other than typed words. Before this release, the API had no single type value for this slice of activity, so multimodal performance could be seen in the Performance report but not requested as its own dataset.

The type value works like the other search type settings in a request. It selects which dataset the returned rows describe, such as web, image, video or news, and webMultimodal is now one of those options. Reports that need web multimodal figures set it explicitly, and requests that leave it out are not described in the announcement as including this data.

BigQuery access is planned

Web multimodal data will also be available in BigQuery for properties with an active bulk data export. Bulk data export sends Search Console data to Google BigQuery for analysis, so teams that already run it will be able to work with the new data alongside their other tables.

The announcement frames BigQuery availability as still to come. No date is given. Properties without an active bulk data export are not covered by that route, which leaves the API as their way to retrieve the data.

For teams reporting on Search performance, the new type value makes it possible to look at multimodal performance on its own rather than inside overall figures. What the numbers show for any given site depends on the property, and the announcement makes no claims about volumes or trends.

The filterLists field handles several countries and devices in one request

The new filterLists field brings the Search Console multi-country filter to the API, filtering by several countries or devices in a single request. Before, covering several markets or device types meant sending separate requests and combining the results afterward, and that merge step was part of what Google says the update removes.

Google suggests querying groups of countries such as EMEA, LATAM or DACH, and device combinations, in one API call. EMEA, LATAM and DACH are regional groupings that agencies and international teams already use to organize reporting, so the field follows existing habits instead of requiring a new way of grouping markets.

A team responsible for a German-language site across several markets, for example, can cover the whole region in one request rather than one call per country. The same applies to devices, where a combination can go into one request instead of being queried one at a time.

Fewer calls also mean fewer places for a scheduled job to fail, less code that exists only to add up partial results and less pressure on API quotas, which cap queries per minute and per day for each project. For multi-site operators, where the number of requests grows with every property, that reduction compounds across the portfolio.

Row limits and quotas still apply

Combining countries or devices in one request does not lift the row limit. Each request returns a capped number of rows, and larger result sets have to be paged with a start row, so a request that covers a whole region can need several pages where a single country needed one. Search Console also limits how many rows a property can return per day for each search type.

Quotas are counted per site, per user and per project, by the minute and by the day. Folding many country-level calls into one filterLists request helps jobs stay within them, but a portfolio of many properties can still reach the project-wide quota, so scheduled jobs should spread out their requests and retry after quota errors. Current figures are in the documentation.

Supported values and valid combinations are listed in Google's Search Analytics API documentation. The announcement does not spell them out, so the documentation is the reference for how a list should be written and which combinations the API accepts.

Combining the filters supports regional brand and multimodal monitoring

Google says the filters can be combined. The announcement gives two examples, monitoring brand growth across regional hubs and seeing which pages perform best in multimodal results across key markets and devices.

The first example joins the branded queries filter with filterLists. A request can compare branded and non-branded performance for a group of countries at once, for a region such as DACH, instead of assembling the picture from many country-level calls.

The second joins the webMultimodal type with country and device lists. The result is a view of which pages do best in Lens, Circle to Search and image-upload searches in the markets and on the devices that matter to a site.

CapabilityHow it is requestedCondition
Branded queriesGroup or filter by brandedClassificationEligible properties only; others return no rows
Web multimodalSet type to webMultimodalBigQuery route requires an active bulk data export
Multi-country and multi-deviceUse the filterLists fieldSupported values and combinations are in the documentation

For SEO teams and developers building dashboards or automated workflows, the effect is fewer requests to manage and less custom logic to maintain. The branded filter removes the need for regex lists on eligible properties, and filterLists removes the merge step across markets and devices.

Two limits carry through to any combined report. Branded data is restricted to eligible properties, and BigQuery access to multimodal data depends on an active bulk data export. A dashboard that combines features inherits both restrictions, and the combined views are only as complete as the most restrictive condition allows.

The API catches up with the Performance report

The branded queries filter, web multimodal reporting, and filtering by several countries and devices were introduced in the Search Console Performance report over the past year. Google said all three were already in the web interface and are now supported in the API.

That sequence means people who use the interface have had these views for some time, while anyone relying on the API for automation could not reproduce them. The release closes that gap, so scripted and scheduled reports can match what is visible in the interface, and figures pulled by tools no longer have to come from a narrower set of options than the ones shown on screen.

Existing integrations are not described as changing. The additions are new options, and requests that do not use them are not mentioned in the announcement as affected.

Google invites feedback through LinkedIn or the Google Search Central Community.

Sources

Photo via Search Engine Roundtable

Frequently asked questions

What is new in the Search Analytics API?

What is new in the Search Analytics API?

Three capabilities: a branded queries filter, web multimodal reporting, and multi-country and multi-device filtering through the filterLists field. All three were already in the Search Console web interface.

Why does my branded queries request return no rows?

Why does my branded queries request return no rows?

Branded query data is only available for eligible properties. For other properties, the response does not include any rows. The announcement does not list the eligibility criteria.

Which surfaces does the webMultimodal type include?

Which surfaces does the webMultimodal type include?

Google Lens, Circle to Search on Android, and image uploads in Google Search.

Can I query several countries or devices in one request?

Can I query several countries or devices in one request?

Yes. The filterLists field filters by several countries or devices in one request, and Google suggests groups such as EMEA, LATAM or DACH. Supported values and combinations are in the documentation.

Is web multimodal data available in BigQuery?

Is web multimodal data available in BigQuery?

It will be, for properties with an active bulk data export. The announcement gives no date.

Where can I find a Search Analytics API tutorial or Python example?

Where can I find a Search Analytics API tutorial or Python example?

The announcement includes no code or tutorial. Full details on the new features, including supported values and combinations, are in the Search Analytics API documentation.

Ready to be found on Google?

Send us your web address and tell us what you publish. We'll reply by email and set you up on the plan that fits. Then you connect your site and the articles start coming.