Why don’t my Search Console clicks match Google Analytics organic clicks?
The two tools measure different moments, so the totals rarely line up. Search Console counts a click on a result in Google Search — the moment a user leaves the results page toward the property. Google Analytics 4 counts sessions and landings recorded by on-site tracking after the user arrives. Several differences follow from that gap:- A Search Console click is counted even when the page never fully loads or the user leaves immediately, so no Analytics session is recorded.
- Search Console anonymizes and omits low-volume queries for privacy, so some clicks are not attributable to a specific row.
- The two products use different time zones and different channel definitions, so day boundaries and the “organic” grouping do not align exactly.
Why does a query + page + country breakdown show fewer rows than I expect?
Combining several breakdowns at once (for example query, page, and country together) raises the query load, and Search Console aggregates or drops some rows to protect privacy and manage volume. The result is a report that looks thinner than a single-breakdown view of the same date range. There is also a hard ceiling: the connector caps results at 50,000 rows per property per day for a given search type, fetched in two pages of up to 25,000 rows each. When that ceiling is reached, the query is treated as over-limit and no partial rows are returned rather than a truncated set. For more complete results, narrowing the date range or reducing the number of breakdowns usually helps. See the data reference limitations for the full list of caps.Why is my CTR showing a dash?
CTR is click-through rate — clicks divided by impressions. When a row has zero impressions, dividing by zero has no defined value, so the row shows a dash (-) instead of a number. CTR is also recomputed across aggregated rows rather than averaged from per-row rates. Adriel fetches clicks and impressions whenever CTR is requested and derives the rate from those totals, which keeps subtotals and grand totals accurate. A dash on an aggregate row means the underlying impressions summed to zero for that grouping.Why can’t I add Search Appearance alongside another breakdown?
Search appearance is only available on its own. It can be paired with a date breakdown (such as Daily or Weekly), but it cannot be combined with another search-performance breakdown like Query, Page, Device, or Country. Requesting it as a second breakdown returns an error prompting a different breakdown selection, and no data loads. To analyze search appearance, it should be the single non-date breakdown on the widget. To slice a different breakdown, remove search appearance first.Why do my most recent days’ numbers keep changing?
Search Console finalizes its data after a short processing delay — typically two to three days. Because the connector reads live from Search Console each time a dashboard loads, the most recent one to three days reflect Search Console’s current processing state and may still shift as those days settle. This is expected rather than a sync problem. For how data freshness works overall, see the data reference.Related
Data reference
Metrics, breakdowns, refresh strategy, and limits for Google Search Console.
How to connect Google Search Console
Steps to connect a verified property as a data source.
Google Analytics 4 data reference
On-site web and app analytics, for comparison with search performance.
Refresh strategies
How Adriel fetches and refreshes data across connectors.