How to Build an SEO Dashboard in Looker Studio (GSC + GA4)

TL;DR

Connect Google Search Console and GA4 to Looker Studio using their native connectors, blend the two sources on a normalized landing-page dimension, then build scorecards and time-series charts for clicks, impressions, CTR, average position, sessions, and conversions. The whole setup takes under two hours and gives you a live, shareable SEO reporting layer at zero tool cost.

The incentive to build this dashboard has never been stronger. Google AI Overviews reduce position-1 organic CTR by 58%, according to Ahrefs' December 2025 research, and zero-click searches have climbed from 54% to 72% of all queries. In that environment, the difference between a page that gets traffic and one that gets impressions-but-no-clicks is exactly the kind of signal a blended GSC + GA4 dashboard surfaces in seconds. Without one, you are making optimization decisions in the dark.

This guide walks through every step: connecting data sources, normalizing landing-page URLs, building the core views, avoiding the common blending mistakes, and knowing when Looker Studio's free tier is no longer enough.

Why Looker Studio Is Still the Right Starting Point

Looker Studio (formerly Google Data Studio) is free, has first-party connectors to both Google Search Console and GA4, and produces shareable live reports without any export or copy-paste. For most SEO teams, that is all they need to replace a weekly slide deck.

Key advantages over a spreadsheet or a paid BI tool at the outset:

Native GSC connector pulls clicks, impressions, CTR, and average position by query, page, country, and device.
Native GA4 connector pulls sessions, engagement rate, conversions, and channel-grouped traffic.
Shared reports update automatically; stakeholders never get a stale PDF.
Looker Studio Pro adds team workspaces, SSO, and organization-level report ownership for $9 per user per month, but you do not need it to build a functional SEO dashboard.

The free tier has real limits. The GSC connector retains only 16 months of query data, the GA4 connector has API quota ceilings that can make charts go dark on large properties, and data blending is capped at five sources per blend. For most mid-size sites, these constraints do not bite for six to twelve months.

Step 1: Connect Your Data Sources

Connect Google Search Console

Open Looker Studio and click Create > Report.
In the data source panel, search for "Search Console" and select the Google-authored connector (blue G icon).
Authorize with the Google account that has GSC property access.
Select your property. For URL-prefix properties, choose the version that matches your site exactly (with or without trailing slash).
Select Site Impression as the table type for domain-level data, or URL Impression to get page-level data. For an SEO dashboard, use URL Impression as your primary connection.
Click Add to Report.

The Guru GSC integration handles this connection automatically for teams running the full Guru workflow, but Looker Studio works as a standalone reporting layer for any property.

Connect GA4

In the same report, go to Resource > Add a data source.
Search for "Google Analytics" and select the Google-authored GA4 connector.
Choose your GA4 account and property.
Click Add to Report.

If GA4 does not have a Landing Page custom dimension defined, create one before proceeding. Go to GA4 Admin, then Data Display, then Custom Definitions, and create a dimension named "Landing Page" with event parameter page_location. Without it, you cannot join GA4 session data to GSC page-level data by URL.

Step 2: Normalize Landing-Page URLs Before Blending

This step is where most dashboards break. GSC records URLs as full strings including protocol and trailing slash, for example https://example.com/blog/post/. GA4 records the path only, for example /blog/post. If you blend on the raw field, you will get a near-zero match rate and wildly wrong numbers.

Fix with calculated fields:

In the GSC data source, create a calculated field named Page Path:

`` REGEXP_REPLACE(LOWER(Landing Page), "^https?://[^/]+", "") ``

This strips the protocol and domain, lowercases everything, and leaves you with /blog/post/.

In the GA4 data source, create a calculated field named Page Path:

`` REGEXP_REPLACE(LOWER(Page path + query string), "\\?.*", "") ``

This strips query strings and lowercases the path.

Then create one more field in each source to strip trailing slashes so /blog/post/ and /blog/post both resolve to /blog/post:

`` REGEXP_REPLACE(Page Path, "/$", "") ``

Now both sources have a clean, comparable Page Path field you can use as the join key.

Step 3: Blend GSC and GA4 Data

Go to Resource > Manage Blends > Add a Blend. Configure as follows:

Left table: GSC URL Impression data source.
Right table: GA4 data source.
Join key: Page Path (the calculated field from both sources).
Join type: Left outer join so GSC pages with no GA4 session data still appear.
Dimensions to include: Page Path, Date (from GSC), Query (from GSC only, not blended).
Metrics to include: Clicks, Impressions, CTR, Average Position (GSC); Sessions, Engaged Sessions, Conversions (GA4).

Name the blend "GSC + GA4 by Page" and save. This blended source is what powers your page-level performance table.

Note: Do not blend at the Query level. Queries do not exist in GA4, so you will have a 0% match rate and empty rows. Keep query-level analysis in a separate, GSC-only table.

Step 4: Build the Core Dashboard Views

A functional SEO dashboard needs four views. Each can be a separate page in the same Looker Studio report.

View 1: Executive Summary

Top-line scorecards refreshed against the prior period. Include:

Total organic clicks (GSC)
Total impressions (GSC)
Average CTR (GSC)
Average position (GSC)
Organic sessions (GA4)
Organic conversions or goal completions (GA4)

Add date comparison scorecards showing the delta versus the same period last month or last year. Use a date range control so stakeholders can self-serve.

View 2: Keyword Performance Table

Source: GSC URL Impression data only (not blended).

Dimensions: Query. Metrics: Clicks, Impressions, CTR, Average Position. Sort by impressions descending by default. Add a filter control for page URL so users can scope to a single URL.

This is your cannibalization detection view. When one URL shows two competing queries with similar average position, you have a signal worth investigating. See how to use Google Search Console to find your highest-ROI SEO wins for the full analytical workflow.

View 3: Page Performance Table

Source: GSC + GA4 blended source.

Dimensions: Page Path. Metrics: Clicks, Impressions, CTR, Average Position, Sessions, Conversions. This view answers the most important question in SEO reporting: which pages rank and convert, and which rank but fail to convert (a UX or targeting problem, not an SEO problem).

View 4: Trend Lines

Two time-series charts on one page:

Line 1: Weekly clicks and impressions over trailing 12 months (GSC).
Line 2: Weekly organic sessions over the same window (GA4).

Overlay a vertical annotation line for any major algorithm update or site change. Do this manually by adding a reference line to the chart with a fixed date value.

Looker Studio data flow: GSC and GA4 each go through a calculated-field normalization step before joining on Page Path; query-level data flows from GSC directly to the keyword table without blending.

Step 5: The Metrics That Actually Matter (and the Ones to Cut)

Most SEO dashboards display too many metrics. Every metric you add creates cognitive load and reduces the chance that anyone acts on the data. Dashboard design research consistently finds that narrowing to the metrics that actually drive decisions, rather than cataloguing every available data point, leads to faster and more confident action from stakeholders.

The table below shows which metrics belong in the core dashboard versus which are optional context.

Metric	Source	Include in Core?	Why
Clicks	GSC	Yes	The only GSC metric that maps to real traffic
Impressions	GSC	Yes	Leading indicator of ranking gains or losses
Average CTR	GSC	Yes	Measures title/meta effectiveness across positions
Average Position	GSC	Yes	Directional rank signal; use as trend, not absolute
Organic Sessions	GA4	Yes	Confirms GSC clicks are landing, not a tracking gap
Engaged Sessions	GA4	Yes	Filters bots and bounces from raw session count
Conversions	GA4	Yes	Ties SEO to business outcomes
Organic New Users	GA4	Optional	Useful for awareness-stage content tracking
Bounce Rate	GA4	Optional	Deprecated metric in GA4; use Engagement Rate instead
Page Load Time	GA4	Optional	Better sourced from CrUX or Core Web Vitals directly
Backlink Count	Third-party	No	Looker Studio cannot pull this without a paid connector
Domain Rating	Third-party	No	Same; pull from Ahrefs API or export separately

For a deeper breakdown of which on-page signals correlate with rankings, see the 20 on-page SEO factors that still move rankings in 2026.

Step 6: Dashboard Filters and Controls Every SEO Needs

A static dashboard without interactive filters is a report, not a tool. Add these controls at the report level so they apply across all pages:

Date range control: Default to last 28 days with prior-period comparison. Add a second preset for last 90 days for trend reviews.
Country filter: Segment organic performance by geography, especially critical for sites targeting multiple markets.
Device filter: Desktop vs. mobile CTR and average position can diverge significantly after a mobile-first indexing change.
Page Path filter (text contains): Lets users scope to a subdirectory, for example /blog/ or /products/.

One control to avoid at the report level: a query filter. Query-level data does not exist in the blended source, so applying a query filter at the report level will break charts that rely on the GA4 data.

Step 7: Automate Alerts and Scheduled Delivery

Looker Studio's free tier does not support scheduled email delivery of reports. The two most reliable workarounds are:

Looker Studio Pro ($9/user/month): Adds scheduled delivery with PDF snapshots to email recipients on a configurable cadence.
Google Sheets + Apps Script: Export GSC and GA4 data into Google Sheets on a trigger, then reference the Sheets data in Looker Studio. The sheet refreshes automatically; stakeholders get a link to the live report rather than a PDF.

For agencies delivering reports to multiple clients, the Sheets approach also gives you a data audit trail: you can see exactly what numbers the client saw on any given date. See how to report SEO ROI so clients renew for the full client reporting framework.

Step 8: Know When to Upgrade Beyond Looker Studio

Looker Studio free is the right starting point, but it has hard limits that affect specific use cases.

Decision tree: start with Looker Studio free, upgrade to Pro for scheduling and org ownership, route through BigQuery when you need extended history or non-Google data sources, and move to a dedicated platform when multi-client management and approval workflows become the bottleneck.

The BigQuery route is the right answer when you need more than 16 months of GSC query data, sub-second dashboard load times on large sites, or joins with non-Google data like CRM conversions or paid search spend. For most SEO use cases, costs are modest: BigQuery offers a generous free tier (10 GB storage, 1 TB queries per month), and typical GSC data volumes fall well within it or cost only a few dollars monthly.

When Looker Studio hits its ceiling for teams: Looker Studio does not have a concept of SEO sprints, approval queues, or per-URL workflow state. It is a reporting and visualization layer, not a content operations platform. When your team needs to track which recommendations have been approved, which are in dev, and which shipped, you need something purpose-built. The Guru platform sits on top of your GSC and GA4 data and adds that workflow layer, including automated title scoring, an approval queue, and per-URL indexation tracking. Agencies managing more than five clients typically hit the ceiling of what Looker Studio can do within six months. See how Guru serves SEO agencies at scale.

Dashboard Setup Checklist

Use this before sharing your dashboard with stakeholders:

[ ] GSC connector authorized with correct property URL (prefix vs. domain property)
[ ] GA4 Landing Page custom dimension confirmed in GA4 Admin
[ ] Calculated Page Path field strips protocol, domain, and trailing slash in both sources
[ ] Blend verified with a spot-check: pick 3 URLs from GSC, confirm their session counts match GA4
[ ] Date range control added and defaulted to last 28 days
[ ] Country filter added at report level
[ ] Device filter added at report level
[ ] Query-level table uses GSC-only source (not blended)
[ ] Page-level table uses blended source
[ ] Trend charts cover at least 12 months
[ ] Report shared with view-only link (not edit access) for clients
[ ] Scheduled delivery configured (Pro) or Sheets-based workaround in place
[ ] GSC data freshness checked: data is typically 48 to 72 hours delayed, so yesterday's numbers are not final

Frequently Asked Questions

Why does my blended data show far fewer rows than my GSC data alone?

The most common cause is a URL normalization mismatch. GSC records full URLs including protocol and domain; GA4 records only the path. If your calculated Page Path fields do not strip and normalize both strings identically (same case, no trailing slash, no query parameters), the left outer join will produce many unmatched rows and the blended table will appear much smaller than the GSC-only table.

How far back can I pull GSC data in Looker Studio?

The native GSC connector in Looker Studio retains 16 months of query-level data. For longer historical windows, you need to export GSC data into BigQuery using the Search Console export connector in Google Cloud, then connect Looker Studio to the BigQuery table. Data exported to BigQuery is retained indefinitely as long as you pay storage costs.

Can I pull keyword ranking data from Ahrefs or Semrush into Looker Studio?

Yes, but not for free. Both Ahrefs and Semrush offer Looker Studio integrations, either bundled with higher-tier subscriptions or available via third-party connector platforms like Coupler.io. These add meaningful cost on top of the underlying tool subscription. For most sites, GSC average position is a sufficient rank proxy without the added cost.

Why do my Looker Studio charts go blank sometimes?

This is almost always a GA4 or GSC API quota issue. The GA4 connector makes live API calls each time the dashboard loads; large date ranges or many concurrent viewers can exhaust the daily quota, causing charts to return empty. Fix it by caching data in Google Sheets or BigQuery instead of querying the API live on every page load.

Should I use the "Site Impression" or "URL Impression" table type for GSC?

Use URL Impression for all page-level analysis. Site Impression aggregates data at the domain level and drops the page dimension entirely, which makes it useless for anything other than a single top-line click and impression scorecard. Add both connections to your report if you want both views.

Do I need Looker Studio Pro to share reports with clients?

No. Looker Studio free allows you to share reports via a view-only link with anyone who has a Google account, or publicly to anyone with the URL. Pro adds scheduled PDF delivery, organization-level ownership, and IAM-based permissions, but basic sharing is available on the free tier.

How often does the data refresh in Looker Studio?

By default, Looker Studio caches connector data for 12 hours. You can reduce the cache duration to 1 hour via Resource > Manage Added Data Sources > Edit > Freshness for each connector, but shorter cache periods increase API quota consumption. GSC data itself is delayed 48 to 72 hours from Google regardless of the Looker Studio cache setting.

When does a Looker Studio SEO dashboard stop being enough?

When you need to act on the data, not just view it. Looker Studio shows you what happened; it does not help you draft a title change, route it through an approval queue, or confirm the change shipped and got indexed. For those steps, you need a platform that connects reporting to operations. See how Guru approaches this workflow for the details.