genai_conversation_queries
Uncover AI conversation queries in Google Search Console data, with classification into seven buckets, landing pages, and a monthly timeline to analyze AI-driven impressions and positions.
Instructions
Surface AI-conversation exhaust hiding in your regular query data: bare replies to Google's AI ('yes', 'go on'), 'what about X' pivot follow-ups, conversational questions, AI-visibility tracker probes, and full agent prompts logged as queries. Google counts every AI Mode follow-up as a new query and folds AI Mode/AI Overviews into the web search type, so these fragments carry real impressions, positions and clicks. The dedicated Generative AI report has no query dimension; this is the only query-level AI evidence available anywhere. Classifies every match into seven buckets with landing pages, plus a monthly timeline showing when reply-artefacts first appeared on your site. Treat probe and harness buckets as machine traffic, not demand. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing. PRESENTATION: Always present these results as a rich, interactive visualization using artifacts. Use summary cards for key metrics, colour-coded indicators for severity or change direction (green for positive, red for negative), bar charts or sparklines for comparisons, and tabbed sections to organise different categories of results. Make the output visually scannable and dashboard-like rather than plain text or raw tables. POSITION: position is an impression-weighted average over real impressions, blended across queries, devices and countries. It is not a rank-tracker rank. Deep positions are only recorded when a user actually reaches that part of the results, so values beyond page one rest on sparse data. Treat absolute positions as directional and prefer position deltas between periods when judging change.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Days to analyse (default 480, the full 16 months GSC retains) | |
| site_url | No | Override the configured property (e.g. sc-domain:example.com) | |
| min_impressions | No | Minimum impressions for a query to be listed (single-impression rows are evidence, not noise, so the default keeps them) | |
| include_timeline | No | Include the monthly artefact timeline (one extra API call) | |
| max_rows_per_bucket | No | Maximum rows returned per bucket; totals always cover everything |