Google has brought branded-query segmentation, web multimodal reporting and grouped country and device filtering to the Search Analytics API. Its November 16, 2026 announcement makes those Search Console capabilities available for custom reporting and automated workflows.[1]
Our read: the practical opportunity is a more repeatable search review. The immediate job is to preserve the meaning of each segment while automating its delivery. Make the reporting definitions part of the work, not a footnote added after the chart is approved.
Move the reporting boundary
Google says to use brandedClassification to group or filter branded and non-branded performance. Ineligible properties return no rows. Set type to webMultimodal for Google Lens, Circle to Search on Android and image uploads in Google Search. The new filterLists field supports several countries or devices in a request.[1]
Our read: this is a useful moment to review the reporting contract with your agency or analytics team. Ask which recurring search questions should become scheduled reports, which require investigation and who owns the definitions. Treat the release as a reason to improve the reporting process before commissioning another dashboard.
Start with a decision the business actually needs to make. A hypothetical retailer might want to review visual-search performance across its priority markets before commissioning new product photography. A service business might want branded and non-branded reporting beside its regional content plan. These are suggested uses, not evidence that either investment will improve performance.
Keep a written definition beside each proposed report: property, reporting period, search type, markets, devices and intended audience. Our recommendation is to make that specification the acceptance criteria for the work. A chart should be reproducible by someone who did not build it.
Keep brand classification visible
Google explains that branded classification uses an internal AI-assisted system rather than a keyword regular expression. It warns that queries can be misidentified and says the filter has no effect on Search ranking.[3]
Our recommendation: label the dashboard as Google-classified branded traffic. If your existing report uses a maintained list of brand terms, retain its definition during the comparison. Avoid presenting the change of method as evidence that brand demand suddenly rose or fell. Investigate disagreement before replacing the established series.
There is also a request constraint: the API supports only equals for brandedClassification. Filtering or grouping by that classification cannot be combined with a query filter in the same request.[2]
For implementation, ask the reporting owner to document which questions require separate requests. Keep the classification view distinct from a custom keyword investigation, with the method stated beside each. Our advice is to preserve the distinction through exports and presentation slides, so a leadership review does not quietly turn a platform classification into a claim about customer intent.
Define the regional view
The API reference says a filterLists entry matches any supplied expression for its dimension. A request cannot filter the same dimension through both filters and filterLists.[2]
Our recommendation: write down exactly which countries belong to each business region before building the request. Use the commercial definition your team has agreed to report against. If that membership changes, annotate the change and reconsider the comparison period. Do the same for device selections rather than leaving them implicit in a connector configuration.
For a hypothetical regional review, ask for the combined view and a market breakdown with matching settings. Use the breakdown to challenge the proposed explanation for a movement. If the team wants to commission localized content, require it to name the market, the page and the customer question that needs attention.
Keep multimodal reporting named explicitly in this specification. Our recommendation is to give it a defined editorial purpose: which product images or landing pages should the team inspect after reviewing the report? Avoid treating an additional reporting surface as a reason to expand production without a concrete question to answer.
Approve the report with its limits
Google cautions that the API does not guarantee every data row; internal limitations mean it returns top rows. Its reference also says that omitting dataState, or setting it to final, returns finalized data.[2]
Our recommendation: require a saved request, a sample response and an explanation of the selected data state before accepting the new report. Test how the dashboard displays an empty response. Given the eligibility restriction, do not automatically translate missing branded rows into an absence of branded searches. Make unavailable data visibly different from a measured result.
Before retiring the old report, compare matching periods and settings, record unresolved differences and assign someone to investigate them. Preserve the previous method long enough to explain the transition. Ask the team to state what the new report can support and which business conclusions still need other evidence.
For the next search review, bring the reporting specification alongside the chart. Use it to decide whether a movement warrants a content audit, a technical investigation or further observation. Our recommendation is to fund the ability to explain a result, with automation serving that responsibility.
Automate the report. Keep someone accountable for what it means.
Make the next reporting brief a definition brief before it becomes a dashboard brief.
Sources
- Google Search Central — New filtering and reporting capabilities in the Search Analytics API. Published 2026-11-16; accessed 2026-11-17.
- Google Search Console API — Search Analytics: query. Accessed 2026-11-17.
- Google Search Central — Introducing the branded queries filter in Search Console. Published 2025-11-20; accessed 2026-11-17.