Back to the homepage
Measurement

How to Use the New Search Analytics API Branded, Multimodal and Multi-Country Filters

Google brought three Search Console reporting features to its API on November 16. Here is how SaaS teams should use them.

Owen Mercer · AI Search and Analytics Writer
Start reading ↓
Desk
Measurement
Format
How-to
Reading time
7 min
Published
Nov 18, 2026

Google added three options to the Search Analytics API on November 16, 2026: a branded-queries grouping, a web multimodal search type, and a filter that accepts several countries or devices in one request. Use them to cut API calls, split brand from non-brand traffic automatically, and track visual search next to ordinary web results in your own dashboards.

This guide is for B2B SaaS marketers and analysts who pull Search Console data into Looker Studio, BigQuery or a spreadsheet. It explains what each new option does, where it helps a software company, and where it will quietly return nothing. cekpr covers measurement for software sites, and API changes like this one decide whether a report stays trustworthy.

What Changed in the Search Analytics API in November 2026?

computer, computer code, programming, links

Google brought three Search Console features to the API: branded query classification, web multimodal reporting, and multi-country and multi-device filtering. The three already existed in the Search Console interface. The announcement from the Search Console team says the change follows requests for custom reporting and automated workflows.

The practical shift is fewer moving parts. Before, a team that wanted brand and non-brand traffic maintained a list of brand keywords and a regular expression. A team with customers in several regions sent one request per country. Both setups break easily and are hard to audit.

Each option maps to a specific field. Here is what to set:

  • Branded queries: group or filter by brandedClassification.
  • Web multimodal: set the type to webMultimodal.
  • Several countries or devices: use the filterLists field.

The full list of supported values and combinations sits in the Search Analytics API reference. Read it before you write code, because field structure matters and a typo returns an error or an empty result.

How Do You Split Branded and Non-Branded Traffic With the API?

business portrait, cybersecurity, data analyst, modern office

You split branded and non-branded traffic by grouping or filtering on brandedClassification in your request. Google labels each query as branded or non-branded for you, so you no longer maintain a keyword list. The data is available only for eligible properties. For any other property, the response contains no rows.

Google describes the logic in its post on the branded queries filter. Branded queries include your brand name or closely associated products. Everything else is non-branded. Google also states that the filter is only for analysis and has no effect on ranking.

Why does this matter for a B2B SaaS company? Brand queries come from people who already know you. Non-brand queries show how well your content finds new buyers. Mixing them hides the real story. A flat total can look healthy while non-brand clicks fall.

Here is an illustrative example. A SaaS site gets 12,000 clicks a month. If 9,000 come from brand searches, only 3,000 come from discovery. A drop of 600 non-brand clicks is a 20 percent loss in discovery, but only a 5 percent dip in the total. The split makes the problem visible.

Handle empty responses carefully. An empty result for a new property is not proof that traffic is zero. It may only mean the property is not eligible. Our guide to measuring SaaS video and social content with Search Console platform properties shows another case where the property type changes what you can see.

How Do You Query Several Countries and Devices in One Request?

social media, icon, people, international

You query several countries or devices in one request by using the new filterLists field. Google gives examples such as groups like EMEA, LATAM or DACH, plus device combinations, in a single call. This replaces a loop of separate requests that you then had to add together yourself.

The saving is easy to count. Say a SaaS company wants desktop and mobile results for Germany, Austria and Switzerland. The old method needs six requests, one for each country and device pair, and then a merge step. The new field handles it in one call.

Merging separate requests can also cause errors. Averages such as position cannot be added across rows without weighting by impressions. One combined request lets Google compute the metrics for the whole group, so the result is more likely to match the Search Console interface.

The filters also work together with the other options. You can compare brand growth in a regional hub, or see which pages perform best in multimodal search across key markets and devices. At cekpr, we suggest starting with one region and checking the totals against the Search Console interface before you scale up.

What Is Web Multimodal Data, and Should a SaaS Site Track It?

camera, phone, picture, capture

Web multimodal data covers searches that start with an image, such as Google Lens, Circle to Search on Android and image uploads. Google's multimodal reporting announcement also lists the Chrome right-click "Search this image" feature. A B2B SaaS site should track it, but not expect large numbers.

Software buyers rarely photograph a product. Visual search still touches SaaS in smaller ways. A person might use Lens on a dashboard screenshot, a diagram or an integration logo. Original product images and clear diagrams are the assets most likely to appear.

The new API option sends this data to your own tools. Google says it will also appear in BigQuery for properties with an active bulk data export. If you already export to BigQuery, you can join multimodal rows with the rest of your search data.

One caution: do not design a dashboard around fields you have not seen. Pull a small sample first and check which dimensions come back for multimodal rows. Then decide which charts make sense.

A Reporting Setup for a B2B SaaS Team

A sound setup uses the new options in a clear order, starting with the one that changes decisions the most. The table lists a sensible rollout for a small marketing team with one analyst.

A Reporting Setup for a B2B SaaS Team
StepWhat to doCheck before moving on
1Add brandedClassification to your main queryRows return, and totals match the interface
2Replace per-country loops with filterListsClicks and impressions match the old sum
3Pull webMultimodal for a 28-day sampleRows exist, and dimensions are understood
4Add a monthly brand versus non-brand chartLeadership reads the split, not only the total

Keep the old queries running in parallel for one reporting cycle. If the new numbers and the old numbers disagree, you want to know why before a quarterly review does.

Pair this with AI visibility reporting. Search Console now shows AI feature data too, and our walkthrough of the generative AI performance report explains how to read it. Brand and non-brand splits also help when you test whether your SaaS brand appears in Gemini and AI Mode answers.

How Do You Turn These Fields Into Useful Alerts?

You turn the fields into alerts by comparing like periods and setting a threshold that fits your traffic size. Weekly non-brand clicks, compared with the same weeks a month earlier, work well for most SaaS sites. Flag any drop larger than 15 percent for review.

Use full weeks, not rolling days, so weekday patterns do not trigger false alarms. B2B traffic falls on weekends and around holidays. Note known events next to the chart. Google started rolling out its November 2026 core update on November 10, and an annotation like that saves guesswork later.

Alert on non-brand impressions as well as clicks. Impressions show whether Google shows you, and clicks show whether people choose you. A fall in clicks with steady impressions points to titles and snippets. A fall in both points to rankings. For multi-country sites, run the same check per region with filterLists, because one region can drop while the global total looks fine.

Where These New Filters Can Mislead You

These options can mislead you in three ways: empty rows from ineligible properties, changed definitions, and unmatched totals. Each one is easy to catch with a short check. None of them is a reason to avoid the new fields.

First, empty rows. A missing branded segment looks like zero brand traffic. Always check whether the branded filter appears in the Performance report for the same property.

Second, definitions. Google decides what counts as branded, and you cannot edit the list. If your product name is a common word, the label may not match your own view. Spot check the top 50 queries by hand.

Third, totals. A grouped request and a filtered request can return different row counts. Compare against the interface for one date range before you trust a dashboard.

Anonymized queries also remain outside any query-level report. Totals at the property level can exceed the sum of the rows you see. That limit existed before this update and still applies.

What Should You Do This Week?

Start with the branded split, because it changes how you judge content performance. Run one request with brandedClassification for the last 90 days, then chart brand and non-brand clicks side by side. That single chart answers a question most SaaS leadership teams ask every quarter.

Next, retire any regular expression brand lists that you maintain by hand. Replace country loops with filterLists. Leave multimodal for a later sprint unless your product is visual.

Verify each number against the Search Console interface first. A new API field is only useful when you can explain why its totals match what Google shows.

Do I need a new API key to use the new Search Analytics fields?
Google's announcement describes new options in the existing Search Analytics API, not a new product. Your current authorization should apply, though you should confirm in the API reference. Test a small request first, because a malformed field returns an error and an ineligible property returns zero rows.
Why does my brandedClassification request return no rows?
Branded query data is available only for eligible properties. For any other property, the response contains no rows. Check whether the branded filter appears in the Performance report for the same property. If it does not, the empty response reflects eligibility, not missing traffic.
Is web multimodal traffic worth tracking for a B2B software site?
Track it as a small experiment. Visual search through Lens or Circle to Search will likely send fewer clicks to a SaaS site than text search. Original screenshots, diagrams and logos are the assets most likely to show up. Pull a 28-day sample and decide from the real numbers.
Can filterLists replace my country-by-country reporting loop?
For most setups, yes. The field accepts several countries or devices in one request, so a DACH or EMEA group needs one call instead of many. Compare the result with your old summed totals for one date range before you retire the loop.

Written by

Owen Mercer

Owen writes about how AI answer engines pick their sources and how to measure search visibility honestly. He is skeptical of any tactic that arrives without data.

More from Owen
Up next · AI Search How to Prepare Your SaaS robots.txt for Google's Shared AI Training Opt-Out
The Thursday letter · free

join the club.

The week's best SEO and AI search posts, plus one thing to check in your own Search Console, every Thursday morning. Unsubscribe whenever.