Why can’t I filter Search Console data by landing page?

You can’t filter by landing page because your report uses the Site Impression table of the Search Console connector – the Landing Page field only exists in the URL Impression table. In Looker Studio, since April 2026 called Data Studio again, a data source can use only one of the two tables, so you add a second data source with URL Impression to the same report and filter that one.

Google dates the rebrand to 16 April 2026 in its release notes; old lookerstudio.google.com links redirect to datastudio.google.com, and existing reports keep working. Expect one side effect of the second table: its totals never match the first one exactly. If long query tables also seem to get cut off, read why a report seems to stop at 10,000 rows.

Site Impression or URL Impression: what is the difference?

Search Console aggregates performance data in two ways, and the Search Console connector mirrors that with two tables. You choose one in the Tables panel when you connect a property.

• Site Impression aggregates data by property and query. It covers web, image, video and news search.
• URL Impression reports each URL separately and adds the Landing Page dimension. It also covers Discover and Google News. Google built its own Search Console dashboard on this table.
• To see both side by side, Google’s answer is two data sources in one report, not one source that does everything.

How do you filter by landing page in Data Studio?

1. Open the report in edit mode and click Add data in the toolbar.
2. Choose the Search Console connector, select your property under Sites, then URL Impression under Tables and web as search type. Add the data source to the report.
3. Select the table or chart, open the Setup tab and switch its data source to the new URL Impression source. Add Landing Page as a dimension.
4. For a fixed filter, use Add a filter in the Setup tab: Include · Landing Page · Contains · /blog/. For a filter your viewers can change, insert a drop-down list via Add a control and set its control field to Landing Page.
5. Keep your Site Impression charts for site totals and query trends.

Landing Page holds the full URL including protocol and domain. Google’s dashboard guide shortens it with a calculated field that uses REGEXP_EXTRACT to cut off the domain, which makes tables much easier to read.

Why do the totals no longer match?

Search Console counts differently depending on the aggregation, as Google’s data documentation explains:

• By property (Site Impression): if two of your pages appear for the same query, that is one impression. Clicks on two of your results from one search count once, and position is your top result.
• By page (URL Impression): every URL counts separately, so impressions and clicks are usually higher, while CTR and position look worse.
• Anonymized queries: queries not issued by more than a few dozen users over two to three months are never listed (Search Central blog). They are part of the totals but disappear as soon as you add the Query dimension or a query filter.

Our own property: 223, 225 or 10 clicks?

We pulled the same 90 days for 1hold.de (23 July to 20 October 2026, web search) from the Search Console API in three ways:

• Aggregated by property, as in Site Impression: 223 clicks and 51,526 impressions.
• Aggregated by page, as in URL Impression: 225 clicks and 53,111 impressions across 262 pages.
• Only rows with a visible query: 1,053 queries with 10 clicks and 26,683 impressions.

The page view adds 2 clicks and 1,585 impressions because several of our FAQ pages appear for the same search. The query view is the real surprise: 213 of 223 clicks, 95.5 %, came from queries Search Console does not show. Our FAQ pages answer long, specific questions, which most likely fall below the privacy threshold. A table with Query and Landing Page side by side had 1,196 rows and the same 10 clicks. For page analysis we therefore read clicks per landing page without the query dimension.

Build landing-page reports on URL Impression and site totals on Site Impression, and label every scorecard with its aggregation. Never add up clicks from both tables, and never compare the sum of query rows with the site total – on a small site most clicks can come from anonymized queries.

Which three mistakes happen in landing-page reports?

• Adding both tables together. Clicks from a Site Impression source and a URL Impression source are not additive, not even in a blend.
• Filtering by query and page at once. Anonymized queries drop out, so the result falls far below the page total. Google’s troubleshooting guide warns that “match” and “does not match” totals may not add up to the unfiltered total.
• The wrong search type. Discover and Google News exist only in URL Impression; Site Impression stops at web, image, video and news.

Sources

• Data Studio Help: Connect to Search Console
• Search Console Help: Performance data aggregation
• Google Search Central Blog: Search Console monitoring dashboard

Need a Search Console report that keeps property and page data apart? We build Data Studio dashboards on Search Console, GA4 and Google Ads and document which number means what. Book a free initial call or see our SEM strategy and analysis services.