Search Console tells you how people find you in Google. GA4 tells you what they do once they arrive. Checking both, every week, in two different interfaces, with different date pickers and different definitions, is slow, and it's even harder to explain to a manager or client. An SEO dashboard puts the numbers that matter on one page that updates itself.
Google's free reporting tool is the obvious place to build it. You may know it as Looker Studio, or from its earlier life as Google Data Studio. In April 2026 Google renamed it back to Data Studio. The product, the connectors and the way you build dashboards are the same, so everything in this guide applies whichever name you see.
You'll learn which data sources to connect, how to plan the layout, a step-by-step build, the charts and filters that make an SEO dashboard useful, and the mistakes that cause numbers not to match.
Key Takeaways
- Looker Studio was renamed Data Studio in April 2026; the core tool remains free.
- The Search Console connector offers two aggregations, Site Impression and URL Impression. One data source can use only one, so add both for a complete dashboard.
- Combine Search Console (visibility) with GA4 (engagement and key events) to connect rankings to business outcomes.
- Plan the dashboard around questions, not charts: “Are we growing?”, “Which pages drive leads?”, “What changed?”
- Use owner's credentials carefully, label every metric and add date comparison so viewers can see trends.
Looker Studio, Data Studio: what changed?
Google's release notes for April 2026 announced the change directly:
“We've rebranded Looker Studio as Data Studio.”
— Google Cloud, Data Studio release notes
The free tier remains for individual analysis and visualisation, and a paid Data Studio Pro tier adds team workspaces, administration and enterprise security. Existing Looker Studio reports keep working. In this article we use “Looker Studio” and “Data Studio” interchangeably, because many tutorials, templates and colleagues still use the old name.
Which data sources to connect
| Data source | Connector | What it adds | Access needed |
|---|---|---|---|
| Search Console – Site Impression | Google Search Console (free) | Site-level clicks, impressions, CTR, average position and queries | At least view permission on the property |
| Search Console – URL Impression | Google Search Console (free) | Page-level performance, including Discover and Google News search types | At least view permission on the property |
| Google Analytics 4 | Google Analytics (free) | Organic sessions, engagement, key events, revenue | Read access to the GA4 property |
| Google Sheets | Google Sheets (free) | Targets, annotations, manual AI visibility tracking | Access to the sheet |
| Rank tracking or backlinks | Partner connectors or Sheets/BigQuery import | Keyword positions, referring domains | Depends on the tool |
For the definitions behind each Search Console metric, see our guide to Google Search Console. If your GA4 setup needs work first, start with our GA4 guide and Google Tag Manager guide.
Plan the dashboard before you build
The best SEO dashboards answer a small number of questions for a specific audience. Sketch it on paper first.
- Page 1 – Overview (for managers): organic clicks, impressions, CTR, organic sessions and organic key events, each with a change versus the previous period, plus a 16-week trend line.
- Page 2 – Queries: top queries, rising and falling queries, branded vs non-branded split.
- Page 3 – Pages: landing pages with clicks, CTR, position, sessions and key events side by side.
- Page 4 – Technical and segments (for the SEO team): device, country, search appearance and any notes.
Choose metrics that tie to goals; our guide to SEO KPIs helps you pick.
How to build an SEO dashboard: step by step
- Create a blank report. Go to the Data Studio (Looker Studio) home page, click Blank report and sign in with the same Google account you use for Search Console and GA4.
- Add Search Console (Site Impression). Choose the Search Console connector, select your property, choose Site Impression and the Web search type, and add it.
- Add Search Console (URL Impression). Add a second data source with the same connector, this time choosing URL Impression. Rename both data sources clearly, e.g. “GSC – Site” and “GSC – URL”.
- Add GA4. Choose the Google Analytics connector and select your GA4 property.
- Set report-wide controls. Add a date range control (default: last 28 days) with comparison to the previous period, and a filter control for device or country if useful.
- Build the scorecards. Add scorecards for Clicks, Impressions, Site CTR and Average Position (from GSC – Site), and Sessions and Key events (from GA4, filtered to the Organic Search channel). Turn on comparison to show change.
- Add trend charts. A time series of clicks and impressions by week, and a separate one for organic key events.
- Add the query table. From GSC – Site: Query, Clicks, Impressions, CTR, Average Position, sorted by clicks, with a comparison column.
- Add the landing page table. From GSC – URL: Landing Page, Clicks, Impressions, CTR, Position. Next to it, a GA4 table of Landing page + query string with Sessions, Engagement rate and Key events for organic traffic.
- Add branded vs non-branded. Create a calculated field with a CASE statement (e.g. queries matching your brand regex = “Branded”, else “Non-branded”) and use it in a pie or bar chart.
- Label and explain. Add short text boxes that define each metric and note data limitations.
- Share. Use Share to invite viewers, or schedule an email delivery of the PDF each month.
A useful branded query field
CASE
WHEN REGEXP_MATCH(Query, ".*(acme|acme plumbing|acmeplumbing).*") THEN "Branded"
ELSE "Non-branded"
ENDReplace the brand terms with your own, including common misspellings. Search Console also introduced a built-in branded queries filter in its Performance report in late 2025 for eligible sites, but a calculated field gives you control in your dashboard.
Charts that work well for SEO
| Question | Chart type | Fields |
|---|---|---|
| Are we growing? | Scorecards with comparison | Clicks, impressions, organic key events |
| What's the trend? | Time series (weekly) | Clicks and impressions, dual axis |
| Which queries matter? | Table with heatmap | Query, clicks, CTR, position, change |
| Which pages convert? | Table | Landing page, sessions, engagement rate, key events |
| Where is CTR weak? | Scatter chart | Impressions (x) vs CTR (y) by page |
| How does mobile compare? | Bar chart | Device, clicks, CTR, position |
The scatter chart is especially handy: pages with high impressions and low CTR are your quickest wins. Our guide to improving organic CTR explains what to do with them.
Blending Search Console and GA4 data
Data blending lets you join two sources on a shared field, such as landing page. It sounds ideal, but Search Console URLs are full URLs while GA4 landing pages are usually paths, so you need a calculated field to make the keys match. Blends can also behave unexpectedly with filters and totals. For most teams, placing a GSC table and a GA4 table side by side, filtered to the same pages, is simpler and less error-prone.
Credentials, sharing and performance
- Owner's vs viewer's credentials. With owner's credentials, anyone who can view the report sees the data through your access. With viewer's credentials, each viewer must have their own access. Use owner's credentials for clients who don't have Search Console access, but understand what you're sharing.
- GA4 quotas. The GA4 connector is subject to Google Analytics Data API quotas; very busy reports with many charts can hit them and show errors. Fewer, purposeful charts help.
- GA4 segments. Google's documentation notes GA4 segments and comparisons aren't available through the connector, so use filters instead.
- Anonymised queries. Search Console hides some queries for privacy, so query tables won't sum to total clicks. Filter out blank queries and explain this in a note.
Common mistakes
- Using only one Search Console aggregation. Site and URL data differ by design. Mixing them in one scorecard row confuses viewers.
- Averaging average position. Averages of averages mislead. Use position as a directional indicator and weight it by impressions when possible.
- No organic filter on GA4 charts. Without a channel filter, “sessions” includes paid, social and direct traffic.
- Too many charts. A dashboard nobody understands isn't used. Keep the overview page to one screen.
- No context. Add annotations (a Sheets source works) for migrations, algorithm updates and campaigns. Our algorithm updates guide helps explain sudden changes.
- Ignoring AI visibility. AI Overviews and AI Mode are counted inside Search Console's Web search type and can't be separated, so consider adding a sheet-based AI visibility tracker and a GA4 AI Assistant channel chart.
From dashboard to report
A dashboard shows what happened; a report explains why and what to do next. Use your dashboard as the data layer for a monthly SEO report, and link campaign traffic correctly with UTM parameters so channels stay clean.
Related Guides
- SEO Reporting: What to Include (With Template)
- Marketing Attribution Models Explained
- Engagement Rate vs Bounce Rate in GA4
Frequently Asked Questions
Is Looker Studio still free?
Yes. Google renamed Looker Studio to Data Studio in April 2026, and the core product remains free for building reports and dashboards. A paid Pro tier adds team management, security and enterprise features.
What is the difference between Site Impression and URL Impression in the Search Console connector?
They are two ways of aggregating Search Console data. Site Impression aggregates by property, which suits site-level totals and query trends. URL Impression aggregates by page, which suits page-level analysis and supports more search types such as Discover. One data source can only use one of them, so many dashboards add both.
Why don't my dashboard numbers match Search Console exactly?
Common reasons include using a different aggregation (site vs URL), different date ranges or time zones, anonymised queries being hidden, and table row limits. Small differences are normal; large ones usually mean a filter or aggregation mismatch.
Can I add rank tracking or backlink data to the dashboard?
Yes, through partner connectors or by importing data from Google Sheets or BigQuery. Many SEO tools offer their own connectors for this purpose.
How often does the dashboard update?
Data refreshes automatically based on each data source's freshness settings and the underlying platform's data availability. Search Console data typically lags by a few days, and the newest days may be preliminary.
Conclusion
A well-built SEO dashboard saves hours every month and makes conversations about SEO much clearer. Connect both Search Console aggregations and GA4, plan pages around real questions, keep the overview simple and label everything. Whether you call it Looker Studio or Data Studio, it's free and it's worth an afternoon. If you'd like us to build a custom SEO dashboard and reporting routine for your business, explore our SEO services or request a free quote.
References
- Data Studio release notes – Google Cloud Documentation
- Connect to Search Console – Data Studio documentation
- Connect to Google Analytics – Data Studio documentation
- Performance report (Search results) – Search Console Help
- Data Studio is back: Google kills Looker Studio name – PPC Land
- Google Data Studio (Looker Studio) Tutorial – Semrush Blog
