Knowledge base v2.13.0 · Community edition · data through 2 October 2026
Topic · Search Console
A community talk showed an agency workflow that exports Search Console data to BigQuery and lets an LLM agent query it. Google's docs confirm the limits behind it: the interface exports only 1,000 rows, the API and the Looker Studio connector up to 50,000 rows per day per site per search type, and only the bulk export avoids the daily cap. The branded versus non-branded filter is made by an AI-assisted system and works only on top-level properties with enough data, and anonymized queries are left out whenever a filter is applied, so filtered rows do not add up to the chart totals. The agency's use cases included reporting content refreshes, finding bad cannibalization and running SEO experiments that start from a hypothesis. Author’s view: tell the LLM about these gaps and spot-check the branded split before trusting its sums. The agency also combines Search Console data, LLM referral traffic from GA4 and the generative AI report in one prompt to compare classic and AI performance, although that report, launched in June 2026 as Day 1 noted, has no click or query data. Day 1's first lightning session, captured by a second recording, showed the same risks from the practitioner side: a chatbot called an average position moving from 8 to 9 an improvement, although position 1 is the top (as Search Console Help defines it), so a community speaker advised giving an LLM fixed metric definitions; another automated monthly reports through the Search Console API, which needs a Google Cloud project and OAuth2 credentials and is free of charge but subject to usage limits. Day 1 also showed the Crawl Stats report's split of crawl requests by response, file type and purpose (discovery versus refresh), with drill-down to the problem URLs. In the Day 1 Q&A a Google panelist expected more AI reporting to launch, without a timeline or a promise, and Google said it should not simply mirror classic results and that AI query data is hard to provide because AI questions do not map back to keywords and the data would have to be grouped to protect privacy while staying useful; it knew of no plans to add crawl stats to the API, a completely new part, whereas a variation of the Performance report would be easier, and said the Search Relations team talks with the Search Console team about the API more than before, partly because with so many vibe-coded systems around it is very easy to say 'use the Search Console API', and annoying when Search Console has no API for that. On Day 2 a community speaker noted that publishers can verify their social accounts in Search Console to track content repurposed for social platforms. Author’s view: since the API itself costs nothing, the cost check before automating is about usage limits and the paid parts of the pipeline, such as storage and model calls.
Things in this topic 7
Counts are claims that name the thing. All things
What to do
A community speaker's example of an LLM error on Search Console data: a chatbot called an average position that went from 8 to 9 an improvement, although position 1 is the top, so the move from 8 to 9 is a decline.
Speaker Rafael KovashikawaIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript
Give an LLM your metric definitions as fixed, protected context, for example that position 1 is the top, and leave nothing for the model to guess, a community speaker advised.
Speaker Rafael KovashikawaIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript
A community speaker who is not a developer automated monthly SEO reports with Python in Visual Studio Code, using Claude and ChatGPT as coding partners and Google Cloud for access to the Search Console API.
Speaker Kira BreuerIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript
Before writing code to pull Search Console data for one property, check which data you actually need, what the API can provide and what the API costs, a community speaker advised.
Speaker Kira BreuerIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript
Pulling Search Console data through the API required setting up a Google Cloud account to get API access, a community speaker said.
Speaker Kira BreuerIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript
The resulting monthly report showed Search Console data on one side and an AI-written summary of what happened that month on the other; an in-house AI specialist built the dashboard from the SEO manager's code.
Speaker Kira BreuerIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript
To check whether a site has a crawl budget problem, use Search Console's crawl report (Crawl Stats), which breaks crawl requests down by response and by file type and shows crawl problems Google finds.
Speaker Cherry PrommawinIn Day 1, 16:00 · How Google thinks about crawl budgetEvidence transcript
Used byrequirement DEV-MON-04glossary term Crawl Stats report
The file-type breakdown of crawl requests in Search Console is useful for spotting anomalies, such as most crawling going to images on a site that has no images worth crawling.
Speaker Cherry PrommawinIn Day 1, 16:00 · How Google thinks about crawl budgetEvidence transcript
Used byrequirement DEV-MON-04
Search Console's crawl data separates discovery (fetches of URLs Google has not seen before) from refresh (fetches of known URLs), and lets you drill down to the problematic URLs.
Speaker Cherry PrommawinIn Day 1, 16:00 · How Google thinks about crawl budgetEvidence transcript
Used byrequirements DEV-MON-04, DEV-MON-11glossary term Crawl Stats report
An audience member asked what changes to expect in Search Console's reporting on Google's AI features.
From the audienceIn Day 1, 16:35 · Q&AEvidence transcript
A Google panelist said he expected more AI reporting to launch in Search Console, without a timeline or a promise, because many people at Google care about giving site owners the information to understand and adapt to what happens in Search.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
Google said reporting on AI features should not simply mirror classic search results, because users get more information before they click and interact with pages differently, so it first has to work out which data would be useful and actionable.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
Query data for AI features is hard to provide because people ask AI very different kinds of questions that do not map back to keywords as in classic search, and the data would have to be grouped to protect privacy while staying useful.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
An audience member asked whether and when crawl stats will be added to the Search Console API.
From the audienceIn Day 1, 16:35 · Q&AEvidence transcript
Google said it knew of no plans to add crawl stats to the Search Console API, because that would be a completely new part of the API.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
A Google panelist said adding a report that is a variation of the Performance report to the Search Console API would be easier than adding crawl stats, because the Performance report is already in the API.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
Google's Search Relations team talks with the Search Console team about the API more than before, partly because with so many vibe-coded systems around it is very easy to just say 'use the Search Console API to do something', and it is annoying when Search Console has no API for that.
Speaker not identifiedIn Day 1, 16:35 · Q&AEvidence transcript
Search Console Help defines position as the position of a link on Google, where 1 is the topmost position, and says the Performance report shows the topmost position a property's link occupied, averaged across all queries.
Publisher Google Search Console HelpAnnotates Day 1, 13:10 · Lightning session A: Automation and AI
To use the Search Console API you need a Google Account with Search Console permission on the property, a project in the Google API Console and OAuth2 credentials (all Search Console APIs except the Testing Tools API need OAuth2).
Publisher Google Search Console API documentationAnnotates Day 1, 13:10 · Lightning session A: Automation and AI
Google states that all use of the Search Console API is free of charge but subject to usage limits.
Publisher Google Search Console API documentationAnnotates Day 1, 13:10 · Lightning session A: Automation and AI
Author's view: the Search Console API itself costs nothing, so the cost check advised on stage before automating reports is about the API's usage limits and the paid parts of the pipeline, such as storage and AI model calls.
Author Ibrahim AnjroAnnotates Day 1, 13:10 · Lightning session A: Automation and AI
After a domain consolidation went live, a community speaker's team checked Search Console every day, ran full site crawls and compared the numbers with the pre-migration baseline for months.
Speaker Martyna AğanoğluIn Day 2, 12:05 · Lightning session E: Managing Duplicates and Site MovesEvidence transcript
Used byrequirement DEV-CAN-09
A community slide (Workflow 1) said the first step is to apply the filters you need, even natively in Search Console, for example branded versus non-branded queries, with clicks and impressions.
“Apply the filters you need, even natively in GSC. For example branded vs non-branded, with clicks and impressions.”
Wording checked against the slide or recording
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence slide photo, transcript
A community slide said the Search Console interface export is limited to 1,000 rows.
“The UI export is limited to 1,000 rows.”
Wording checked against the slide or recording
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence slide photo
Used byrequirement DEV-MON-08
A community slide said the Search Console bulk data export to BigQuery gives the most complete query dataset available, with anonymized queries excluded.
“The bulk export to BigQuery gives the most complete query dataset available - anonymized queries excluded.”
Wording checked against the slide or recording
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence slide photo
Used byrequirement DEV-MON-08glossary term Search Console bulk data export
The community workflow's third step feeds the exported Search Console dataset into the agency's LLM agent, which queries the dataset and returns the evidence rather than a sample.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence slide photo, transcript
Nik Vujic's slide said no agent is needed to start: pull the Search Console data, import it into any LLM and query it in conversation; his agency built its agent to have everything in one place.
“No agent needed to start: pull the data and import it into the LLM of your choice, and talk with it.”
Wording checked against the slide or recording
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence slide photo, transcript
In a community lightning talk, agency founder Nik Vujic presented how his agency feeds Search Console and GA4 data to an LLM agent to support decisions for its clients.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic called Google Search Console his favourite SEO tool, used alongside GA4, and said third-party SEO tools give only estimates, although they have some use cases.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic said it is super important to export all of a site's Search Console data, and his agency's workflow starts from Search Console's export to BigQuery.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Used byrequirement DEV-MON-08glossary term Search Console bulk data export
Nik Vujic recommended Looker Studio as a second way to get past Search Console's data limits.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic said his agency uses the Search Console data fed to an LLM in five use cases, the first being cross-comparing and following up different articles.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic said that after a page is published, the queries it appears for are the first thing to show up in Search Console, while clicks and impressions come much later.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
To report content refreshes on large sites, Nik Vujic's agency compares date ranges and has an LLM give the exact number of queries the content improved on, then reports that number to the client.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic said analysing Search Console query data with an LLM also helped his agency spot developer mistakes, such as unwanted pages that got indexed, which can also be found in Search Console itself.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic said some keyword cannibalization is fine because it is logical, but for bad cannibalization his agency groups all of an article's Search Console queries and then decides whether to redirect the pages or rewrite and split the content.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic advised starting every SEO experiment with a hypothesis, for example a bulk change to one page element across a group of pages, and using an LLM to report the group's Search Console data, for example click-through rate, for the test.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Nik Vujic's agency puts Search Console data, LLM referral traffic from GA4 and the data from Search Console's generative AI report into one LLM prompt to compare a client's performance in classic search and in AI features.
Speaker Nik VujicIn Day 3, 14:20 · Lightning session L: Understanding SERPs and your usersEvidence transcript
Google's launch post for Search Console's branded queries filter (20 November 2025) says the branded versus non-branded split is made by an internal AI-assisted system, not by a regular expression, and that some queries may occasionally be misidentified.
Publisher Search Central blog (20 November 2025, updated 11 March 2026)Annotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Used byglossary term Branded queries filter
A Search Central blog post on Search Console data limits (October 2022) says the interface exports at most 1,000 rows, while the Search Analytics API and the Looker Studio connector return up to 50,000 rows per day per site per search type.
Publisher Search Central blog (19 October 2022)Annotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Used byrequirement DEV-MON-08
Google's blog post on Search Console data limits says anonymized queries are always left out of the report tables but counted in chart totals unless you filter by query, and are left out whenever a filter is applied, so filtered rows do not add up to the chart totals.
Publisher Search Central blog (19 October 2022)Annotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Used byrequirement DEV-MON-08
Search Console's branded queries filter works only for top-level properties, not URL-path or subdomain properties, and only for sites with enough queries and impressions; Google made it available to all eligible sites on 11 March 2026.
Publisher Search Central blog (20 November 2025, updated 11 March 2026)Annotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Used byglossary term Branded queries filter
In the bulk export, 'anonymized queries excluded' means the query text, not the traffic: Google's table reference and query guidelines show those rows kept with an empty query field, often as the single most common 'query'. Tell an LLM to skip empty queries when ranking top queries, but keep them in totals.
Author Ibrahim AnjroAnnotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Used byrequirement DEV-MON-08
A query reaches Search Console's Performance report only through an impression, so queries cannot come before impressions; what rises first after a publish or refresh is the number of queries with a few impressions each, before total impressions and clicks grow noticeably.
Author Ibrahim AnjroAnnotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Because Google says anonymized queries are left out whenever a filter is applied, branded plus non-branded exports should not be expected to add up to the unfiltered chart totals; tell an LLM that sums filtered exports that the gap is expected, not missing data.
Author Ibrahim AnjroAnnotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Before feeding a branded versus non-branded split to an LLM, spot-check a sample of queries in each group, since Google's AI-assisted classification can misidentify queries; on URL-path or subdomain properties, where the filter is unavailable, a regex query filter is the fallback.
Author Ibrahim AnjroAnnotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Looker Studio lifts Search Console's 1,000-row interface limit but keeps the connector's cap of 50,000 rows per day per site per search type; only the bulk export to BigQuery is free of the daily row limit, so large sites that need every non-anonymized query should use it.
Author Ibrahim AnjroAnnotates Day 3, 14:20 · Lightning session L: Understanding SERPs and your users
Used byrequirement DEV-MON-08
Google called AI reporting in Search Console an evolving space and expects the generative AI report to get richer, with more information in the future.
In a community lightning talk, agency founder Nik Vujic presented how his agency feeds Search Console and GA4 data to an LLM agent to support decisions for its clients.
A community speaker who is not a developer automated monthly SEO reports with Python in Visual Studio Code, using Claude and ChatGPT as coding partners and Google Cloud for access to the Search Console API.
Google's launch post for Search Console's branded queries filter (20 November 2025) says the branded versus non-branded split is made by an internal AI-assisted system, not by a regular expression, and that some queries may occasionally be misidentified.
Google said query groups are not built by matching query text alone: deciding which queries belong in which group goes beyond simple text filtering.
The community workflow's third step feeds the exported Search Console dataset into the agency's LLM agent, which queries the dataset and returns the evidence rather than a sample.
An agency's automated monthly SEO report follows four simple steps: the data comes in, a script processes it, AI summarises it and the result goes onto a dashboard.
Nik Vujic's slide said no agent is needed to start: pull the Search Console data, import it into any LLM and query it in conversation; his agency built its agent to have everything in one place.
An agency's automated monthly SEO report follows four simple steps: the data comes in, a script processes it, AI summarises it and the result goes onto a dashboard.
Before feeding a branded versus non-branded split to an LLM, spot-check a sample of queries in each group, since Google's AI-assisted classification can misidentify queries; on URL-path or subdomain properties, where the filter is unavailable, a regex query filter is the fallback.
Review the filters and regexes that Search Console's AI-powered configuration proposes before trusting the numbers: Google's launch post calls the feature experimental, warns that AI can misinterpret requests, and limits it to the Search results Performance report (not Discover or News) and to configuration, not sorting or exporting.
Set up the Search Console bulk data export to BigQuery on large sites
Rests on 7 claims, 7 of them in this topic
Monitor Crawl stats and server logs for verified Googlebot traffic
Rests on 13 claims, 3 of them in this topic
Rests on 14 claims, 1 of them in this topic
Measure the time from publishing a URL to Googlebot's first crawl of it
Rests on 7 claims, 1 of them in this topic