GSC vs GA4: Which Metrics Actually Matter for SEO

Google Search Console and Google Analytics 4 both report on organic search, and their numbers almost never match. That is not a bug. Google describes the difference simply: Search Console covers what happens before someone reaches your site from Google Search, and Analytics covers what they do after they arrive. This guide explains what each tool measures, why the numbers differ, which metrics belong in an SEO report, and how to use the two together.

The short version

What Search Console measures

Search Console’s Performance report shows how your site appears in Google Search: impressions, clicks, click-through rate and average position, by query, page, country, device and search appearance.

• Position is the topmost position your site held for a query, averaged across queries. Each element on the results page counts as one position: a featured snippet typically occupies position 1, and an AI Overview takes a single position shared by every link inside it. See how Search Console counts impressions, position and clicks.
• AI features are included. Google says traffic from AI Overviews and AI Mode is part of the overall search traffic in Search Console.
• Some queries are hidden. To protect privacy, Search Console omits anonymized queries, those not issued by more than a few dozen users over two to three months, from its tables, while still counting them in the chart totals. That is why the rows rarely add up to the total.
• It reports canonical URLs and uses Pacific Time, and it keeps data for the last 16 months.

What it cannot tell you: what visitors did after they clicked, or anything about Bing and other search engines.

What GA4 measures

GA4 measures what happens on your site, for every channel. For SEO, the useful parts are:

• Sessions from the Organic Search channel. In GA4’s default channel group, Organic Search covers non-ad links in organic search results, including Google’s AI Overviews and AI Mode, from search engines in general, not only Google.
• Engaged sessions and engagement rate. GA4 counts a session as engaged if it lasts longer than 10 seconds, has a key event, or has 2 or more page or screen views. Bounce rate is simply the opposite: the share of sessions that were not engaged.
• Key events and revenue from organic visitors: sign-ups, purchases, leads, whatever you mark as a key event.
• Landing pages, to see which pages people enter the site on from search and what they do next.

What it cannot tell you: why a page ranks or does not, which queries brought people in (unless you connect Search Console), or anything about visitors whose visits were not recorded.

Why the numbers never match

Google’s own guide to using Search Console and Google Analytics together says clicks and sessions are calculated differently, so the totals will not match; what matters is that the trends follow the same pattern. A small gap is normal and nothing to fix. For a large gap, Google lists these causes:

• Analytics implementation: pages where the GA4 tag is missing or misconfigured. Search Console needs no tag.
• Cookies and consent: if visitors decline tracking, GA4 records less of their activity.
• Time zone: Search Console uses Pacific Time; GA4 uses the one you set.
• Attribution: GA4 applies an attribution model, while Search Console counts every click.
• Canonical URLs: Search Console reports only the canonical URL; GA4 reports every URL with the tag, so it shows more URLs.
• Traffic breakdowns: Search Console splits web, image, video, news and Discover differently from GA4.
• Non-HTML files: PDFs clicked in Search appear in Search Console but may not be measured in GA4.
• Bots: GA4 excludes known bots automatically; Search Console does not necessarily filter them.

Add to that the anonymized queries Search Console leaves out of its tables, and that GA4’s Organic Search includes other search engines. Compare the two only after filtering GA4 to Google.

The metrics that belong in an SEO report

From Search Console: visibility

• Clicks from Google Search, the clearest measure of the traffic Google sends.
• Impressions for the queries you target, to see whether your pages are being shown at all, often before clicks move.
• Click-through rate by query and page, to find pages that are shown but rarely chosen, usually a title or description problem.
• Average position as a trend for a defined set of queries, rather than a single site-wide number.

From GA4: value

• Engagement rate of organic landing pages, to see whether visitors found what the result promised.
• Key events and revenue from organic search, the business case for the work.
• Top organic landing pages by sessions and key events, to see which content earns its keep.

Combined: where to act

• High impressions, low CTR in Search Console: rewrite the title and description. See title tag length and meta descriptions.
• Good CTR, low engagement in GA4: the page does not deliver what the query expected. Rework the content or the target query.
• Falling clicks with stable rankings: check whether a featured snippet or AI Overview now answers the query. See featured snippets and AI Overviews.
• A large gap between clicks and sessions on one page: check that page’s GA4 tag first.

Segment GA4 correctly

• For Google only, filter sessions by source google and medium organic; the Organic Search channel also includes Bing and other engines.
• Mind the date range and time zone when you put the two side by side, especially for daily figures.
• Report trends, not exact matches. Compare month over month or year over year in each tool, and explain the difference in method once rather than every month.

A monthly routine with both tools

1. Search Console, Performance report: compare the last 28 days with the previous period and with the same period last year. Note the queries and pages with the biggest changes in clicks and impressions.
2. Search Console, Page indexing report: check whether important pages have dropped out of the index, and why.
3. GA4, organic landing pages: for the pages that changed most in step 1, check sessions, engagement rate and key events. A page that gained clicks but lost key events needs a different fix from one that lost clicks.
4. Sanity check the gap: if Search Console clicks and GA4 Google organic sessions moved in opposite directions, look for a tracking change first: a new consent banner, a tag removed in a redesign, a changed time zone.
5. Pick three actions for the coming month, such as rewriting two titles with low CTR and updating one page that lost engagement, and record them so next month’s report can show the result.

The routine takes under an hour once the reports are set up, and it keeps the conversation on what changed and what you are doing about it, rather than on why two tools show different numbers.

Putting them in one report

Google offers a Looker Studio dashboard template that combines Search Console and Analytics data for organic search, and recommends exporting both to BigQuery if you need the most detail with the fewest discrepancies. For client work, keep the report short: a few visibility metrics from Search Console, a few value metrics from GA4, and a plain-language note on what changed and what you will do next. Our guide to building a monthly SEO report covers the format, with a template you can copy.