Site Impression vs URL Impression in Looker Studio

When you connect Google Search Console to Looker Studio, the connector asks you to choose between two tables: Site Impression and URL Impression. The labels can make this look like a minor setup choice, but each option represents a different way of aggregating the same search performance data.

Site Impression groups performance at property level. URL Impression groups it at page level. This affects how impressions, clicks, click-through rate and average position are calculated when more than one page from your site appears for the same query.

The right choice therefore depends on the question your dashboard needs to answer. Site Impression is better for understanding the overall search visibility of the property. URL Impression is required when the analysis needs to identify which landing pages earned that visibility.

Site Impression aggregates results by Search Console property. If two or more URLs from the same property appear on one results page for the same query, the property records one impression rather than a separate impression for every URL.

Position is based on the highest-ranking result from the property. If your pages appear in positions two, five and eight, the property-level position for that appearance is two. This makes Site Impression the closest choice when you want headline metrics that align with the property-level chart in the Search Console Performance report.

Because the page is not the unit of aggregation, this table is not designed to answer landing-page questions. It is useful for query, country, device, date and property-level trend analysis where the main concern is how the site performed as a whole.

URL Impression aggregates performance by canonical page. When several pages from the property appear in the same set of results, each unique URL can record its own impression, click and position.

This table exposes the landing-page dimension, making it possible to evaluate individual pages, templates, directories and content groups. It is the practical choice for finding pages that receive many impressions but few clicks, comparing branded and non-branded landing pages, or measuring the effect of page-level SEO changes.

Search Console generally assigns performance to the canonical URL selected by Google. The URL shown in the data may therefore differ from the exact URL a user saw or the URL you expected to receive credit.

Both tables provide the familiar Search Console metrics: clicks, impressions, CTR and average position. The difference is the level at which those metrics are counted.

A common mistake is to place Site Impression and URL Impression scorecards next to each other and assume that one is wrong when the numbers differ. A difference can be expected because the two sources are answering different counting questions.

Imagine one search results page contains three URLs from the same property. At property level, that appearance can count as one impression and use the highest position. At page level, it can count as one impression for each of the three URLs, with a separate position assigned to each page.

This is why URL Impression totals can be higher and why CTR or average position can differ from Site Impression. The gap is not a Looker Studio calculation error. It is a consequence of property aggregation versus page aggregation.

Use Site Impression when the question begins with “How did the website perform?” Use URL Impression when it begins with “Which page performed?” That simple distinction solves most setup decisions.

A complete SEO dashboard may legitimately use both as separate data sources. The overview page can use Site Impression for property-level clicks, impressions, CTR, position and query trends. A landing-page section can use URL Impression for page tables, content groups and page-level opportunity analysis.

Create and clearly name two data sources if your report needs both levels of detail. Names such as “GSC — Site Impression — Web” and “GSC — URL Impression — Web” make the aggregation visible to anyone editing the report later.

Keep the property-level KPIs and page-level tables in clearly labelled sections. Avoid reusing a scorecard without checking which source powers it, and do not expect a filter based on Landing Page to control charts using Site Impression because that dimension does not exist at property level.

Site Impression and URL Impression are not interchangeable versions of the same table. Site Impression explains how the property appeared in search. URL Impression explains how individual pages appeared.

Choosing the correct aggregation makes a Looker Studio dashboard easier to validate and prevents false discrepancy investigations. Start with the business question, match it to the appropriate level of detail, and label the source clearly so the meaning of every metric remains visible.