Overview
Google AI is a tab in the Search section (Visibility → Search) focused on how Google’s AI features — AI Overviews and AI Mode — affect your search traffic. As Google answers more queries directly with AI, clicks to the open web fall even when your ranking doesn’t change. This tab helps you spot that erosion and act on it. It lives atapp.trysight.ai/visibility/ai-search and requires a connected Google Search Console property on a licensed site.
The tab has two sub-views:
- AI Overview risk — queries where Google is likely answering with an AI Overview and siphoning your clicks (inferred from your Search Console data).
- Imported AI impressions — Google’s official AI-surface impression numbers, brought in from a CSV export.
Google doesn’t expose AI Overview / AI Mode data through the Search Console API yet — the official report is impressions-only and UI-only. So Sight AI infers click loss from the GSC data you already sync, and lets you import the official numbers manually when you want them.
AI Overview risk
This is the default view. It surfaces queries where you rank well and get impressions, but your click-through rate has collapsed in a way that’s characteristic of an AI Overview eating the click.What you see
A summary strip shows the count of at-risk queries and the estimated clicks at risk this period. The table lists each at-risk query with:| Column | Meaning |
|---|---|
| Query + reason badge | The search term and why it’s flagged (see below) |
| Impressions | Impressions in the selected window |
| Position | Average Google position (it must actually rank to be flagged) |
| CTR now | Current click-through rate |
| Benchmark | The CTR we’d expect for this query (its own past CTR, or the expected CTR for its ranking) |
| Est. lost clicks | impressions × (benchmark CTR − current CTR) — your estimated click loss |
| Actions | Create article or Track as prompt |
Why a query is flagged
| Badge | What it means |
|---|---|
| CTR dropped vs prior period | The query’s CTR fell sharply (≥35%) versus the previous period while its ranking stayed roughly the same — a classic sign an AI Overview started intercepting clicks. |
| Low CTR for its ranking | The query ranks near the top (position ≤ 8) but earns far less than the typical CTR for that position — clicks are going somewhere other than your result. |
Acting on at-risk queries
Each row gives you two one-click moves:- Create article — open the agent pre-filled to write (or strengthen) content for that query. Stronger, more comprehensive content is the best defense against losing the click outright.
- Track as prompt — add the query to AI Visibility as a tracked prompt, so you can monitor whether AI assistants mention you for it. (Respects your site’s 500-prompt limit and runs an instant check.)
AI Overview risk rows are computed live from your GSC data — they’re not added to your Search Opportunities queue. Act on them right from this tab.
Imported AI impressions
Google’s Search Console UI has a Generative AI performance view that shows impressions on AI surfaces — but there’s no API for it. The Imported AI impressions sub-view lets you bring those official numbers into Sight AI via CSV so you can see them alongside your articles.How to import
Export from Google Search Console
In Search Console, open Performance → Generative AI, pick your date range, switch to the Pages tab, and export the CSV.
Open the import dialog
In Sight AI, go to Visibility → Search → Google AI → Imported AI impressions and click Import data.
Tracked prompt suggestions (in the background)
Separately from this tab, once your GSC history matures Sight AI periodically scans your top queries and suggests tracked prompts worth monitoring in AI Visibility. These appear as suggestions on Visibility → Prompts for you to accept — no action needed here.Related
- Search (Google) Section — the full GSC query/page/article tables
- What is AI Visibility? — track how AI assistants mention your brand
- Search Opportunities — content gaps, refreshes, interlinks, and rising pages
- Connect Google Search Console — required for this tab to have data