How to Build an SEO Dashboard in Looker Studio
Connecting Search Console and GA4 in Looker Studio, blending them without breaking the numbers, and why the dashboard is sometimes a few days behind reality.
Building an SEO dashboard in Looker Studio means connecting Search Console and GA4 as separate data sources, blending them on a shared field like landing page and date, and setting the layout around the handful of numbers a client actually reads. The free tool covers this without a software cost; the setup takes an afternoon, not a subscription.
This is the hands-on half of SEO reporting, which covers what the finished report should say once the dashboard behind it is working.
On this page
What do you need before you start building?
Access to the Search Console property and the GA4 property, at viewer level or above, under the same Google account you will use to build the report. Confirm both before opening Looker Studio — a missing permission is the single most common reason a first attempt stalls halfway through, and it is worth checking before you have already spent twenty minutes on layout.
It also helps to know the shape of the finished report before you start, even loosely. Building charts first and deciding what story they should tell afterward is how a dashboard ends up with twelve widgets nobody asked for. Sketch the three or four numbers a reader actually needs, then build toward that.
Confirm Search Console access
You need at least Restricted access on the exact property (domain or URL-prefix) the dashboard will report on.
Confirm GA4 access
Viewer role on the GA4 property is enough to build a report; Editor is only needed if you will also be changing the property's own settings.
Decide the date range up front
Rolling last-28-days is the sane default for a recurring monthly report; a fixed range is for a one-off.
Pick who owns the Looker Studio file
Whoever's account owns the report is whoever the data connections run through — usually your own account, not the client's.
How do you connect Search Console and GA4 as data sources?
As two separate connections, because Looker Studio treats each platform as its own data source [1] [3]. Create a new data source, choose the Search Console connector, select the property and the "Site Impression" or "URL Impression" table depending on whether you want page-level or query-level rows, then repeat the process with the GA4 connector on its own data source.
The table choice inside the Search Console connector is easy to get wrong on a first build. Site Impression rows are aggregated per page and per date; URL Impression rows go further, adding query and device as dimensions but at the cost of a much larger row count. Start with Site Impression for a summary dashboard and only switch to URL Impression for a page that needs query-level detail — pulling the bigger table everywhere slows every chart down for no benefit on the pages that did not need it.
| Data source | Strong at | Missing |
|---|---|---|
| Search Console connector | Queries, impressions, average position | Sessions, conversions, on-site behaviour |
| GA4 connector | Sessions, channels, goal completions | Search queries, impressions |
| Blended source | Both, joined on a shared field | Some metric types cannot be blended cleanly |
Keep both raw, unblended sources in the report even after you build a blend. When a number looks wrong later, checking it against its original, unblended source is the fastest way to tell whether the problem is in the data or in the blend itself.
How do you blend them into one table?
Create a blended data source, add both connections as sources within it, and join them on the fields they actually share — landing page (matched against Search Console's page dimension) and date are the standard pair. GA4 and Search Console do not share a query dimension by default, so a blend cannot show "this query drove this many GA4 sessions" directly; it can only show that a page which ranked for that query also had a certain number of sessions on that date.
That distinction matters more than it sounds. A client asking "which keyword brought this traffic" is asking a question the blend cannot answer precisely — only a page-and-date correlation can, and it is worth saying so in the dashboard rather than letting a confident-looking chart imply more precision than the data actually has.
What filters should the dashboard include by default?
At minimum three: a regex filter separating branded from non-branded queries, a country filter if the site serves more than one market, and a device filter, since mobile and desktop behaviour rarely tell the same story. Build these as report-level controls a viewer can toggle, not as hard-coded filters baked into the chart, so the same dashboard answers both "how is non-branded doing" and "how is everything doing" without a second report to maintain.
A page-path filter is worth adding too, once the site has distinct sections worth reporting separately — a blog and a product catalog rarely move for the same reasons, and a single blended trend line across both will average away whichever one actually needs attention.
Why does the dashboard sometimes look wrong or behind?
Usually because it is genuinely behind, not broken. Search Console data is typically available within two to three days, and the most recent day or two in any pull should be treated as incomplete rather than final [2].
2–3 days
What should the layout actually show?
Three sections, not fifteen widgets: a trend line for the headline metric at the top, a table of top pages or queries in the middle, and a comparison against the previous period somewhere visible without scrolling. Anything beyond that belongs in a secondary page a reader can open on request, not the first screen they see.
Put the comparison number as text, not just as a second line on a chart. "Non-branded sessions: 4,120, up from 3,610 last period" reads in one glance; the same information encoded only as two overlapping lines on a graph asks the reader to do arithmetic before they can answer their own question. A dashboard is read on a phone as often as a laptop now, and a chart that needed a wide screen to compare two lines will not survive that.
Order the report by how a reader actually scans it: top to bottom, most important first. Put the number someone is checking in under ten seconds at the very top of the page, above any control or filter row, so a quick glance answers the question before anyone has to interact with anything.
SEO reporting tools covers where Looker Studio fits against paid, white-label alternatives if the client list eventually outgrows what one free dashboard can comfortably manage.
How do you share it without exposing raw account access?
Use link-based sharing rather than adding a client's email as a viewer on the underlying GA4 or Search Console property. "Anyone with the link can view" keeps the report open without ever giving the client, or anyone they forward the link to, direct access to the accounts the dashboard is built on.
This is not a minor distinction. Adding someone as a viewer on the Search Console property itself hands them a door into raw account settings they were never meant to touch, and removing that access cleanly later is easy to forget. A shared report link, by contrast, can be revoked or regenerated in seconds without touching the underlying account at all — keep the two forms of access separate from the start rather than untangling them after the fact.
Revisit that sharing setting whenever a client relationship ends. A report link left active after a contract closes is a small, easy-to-forget loose end, and it is worth a standing checklist item rather than relying on memory. If the relationship is ending because reporting itself became the complaint, when to fire an SEO agency covers what that pattern usually looks like from the other side of the table.
The dashboards that fall apart are almost never the ones with a data problem. They are the ones nobody looked at again after the first build, so a broken connector sat there for two months before anyone noticed the numbers had stopped moving.
Questions people also ask
Is Looker Studio free?
Yes, for the core product used to build reports like this one. Its Pro tier adds team workspace and access-management features that most single-agency or in-house setups do not need to get started.
Why does my Looker Studio dashboard show fewer clicks than Search Console itself?
Usually a filter or a date range mismatch introduced during the blend, or the normal reporting delay — Search Console data typically needs two to three days to fully settle before it is complete.
Can I blend GA4 and Search Console data in one table?
Yes, using a blended data source with a shared join key such as landing page and date. Blending trades some flexibility for convenience — always check a blended metric against its unblended source before trusting it in a client report.
Do clients need a Google account to view the dashboard?
Not if you set sharing to "Anyone with the link can view." A Google account is only required if you want to restrict access to specific people rather than anyone holding the link.
How often should the dashboard be checked, not just shared?
Monthly at minimum, before the report goes out, specifically to confirm every data source is still connected. A broken connector fails silently and will keep showing the last successful pull unless someone checks.
Sources
- Connect to Search Console — Looker Studio Help (checked 23 September 2026)
- About Search Console data — Google Search Central (checked 23 September 2026)
- [GA4] Traffic acquisition report — Google Analytics Help (checked 23 September 2026)
- Manage data freshness — Google Cloud Documentation (checked 23 September 2026)
Want this dashboard built for you instead of from scratch?
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- SEO reporting: what a good report showsA guide to SEO reporting: what a monthly report must include, which KPIs matter at each stage, and how to tie organic search to real revenue.
- SEO Reporting Tools: What to Actually UseThe real categories of SEO reporting tools, what each one is for, and why most teams need two of them rather than one all-in-one platform.
- Search Console vs GA4: Why the Numbers DifferWhat Search Console and GA4 each actually measure, why their numbers never match, and which one to trust for clicks, sessions, queries and revenue.
- When to Fire Your SEO AgencyThe clear signs an SEO agency isn't working, how long to wait before deciding, and how to leave cleanly with your data intact.