How to Connect Google Search Console to Looker Studio (Free Dashboard Guide)

The Google Search Console interface is genuinely useful, but it was built for spot-checks, not reporting. You can only see one date range at a time, comparisons are clunky, and the moment you try to export a Performance table you hit a hard ceiling of 1,000 rows. If you manage a site with thousands of queries and pages, that ceiling means most of your data never makes it onto your screen, let alone into a report you can share with a client or a colleague.

Looker Studio (the tool Google renamed from Data Studio in 2022) solves most of these problems for free. It connects directly to Search Console through an official connector, lets you visualize far more than 1,000 rows per table, and produces dashboards you can share with a link or schedule as a recurring email. Once it's set up, you stop logging into GSC to "go check the numbers" and instead open a single page laid out the way you want it.

This guide walks through connecting Google Search Console to Looker Studio from scratch, explains the two data source types the connector offers (and why the choice matters more than most tutorials admit), and shows you how to build the core charts a real SEO dashboard needs: traffic trends, top queries and pages, a position distribution, and a striking-distance table for quick wins. It also covers date and branded/non-branded filters, scheduled email reports, and the connector's real limitations so you don't trust numbers it can't actually give you.

Why use Looker Studio instead of the GSC interface

The Search Console UI is fine for a quick question. It becomes a bottleneck the moment you need anything repeatable. Looker Studio is worth the setup for a few concrete reasons:

• It's free. No paid tier is required for the Search Console connector — just a Google account and verified access to the property.
• It blows past the 1,000-row export limit. The GSC UI caps table exports at 1,000 rows; the connector returns far more, so your top-queries and top-pages tables can reflect the long tail. (For the mechanics of that cap, see our breakdown of the Google Search Console 1,000-row limit.)
• It's shareable. Send a view-only link and stakeholders see a live dashboard without touching your GSC account.
• It supports scheduled email reports. Looker Studio can email a PDF on a daily, weekly, or monthly cadence, killing the "can you pull last month's numbers?" loop.
• Comparisons and date ranges are first-class. Drop a date-range control on the page and viewers can switch periods or compare against the previous period without rebuilding anything.

The trade-off is that Looker Studio is a reporting layer, not a data warehouse. It still pulls from the same Search Console API, so it inherits GSC's retention window (roughly 16 months) and some of its sampling and row-limit behavior at the API level. We'll come back to those limits later, because pretending they don't exist is how dashboards end up lying to people.

What you need before you start

Three things, all free:

1. A Google account that has at least restricted access to the Search Console property (full or owner access is better and required for some metrics).
2. The property already verified in Google Search Console.
3. Access to Looker Studio (just sign in with the same Google account).

If you only need raw data rather than a visual dashboard, connecting through the API or a JSON export may fit better. Our guides on the Google Search Console API and exporting GSC data as JSON cover those paths.

Step 1: Connect the Search Console data source

1. Go to lookerstudio.google.com and sign in.
2. Click Create in the top-left, then choose Data source (you can also start from a blank report and add the source from inside it; starting with the data source first keeps things tidy).
3. In the connector gallery, find and select Search Console. This is Google's own connector, listed under "Google Connectors."
4. The first time you use it, click Authorize and grant Looker Studio access to your Search Console data.
5. Pick the property (site) you want to report on from the list.

At this point the connector asks you to make the single most important decision in this whole process: which table to use. This is the URL Impression vs Site Impression choice.

Step 2: Choose between URL Impression and Site Impression

The connector exposes two different tables for the same property. They are not interchangeable, and choosing the wrong one will quietly break some of your charts.

• Site Impression aggregates data at the property level. An impression means "your site appeared in the results for this query," counted once per search even if you ranked with multiple URLs. Because it's aggregated by site, it does not include the Landing Page (URL) dimension.
• URL Impression aggregates at the page level. It includes the Landing Page dimension and search-appearance breakdowns, but impressions and position are counted per URL, so totals can differ from the Site Impression table or the GSC UI's default view.

The practical rule: if a chart needs to break data down by page, use URL Impression. If a chart is about queries or sitewide totals, Site Impression is usually the cleaner match. Many people build two separate data sources from the same property so they can use the right one per chart.

| | Site Impression | URL Impression | |---|---|---| | Aggregation level | Whole property | Individual URL / page | | Landing Page (URL) dimension | Not available | Available | | Query dimension | Available | Available | | Search Appearance dimension | Available | Available | | How impressions are counted | Once per search the site appears in | Per URL that appears | | Best for | Query reports, sitewide trends, position | Top-pages reports, page-level analysis | | Matches GSC UI "Pages" tab? | No | Yes (closely) |

If you only set up one source, URL Impression is the more flexible default because it keeps the page dimension available, but be aware its sitewide impression totals can read higher than Site Impression for the same period. For accuracy, label your data sources clearly (e.g., "GSC – URL Impression" and "GSC – Site Impression") so you never confuse them on a busy report.

This distinction mirrors how the Performance report itself works; if you want a refresher on GSC's underlying metrics, see our Google Search Console performance report guide.

Step 3: Know your dimensions and metrics

Once connected, Looker Studio gives you these fields from Search Console.

Metrics: Clicks (clickthroughs to your site), Impressions (times your result was shown), CTR (clicks divided by impressions as a percentage), and Average Position (average ranking, where lower is better).

Dimensions: Date (time-series), Query (both tables), Landing Page (URL Impression only), Country and Device, Search Type (Web, Image, Video, News), and Search Appearance (special result types like recipes or videos).

A word of caution on Average Position and CTR: these are ratios, and Looker Studio will average them across rows if you let it, which produces nonsense. For position, this is a known limitation; treat aggregated position as directional rather than exact. For CTR, set the metric's aggregation so it's derived from total clicks and total impressions.

Step 4: Build the core charts

Now build a report. From your data source, click Create Report (or add the source to an existing report). Here's a practical set of charts, with the exact configuration for each.

Clicks and impressions over time

This is the headline chart for any GSC dashboard.

1. Insert a Time series chart.
2. Set the Dimension to Date.
3. Set Metric 1 to Clicks and Metric 2 to Impressions.
4. Because clicks and impressions are on wildly different scales, open the chart's Style tab and assign Impressions to a right (secondary) axis so the clicks line isn't flattened to zero.
5. Optionally add a comparison in the chart's date range settings to show "vs. previous period."

Top queries table

1. Insert a Table chart.
2. Set the Dimension to Query.
3. Add Metrics: Clicks, Impressions, CTR, and Average Position.
4. Sort by Clicks descending.
5. In the table settings, set Rows per page to something generous (25–100) and enable pagination. This is where you feel the benefit of escaping the 1,000-row limit.

Top pages table

Use your URL Impression data source for this one.

1. Insert a Table chart.
2. Set the Dimension to Landing Page.
3. Add the same four metrics: Clicks, Impressions, CTR, Average Position.
4. Sort by Clicks descending.

If the Landing Page dimension doesn't appear, you're on a Site Impression source; switch the chart's data source to your URL Impression one.

Position distribution

A quick way to see how much of your visibility sits on page one versus deeper.

1. Insert a Bar chart.

2. Create a calculated field that buckets Average Position into ranges. Add a new field with a formula like:

   CASE
     WHEN Average Position <= 3 THEN "1-3"
     WHEN Average Position <= 10 THEN "4-10"
     WHEN Average Position <= 20 THEN "11-20"
     ELSE "21+"
   END
   

3. Use that bucket field as the Dimension and Clicks (or Impressions) as the Metric.

Because aggregated position is approximate, read this as a shape, not a precise census.

Striking-distance table (positions 8–20)

This is the chart that earns its keep. Queries sitting just off page one — roughly positions 8 to 20 — are your fastest wins, because a small improvement can push them into clickable territory.

1. Duplicate your Top queries table.
2. Add a filter to this chart: Include → Average Position → Greater than or equal to 8 AND Less than or equal to 20.
3. Add a second condition if you like, e.g. Impressions greater than 100, to ignore queries with no real demand.
4. Sort by Impressions descending so the highest-opportunity terms float to the top.

Each query in this table is a content opportunity: a phrase you already rank for but aren't getting clicks from yet. That's exactly the kind of signal you can turn into a content brief.

Step 5: Add interactive filters and controls

Charts are static until you add controls. Place these at the top of the report so they apply page-wide.

Date range control

Insert a Date range control (from the toolbar). With no chart selected, it governs every chart on the page. Set a sensible default like "Last 28 days" or "Last 3 months." Viewers can then change the range without you rebuilding anything.

Branded vs. non-branded filter

Separating branded queries (people searching your company name) from non-branded ones is one of the most valuable cuts in SEO reporting, because branded traffic inflates totals and hides how you're really performing on discovery terms.

1. Insert a Drop-down list control (or two Filter controls), or build it as a calculated field.

2. The cleanest approach is a calculated field on the data source. Create a field like:

   CASE
     WHEN REGEXP_MATCH(Query, ".*(yourbrand|your brand|yourbrnd).*") THEN "Branded"
     ELSE "Non-branded"
   END
   

   Replace the terms in parentheses with your brand spellings and common misspellings.

3. Add this field as a Drop-down control at the top of the page, or use it as a dimension/filter on individual charts.

Now anyone can toggle branded out and see the non-branded picture instantly.

Step 6: Share and schedule email reports

A dashboard nobody opens is wasted work. Looker Studio makes distribution easy.

• Share a link: Click Share → manage access. Use "Anyone with the link can view" for low-friction sharing, or add specific Google accounts for tighter control. Viewers never need GSC access.
• Schedule emails: Click the dropdown next to Share and choose Schedule email delivery. Set recipients, frequency (daily, weekly, or monthly), the time, and which pages to include. Looker Studio sends a PDF snapshot on that schedule. This is the feature that quietly replaces a recurring manual reporting task.
• Embed it: You can also embed the report in an internal wiki or site via Share → Embed report.

Understanding the connector's limits (so you don't get burned)

Looker Studio is a window onto the Search Console API, and it inherits that API's constraints. Be honest about these:

• Roughly 16 months of data. GSC retains about 16 months of Performance data, and Looker Studio can't show what GSC doesn't keep. For longer history, you need to warehouse the data yourself, for example via the BigQuery bulk export.
• Sampling and row limits still apply. The connector pulls through the same API the GSC API guide describes, so very large queries can be sampled or truncated at the API level. It's far better than the 1,000-row UI export, but it is not a guarantee of every row.
• Aggregated Average Position is approximate. As noted, position is a weighted average that doesn't aggregate cleanly in Looker Studio; treat it as directional.
• Data freshness lags. Search Console data is typically a couple of days behind, so your most recent dates will be incomplete or empty. Default your date range to end a few days back to avoid showing a misleading drop.
• CTR aggregation must be configured. If you don't set CTR to compute from total clicks and impressions, aggregated rows show averaged percentages that are simply wrong.

None of these are reasons to avoid Looker Studio. They're reasons to label your sources, choose the right table, and read position and CTR with appropriate skepticism.

From dashboard to action

A Looker Studio dashboard tells you what is happening: traffic is up, these pages are slipping, these queries are stuck at the bottom of page one. The harder question is what to do about it. That striking-distance table is a list of pages that need better, more targeted content — but turning a list of queries into an actual editing plan is still manual work.

That's the gap Search Console Tools fills. Connect your Google account with one click (Google OAuth, no dashboard building required) and it reads the same Search Console data, then turns striking-distance queries and underperforming pages into ready-to-use content briefs and prebuilt insights. If you'd rather skip the chart-building and jump straight to recommendations, start there; to see how it compares to other options, our roundup of the best Google Search Console tools for 2026 is a good place to start.

Build the Looker Studio dashboard for at-a-glance reporting and stakeholder emails. Use a brief-generation tool for the actual optimization work. Together they cover both halves of the job.

Frequently Asked Questions

Is connecting Google Search Console to Looker Studio free?

Yes. Looker Studio and the official Search Console connector are both free to use. You only need a Google account with access to the verified property. There is no paid tier required to build dashboards, share links, or schedule email reports.

What is the difference between URL Impression and Site Impression in the GSC connector?

Site Impression aggregates data at the whole-property level and counts an impression once per search the site appears in, but it has no Landing Page dimension. URL Impression aggregates per page, includes the Landing Page dimension, and counts impressions per URL, so its sitewide totals can read higher. Use URL Impression for page-level reports and Site Impression for query and sitewide trends.

Does Looker Studio bypass the 1,000-row export limit in Search Console?

Largely, yes. The GSC interface caps table exports at 1,000 rows, while the Looker Studio connector pulls through the API and can return far more rows in a single table. It still inherits the API's own sampling and limits on very large queries, so it isn't a guarantee of literally every row, but it's a dramatic improvement over the UI export.

Why is my Average Position number different from the GSC interface?

Average Position is a weighted average that does not aggregate cleanly when Looker Studio combines rows, and the URL Impression table counts position per URL rather than per site. Both factors cause small differences from the GSC UI. Treat the connector's position figure as directional rather than an exact match.

How far back does Search Console data go in Looker Studio?

About 16 months, because that's roughly how long Google Search Console retains Performance data, and Looker Studio can only show what the API provides. If you need a longer history, set up the BigQuery bulk export to warehouse the data yourself before it ages out of GSC.

Can I schedule automatic email reports from a Looker Studio GSC dashboard?

Yes. Use the dropdown next to the Share button and choose Schedule email delivery. You can set recipients, choose daily, weekly, or monthly frequency, pick the send time, and select which pages to include. Looker Studio then emails a PDF snapshot of the dashboard on that schedule automatically.