GA4 for SEO: Organic Traffic
GA4 for SEO is the tool that shows what organic traffic does after the click: which pages people view and what actions they take. Search Console tells what came before the click: impressions, clicks and queries. Google's guide to using the two together puts it this way: the source of truth for Search performance is Search Console, while the source of truth for behavior inside your site is Google Analytics. It is a widespread belief that GA4 does not show queries, yet after linking a report with queries appears inside GA4. Let us see: what GA4 shows by itself, what appears after linking, and why the numbers do not match.
The basis is Google's guide to using Search Console and Google Analytics for SEO and the Analytics help page on the Search Console integration. On Search Console itself, see the lesson on GSC.
What each tool measures
- Search Console gives data on how the site performs in Google results: impressions, clicks, queries. It focuses on activity that happened before a person arrived at your website;
- Google Analytics gives visitors' interactions with the site: which pages they visit, how long they stay, what actions they take; and where the audience comes from, to measure the effectiveness of channels: email, referrals from other sites, social platforms, paid and organic search.
Which GA4 measures matter for SEO
| Measure | What it means for SEO |
|---|---|
| Sessions | the volume of traffic attributed to organic search. A session starts when a user views a page and no session is active |
| Engagement rate | the share of sessions that engage with your content; an assessment of traffic quality |
| Returning users | show whether people come back to the site through organic search |
| Key events | actions that matter to you: a purchase, a lead, a subscription |
An engaged session is one that meets any of these criteria: it had a key event, lasted longer than 10 seconds or had 2 or more page views. Note that instead of the familiar word "conversions", Google's guide calls such actions "key events".
How to isolate organic search in GA4
Google suggests two reports:
- The Traffic acquisition report. It shows how many sessions originated from the channel "Organic Search" and the source "Google", which actions people took and whether they eventually made a purchase or subscribed;
- The Landing page report with a filter for sessions from google organic. It shows how useful the page is to organic traffic and how well it drives engagement and conversions.
For such filters, Google's ready-made dashboard uses the conditions "session source = google" and "session medium = organic". If your filter differs, you may be looking at a different set of data than the one you compare against.
Linking to Search Console: two reports inside GA4
This is what linking changes. After it, Analytics gets two reports:
- "Google Organic Search Queries" displays search queries and associated Search Console metrics for the linked property. You can drill into Search Console dimensions, but not Analytics dimensions;
- "Google Organic Search Traffic" displays landing pages with associated Search Console and Analytics metrics; you can drill into country and device.
Conditions and caveats from the help page:
- Permissions. You need the Editor role on the Analytics property and to be a verified owner of the Search Console property. Link under Product links, Search Console Links;
- The collection is unpublished by default. Find it under Library and publish it;
- Compatible dimensions. Search Console metrics work only with Search Console dimensions and three Analytics dimensions: landing page, device, country;
- Depth. Search Console keeps data for 16 months, so Analytics has at most 16 months; data appears 48 hours after collection;
- One to one. A web data stream can be linked to only one Search Console property and vice versa;
- The same set of pages. Make sure both properties collect data for the same pages;
- Search Console reports don't support time-series charts, and a link can't be edited: delete it and create a new one.
Why clicks and sessions don't match
The most comparable measures are clicks in Search Console and sessions in Analytics, but they are calculated differently, so the numbers will differ. What matters is that the general trends match. A small difference can be ignored; a big one calls for finding the reasons. Google lists them:
- Implementation. Analytics collects data through a tag, and it may be missing on some pages; Search Console processes Search data uniformly for all properties;
- Cookies and consent. If visitors opt out of tracking, Analytics data is skewed;
- Time zone. In Analytics you choose it, in Search Console the default is Pacific Time, noticeable for sites with a big offset;
- Attribution. Analytics has three models, while Search Console counts every click in Search;
- Canonical URLs. Search Console reports on the canonical URL, Analytics on any URL that includes the tag, so there are usually more URLs in it;
- Result types. Search Console splits web, image, video, news and Discover, while Analytics breaks them down differently;
- Non-HTML pages. PDFs, for example: Search Console includes them if shown or clicked, while Analytics may not measure them;
- Bots. Analytics automatically excludes known bots, while Search Console doesn't necessarily filter them out.
For comparison it is recommended to pick the same country and device filters in both sources. Search Console data can be delayed by a couple of days.
Seeing both sides together
- Looker Studio. Google gives a dashboard template with Search Console and Analytics data side by side: sessions and engagement, clicks and CTR, top pages and queries, countries. The dashboard's goal is to spot a change quickly, not to analyze it in depth;
- BigQuery. To get the most detail and minimize discrepancies, it is recommended to export Search Console data to BigQuery and merge it with the Analytics export;
- our performance analyzer joins URLs from Search Console and GA4 and shows clicks, impressions, CTR, position and revenue, the query-to-conversion bridge matches queries with outcomes, and you can pull data with the Search Console export.
What is not in the documentation
- A claim that GA4 "does not show queries": after linking they are in the "Google Organic Search Queries" report;
- Menu paths such as "Explore, Free form" as the recommended SEO route: Google names other reports;
- An expectation that clicks and sessions will be equal.
How to use this in practice
- Link Search Console and GA4 and publish the collection of reports.
- For organic, look at the acquisition report for the Organic Search channel and the landing page report filtered to google organic.
- Watch two pairs of numbers together: sessions and engagement, clicks and CTR.
- With a big gap check the listed reasons: tag, consent, time zone, canonical URLs.
- For a sharp change go to Search Console and break it down by query and page: see the lesson on traffic drops. Measures for reporting are in the lesson on SEO KPIs.
Checklist
- Search Console and GA4 are linked and the report collection is published.
- Organic traffic is isolated by the Organic Search channel and the Google source.
- The same country, device and period are chosen for comparison.
- It is understood that clicks and sessions won't match, and trends are compared.
- Key events are set for actions that matter to the business.
- I look at queries in Search Console or in the queries report inside GA4.
Mistakes
- Believing GA4 never shows queries.
- Demanding an exact match of clicks and sessions.
- Comparing data with different country and device filters.
- Forgetting to publish the Search Console collection.
- Judging the quality of organic by sessions alone.
What comes next
Next is Search Console in depth: the performance report and its possibilities. An introduction to the tool is in the lesson Google Search Console.