Search Console AI report: what indie developers can measure
What indie developers can measure in Search Console, how Google reports AI search traffic, and where attribution and visibility claims stop.
If you are looking for a Search Console AI report for your game's website, start with what Google actually documents. Its guidance puts visits from AI Overviews and AI Mode in the Search results Performance report, under the Web search type. That is not a separate measurement of how many people discovered or bought your game through an AI answer.
Start with the report you actually have
Google's AI features guidance says that AI Overviews and AI Mode are included in overall search traffic. A page needs to be indexed and eligible for a snippet to qualify as a supporting link; eligibility does not guarantee inclusion.
The Search results Performance report lets you examine clicks, impressions, CTR and average position, with filters such as page, query, country and device. Record the dates, search type and filters when saving a comparison. Otherwise two screenshots can describe different things while looking comparable.
Ask a question about your game, not a dashboard score
For a small studio, I would begin with one useful question: can someone searching for the game name find the correct page, and does that page give them an obvious next step? Filter the game page, look at the queries that appear, and check whether the name is being confused with something else.
Then inspect the page itself. Can a player understand the mechanic? Are the platforms and release status accurate? Does the demo or store link work? An impression count cannot answer those questions for you.
A visible page is not a sale
Search impressions, clicks to your website, website visits, store visits, wishlists and purchases describe different stages. Keep them in separate columns. A change in one does not establish a change in the next, and a mention in an AI answer may produce no measurable visit.
I would not label the entire Web total “AI traffic.” Nor would I infer that an empty or missing feature-specific view proves that no AI answer has mentioned the game. Only claim the scope that the report and your saved export actually support.
For a comparison, use equal windows and the same filters. Note a demo release, festival, site edit or press appearance beside the dates. If all of those change together, a rising line cannot identify which one caused it.
Check controls separately from reporting
Google documents Googlebot and the usual search preview controls, including nosnippet, data-nosnippet, max-snippet and noindex, for managing content in Search. Google-Extended concerns other Google systems; it is not a universal switch for removing a page from AI answers in Search. Read the current documentation before changing access: a control can affect ordinary search visibility as well.
This article does not change your site's crawler settings. For an indie game page that you want players to find, decide what should be public first. Keep non-public builds, credentials and private material behind real access controls.
A small next step
Save one baseline for the main game page, with its dates and filters. Check the page and its store link. Pick one improvement that makes the game easier to understand, record when you made it, and compare again after a useful observation window. If the data are too sparse, say that instead of making a growth claim.
My website-not-showing-up guide covers the earlier diagnosis. The AI visibility guide separates mentions, visits and the decisions they can actually inform.
Sources
- Google Search Central: AI features and your website, checked 27 October 2026.
- Search Console Help: Search results Performance report, checked 27 October 2026.