SEO Dashboard: How to Build and Read One in Looker Studio
By Christoph Olivier, Founder, CO Consulting
Last reviewed: July 2026
An SEO dashboard is one connected reporting view that pulls Google Search Console for demand and Google Analytics 4 for outcomes into a single Looker Studio report, so you can answer “did organic search make us money this month?” in about 90 seconds. Most people confuse the dashboard with the metric list. Those are two jobs. This page is the wiring and reading manual: which sources connect to which tabs, the one blend decision that stops the arguments, and how to run the monthly review off it. For which numbers belong on it, see our guide to the SEO metrics that matter. Here we assume you already know the metrics and want to assemble and read the report.
What an SEO dashboard actually is (and is not)
An SEO dashboard is a live, self-updating reporting layer built on top of your raw data sources. It is not a spreadsheet you rebuild each month, and it is not the metrics themselves. Think of it as the dials on a car: the dials are the dashboard, the engine sensors are Search Console and GA4, and reading the dials is the monthly review.
The distinction matters because it decides where you spend effort. A dashboard’s value comes from three things: correct connections, a defensible blend, and a layout that maps to decisions. Get those right once and the dashboard runs itself. Get them wrong and you spend every month reconciling totals that will never agree.
We build these in Looker Studio because it is free, connects natively to both Google sources, and refreshes on its own. Paid tools like Agency Analytics or Databox do the same job with less setup and a monthly fee. The build logic below is identical across all of them.
The two data sources every SEO dashboard needs
Every SEO dashboard is built on Google Search Console for demand and visibility and Google Analytics 4 for behaviour and conversions. GSC tells you how Google shows and ranks your pages before the click. GA4 tells you what happened after the click. You need both because neither answers the money question alone.
Connect them as separate data sources first, before you blend anything. In Looker Studio, click Create, then Data source, then add the Search Console connector (choose the “Site” table, not “URL impression”) and the GA4 connector for your property. Authorise each once. If you have not wired GA4 yet, our GA4 setup walkthrough covers the property and key-event configuration this depends on.
Here is what each source contributes, so you know which tab pulls from which.
| Source | Contributes | Attribution model | Counting unit |
|---|---|---|---|
| Google Search Console | Clicks, impressions, CTR, average position, by query and page | Last click in Google Search | Clicks (one search result click) |
| Google Analytics 4 | Organic sessions, engagement rate, key events, revenue | Data-driven (default) | Sessions and users |
Those two rows explain 90% of the “why don’t the numbers match?” complaints. GSC counts clicks with last-click attribution; GA4 counts sessions with data-driven attribution. One person clicking twice is two GSC clicks but often one GA4 session. Expect a gap of 10 to 20% and stop trying to close it.
The one blend decision that makes or breaks the dashboard
When you blend GSC and GA4 in Looker Studio, always left-join from the source you trust as the answer to the question that view asks. This single rule prevents the endless “the totals are wrong” arguments, because it defines up front which source is the truth and which is context.
Blending merges two datasets on a shared key, usually Landing Page. But a blend has a direction: the left source keeps all its rows, the right source adds columns where the key matches. Pick the left source by the question:
- “Which landing pages lost organic clicks?” The truth is visibility, so GSC is the left source. Add GA4 outcomes (sessions, key events) as extra columns to explain the drop.
- “Which landing pages lost leads from organic?” The truth is the outcome, so GA4 is the left source. Add GSC visibility (impressions, position) as columns to explain why.
Match the keys carefully. GSC gives you a full URL; GA4 gives you a page path. Create a calculated field to strip the domain from the GSC URL so both sides share the same path format, or the join will silently drop rows. This is the single most common reason a blended table shows fewer pages than it should.
Set the join type to left outer, not inner. Inner joins hide any page that exists in one source but not the other, which is exactly the page you most want to see, the new one with impressions but no sessions yet.
The four tabs of a working SEO dashboard
A working SEO dashboard has four tabs, ordered from decision-maker to practitioner: an executive summary, a demand and visibility tab from GSC, an outcomes tab from GA4, and a page-level blend that joins the two. Each tab answers one question, so nobody has to interpret raw data.
The ordering is deliberate. The person with the least time sees the summary first. The person doing the work drills into the blended page table last. Below is the layout, the source, and the one question each tab answers.
| Tab | Primary source | The question it answers | Core components |
|---|---|---|---|
| 1. Executive summary | GA4 (with GSC scorecards) | Did organic search grow the business this month? | Scorecards for organic sessions, key events, revenue vs prior period; one trend line; a text box for the written takeaway |
| 2. Demand and visibility | Search Console | Is Google showing and ranking us more? | Clicks and impressions time series; average position trend; top queries table with position change |
| 3. Outcomes | GA4 | What did organic visitors do once they arrived? | Organic sessions, engagement rate, key events by landing page; conversion path to revenue |
| 4. Page-level blend | GSC + GA4 blend | Which specific pages are winning or slipping, and why? | Blended table: page, clicks, position, sessions, key events, all sortable |
Add a date-range control and a device or country filter to the top of every tab so a viewer can re-slice without editing. Set every scorecard to compare against the previous period, not a fixed date, so the dashboard reads itself on the first of every month.
One design rule beats the rest: put no metric on the executive tab that an executive cannot act on. Raw impressions and indexed-page counts are practitioner context, so they live on tabs 2 and 4. For the full split of which metrics earn a spot, see our SEO metrics that matter breakdown.
How to build it in Looker Studio: the 7 steps
Building the dashboard takes about 45 minutes the first time and follows a fixed order: connect sources, fix the join key, blend, then lay out the four tabs and set the comparison periods. Do the steps in order, because the blend fails if the sources and key fields are not ready first.
- Connect Search Console. Create a new report, add the GSC connector, pick your verified property, and choose the Site table for query and page data.
- Connect GA4. Add the GA4 connector for the same site’s property. Confirm your organic sessions segment and key events are firing before you trust the numbers.
- Create the join key. In the GSC source, add a calculated field that strips the protocol and domain from Landing Page so it matches GA4’s page path exactly.
- Blend for the page table. Blend GSC and GA4 on the cleaned page path, left outer join, GSC on the left for the visibility question. Keep the blend to the fields the page table needs; extra fields slow the report.
- Build the four tabs. One page per tab from the table above. Use scorecards on tab 1, time series on tab 2, tables on tabs 3 and 4.
- Set comparison periods. On every scorecard and chart, set comparison to Previous period. This is what makes the dashboard self-reading.
- Add controls and share. Drop a date-range control and one segment filter on each tab, then share view-only links so nobody edits the live report.
If you would rather not build from scratch, free templates from SE Ranking, Kodalogic, and Gaille Reports pre-wire the GSC and GA4 connectors; you just swap in your own sources. A template saves the layout work but not the join-key fix, which you still have to do by hand.
How to read the dashboard in your monthly review
Read the dashboard top-down, one tab at a time, and turn each tab into a single sentence before moving on. The review is not about staring at charts; it is about writing four sentences and one action. Because SEO effects lag 2 to 8 weeks, monthly is the right cadence to read it.
Here is the exact read order we use, and what a good and a bad signal looks like on each tab.
| Read this tab | Good signal | Warning signal | Write this sentence |
|---|---|---|---|
| 1. Executive summary | Organic sessions and key events both up vs prior period | Sessions up but key events flat (traffic without value) | “Organic did / did not grow the business, by X%.” |
| 2. Demand and visibility | Impressions and average position improving together | Impressions up, clicks flat (ranking for the wrong queries) | “Google is showing us more / less, and ranking us higher / lower.” |
| 3. Outcomes | Engagement rate steady, key events per session rising | Engagement rate dropping on your top landing pages | “Visitors are / are not converting once they land.” |
| 4. Page-level blend | Your money pages hold clicks and position | A page with high impressions and near-zero clicks | “Page X is my one action for next month.” |
The four sentences plus one action are the report. Paste them into the text box on tab 1 so the next reader sees the conclusion before the charts. A dashboard nobody narrates is just decoration.
Watch for two traps. First, do not react to a single month; SEO trends need three data points, so a one-month dip inside a rising quarter is noise. Second, ignore vanity spikes: a jump in impressions from an irrelevant query inflates tab 2 while tab 1 stays flat, which is the dashboard telling you the traffic did not matter.
A worked example: reading a real monthly view
Here is a read we ran for a 7-figure home-services client, so the four-sentence method is concrete rather than abstract. The dashboard covered June against May.
Tab 1 showed organic sessions up 14% but key events (booked consultations) up only 3%. Sentence one: “Organic grew traffic more than it grew bookings.” Tab 2 showed impressions up 22% and average position improving from 8.4 to 6.9. Sentence two: “Google is showing and ranking us noticeably more.” Tab 3 showed engagement rate flat but the top service page’s key-event rate down. Sentence three: “Our best page is getting more visitors who convert at a lower rate.”
Tab 4, the blend, told the story: a comparison page had jumped to position 4 and was pulling a flood of top-of-funnel impressions, diluting the service page’s conversion rate in the aggregate. Action: split the reporting segment so the money page is read on its own, and add a stronger call to action to the comparison page. That single read, maybe six minutes, changed the next month’s work. That is the entire point of assembling the dashboard: not to admire data, but to find the one page that decides next month.
Frequently asked questions
What is an SEO dashboard?
An SEO dashboard is a single live reporting view that combines Google Search Console demand data with Google Analytics 4 outcome data, usually in Looker Studio, so you can see how organic search drives traffic and conversions without rebuilding a report each month. It is the reading layer on top of your metrics, not the metrics themselves.
What should an SEO dashboard include?
An SEO dashboard should include four tabs: an executive summary of organic sessions, key events and revenue; a Search Console tab for clicks, impressions and average position; a GA4 outcomes tab for engagement and conversions; and a blended page-level table joining both. Add a date-range control and previous-period comparison so it reads itself monthly.
How do I build an SEO dashboard in Looker Studio?
Connect Google Search Console and GA4 as separate sources, create a calculated field to match the GSC URL to the GA4 page path, then blend them with a left outer join on that path. Build one report page per tab, set every metric to compare against the previous period, and share a view-only link. It takes about 45 minutes the first time.
Should I blend Search Console and GA4 data?
Yes, but only for the page-level tab, and always left-join from the source that answers the question. Use GSC on the left for “which pages lost clicks” and GA4 on the left for “which pages lost leads.” Keep the other tabs on single sources so their totals stay clean and defensible.
Why don’t my GSC and GA4 numbers match on the dashboard?
They will never match exactly. Search Console counts clicks with last-click attribution while GA4 counts sessions with data-driven attribution, and one user can click twice but start one session. A 10 to 20% gap is normal. Report each source for what it measures rather than forcing the totals to reconcile.
How often should I read my SEO dashboard?
Read it monthly, because SEO changes take 2 to 8 weeks to show measurable effects, so weekly reads mostly show noise. The exception is a new site or a penalty recovery, where weekly check-ins during the first 90 days help you catch problems early. Always judge trends across three months, not one.