GA4 for SEO: The Five Reports That Answer "Is It Working?"

Search Console tells you how you appear in Google. Google Analytics 4 tells you what happens after the click. To know whether SEO is working you need both, and in GA4 the answer lives in about five places. Everything else in the interface is either noise for this question or a trap that quietly misleads you.

This is the monthly routine, with the pitfalls marked.

Before any report: link Search Console

GA4 and Search Console can be linked, and once they are, two extra reports appear in GA4 that put search appearance and on-site behaviour side by side. Google's instructions are short: Admin, Product links, Search Console Links, pick the property, pick the web data stream. You need the Editor role in Analytics and verified ownership of the Search Console property.

Three things people miss:

• The reports are unpublished by default. After linking, go to Reports, Library, find the Search Console collection and publish it, or the reports will not appear in the navigation.
• Search Console keeps 16 months of data, so the linked reports show at most 16 months, and the data arrives about 48 hours after Search Console collects it.
• One web data stream links to one Search Console property. If your Search Console property is a domain property and your stream is a subdomain, make sure they cover the same pages, or the numbers will not line up.

Report one: Traffic acquisition, filtered to organic

Reports, Acquisition, Traffic acquisition. The default dimension is session default channel group; the row you want is Organic Search. This gives you sessions, engaged sessions, engagement rate, average engagement time and key events for organic visits over any period, with a year-over-year comparison a click away.

Use it for the headline: is organic traffic up or down against the same period last year, and is it producing key events (GA4's name for conversions since 2024). Do not use it for anything finer than that.

Trap: Organic Search is every search engine, not just Google. For Google alone, switch the dimension to session source / medium and look for google / organic. Trap two: a month-over-month comparison will mostly show you seasonality. Compare to the same month a year earlier.

Report two: Landing pages, organic only

Reports, Engagement, Landing page. Add a filter for session default channel group equals Organic Search, or use the comparison feature so you can see organic next to everything.

This is the report that tells you which pages are earning the organic traffic and what those visitors do. Sort by sessions to see where search sends people; sort by key events to see which pages turn searchers into enquiries. The gap between the two lists is your to-do list: pages with lots of organic sessions and few key events need a clearer next step, and pages with a high key event rate and few sessions deserve more visibility.

Trap: the (not set) landing page row. GA4 assigns a landing page from the first page_view in a session; if a session starts with an event that fires before the page_view, or the session timed out and resumed, the landing page is (not set). A small share is normal. A large share usually points to a tag firing order problem or a very long session timeout, and it means some of your organic sessions are being counted without a page.

Report three: Google Organic Search Traffic

This is one of the two reports the Search Console link adds. It shows landing pages with Search Console metrics (clicks, impressions, average position, click-through rate) next to Analytics metrics (users, engaged sessions, key events). It is the only place in Google's tools where "how many people saw and clicked this page in Google" sits beside "what they did afterwards".

Use it to find:

• Pages with high impressions and low clicks: a title or snippet problem, or an AI Overview answering the query. Cross-check in Search Console's generative AI report.
• Pages with good clicks and poor engagement: the page is not delivering what the result promised.
• Pages with strong key events per click: your most valuable organic pages, which should be the first to get internal links, refreshes and protection.

Trap: Search Console metrics here only combine with Search Console dimensions plus landing page, device and country. You cannot cut them by GA4 dimensions like city or user type, and there are no time-series charts in these reports. For trends, go back to Search Console itself.

Report four: Google Organic Search Queries

The second linked report: the queries from Search Console, with clicks, impressions, CTR and position, inside GA4. It is the same data you can see in Search Console, placed where the people who live in Analytics will actually look at it.

Use it to separate branded from non-branded demand. Filter the query dimension to contain your brand and watch impressions over time; that is a brand awareness meter. Everything else is the demand your SEO is competing for.

Trap: thresholding. Rows in reports that include search query information can be withheld when there are not enough users, and Google's data thresholds documentation says you cannot turn this off. Widening the date range usually brings the rows back. A query list that looks suspiciously short is probably thresholded, not quiet.

Report five: a key events exploration by landing page and channel

The standard reports answer most questions. One exploration earns its place: Explore, Free form, with landing page + query string and session default channel group as rows, and sessions, key events and session key event rate as values. Filter to Organic Search. Add the previous year as a comparison.

This gives you one table that says, per page: how many organic visits, how many enquiries, and how that compares to last year. It is the report to send to anyone who asks whether the SEO money is doing anything.

Trap: explorations sample on large data sets and only reach back as far as your event data retention setting, which for standard properties is 2 months by default and 14 months at most. If you want year-over-year comparisons in explorations, check Admin, Data settings, Data retention now, because the setting only affects data collected after you change it. Standard reports are not subject to the retention limit.

Traps that distort the whole picture

Key events that are not set up, or set up wrongly. If no key event is marked, every report above shows zeros and SEO "produces nothing". Mark the enquiry form submission, the quote request, the phone tap and the booking as key events, and only those; marking scroll depth as a key event makes everything look like it converts.

Attribution. GA4's default is data-driven attribution for key events, so a key event can be credited partly to organic and partly to paid or email. The session-scoped reports above count the key event in the session it happened in, which is usually what you want for "did this organic visit enquire". Know which one you are looking at before comparing numbers across reports.

Consent and modelling. In regions with consent banners, GA4 may model some behaviour from users who declined. Modelled data is flagged in the reports. It is useful for trends and dangerous for exact counts.

Internal traffic. Your own team visiting your pages from the office looks like direct or organic traffic unless you filter it. Define internal traffic in Admin and enable the filter.

Google signals thresholding. If Google signals are on, demographics and some other rows get thresholded in reports. Turning signals off removes the thresholding on those reports but also removes the demographic data, so it is a trade.

The monthly routine, in ten minutes

1. Traffic acquisition, Organic Search, versus the same period last year: direction of travel.
2. Landing pages filtered to organic, sorted by key events: where the business comes from.
3. Google Organic Search Traffic: pages with impressions but weak clicks or weak engagement.
4. Google Organic Search Queries filtered to brand: is awareness growing.
5. The key events exploration: the one table for the stakeholder.

Write down the three numbers that matter (organic sessions, organic key events, branded impressions) and the one page you are going to fix this month. That is the whole report.

Questions people ask

Why do GA4 organic sessions and Search Console clicks never match?

They measure different things. A click in Search Console is a tap on a result; a session in GA4 needs the page to load and the tag to fire, and one session can contain several clicks or none. Blocked scripts, consent declines and bounces before the tag loads all widen the gap. Treat them as two views, not one number.

Should I use Analytics or Search Console for keyword reporting?

Search Console. GA4 only sees queries through the link, with the same thresholds and a 48-hour delay. Use GA4 for what happens after the click and Search Console for what happens before it.

Do I need Data Studio or a dashboard tool?

Not to answer "is it working". The five views above do it. A dashboard helps when several people need the same numbers every month without logging in, which is a communication problem rather than an analytics one.

If you want this done for you

Setting up key events properly, linking Search Console and reading these five views each month is part of the reporting on every Ranked SEO project, and the same organic figures appear in the client reports alongside rankings and AI visibility. If your GA4 is showing zeros and you are not sure why, tell us and we will take a look.