Skip to content
🌍Global

Choose your region

🌍 Global / International

Search Analytics API adds brand + multimodal filters (Nov 16): act now

Google Updates 17 November 2026 Gaurav Rajani Google Search Central Blog
Search Analytics API adds brand + multimodal filters (Nov 16): act now

Changed on Nov 16, 2026: Google’s Search Analytics API can now apply the same cuts many teams already use in the Search Console Performance UI: branded query filtering, web multimodal reporting, and multi-country + multi-device filtering.

This matters because it ends a stupid reporting gap. Until now, lots of teams were stuck doing “proper” SEO analysis in the UI, then exporting messy spreadsheets (or building fragile workarounds) to automate dashboards. Now you can automate those same views—cleanly—through the Search Analytics API.

What happened (and what’s actually new)

Google says the last year of Search Console Performance improvements is now landing in the API. The headline additions are:

  • Branded queries filter so you can split brand vs non-brand without hand-maintained regex lists.
  • Web multimodal search reporting so you can isolate performance from queries where Search blends modalities (for example, text results with heavier visual intent signals).
  • Multi-country and multi-device filtering so you can slice performance in combinations that better match how you plan budgets and launches.

Primary source: Google’s announcement on new Search Analytics API filtering and reporting.

Why business owners should care (not just SEO nerds)

Most leadership teams don’t fund “SEO.” They fund growth, pipeline, and risk reduction. The old reporting reality made it too easy to accidentally overstate SEO gains because brand demand rose (PR, offline, partnerships, even a competitor going viral) and the SEO dashboard quietly counted it as “organic growth.”

Branded query filtering in the Search Analytics API is the fix. It lets you tell a cleaner story: what’s happening to discovery (non-brand) versus what’s happening to demand capture (brand). That’s the difference between “SEO is working” and “people already looking for us are still finding us.”

Web multimodal is the sleeper change. Everyone’s talking about AI search, but multimodal reporting is where measurement goes to die: new SERP experiences show up, traffic shifts, and teams only notice months later when revenue is down and the post-mortem is mostly guesswork.

Our take: who wins, who loses

Winners: teams with an analytics pipeline (Looker Studio, BigQuery, Power BI, dbt) and anyone running multi-market sites. This update means your automated SEO reporting can finally match what a human sees in Search Console—without screenshotting graphs like it’s 2014.

Losers: teams that rely on “overall clicks up” as the KPI. Once you split brand vs non-brand, some feel-good dashboards will deflate. That’s not bad news; it’s clarity.

Overhyped angle to ignore: “This will instantly improve rankings.” It won’t. This is measurement infrastructure. But measurement is what stops you funding the wrong work for the next quarter.

Everyone will miss this: dashboards will change behaviour

When brand and non-brand are mixed, content teams tend to chase brand-heavy pages because the numbers look safe. Once you can push a weekly non-brand view to stakeholders automatically, the incentive flips: teams start prioritising discovery content, technical fixes, and intent matching because that’s what’s visible.

That behavioural change is the real ROI of this update.

What this means for your site (actions for this month)

  • Rebuild your SEO reporting to separate brand vs non-brand and make non-brand the default exec view. Keep brand visible, but stop letting it mask discovery losses.
  • Create a “web multimodal” watch panel (weekly) for your top 20 landing pages and top 50 queries. If multimodal clicks drop while classic web holds, that’s a content-format and SERP-feature problem—not “SEO broadly.”
  • For multi-country sites, stop averaging performance. Use multi-country filters to spot where you’re slipping (often one market has indexing/template issues while others look fine).
  • For multi-device, check mobile-only declines before you blame algorithms. Mobile can be a UX/CLS/templating regression; desktop can hide it.

How we’re changing client work this week (effort vs impact)

We’re treating this like an analytics refactor sprint, not a “nice to have.” For most teams, this is 1–2 weeks of work depending on how tangled the current reporting is and whether there’s already a data warehouse.

What we’re doing first:

1) Update the Search Analytics API extraction so the same views stakeholders use in Search Console are available in automated reporting (brand/non-brand, multimodal, country+device). 2) Re-baseline KPIs: we keep the old “total” line, but decision-making moves to non-brand and segment views. 3) Tie segments to actions: if non-brand drops in one country on mobile, we route it to technical triage instead of content.

If you need implementation help beyond just SEO—API ingestion, dashboards, instrumentation—this is where a dev+SEO team beats a pure SEO shop. We often bundle this work into broader analytics rebuilds during builds for web development in Canada and measurement-heavy rebuilds under our web development work in London.

A quick note on cost and resourcing

If your internal team asks “how big is this really?”, the honest answer is: small if you already have connectors and modelling; medium if you’re still emailing CSVs. When clients want a ballpark for the plumbing work, we point them to our software development cost guide for planning and then scope the reporting layer separately.

Context: this fits a bigger pattern at Google

Google has been steadily pushing Search Console from “a web UI you check” into “a dataset you operationalise.” The API catching up to the UI is part of that. Search Engine Roundtable also flagged the same additions rolling into the API from the UI side: coverage of branded, multimodal and country/device filters coming to the Search Analytics API.

Separate but relevant: measurement has been messy during periods of ranking flux, and tooling doesn’t always keep up. If you’re trying to make sense of volatility right now, keep that in mind when you interpret week-over-week changes: notes on the November 2026 core update volatility and tracking limitations.

If you want more updates like this without the noise, we’re filing them in our Trending Tech News hub.

If you do nothing for 90 days

You’ll keep reporting blended performance while competitors start separating brand vs non-brand and spotting early drops in new SERP formats. That usually ends the same way: budget goes to the wrong channel, the wrong content gets produced, and when organic revenue dips you won’t know which segment broke until it’s expensive to fix.

Next step: pick one property, rebuild the Search Analytics API pull with brand/non-brand + multimodal + country/device cuts, and ship a new exec dashboard in 14 days.

If you operate in Europe and need local-language SEO execution alongside the reporting rebuild, our teams cover SEO support via our German SEO agency page and delivery through our SEO agency page in France.

Primary source: Google Search Central Blog

Search ConsoleSearch Analytics APISEO reportingBranded queriesMultimodal
Consultation with our teamTeam working together

Need any help? Contact us today

+1 (502) 780-5714

Frequently Asked Questions

FAQ: Search Analytics API’s new filters and reporting

1. Does the Search Analytics API branded queries filter replace our regex brand lists?

For many teams, yes. The point is to stop maintaining fragile brand keyword lists and instead use Google’s own branded/non-branded classification in API reporting. Keep your old method for comparison during the first few weeks.

2. What should we do first with web multimodal reporting?

Create a simple weekly view for your top pages and queries that isolates web multimodal performance. Treat unexpected drops as a signal to review SERP appearance, media assets, and intent alignment—not as a generic “SEO traffic down” problem.

Let’s make something great work together.

From day one to enterprise – we’re your partner in long-term tech success.