SEO Dashboard with Data Studio and Search Console

Looker Studio no longer exists under that name: in April 2026 Google renamed it back to Data Studio. Its free Search Console connector lets you build a self-updating SEO dashboard that shows clicks, impressions, CTR and position without juggling ten browser tabs.

This guide covers what changed with the name, how to connect Search Console step by step, the five data limits that ruin conclusions, and how to protect your history. One warning first: a dashboard does not fix a site with no traffic, and this data is not your web analytics data.

Data Studio (formerly Looker Studio): what changed in 2026

The tool launched in 2016 as Google Data Studio. In October 2022 Google grouped its business intelligence products under the Looker brand and the reporting tool became Looker Studio. On April 10, 2026, the official Google Cloud blog announced the opposite: Looker Studio is Data Studio.

Existing reports, data sources and users were migrated automatically, with no action on your part, and the only visible change is the address, now datastudio.google.com. The standard edition is still free and the Search Console connector works the same way. Keep the naming map handy, because you will find all three names mixed together: Data Studio (2026 onward) = Looker Studio (2022-2026) = Google Data Studio. Data Studio Pro adds governance, but for an SEO dashboard the free edition is more than enough.

What you can (and cannot) measure with Search Console data

Search Console gives you four metrics: clicks, impressions, CTR and average position, broken down by date, query, page, country, device and search type. It is the only first-party source about how you appear in Google. Five limits to understand before building anything:

The window is 16 months: older data is deleted, not archived. To compare against an old year, you must have exported it earlier.
There is sampling: most reports show a representative sample of URLs.
Anonymized queries arrive blank, grouped into one row with an empty Query value. If you do not filter out nulls, rows will not match total clicks.
Data takes time to settle: a newly verified site can take up to a week to show data.
Average position is an average: a 7.3 includes impressions from around position forty. And aggregate CTR cannot be averaged row by row.

Site Impression or URL Impression: pick one and do not mix

The connector aggregates by site (Site Impression) or by URL (URL Impression), and each data source can only use one: to see them together you create two sources and add both to the same report. The practical difference is in the supported search types: site-level data has web, image, video and news; URL-level data adds discover and googleNews. Discover data only exists in the URL view, so a drop in the site-level report may be a redistribution toward Discover or News. Add the Search type control so readers can switch it without editing the dashboard.

Search Console is not Google Analytics (and that is why you should combine them)

Search Console measures appearances and clicks in the search engine; Analytics measures what happens next (sessions, conversions, revenue). Neither replaces the other. The Analytics queries report also pulls Search Console metrics when the property is linked, with the same 16-month ceiling. See the Search Console and Google Analytics guides for the detail.

Step by step: connect Search Console to your SEO dashboard

The steps for the free native connector, as described in the official documentation, last updated in September 2026:

Open Data Studio with the same Google account you use to see the property in Search Console, and with at least view permission: "my site does not show up" almost always means the wrong account.
Click Create and choose Data source.
Select the Search Console connector.
Click AUTHORIZE to grant access, a permission you can revoke at any time.
Configure the panels: Sites for the property, Tables for Site Impression or URL Impression, and Search Type for the search type.
Click CONNECT and, from the field panel, CREATE REPORT and ADD TO REPORT.

Before sharing anything, decide how the data is authenticated, because it is a security decision: with owner's credentials, anyone holding the link sees the data; with viewer's credentials, each person authorizes with their own account; a service account is a non-human user. Simple rule: viewer's credentials for client data, owner's credentials only for public reports. Two shortcuts: the template gallery already has a Search Console category, and data controls let readers pick the account without you duplicating the dashboard.

The minimum viable SEO dashboard: six blocks that actually get used

Most reports get abandoned because they carry twenty charts and no answers. These six blocks cover nearly everything:

Scorecards with clicks, impressions, average CTR and average position, with period-over-period comparison turned on.
A time series of clicks versus impressions, on two axes or two charts: mixing units on one axis gets misread.
A query table sorted by opportunity: highest impressions first, with low CTR in plain sight. These are the candidates for rewriting titles and meta descriptions, the cheapest fix there is. Use the SEO titles and meta descriptions guides.
A declining pages table: compare the last 28 days against the previous 28. That is the starting point for diagnosing a traffic drop and for working on old content.
A device or country breakdown, so you know where to prioritize: almost always mobile.
The two filters you cannot skip: nulls on the Query dimension, and brand versus non-brand.

Report hygiene: one single source of truth (by URL for pages, by site for global queries) and a visible note with the last refresh date and the window used.

Five rules that separate a useful report from a false conclusion

Separate brand from non-brand with regular expressions: without that filter, searches for your brand drown the real SEO signals.
Compare year over year for seasonality, but only inside the 16 months. If you are unsure whether a rise is a trend or seasonality, Google Trends helps.
Never read positions without impressions: moving up with flat impressions may just mean less competition.
Be careful when grouping page and query together: it is the most expensive query for the API and the slowest.
Document what counts as a click: Search Console counts clicks in Google results, not sessions on your site.

When the dashboard is not enough: automate and protect your history

Path 1: the Search Console API, for custom reports, drop alerts and internal pipelines. Details almost nobody quotes: rowLimit accepts 1 to 25,000 rows with a default of 1,000, so you must paginate with startRow; dates are interpreted in Pacific time; and quotas are per site, with a load limit and a daily allowance: if you exceed it, wait fifteen minutes and spread queries across the day. The most expensive queries group by page and query at once, and those covering long periods. See quotas and limits and the query reference. The URL inspection API has a much smaller quota.

Path 2: bulk export to BigQuery, the only way to break the 16-month ceiling. You set up a Google Cloud project with billing and BigQuery. Two warnings from the official documentation: data accumulates forever unless you set an expiration date on partitions, and that costs money. In exchange, you can join Search Console with server logs and build dashboards free of API limits.

Golden rule: automate the repetitive parts, like storing history or alerting on a sharp drop. Do not automate the decision.

Checklist: your SEO dashboard in one afternoon

Correct Google account, with view permission, and the connector authorized.
Two data sources if you want Site and URL Impression together; default search type chosen deliberately.
Null filter on the Query dimension and brand versus non-brand filters.
Period comparison enabled and the window used noted in the report.
Four scorecards, one time series and two opportunity tables.
Data source credentials chosen according to who will see the report.
History plan decided: the connector with its 16 months, or a BigQuery export.

With that in place you have an SEO dashboard that updates itself and one place to look before deciding. If you want to go deeper into what you measure, the SEO KPIs guide complements this dashboard with the business metrics that do not live in Search Console.