How to track AI Agent Search in YG3

AI Agent Search is how people find you when Google answers with AI Overviews or AI Mode — not only classic blue links. YG3 tracks that traffic from Google Search Console’s Generative AI performance report so agencies can see which pages earn AI impressions and how that changes over time.

What AI Agent Search means in YG3

Classic Search Console organic rows cover traditional results. Generative AI performance covers impressions from AI-generated answers (AI Overviews, AI Mode, and related surfaces Google groups under that report). Importing that CSV into YG3 AI Search is how you measure AI Agent Search alongside organic queries and competitive standing.

Before you start

You need access to the site’s Google Search Console property and a client open in YG3 with AI Search. Export from the same property you care about (for YG3’s own workspace, that is typically the marketing site — www.yg3.ai — not the editorial subdomain).

Step-by-step

In Google Search Console, open Generative AI performance for the property.
Export a CSV. Prefer an export that includes Date and Page (and Impressions) so YG3 can chart and rank URLs.
In YG3, open the client → AI Search → Google Search.
Click Import data on the AI impressions tile, or scroll to the AI Agent Search import panel and upload the CSV.
Confirm the tile shows AI impressions and that last import updated. Top Generative AI pages appear in the import panel.

What YG3 stores

Each import upserts Generative AI performance rows (date, page, country, device, impressions) for that client. The AI Search dashboard sums impressions in the selected window, draws a small trend from dates in the file, and lists top pages by AI impressions. Re-importing the same keys updates counts; it does not invent SerpApi or AI Overview scrapes — this path is Search Console only.

Troubleshooting

If import fails, check that the CSV has an Impressions column and that dates parse as YYYY-MM-DD or M/D/YYYY. Empty files or exports without impressions are rejected. If numbers look wrong, confirm you exported the correct property and date range, then import again.