Google today opened three of its newer search reporting features to developers, adding branded query classification, a search type for Google Lens and Circle to Search, and filters that accept several countries or devices at once to the Search Analytics API. Until now the three had lived only inside the Performance report of Search Console, the free tool in which site owners track how their pages appear in Google Search. The post on the Google Search Central Blog carries the names of Daniel Waisberg, Nati Yosephian and Karin Gadasi of the Search Console team, and the API's reference page for the query method was updated on the same day.
According to Google, the change follows "ecosystem requests to make this data available for custom reporting and automated workflows." That is a polite way of describing a gap of up to a year. Agencies, publishers and the software companies that build products on Search Console data had watched the features arrive in the web interface while the API, which feeds their dashboards, stayed behind.
In Short
Google today made three Search Console reporting features available through the Search Analytics API: a split of queries into branded and non-branded, a search type covering Google Lens, Circle to Search and image uploads, and filters that take several countries or devices in one request. The change matters to agencies, international brands and SEO software companies that pull Search Console figures into their own dashboards, because one call can now do what used to take hand-built brand lists or a request per market. The fine print sits in the documentation: branded data starts on February 21, 2026, covers only top-level properties with enough volume, and cannot be combined with a query filter in the same request.
Three features, one endpoint
The update touches a single method, searchanalytics.query, which answers a POST request with rows of clicks, impressions, click-through rate and average position. Google's announcement lists the additions as three new options.
The first is branded queries. Requests can now "group or filter your data by brandedClassification to compare branded and non-branded performance," according to the post. The second is web multimodal: setting the type parameter to webMultimodal returns "performance data from Google Lens, Circle to Search on Android, and image uploads in Google Search." The third is a new field, filterLists, which Google describes as a way "to filter by several countries or devices in a single request."
Google frames the practical gain in terms of work saved. "Instead of stitching together separate requests or maintaining complex keyword regex lists, you can now query a group of countries (such as EMEA, LATAM, or DACH) and device combinations in a single API call, and automatically segment branded from non-branded traffic in your dashboards," the post states.
It also says the pieces can be stacked. "Because these filters work together, you can slice your data even further, such as monitoring brand growth across specific regional hubs or seeing which pages perform best in multimodal search across key markets and devices." The reference page, as the sections below show, sets limits on how far that stacking goes.
None of this is new data in the strict sense. Each capability had already been introduced in the Performance report over the past year, a point Google makes in its opening paragraph. What changes today is who can reach it without a browser, and at what scale.
| Addition | Where it sits in the request | Accepted values | Documented conditions |
|---|---|---|---|
| Branded queries | dimensions[] and dimensionFilterGroups[].filters[].dimension = "brandedClassification" | BRANDED, NON_BRANDED | "equals" operator only; cannot be combined with a "query" filter; data from February 21, 2026; top-level properties with sufficient volume only |
| Web multimodal | type = "webMultimodal" | One of seven type values | Also to be available in BigQuery for properties with an active bulk data export |
| Multi-value filters | dimensionFilterGroups[].filterLists[] | dimension: "country" or "device"; expressions: list of strings | Same dimension cannot appear in both filters and filterLists in one request |
Branded queries: what the reference page allows
The most consequential of the three is also the most fenced in. The reference page defines brandedClassification as a filter dimension and lists two values, BRANDED and NON_BRANDED. The definitions are short, and each clause carries a restriction.
According to the documentation, the dimension will "Filter results against the specified branded query classification (only the "equals" operator is supported)." The operators contains, notContains, notEquals and the two regular expression operators therefore do not apply to it. A second sentence rules out a combination that many analysts would reach for first: "Filtering or grouping by "brandedClassification" can't be combined with a "query" filter in the same request." A request cannot, in other words, ask for the branded share of queries containing a given product name. Grouping by query alongside brandedClassification is not addressed by that sentence, which refers only to a query filter.
The third condition concerns time and eligibility. "Data is available starting February 21, 2026, and only for top-level properties with sufficient query and impression volume," the page states. By PPC Land's calculation, that gives the API 268 days of branded history as of today. Google introduced the branded queries filter in the Search Console interface in November 2025, so the API's history begins roughly three months after the feature first appeared.
What happens to properties that do not qualify? The blog post answers plainly: "As in Search Console, this data is only available for eligible properties. For other properties, the response won't include any rows." Elsewhere the reference page describes a request that runs past the end of the results as "a successful response with zero rows." Neither document describes an error message or a field that tells a caller its property is ineligible.
Then there is the question of who decides what counts as a brand. Under the old method, which Google's post calls "maintaining complex keyword regex lists," a site owner wrote the rule. Under brandedClassification, Google applies the label, and the reference page gives no mechanism for reviewing or editing it. Microsoft took a different route with its own analytics product: Microsoft Clarity lets site owners edit the Brand Terms behind its branded and non-branded split of AI traffic, including abbreviations, spellings, translations and typos, 57 days after it introduced that split on August 3, 2026.
Web multimodal: a seventh search type
The type parameter decides which Google surface the figures come from. With today's change it accepts seven values, and the reference page defines each one. The older searchType parameter is still listed but marked "Deprecated, use type instead."
| type value | Definition in the reference page |
|---|---|
| "discover" | Discover results |
| "googleNews" | "Results from news.google.com and the Google News app on Android and iOS." "Doesn't include results from the "News" tab in Google Search." |
| "news" | "Search results from the "News" tab in Google Search." |
| "image" | "Search results from the "Image" tab in Google Search." |
| "video" | "Video search results" |
| "web" (default) | "Filter results to the combined ("All") tab in Google Search." "Does not include Discover or Google News results." |
| "webMultimodal" | "Search results from Google Lens, Circle to Search on Android, and image uploads in Google Search." |
The interface version of this report arrived recently. On September 24, 2026, Google began rolling out a Multimodal option under Web in the Performance report's search type filter, splitting Web into text-based and multimodal results. That rollout came with a notable omission: the queries dimension is not available in the interface when the multimodal type is selected. The description recorded then also named Chrome's "Search this image" among the covered entry points, while the API reference names three surfaces only.
Google adds one commitment beyond the API itself. "This data will also be available in BigQuery for properties with an active bulk data export," the blog post says. The sentence is in the future tense, and no date is attached.
The scale of the behavior being measured is still largely described by Google itself. In July 2025, Robby Stein, who leads Google's AI Search team, said visual searching was up 65% year over year, without publishing a base period or method. An API feed of Lens and Circle to Search clicks gives site owners a way to check a slice of that trend against their own traffic, at least for the pages Google sends visitors to.
filterLists: one request, several markets
The third addition is the most mechanical, and possibly the most used. Before today, a request could contain filter groups, but the reference page still defines groupType as "Whether all filters in this group must return true ("and"), or one or more must return true (not yet supported)." Only "and" is accepted. A list of countries in one request had no documented "any of" form.
The new field supplies one, for two dimensions. According to the reference page, filterLists holds "Zero or more multi-value dimension filters to test against the row," and "A row matches a filter list if its value for the specified dimension equals any of the provided expressions." The dimension must be "country," expressed as ISO 3166-1 alpha-3 codes, or "device," which takes DESKTOP, MOBILE or TABLET. Page, query and search appearance are not listed for filterLists.
One rule prevents overlap: "Note that a single request cannot filter on the same dimension in both filters and filterLists at the same time." A request can therefore pair a list of countries in filterLists with a device filter in filters, but not a country list with a separate country exclusion.
The interface side of this feature had a less tidy history. On October 6, 2026, Google Search Console began letting sites view several countries as one total, according to a Google Search Central post on LinkedIn; before that, comparisons were limited to two items. PPC Land's report at the time described the country change and left any device change unconfirmed. Today's blog post refers to "multi-country and multi-device filtering" as already introduced, and links to the same LinkedIn post.
How a request is built
The reference page describes the structure of a call in detail. According to Google's documentation, a request to the method is assembled from the following parts.
- Endpoint. A POST request goes to https://www.googleapis.com/webmasters/v3/sites/siteUrl/searchAnalytics/query, where siteUrl is "The URL of the property as defined in Search Console," for example http://www.example.com/ for a URL-prefix property or sc-domain:example.com for a Domain property.
- Authorization. The request requires one of two OAuth scopes: https://www.googleapis.com/auth/webmasters.readonly or https://www.googleapis.com/auth/webmasters.
- Date range. startDate and endDate are required, in YYYY-MM-DD format, "in PT time (UTC - 7:00/8:00)." The start date "Must be less than or equal to the end date."
- Grouping. dimensions[] is optional. "There is no limit to the number of dimensions that you can group by, but you cannot group by the same dimension twice." Valid names are the filter dimensions plus "date" and "hour." "If no dimensions are specified, all values will be combined into a single row."
- Search type. type is optional and defaults to "web." Setting it to "webMultimodal" returns Lens, Circle to Search and image upload data.
- Filters. dimensionFilterGroups[] holds filters (a dimension, an operator and an expression, with a "Max length 4096 characters") and, from today, filterLists (a dimension and a list of expressions).
- Aggregation and paging. aggregationType defaults to "auto." rowLimit is "Valid range is 1-25,000; Default is 1,000," and startRow is a zero-based offset for paging.
- Freshness. dataState defaults to "final." "all" includes fresh data, and "hourly_all" includes an hourly breakdown that the page says "includes partial data."
- Response. Each row returns keys, clicks, impressions, ctr and position. The response also reports responseAggregationType and, for fresh data, a metadata object with first_incomplete_date or first_incomplete_hour, given in the America/Los_Angeles time zone.
The request body structure, as published in the reference page, now reads:
{
"startDate": string,
"endDate": string,
"dimensions": [
string
],
"type": string,
"dimensionFilterGroups": [
{
"groupType": string,
"filters": [
{
"dimension": string,
"operator": string,
"expression": string
}
],
"filterLists": [
{
"dimension": string,
"expressions": [
string
]
}
]
}
],
"aggregationType": string,
"rowLimit": integer,
"startRow": integer
}
The operators available to ordinary filters are unchanged. According to the reference page, "contains" means "The row value must either contain or equal your expression (non-case-sensitive)"; "equals," the default, means "Your expression must exactly equal the row value (case-sensitive for page and query dimensions)"; "notContains" and "notEquals" are their opposites; and "includingRegex" and "excludingRegex" take "An RE2 syntax regular expression" that must or must not be matched.
| Parameter | Status | Documented values or limits |
|---|---|---|
| startDate, endDate | Required | YYYY-MM-DD, Pacific Time; start on or before end |
| dimensions[] | Optional | country, device, page, query, searchAppearance, brandedClassification, date, hour; no limit on count, no repeats |
| type | Optional | discover, googleNews, news, image, video, web (default), webMultimodal |
| groupType | Optional | "and" only; "or" listed as not yet supported |
| filters[] | Optional | dimension, operator, expression; max length 4,096 characters |
| filterLists[] | Optional (new) | dimension "country" or "device"; expressions list required |
| aggregationType | Optional | auto (default), byNewsShowcasePanel, byPage, byProperty |
| rowLimit | Optional | 1 to 25,000; default 1,000 |
| startRow | Optional | Default 0; past the end returns zero rows |
| dataState | Optional | final (default), all, hourly_all |
The limits that did not move
Today's additions sit on top of constraints that remain in place. The reference page still warns that "The API is bounded by internal limitations of Search Console and does not guarantee to return all data rows but rather top ones." Results are sorted by click count in descending order, unless grouped by date, in which case they run oldest first. "If there is a tie between two rows, the sort order is arbitrary."
Aggregation rules also persist. "If you group or filter by page, you cannot aggregate by property," the page states, and "The API will never change your aggregation type if the requested type is invalid." The byProperty option is "Not supported for type=discover or type=googleNews." The ctr field, for its part, is expressed as a fraction: "Values range from 0 to 1.0, inclusive," which matters to any dashboard that treats click-through rate as a percentage.
The last major API change in this area came in April 2025, when Google added hourly data support to the Search Analytics API, introducing an HOUR dimension and the hourly_all data state, with up to 10 days of hourly figures against 24 hours in the interface. That release, like today's, moved the API ahead of or level with the browser view rather than behind it.
Why reporting plumbing matters now
For the marketing community, the significance lies less in any single field than in who controls the measurement. Search Console is Google's own record of how a site performs in organic search, and its API is the route by which that record reaches agency dashboards, rank trackers and data warehouses. Each feature that stays interface-only forces manual exports or workarounds.
Third-party tools have had particular reason to lean on Google's own feeds. In September 2025, Google eliminated the n=100 search results parameter, which meant 10 requests instead of one to collect 100 results and raised costs for SEO software. Branded segmentation, previously rebuilt by each tool with its own keyword lists, now comes from Google in a standard form, with Google's definition attached.
The search results themselves have also become harder to read through the old categories. Since June 2025, AI Mode clicks, impressions and position have counted toward Search Console totals, merged into Web with no separate segment. On June 3, 2026, Google gave Search Console its own generative AI visibility reports, though clicks and queries were not part of the data described. A dedicated multimodal type in the API is a further split of the Web bucket, while AI Mode remains folded inside it.
Reconciliation is a recurring problem too. Only last week, on November 12, 2026, Google explained why analytics tools will not match Search Console click counts, listing four reasons the two sets of numbers differ. Data quality has been uneven on occasion: PPC Land reported performance data frozen since October 19, 2025 and a Discover logging error on May 21, 2026 that reduced recorded clicks and impressions with no backfill indicated.
Competitors have been filling similar gaps at their own pace. Bing Webmaster Tools added device and country breakdowns to its Search Performance report in August 2025 without an official announcement. Microsoft Clarity built its own branded and non-branded view of AI traffic in 2026, with the brand list in the site owner's hands.
What the documentation leaves open
Several questions remain unanswered in both documents. Neither defines a "top-level" property or the volume that counts as "sufficient," and neither describes a signal that separates an ineligible property from one with no branded traffic. The reference page does not explain how queries are classified as branded or why the classification cannot be combined with a query filter. It sets no maximum number of filter lists or expressions per request. It does not say whether the query dimension returns rows for webMultimodal, given that the interface hides queries for that type, and Google gives no date for the BigQuery bulk export of multimodal data or any word on brandedClassification in that export.
Key facts
- Announcement: "New filtering and reporting capabilities in the Search Analytics API," Google Search Central Blog, dated Monday, November 16, 2026; posted by Daniel Waisberg, Nati Yosephian and Karin Gadasi, Search Console team. URL: https://developers.google.com/search/blog/2026/11/search-analytics-api-update
- Documentation: "Search Analytics: query," Search Console API reference, "Last updated 2026-11-16 UTC." URL: https://developers.google.com/webmaster-tools/v1/searchanalytics/query
- Method and endpoint: POST https://www.googleapis.com/webmasters/v3/sites/siteUrl/searchAnalytics/query
- Scopes: webmasters.readonly or webmasters
- New dimension: brandedClassification, values BRANDED and NON_BRANDED, "equals" operator only, not combinable with a "query" filter, data from February 21, 2026, top-level properties with sufficient query and impression volume only
- New type value: webMultimodal (Google Lens, Circle to Search on Android, image uploads in Google Search); BigQuery availability promised for properties with an active bulk data export, no date given
- New field: dimensionFilterGroups[].filterLists[], dimensions "country" (ISO 3166-1 alpha-3) and "device" (DESKTOP, MOBILE, TABLET)
- Unchanged limits: rowLimit 1 to 25,000 (default 1,000); filter expression max 4,096 characters; groupType "and" only
- Deprecated parameter: searchType, replaced by type
- Interface launches referenced by Google: branded queries filter (November 2025), web multimodal reporting (September 2026), multi-country and multi-device filtering (announced on LinkedIn; country change reported October 6, 2026)
Timeline
- April 9, 2025: Google adds hourly data support to the Search Analytics API, with an HOUR dimension and up to 10 days of hourly data
- June 2025: AI Mode clicks, impressions and position begin counting toward Search Console totals
- July 23, 2025: Robby Stein says visual searching on Google is up 65% year over year
- August 7, 2025: Device and country filters appear in Bing Webmaster Tools
- September 14, 2025: Google discontinues the n=100 search results parameter
- October 19, 2025: Search Console performance reports stop updating
- November 2025: Google introduces the branded queries filter in the Search Console Performance report
- November 17, 2025: Search Console adds custom chart annotations
- February 21, 2026: First date for which branded classification data is available in the Search Analytics API
- May 21, 2026: A logging error reduces Discover clicks and impressions in Search Console
- June 3, 2026: Search Console gets generative AI visibility reports
- August 3, 2026: Microsoft Clarity splits AI traffic into branded and non-branded
- September 24, 2026: Search Console begins rolling out the Multimodal search type for Lens and Circle to Search
- September 29, 2026: Microsoft Clarity lets site owners edit the terms behind its branded AI query split
- October 6, 2026: The Search Console country filter accepts several countries as one total
- November 12, 2026: Google publishes guidance on why analytics and Search Console click counts differ
- November 16, 2026: Google brings branded classification, the webMultimodal type and filterLists to the Search Analytics API; the API reference page is updated the same day
Related PPC Land coverage
- Google Search Console gains Lens and Circle to Search data, without queries - the September 24, 2026 interface rollout of the Multimodal search type, which hides the queries dimension.
- Google Search Console lets sites view several countries as one total - the October 6, 2026 change to the Performance report's country filter.
- Google adds hourly data support to Search Analytics API - the April 2025 API update that introduced the HOUR dimension and hourly_all data state.
- Google explains why analytics won't match Search Console click counts - Google's November 12, 2026 guidance on referrer values and four sources of mismatch.
- Google finally gives Search Console its own generative AI visibility reports - the June 2026 reports for AI Overviews, AI Mode and generative features in Discover.
- Google AI Mode now counts toward Search Console totals - how AI Mode data was merged into Web totals without a separate segment in 2025.
- Microsoft Clarity lets brands edit what counts as a branded AI query - Microsoft's editable brand terms, a contrast with Google's fixed classification.
- Google eliminates n=100 SERP parameter forcing cost increases for SEO tools - the September 2025 change that raised data collection costs for SEO software.
- Google reports 65% surge in visual searches as AI mode drives multimodal adoption - Robby Stein's July 2025 figure on visual search growth.
- Bing Webmaster Tools adds device and country data filtering options - Microsoft's August 2025 addition of device and country breakdowns.
- Google Search Console adds custom annotations for performance tracking - the November 2025 annotation feature in the Performance report.
- Google's Discover data went dark on May 21 - what publishers need to know - a 2026 logging error that reduced Discover figures with no backfill indicated.
- Google Search Console performance data frozen since October 19 - the October 2025 interruption to performance report updates.
Summary
Who: Google's Search Console team, with the post signed by Daniel Waisberg, Nati Yosephian and Karin Gadasi. The change affects site owners, agencies, international businesses and third-party SEO and reporting tools that use the Search Analytics API.
What: Three Performance report features reached the API: brandedClassification (BRANDED or NON_BRANDED, from February 21, 2026, for eligible top-level properties only, "equals" only and not with a query filter), the webMultimodal type for Google Lens, Circle to Search on Android and image uploads, and filterLists for matching several countries or devices in one request.
When: Today, with the API reference page updated the same day. Branded data in the API starts on February 21, 2026; BigQuery availability of multimodal data has no date.
Where: The searchanalytics.query method of the Search Console API, at https://www.googleapis.com/webmasters/v3/sites/siteUrl/searchAnalytics/query, and later the Search Console bulk data export to BigQuery.
Why: According to Google, the update follows "ecosystem requests to make this data available for custom reporting and automated workflows," replacing separate requests per market and hand-maintained brand keyword lists with single calls and Google's own classification.
Discussion