Google Search Console Looker Studio Dashboard: A Free Setup Guide

To connect Google Search Console to Looker Studio, create a new data source, pick the free Search Console connector, choose your property, then choose one table: Site Impression or URL Impression. That table choice matters more than any chart you build later. Site Impression counts one impression per search for your whole property. URL Impression counts one impression per page that appeared.

One naming note first. Google rebranded Looker Studio as Data Studio on April 16, 2026, according to the Data Studio release notes. Your old reports, calculated fields and URLs still work. I use both names in this post because most people still search for a “Google Search Console Looker Studio” dashboard, and the connector is the same one.

If you want the report itself explained metric by metric, my Search Console performance report guide covers that. This post is only about getting the data into a dashboard and reading it without fooling yourself.

Which Table Should You Pick: Site Impression or URL Impression?

This is the fork in the road, so I start here. Google’s connector documentation says a single data source can only use one of the two methods. If you want both, you create two data sources and add both to one report.

Here is how I think about it. Site Impression answers “how is my site doing in Google?” URL Impression answers “which pages are doing the work?” Google’s own help page for the performance report gives the classic example: when several of your pages show in one result card, grouping by property counts one impression, while grouping by page counts one per page.

That last row catches people out. Per Google’s connector page, Site Impression supports web, image, video and news, while URL Impression adds discover and googleNews. So if you run a publishing site and want Discover numbers, the URL table is your only door.

If you only build one data source, then make it URL Impression. It answers more questions. If the dashboard is for a client or a boss who compares it to Search Console, then add a Site Impression source too, because that is the number they will see in the UI.

Google Search Console Looker Studio Setup in Seven Steps

The whole thing takes about five minutes. Sign in to Data Studio with the same Google account that has access to the Search Console property. Google’s documentation says you need at least view permission on the property, and mismatched accounts are the most common reason the property list comes up empty.

1. Open Data Studio and click Create, then Data source.
2. Pick the Search Console connector made by Google. Partner connectors sit in the same gallery, so check the author.
3. Click Authorize if asked.
4. Select your site in the Sites panel.
5. Choose Site Impression or URL Impression in the Tables panel.
6. Choose a default search type, usually Web.
7. Click Connect, then Create report.

One setting deserves a second look before you share anything. The connector lets you use the owner’s credentials, the viewer’s credentials or a service account. With owner’s credentials, anyone you share the report with sees your Search Console data without needing their own access. That is handy for a client dashboard and risky for a report link that gets forwarded around.

The Five Charts I Put on Every Dashboard

I keep my own dashboards boring on purpose. Nobody makes decisions from a pie chart of countries. These five charts answer the questions I actually get asked on calls.

Add a date range control at the top and set the default to the last 28 days, compared with the previous period. Honestly, that one control saves more time than any clever chart.

For the query table, I sort by impressions rather than clicks. Rows with big impressions and tiny CTR are where the work is. When that pattern shows up, I follow my high impressions low clicks checklist before touching a single title.

Brand vs Non-Brand Split With a Regex Field

This is the chart that changes conversations. A site can look healthy while all its growth comes from people who already know the brand. In Data Studio, click Add a field, name it “Brand”, and paste a CASE statement like this:

CASE
  WHEN REGEXP_CONTAINS(Query, R"(?i)sky\s?rank") THEN "Brand"
  ELSE "Non-brand"
END

Swap sky\s?rank for your own brand and its common misspellings, separated with |. Three details matter here, and all three come from Google’s Data Studio docs:

• Use REGEXP_CONTAINS, not REGEXP_MATCH. REGEXP_MATCH must match the entire value, so “skyranko” alone would miss “skyranko reviews”. REGEXP_CONTAINS matches anywhere in the query.
• Add (?i) for case-insensitive matching. Regex in Data Studio is case-sensitive by default.
• Use the R prefix for a raw string. Without it, you have to double every backslash, so \s becomes \\s.

Data Studio uses RE2, the same engine as Search Console filters. That means no lookaheads. If you need a pattern library to start from, my Google Search Console regex post has 20 patterns that also work inside REGEXP_CONTAINS.

What about Search Console’s own branded filter? Google introduced a branded queries filter in November 2025, driven by an AI-assisted system. Google’s help pages say it only works for top-level properties with enough query volume. They say nothing about the connector, and I have not seen a branded field in it, so my regex field stays.

Why Doesn’t the Dashboard Match the Search Console UI?

Sooner or later, someone puts the dashboard next to Search Console and asks why the numbers differ. Usually four things explain it, and none of them means the connector is broken.

Anonymized queries. Google’s connector page says Search Analytics doesn’t show all data to protect privacy. Rare queries, or ones with personal or sensitive information, may show up as a single row with a blank Query value. Google’s advice is to filter out null values in the Query dimension. I add that filter to the query table only, not the site totals.

Table choice. A Site Impression total and a URL Impression total will not match, by design. If a stakeholder compares your landing page table with the Search Console chart, the page table will usually show more impressions.

Row limits on big sites. The Search Console API, which exposes the same Search Analytics data, returns a maximum of 50,000 rows per day per search type, sorted by clicks. Google also warns that adding page and query dimensions can drop some data. On a small business site, you’ll never hit that ceiling. On a large ecommerce or publishing site with a long tail of queries, I treat the dashboard as a view of the top of the data, not all of it.

Fresh days. Google’s API docs say data typically arrives after 2 to 3 days. The last couple of days in any chart will look like a dip. It isn’t one. I set my default date range to end three days ago so nobody panics on a Monday.

There’s also the 16-month limit. Search Console keeps 16 months of performance data, and the connector can’t reach further back than Search Console itself. If you want year-on-year comparisons three years from now, you have to start storing data today.

When Should You Move to BigQuery Bulk Export?

For most small and mid-sized sites, the free connector is enough. BigQuery bulk export is the next step when the connector’s limits start costing you real insight. Google’s help center describes it as a scheduled daily export of your performance data into BigQuery.

Here is what changes, based on Google’s bulk export documentation. You get two data tables, searchdata_site_impression and searchdata_url_impression, plus an ExportLog table. The tables are retained forever by default unless you set an expiration. Anonymized queries are still hidden, but they stay in the data as rows marked with is_anonymized_query, where the query field is null.

Three catches before you jump. First, you need a Google Cloud project with billing enabled; there is a free usage tier, but storage and queries beyond it cost money. Second, the first export happens up to 48 hours after setup and there is no backfill, so history before that date still has to come from the API or the reports. Third, you now need someone who can write SQL, or at least edit it.

You can then connect Data Studio to BigQuery instead of the Search Console connector. The dashboard looks the same. The data underneath is fuller and permanent.

Decision Matrix: Which Setup Fits Your Site?

This is the summary I’d give a client who asks what they should build. Pick the row that sounds like you.

My take, after building these for a lot of different sites: the dashboard is the easy part. The hard part is deciding what you’ll do when a line goes down. If a chart has never changed a decision, delete it, and I apply the same test to the one-page summary in my monthly SEO report guide.

When a Dashboard Isn’t Enough

A dashboard tells you something moved. It rarely tells you why. When traffic drops across a whole section, or clicks fall while rankings hold, you’re into diagnosis, and that usually means crawling the site, reading the Page indexing report and checking what changed on the SERP.

That’s the kind of work my team does in our complete SEO service, where reporting is built around the decisions it should drive. If you’d like a second pair of eyes first, you can request a free SEO audit. And if the numbers that confuse you are the gap between Search Console clicks and analytics sessions, read my Search Console vs Google Analytics breakdown before blaming the connector.

For the official reference on connector settings, Google’s Search Console connector page is short and worth reading once. For bulk export, start with Google’s bulk data export overview.

Frequently Asked Questions

Is the Search Console Connector in Looker Studio Free?

Yes. The Search Console connector built by Google is free, and so is Data Studio itself. You only pay if you choose a partner connector from the gallery or move to BigQuery bulk export beyond its free usage tier. Check who built a connector before you authorize it.

Did Looker Studio Change Its Name?

Yes. Google rebranded Looker Studio as Data Studio on April 16, 2026. Existing reports, data sources and calculated fields carried over unchanged, so a dashboard you built under the old name keeps working.

Why Is There a Blank Row in My Query Table?

That row holds queries Google hides for privacy, such as rare searches or ones with personal information. The connector may group them into one row with a blank Query value. Add a filter that excludes null values in the Query dimension if the row clutters your table.

Can I Get More Than 16 Months of Search Console Data in Looker Studio?

Not through the connector. It reads from Search Console, which keeps 16 months. To build longer history, set up bulk data export to BigQuery, which keeps tables until you set an expiration. Export only starts from the setup date, so start early.

Should I Use Site Impression or URL Impression for a Client Report?

Use both if the client compares your numbers with Search Console. Site Impression matches the totals they see in the UI, while URL Impression shows which landing pages earned clicks. Build two data sources and label each chart with its table so nobody mixes them up.

Last updated: September 2026 by Mizanur Rahman