- date
- author
- WiseSEO Editorial
- category
- [GSC]
- impact
- MED
- status
- OFFICIAL DOC
- read
- 4 min
New Search Analytics API filters arrived in the middle of a core update
Google added branded, multimodal and multi-country filters to the Search Analytics API on 16 November, mid-core-update.
On 16 November 2026, the Search Console team added three cuts to the Search Analytics API: a branded-query classification, a web multimodal search type, and a way to filter several countries or devices in one request. Daniel Waisberg, Nati Yosephian and Karin Gadasi announced the change on the Google Search Central blog. All three already existed in the Search Console Performance report.
The timing is what makes the release more than a developer convenience. Google released the November 2026 core update on 10 November. In a LinkedIn post that day, Google Search Central called it "a regular update designed to better surface relevant, satisfying content for searchers from all types of sites," and said the rollout "may take up to 2 weeks to complete." The Search Status Dashboard recorded the start at 10:06 US/Pacific on 10 November and, as of 17 November, still listed the incident as active, with no completion notice. Google's core-update documentation says to wait until the dashboard shows the rollout has finished, wait at least a further week, compare that week with a week before the rollout started, and "analyze different search types separately."
That is the job the new API fields are good for this week, if you keep the series apart rather than blending them into one number.
Advertisement
brandedClassification lets you group or filter rows as BRANDED or NON_BRANDED. The blog is explicit that this is only available for eligible properties, and that other properties get a response with no rows. The API reference, last updated the same day, adds three constraints: the data starts on 21 February 2026; it is limited to top-level properties with enough query and impression volume; and you cannot combine a brandedClassification dimension or filter with a query filter in the same request. Google's 2025 announcement also matters: the classification is not a regular expression of brand names. It is "an internal, AI-assisted system" that can include typos and product names, and "has no effect on how Google Search ranking works." An empty API response is ambiguous: the property may be ineligible, or the dates may truly have no rows.
webMultimodal is a type, not a dimension. Setting it returns performance data from Google Lens, Circle to Search on Android, and image uploads in Google Search. The default web type remains "the combined ('All') tab in Google Search" and, the reference says, does not include Discover or Google News. Multimodal results will not appear in a standard web query, so a dashboard that only requested web can look stable while Lens or Circle-to-Search traffic moves. The blog says this data will also be available in BigQuery for properties with an active bulk data export.
filterLists sits inside dimensionFilterGroups and accepts several exact-match values for country (ISO 3166-1 alpha-3 codes) or device (DESKTOP, MOBILE, TABLET) in one call, so a regional cut such as DACH or EMEA does not need a loop of requests. The reference says a request cannot filter the same dimension in both filters and filterLists.
What is not confirmed is any special connection between these fields and the core update itself. Google presented the API work as a response to ecosystem requests, not as a measurement tool for this rollout. The fields do not tell you why a page moved.
what to do
- Wait for the official end date. Check the November 2026 core update incident before you close an "after" window. Google's guidance is to wait at least a week after that date, then compare that week with a week that ends on 9 November, the day before the rollout started.
- In the Search Console Performance report, confirm whether your property already shows the branded-queries filter. If it does not, an API call grouped by
brandedClassificationmay also return no rows. Do not treat that empty response as "no branded traffic." - If the filter is present, pull branded and non-branded Search results as two series for the same dates. A blended total will hide which one moved.
- Query
webMultimodalon its own, then join it to yourwebseries by date. Do not add the two types together and call the result "Google Search traffic." - Use
filterListsfor the country or device groups you already report as regions, rather than issuing one request per country and adding the rows yourself. Do not also put that same dimension infilters. - When you request recent dates, look at the response
metadata.first_incomplete_dateif you grouped by date withdataStateset toall. Days after that stamp can still change. - After the rollout is complete and the extra week has passed, use those same cuts to inspect the pages and queries with a large position drop. The API will not explain the drop.
refs
- [1] New filtering and reporting capabilities in the Search Analytics APIhttps://developers.google.com/search/blog/2026/11/search-analytics-api-update
- [2] Search Analytics: query (Search Console API reference)https://developers.google.com/webmaster-tools/v1/searchanalytics/query
- [3] Introducing the branded queries filter in Search Consolehttps://developers.google.com/search/blog/2025/11/search-console-branded-filter
- [4] November 2026 core update (Search Status Dashboard incident)https://status.search.google.com/incidents/WLxcJyC6jMWMfryxsKMc
- [5] History for Ranking | Google Search Status Dashboardhttps://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history
- [6] Google Search Central on LinkedIn: November 2026 core updatehttps://www.linkedin.com/posts/googlesearchcentral_google-search-status-dashboard-activity-7525982777905709056-HuJD
- [7] Google Search's Core Updateshttps://developers.google.com/search/docs/appearance/core-updates
Advertisement