Search Console Reporting: A Complete Guide

A third of all Search Console calls on Windsor.ai come through Claude and ChatGPT, more than any other connector on the platform. Search Console is also almost never pulled alone: most teams pull it alongside GA4 or Google Ads in the same week, joining organic performance with on-site behavior or paid spend rather than reading it in isolation.

Pull query, clicks, impressions, ctr, and position for my Search
Console property over the last 30 days, sorted by clicks.

Query-level performance

query, clicks, impressions, ctr, and position together are the single most-pulled combination on the connector. The rule worth stating plainly: position should be read per query, weighted by impressions, never as a page’s single averaged position across every query it ranks for. A page’s overall average is diluted by every long-tail query it barely competes on, which hides real movement on the queries that actually matter.

Page-level performance and directory roll-ups

page and pagepath give page-level detail; the pathlevel1 through pathlevel4 fields let you roll performance up by URL directory instead of reading one page at a time, useful for spotting which section of a site is gaining or losing visibility as a whole.

Cannibalization

Two pages competing for the same queries show up as one page drawing the majority of its own impressions from queries the other page already outranks it on. This is exactly the method Windsor’s SEO Director runs on windsor.ai’s own Search Console data:

Which of our page pairs have one page drawing 80%+ of its own impressions
from non-branded queries it shares with another page, each query with a
minimum of 30 impressions over the last 30 days?

See How I Catch Keyword Cannibalization with Search Console and Claude for the full method, including why a GA4 engagement check and a crawl-date check both come before any redirect decision.

Branded versus non-branded

branded_vs_nonbranded is one of the most-requested fields on the connector, ahead of country, device, and most sitemap fields. It separates queries that already know your brand name from queries where you’re winning on the content itself; the second group is the one that shows whether SEO is bringing in new demand rather than just capturing search traffic you’d get anyway. words_in_query is a useful companion, since branded queries and short head terms behave very differently from long-tail, non-branded ones.

Content update timing

Search Console has no crawl-date field; Performance data tells you what happened, not when a page was last crawled. A before/after comparison on a page you just edited is only valid once Google has recrawled it, otherwise you’re comparing old rankings to old rankings and calling it a result. The include_fresh_data option pulls the most recent, not-yet-finalized data; Search Console’s own numbers typically take 2 to 3 days to settle, so a report built on the most recent couple of days can still shift under you.

Search Console with GA4

A large majority of Search Console accounts also pull GA4 in the same week, the most common cross-connector pairing for this data. Joining the two on URL, organic queries alongside on-site engagement, is the data behind the cannibalization method above and most of the other checks on this page. See GA4 Reporting: A Complete Guide.

Search Console with Google Ads

Nearly half of Search Console accounts also pull Google Ads in the same week, comparing paid and organic performance on the same queries rather than reading the two platforms separately. See Google Ads Reporting and Analytics: A Complete Guide.

Sitemaps monitoring

submitted, errors, warnings, and last_downloaded are the only technical, non-performance data the connector has; Search Console’s Performance data has no crawl or indexing information beyond what the sitemap report itself tracks.

SEO reporting for clients

For the full report skeleton built from these same fields, one section per job, see the SEO Report Template.

Rank tracking from Search Console

position tracked daily turns into a rank-tracking history without a dedicated rank tracker. See the Free Google Keyword Rank Tracking Looker Studio Dashboard for the scheduled version.

MCP and AI assistants

Search Console has the highest AI-assistant share of any connector on Windsor.ai. See Google Search Console MCP for AI Insights to connect it to Claude, ChatGPT, or Copilot.

Using the raw API

For the Search Analytics API’s own row limits, the filter and date errors that actually show up in real usage, and the separate URL Inspection API that returns crawl date, see the Google Search Console API Guide.