TL;DR A useful SEO dashboard answers three questions: are we visible, does that visibility bring visitors, and do those visitors do what the business needs. Search Console answers the first, GA4 the other two. Build it from a short list of SEO KPIs, a few organic reports in GA4, the Search Console collection, and one panel that tells you whether the data is right. Without that last panel, the dashboard is only as good as your tracking on the day you read it.
Most SEO dashboards fail the same way: thirty charts, no question behind any of them, and a meeting spent arguing about why GA4 and Search Console disagree. A good one is short. Every number on it maps to a decision, and the people reading it trust that the numbers are real.
This guide covers how to use GA4 for SEO, which KPIs belong on the dashboard, how to build it in GA4 and in Looker Studio, and the checks that keep it honest.
What GA4 is for in SEO
GA4 and Search Console split the job at the click.
- Search Console sees everything before the click: impressions, clicks, click-through rate, position, queries and indexing. It knows nothing about what visitors do on your site.
- GA4 sees everything after the click: the landing page, engagement, key events and revenue. It does not know the query, and it only knows a visit came from Google if the referrer says so.
So the questions GA4 answers for SEO are about value: which landing pages bring organic visitors who engage and convert, which content earns traffic but no business, and which pages lose visitors as soon as they arrive. Linking the two tools puts queries and landing pages next to those outcomes. How to set that up is in our guide to integrating Search Console with GA4.
The SEO KPIs worth reporting
Pick a few from each group. If a number does not change a decision, leave it off.
| Group | KPI | Source | Why it matters |
|---|---|---|---|
| Visibility | Impressions and clicks, non-branded | Search Console | Branded demand is not SEO performance; split it out |
| Visibility | Click-through rate by page or query | Search Console | Low CTR at a good position means the title or snippet is not winning the click |
| Visibility | Average position for a tracked set of queries | Search Console | A trend for queries you care about; a site-wide average hides everything |
| Traffic | Sessions and engaged sessions from google / organic | GA4 | The visits search actually brings, comparable with Search Console clicks |
| Traffic | Organic sessions by landing page | GA4 | Where SEO traffic arrives, which is where you act |
| Traffic | AI Assistant channel sessions | GA4 | Visits from ChatGPT, Gemini and other assistants, reported as a floor |
| Results | Organic key events and conversion rate | GA4 | Whether organic traffic does what the business needs |
| Results | Organic revenue, or lead value | GA4 | The number leadership asks about |
| Health | Indexed pages for important templates | Search Console | Pages that cannot rank because they are not in the index |
| Health | Core Web Vitals pass rate | Search Console, real-user data | Page experience, by template and device |
Report each one against the previous period and the same period last year, so seasonality does not look like a trend.
Build the dashboard in GA4
GA4's own reports are enough for a working SEO dashboard, and they need nothing outside Google Analytics.
1. Publish the Search Console collection
After you link Search Console to GA4, go to Reports > Library, find the Search Console collection and publish it. It adds two reports to the navigation: Queries, with impressions, clicks, CTR and position by query, and Google organic search traffic, with Search Console metrics and GA4 engagement by landing page. These reports show Search Console's numbers next to GA4's; they do not reconcile them.
2. Create an SEO collection
In Reports > Library, create a new collection called SEO and add:
- Traffic acquisition, with a filter on Session default channel group · Organic Search, or on Session source / medium ·
google / organicwhen you want only Google. - Landing page, filtered the same way, with sessions, engaged sessions, key events and revenue.
- The two Search Console reports.
Publish the collection so everyone on the property sees the same view. Editing the Library needs the Editor role.
3. Add explorations for the questions reports cannot answer
Use Explore > Free form for the analysis you run every month:
- Landing pages by device, organic only, with engaged sessions and key events, to find templates that work on desktop and fail on mobile.
- New versus returning organic visitors by landing page, to see which content brings people back.
- Organic landing page performance over time, with a line chart by week, to catch a page that stopped bringing traffic.
When the standard reports fall short, our guide to custom reports in GA4 goes further.
Build the stakeholder view in Looker Studio
GA4 is where analysts work. A dashboard for stakeholders is usually one page that mixes sources, which is what Looker Studio does well.
- Add three data sources: GA4, Search Console with the Site impression table (totals by query), and Search Console with the URL impression table (totals by page).
- Top row: scorecards for non-branded clicks, organic sessions, organic key events and organic revenue, each with a comparison period.
- Middle: trends. Clicks and organic sessions on the same time series, so a gap between them is visible at a glance.
- Bottom: tables. Landing pages with clicks, sessions, engagement and key events; queries with impressions, CTR and position.
- Filters for date, device and country at the top, applied to every chart.
Keep it to one page. A second page is where nobody looks.
Add a data-quality panel
Every number above depends on tracking that works. When it breaks, the dashboard does not show an error; it shows a drop, and the team spends a week explaining a ranking loss that never happened. A small panel catches that first:
- Search Console clicks versus GA4 organic sessions. The two never match, but the ratio between them is stable. A sudden change means tracking, not rankings. Why they differ.
- Share of organic sessions with landing page
(not set). A rise means sessions without a page view, often a tag or consent problem. - Share of Direct sessions on deep pages. Visitors rarely type a product URL. A rise often means a referrer is being lost.
- Organic key events per session. A sudden fall with steady traffic usually means a conversion tag broke, not that visitors changed.
If any of them moves, check the data before you report the trend. Diagnosing an organic traffic drop covers the order of the checks.
Keep the dashboard true between reviews
A dashboard is read once a week or once a month. Tracking breaks on any day a release, a tag manager publish or a consent change ships. Trackingplan watches that side continuously: it reads the hits your site sends and shows landing pages, referrers, sources and mediums from your real visitors, independent of how GA4 processes them, with warnings on the landing pages and referrers you choose. It also tracks Core Web Vitals on real users. The dashboard tells you what happened; the monitoring tells you whether to believe it.
An SEO dashboard is a promise that the numbers on it are right. Build it short, build it around decisions, and check the data underneath before every review.
Frequently asked questions
What should an SEO dashboard include?
Four groups of numbers: visibility from Search Console (impressions, clicks, click-through rate, position), organic traffic from GA4 (sessions and engaged sessions from google / organic, by landing page), business results (key events, conversion rate and revenue from organic), and technical health (indexed pages and Core Web Vitals). Add a small data-quality panel so you know the numbers are right.
What are the most important SEO KPIs?
Non-branded clicks and impressions from Search Console, organic sessions and engaged sessions by landing page, organic key events and revenue, and the share of important pages that are indexed and pass Core Web Vitals. Average position is useful as a trend for a set of queries, not as a single site-wide number.
Can you build an SEO dashboard in GA4 without Looker Studio?
Yes. Link Search Console to GA4, publish the Search Console collection, and create a custom collection in the Library with a traffic acquisition report filtered to organic search and a landing page report. Use explorations for deeper questions. Looker Studio is better when you need one page that mixes GA4, Search Console and other sources for stakeholders.
How do I use GA4 for SEO?
Use it for what happens after the click: which landing pages organic visitors arrive on, whether they engage, and whether they convert. Search Console covers what happens before the click. Linking the two puts queries and landing pages next to engagement and conversions, which is where most SEO decisions are made.