Skip to content

Latest news

Eleutheros Ltd
Red and white light trails curving along a highway at night

Traffic acquisition

Google adds brand filter and multimodal data to Search Analytics API

Google announced on 16 November 2026 that the Search Analytics API now includes three features already available in the Search Console Performance report. The brand filter only applies to eligible properties, which raises questions for teams that automate their reporting.

Search Console's API is where most serious SEO reporting actually lives: dashboards, data warehouses, alerting scripts. According to Abondance, which reported on Google's 16 November 2026 Search Central announcement, the Search Analytics API now carries three functions that until now existed only in the Performance report of the interface. One of them, the `brandedClassification` field, separates brand queries from non-brand queries.

The announcement matters less for what it adds than for where it adds it. A capability that exists only in a user interface forces anyone who wants it at scale to rebuild it by hand, usually with imperfect keyword lists. Moving it into the API changes what can be automated, and therefore what can be measured consistently over time.

The eligibility caveat is the real story

Abondance notes that the brand split is reserved for eligible properties. The report does not specify the criteria used to determine eligibility, nor whether ineligible properties receive an error, an empty field, or a fallback behaviour. That gap is worth taking seriously before planning any migration.

In practice, teams live with two definitions of a brand query: the official one from Google, and their own regex-based approximation. The second is controllable and auditable. The first is convenient but opaque, and if it only applies to some properties, two sites in the same portfolio can end up producing non-comparable numbers in the same dashboard. Before adopting the new field as a KPI source, check three things this week: whether your properties are eligible, how the field behaves on a property that is not, and whether historical data is backfilled or only new data is classified. Google's announcement, as reported, does not answer these questions.

The multimodal and multi-country filters raise a similar practical question. Grouping several countries in a single query is convenient for regional reporting, but it can quietly flatten differences that matter for acquisition: search behaviour, query mix and brand recognition rarely align across markets. If your reporting aggregates countries, make sure the aggregation stays a deliberate choice rather than a default that arrived with an API update.

What to do before changing your pipelines

Nothing here requires urgency, but the change touches the plumbing that feeds traffic decisions.

  • Verify eligibility for each property you report on, and document the result.
  • Test the new fields in a sandbox query before touching production dashboards.
  • Keep your existing brand classification alongside the native one for at least a quarter, and compare.
  • Confirm with whoever owns your data warehouse how the new fields will be stored and whether history exists.

The underlying shift is familiar. Search Console keeps pushing analysis into the API, which rewards teams with clean data infrastructure and penalises those whose reporting is a patchwork of manual exports. The brand filter is a good example: useful, but only if you know what it excludes and why.

Also worth reading

All news

Aerial night view of Alexander Nevsky Cathedral in central Sofia

Contact

Tell us where the project stands.

A few lines are enough: what you are building, where it is today, and what is blocking it. We answer every message personally.

Contact us contact@eleutheros.eu