Google added three reporting options to the Search Analytics API on November 16, 2026. You can pull branded and non-branded search data, report web searches that start with an image, and filter several countries or devices in one request. We’d keep the existing search totals and add these views beside them. Google’s release notes
Start with the question your team already asks every Monday. If it’s “are new buyers finding us?”, add the non-branded view first. If you sell products shoppers recognize from a photo, check visual search by product page. If your business covers several markets, decide which countries belong in each report before you automate the pull.
What Google added to the API
The Search Console Performance interface already offered these ways to cut the data. The November update makes them available to scripts and dashboards that call Search Analytics. You can schedule the same report each week and keep its filters with the numbers, without someone running the export again. Search Analytics API reference
| Change | What to request | What it helps you decide |
|---|---|---|
| Brand classification | Group or filter with brandedClassification |
Are people finding us for a category or looking for us by name? |
| Visual search on the web | Set type to webMultimodal |
Which pages appear when somebody starts with an image? |
| Several countries or devices | Add filterLists to a dimension filter group |
Which markets and devices should we review together? |
The API still reports the Google Search performance of the property you can access. A new column in a dashboard can explain a change in traffic. It can also create one on paper if a connector starts pulling a different search type or stops including some countries. Save the old request and its results before you change either.
Ask the person who maintains the report which API request each chart uses. A vendor may update its connector after Google updates the API. If the new fields are missing in your reporting tool, the Search Console interface still gives you a place to inspect the corresponding views.
What non-branded search can tell you
We’d put non-branded search beside total web search when the goal is to reach buyers who have yet to search for you by name. Google can group or filter eligible data as BRANDED or NON_BRANDED. Start with your current landing pages. See which appear for category and problem searches before choosing what to improve.
Google says brand classification can include company names, variants, misspellings, and products or services linked to the brand. Its system can also classify a query incorrectly. The feature requires a top-level property with enough query and impression volume. The API reference lists February 21, 2026 as the start of available classification data. If Google has no eligible data, the request can come back without rows. Google’s branded query announcement · API eligibility and dates
Suppose an industrial supplier sees clicks rise after a trade show. Branded clicks might come from people who heard the company’s name there. A separate rise in non-branded clicks to its fitting guide suggests more people found that guide through a wider product or problem search. Each view points to a different follow-up. The guide may need a clearer fit chart, or the branded landing page may need to make the next sales step easy.
Run the new classification beside your old brand-name rule for a few reporting periods. Record the rule, the property, and the dates. Inspect the biggest gaps before deleting the old view. If your business sells through several brands, check which names you previously counted as your own and how Google’s labels behave at property level. The report can help you choose pages to check. You still need to look at the search result and the landing page to understand what a buyer saw.

Where web multimodal search shows up
webMultimodal covers web searches that start with image inputs. Google names Lens, Circle to Search on Android, and image uploads in Google Search. This can make a useful separate view for a store, a manufacturer, or a publisher whose pages answer questions about things people can photograph. Google’s multimodal announcement
The regular API image search type refers to the Image tab. Keep a distinct name for each row in your dashboard. A shopper who uploads a photo of an adapter and sees a product page in web results is using a different search path from someone browsing the Image tab. Google also says multimodal data will reach BigQuery for properties with active bulk data export. Check the dates your property returns before you draw a trend line.
Take a replacement-parts retailer as an example. Pull multimodal rows by page and look for the pages that earn impressions. Open a few on a phone. Is the model number visible? Do dimensions include the parts a buyer needs to measure? Can a shopper see which variants fit and which are in stock? Those checks can reveal a gap even if the photo looks good.
If the row grows after the retailer updates those pages, compare the changed pages with similar pages where the content stayed the same. Check stock and seasonality as well. A correlation gives you a reason to inspect the work. Keep dates and edits in the report so the next person can repeat the comparison.
How to filter countries and devices together
Inside dimensionFilterGroups, filterLists lets you match several exact values for a country or device dimension in a single request. Include the dimensions you need in the returned breakdown. A country filter can limit the data to the US and Canada. Add country as a grouping dimension if the dashboard needs one row for each.
For an illustrative North American report, use three-letter codes such as usa and can in the country list. A separate device list can include MOBILE and DESKTOP. Match all filter conditions in one group when the report needs those countries on those devices. The result can show the selected region total, or a country and device breakdown if you group by both. The API also supports TABLET when you want it in the view. API filter list and grouping rules
Watch for two limits when you change a request. You cannot put the same dimension in both filters and filterLists. You also cannot combine a query-text filter with grouping or filtering by brandedClassification in the same request. Use separate requests for an exact query audit and a brand-classified view. Record both requests so a later export keeps the same definitions.
Country and device cuts are most useful when they change the next step. If non-branded mobile clicks fall in one market, open the landing pages on a phone and check whether the offer, price, or service coverage fits that market. If your team manages several outlets, check the local profile and location page together. Multi-location SEO guide

What to check when a new view comes back empty
Start with the same property in Search Console and run a familiar web query for a completed date range. If that returns clicks, make one change to the request at a time. Switch the search type, apply one country or device filter, or add the branded split. Keep the same date range so you can tell which change removed the rows.
An empty branded report needs its own check. Confirm you use a top-level property that can access the split in the Search Console interface. A subdomain or a URL-prefix property at a path may still return normal web data, even when classification is unavailable. Test dates from February 21, 2026 onward. If you see branded and non-branded data in the interface but the connector returns none, compare the connector request with the API field names and values. Google’s branded filter eligibility
If visual search returns no rows, check the same dates under the web multimodal search type in Search Console. Confirm the property includes the pages you expected and remove a narrow device or country filter for the check. If the unfiltered view has data, add the filters back in order. One mobile-only export can conceal desktop data for the full property.
Agree on how the dashboard shows the result before it feeds a weekly alert. We’d mark periods before coverage as unavailable. We’d mark a view with no rows as having no reported data until we check its scope and eligibility. Reserve zero for a measured result. If a whole property falls off the report, review the import and permissions before asking anyone to change a page.
Keep AI visibility and visits in their own reports
Google’s dedicated Generative AI performance report shows impressions for AI search features such as AI Overviews and AI Mode. The November Search Analytics API announcement covers brand classification, multimodal web search, and country or device filter lists. Use the dedicated AI report for AI impressions and the new API options for the search slices they describe. Google’s AI report explanation
Google already includes activity from its AI features in overall Search performance. Treat the dedicated impression count as a view into that activity. Adding it to total search impressions would inflate the total. The dedicated report can tell you which pages appear in AI search and where. It cannot give you a separate click or conversion count for those appearances. Google’s AI report launch · Our Search Console AI reporting guide
Check the data notices before you connect a change in the AI chart to a site release. Google documented a logging error that lowered impressions in the Search generative AI report for November 9 through 11, 2026. If your graph drops across those dates, mark the known issue and check your other views before asking a writer to change the page. Google’s data anomaly log
Use analytics to see what people did after they reached your site. Use saved forms or orders to check business outcomes. For a lead form, confirm that the submission reached the place your team uses to follow up. An increase in impressions can justify a closer look at the page. A saved enquiry gives the sales team something to act on. Lead tracking guide
Compare the same landing pages and periods when you put Search Console and GA4 beside each other. Search Console counts a click in Google Search. GA4 counts sessions under its own rules when it receives activity from your site. Different tags, reporting dates, or attribution can make the numbers differ. Compare the direction of the two series and check why they diverge before using them to explain a change in enquiries. Google’s guide to comparing Search Console and Analytics
How we’d change the first dashboard
Keep the current web row as the reference. Run the new requests next to it with the same property, date range and market definitions, then add views that someone will use. A good report tells the team which page to inspect or experiment to run. You can leave an empty tile out.
- Save a completed baseline. Start with a closed reporting period and store its request, filters, totals and export date. Check it against Search Console before you use it to judge changes.
- Pilot one new view. Add non-branded clicks for discovery, multimodal pages for visual shopping, or grouped country and device reporting for regional work. Keep the distinction between a verified zero and missing or ineligible data.
- Check how the request groups data. A property-level total and a sum of top page or query rows can differ. Google documents that the API returns top rows and can omit some data. Use the same aggregation on both sides of a comparison. Google’s Search Analytics API limits
- Write the next page decision. Note the URL, the buyer question and the change you’d test. Leave the existing report definition in place until the new view earns a spot beside it.
If you work on a site move or redesign at the same time, record the release date and keep a copy of the old landing paths. That gives you a way to spot a redirect, removed page or changed tracking tag that could explain the numbers. SEO migration checklist

Which view should you build first?
We’d start with one search view that matches how the business earns revenue. For B2B, that might be non-branded clicks to a small set of service and pricing pages. For a parts seller, it could be visual searches bringing shoppers to pages with fitting data and direct links to products. Give that view its own baseline and report what happened on the pages after people arrived.
If your team spends more time explaining discrepancies than fixing pages, pull one old export, one new export, and the landing page that moved. Compare the report definitions before you compare the chart. If you need help connecting the search question to a page and its next action, bring that example to an SEO, GEO and AEO audit.
FAQ
What changed in the Search Console API in November 2026?
On November 16, Google brought three existing Performance report features to the Search Analytics API: branded query classification, web multimodal search reporting, and lists of countries or devices as filters. Site teams can now pull those views into scheduled reporting. Each view needs a property, date window, and filter definition.
How do I pull non-branded clicks from the Search Console API?
Use the brandedClassification dimension as a filter with the equals operator and the value NON_BRANDED. You can also group by that dimension for eligible properties. Run query-text filters separately. Google lists February 21, 2026 as the start date for available classification data in the API.
What is web multimodal search in Search Console?
It covers web searches that use image inputs, including Google Lens, Circle to Search on Android, and image uploads in Google Search. Request type: webMultimodal in Search Analytics. Keep the view separate from the image search type, which represents results from Google’s Image tab.
Can I filter several countries and devices in one request?
Yes. Use filterLists inside dimensionFilterGroups to give Search Analytics a list of exact country or device values. Use one list per dimension. Add country and device as grouping dimensions if you want a breakdown. Keep the same dimension out of the single-value filter list in that request.
Is the Generative AI performance report part of this API update?
The November release announces web multimodal search, brand classification, and lists for country and device filters. It does not announce a new dedicated AI Overview or AI Mode API report. Use Search Console’s Generative AI performance report for separate AI impressions, and keep the overall Google Search totals as their own figures.
You're All Set!
We have your request.
Expect a reply from our team within 24 hours. Want to talk sooner? Pick a time below.
Or call us at +1 (914) 297-6638


