Search Console data, read correctly

Average position is not a rank tracker. Search Console records the topmost position your property or page occupied for an impression, then averages those values. Position 1 is the topmost position in the results. If your site appeared at positions 2, 4 and 6 for one query, the recorded position is 2, not 4.

Aggregation matters. When data is grouped by property, impressions and clicks are counted once per query and the topmost position of the property is used. When grouped by page, each URL is counted separately. That is why CTR and average position can look better in a property-level chart than in a page-level table. Position is only recorded when there was an impression; a dash means no position was recorded, not position zero.

A Search Console click is a click from a Google Search result to your site. A session is a period of activity measured by an analytics tool. Google documents several reasons the numbers differ: Search Console uses Pacific Time, reports the Google-selected canonical URL, includes non-HTML results and does not necessarily filter bots; analytics depends on JavaScript, consent, redirects and its own attribution model. A missing tag or a cookie banner can lower sessions without changing clicks.

Compare trends rather than exact totals. If clicks are stable and sessions fall, look at tracking, consent or redirects before assuming a ranking loss.

The Performance report supports custom regular expression filters on queries and pages. Search Console uses RE2 syntax, matches anywhere in the string by default, and is case-insensitive unless you prepend (?-i). Anchor with ^ and $ when you need an exact prefix or suffix, and use | for alternatives.

Useful patterns include grouping brand misspellings (brand|brandname|brand name), isolating a directory (^https://example.com/blog/), or finding question queries (what|how|when|why). The filter also supports a negative match. Keep expressions small enough to read; a filter that excludes too much can hide the pages you meant to inspect.

The official Looker Studio (formerly Data Studio) connector reads Search Console data through two aggregation tables: Site Impression and URL Impression. Pick one per data source; to show both side by side, create two sources. The connector exposes search type as a parameter, and query rows can be blank because Google withholds some queries for privacy.

Google's connector page also points to a template gallery if you want a starting dashboard rather than a blank report. For recurring reporting, connect the same property and date range every time, label the timezone, and separate Search Console metrics from analytics metrics. If you need every query rather than the top rows, use Search Console bulk export or the API instead of a dashboard table.

Search Console omits some queries to protect privacy, especially rare or sensitive searches. The table shows up to 1,000 rows, and the API returns top rows rather than every row. The report also keeps a limited history; Search Console data is available for the last 16 months. These are product limits, not a sign that your property is broken.

Bulk export is the right tool when you need the full set of rows for analysis. For day-to-day decisions, work with the visible trends and treat the missing long tail as missing, not as zero.

The newest days can be preliminary. The chart marks preliminary data with a dotted line, and the last updated date tells you the last day with data. Collected data is usually available in two to three days. GA4's Search Console integration notes that data can take 48 hours to appear there, and Search Console keeps 16 months of history.

If the date range includes today, do not compare it with a complete day. Check the data status first, then the property, the timezone (Pacific Time outside the 24-hour view), and whether a filter is hiding rows. A reporting lag is normal; a permanent flat line is not.