20 November 2026 · 9 min

Search Console API: measure brand, non-brand and multimodal search

Google has added brand classification, multimodal search and combined country and device filters to the Search Analytics API. SEO reporting can now answer commercial questions instead of merely producing attractive charts.

Search Console API: measure brand, non-brand and multimodal search

SEO reporting stayed manual for too long

Google released three additions to the Search Analytics API on November 16, 2026. Brand and non-brand queries can be separated automatically. Multimodal searches from Google Lens, Circle to Search and uploaded images have their own data type. Countries and devices can be grouped in a single filter.

This sounds like an update for analysts. It matters to every company that needs to know whether search visibility is creating new demand or merely serving people who already know the name. Until now, teams maintained their own regular expressions, queried countries separately and treated visual search as a separate reporting problem. Much of that work can now use classifications and filters provided directly by Google.

The value is not another dashboard. The value is a better decision about which content, landing pages and campaigns are actually expanding the market.

Brand traffic shows trust, non-brand traffic shows opportunity

More organic clicks can tell two very different stories. If more people search for the company name, brand awareness is growing. If they discover the website through a problem, service or product category, the business is gaining visibility before the customer has chosen a provider.

Both outcomes matter, but they should not be mixed. Brand traffic responds strongly to recommendations, PR, offline conversations and paid campaigns. Non-brand traffic is a clearer signal that Google understands a website as an answer for searches such as web design Hamburg, app development or AI automation.

The new brandedClassification dimension can separate these groups in the API. Google states that it is available only to eligible properties. If a property is not eligible, the response contains no corresponding rows. Reporting must handle that state explicitly. Missing classification data does not mean the site has zero brand traffic.

Regular expressions were always an approximation

Many SEO teams currently classify brand queries with regular expressions. They collect the company name, spelling variations, products, domains and common mistakes. This works while the brand is small and the language set is limited.

The list quickly becomes fragile. An international business has local product names and multiple spellings. Campaigns create new phrases that the rule does not know. A generic brand name can also match unrelated intent. Queries that combine a company and a category are difficult to classify consistently.

Google’s classification does not remove the need for quality control, but it provides a more consistent starting point. We would run the new field and the existing rules in parallel for several weeks, investigate differences and only then retire old logic. A new dimension should not silently rewrite the historical time series.

Multimodal search becomes measurable traffic

People no longer search only with words. They point Google Lens at a product, select part of an image with Circle to Search or upload a photograph. This route matters to ecommerce, travel, interiors, local services and technical products. A person may not know the correct term but can clearly show the object or problem.

The webMultimodal type lets the Search Analytics API report this traffic separately. Google groups Lens, Circle to Search on Android and image uploads in Google Search under that type. Properties with an active bulk export can also receive the data in BigQuery.

This does not turn every image into a performance channel. It finally shows whether images contribute to one. Teams can identify which pages receive multimodal impressions, which devices are involved and whether visual discovery produces clicks.

Useful images need more than a pretty subject

Publishing more stock photography is not a multimodal SEO strategy. Google needs to understand what an image shows and why it belongs to the search intent. That begins with a clear subject, enough resolution and a stable image URL. The surrounding copy, heading, page context and precise alternative text help describe the subject.

For a property platform, real rooms, plans and distinctive details can be useful. For a plumbing business, visible components, typical damage and understandable repair stages are more informative than a smiling model with a toolbox. For an app, clear product screens matter more than decorative device mock-ups that make the interface impossible to read.

The new report does not reward a design technique. It reveals whether visual content answers a real search task.

DACH and mobile no longer require separate requests

The new filterLists field can combine several countries or devices in one request. A company can treat Germany, Austria and Switzerland as a DACH reporting group while filtering for mobile and tablet traffic together.

That sounds simple, but it removes fragile work from automated reporting. Teams previously issued multiple requests and merged the results. Dates, filters or dimensions could drift between those requests. One request can now describe the intended region and device group directly.

An aggregate must still not hide local differences. A DACH view answers whether the region is growing. Decisions still require the country, language and landing page below it. Germany can improve while Switzerland declines. The combined number must not make that change disappear.

Reporting starts with a decision

Most dashboards fail because they lack a question, not because they lack data. They display clicks, impressions, CTR and position without telling anyone what to do on Monday morning.

An agency might ask whether new service pages are winning more non-brand demand in Hamburg and across DACH. A retailer might ask which category pages are discovered through multimodal search and whether their click rate trails ordinary web search. An app company might need to separate brand growth from a campaign and discovery created by educational content.

Only after that question is clear should the team choose dimensions, filters and comparison periods. The API automates collection. It cannot decide which movement is commercially meaningful.

How we would build a dependable SEO dashboard

We would collect data daily with a stable property identifier and a documented date range. Raw responses remain unchanged. Derived views then separate brand traffic, non-brand traffic and multimodal search. Countries, devices, pages and queries are combined only as far as the business question requires.

Every metric needs a comparison. The last 28 days against the previous 28 reveal recent movement. The same period one year earlier protects seasonal businesses from false alarms. Releases, redesigns and campaigns belong as annotations on the timeline so a later change still has context.

Alerts should not fire for every fluctuation. A useful rule looks for sustained change with enough impressions behind it. Reporting then becomes an operating tool rather than a machine for nervous Slack messages.

The API does not return every individual row

Search Console data requires honest interpretation. Google documents that internal limits mean the Search Analytics API does not guarantee every data row. Results are sorted by clicks. Small and rare queries may be absent, particularly when a request combines many dimensions.

Average position is not a daily rank tracker for one keyword either. It combines locations, devices and search contexts. A value of eight can be produced by several very different patterns of visibility.

For decisions, trends are useful and false precision is not. We would connect API data with landing page conversions, server logs and focused manual SERP checks. No single report can explain by itself why a lead was created.

Example: an agency wants growth beyond its name

Imagine an agency publishing new pages for web design Hamburg, app development and AI automation. Its dashboard separates brand and non-brand traffic, groups the DACH markets and compares mobile with desktop. After launch, non-brand impressions rise while CTR remains weak.

The answer is not automatically to publish more articles. The team first inspects the queries and landing pages. The agency may rank for terms that are too broad. Its title and description may miss the expectation. A case study may appear where the searcher needs a service page.

If a campaign increases brand clicks at the same time, that gain remains visible without inflating the apparent success of the new SEO pages. This is what makes the API update commercially useful.

Our conclusion

The new Google Search Analytics API filters do not solve an SEO problem on their own. They make three developments easier to measure: demand for a brand, visibility beyond the brand and search that starts with an image rather than text.

Marketing teams gain a stronger basis for content and budget decisions. Developers can simplify reporting because countries and devices can be grouped in one request. Sales and leadership can see whether organic reach merely captures existing awareness or creates new demand.

The right response is not to build a larger dashboard immediately. Choose one important growth question and create a dependable measurement for exactly that question.

Primary sources

Google Search Central: New filtering and reporting capabilities in the Search Analytics API explains brandedClassification, webMultimodal and filterLists, including availability through the BigQuery bulk export.

Google Search Console API: Search Analytics query documents authorization, dimensions, filters, sorting and the limits of returned data rows.

Cloud
Cloud
Contact us

We can say a lot. It is better to make something great together.

Tell us briefly what you have in mind — we will reply with a few concrete first thoughts.

Personal reply · usually within 1 working day · first call is free