GA4 for SEO: How to Build Reports for Organic Search Traffic

Maybe you want to know how many visits Google and other search engines sent you, and what those visitors did next. The answer sits in a GA4 organic search report that you build yourself. Open Reports > Acquisition > Traffic acquisition, filter on Session default channel group = Organic Search, and you have the core view. Everything else in this guide builds on that one filter.

GA4 does not come with a ready-made “SEO report”. That is why so many marketers end up looking at the wrong numbers. Below I walk through the reports I find worth using, how to link Search Console, how to keep AI assistant traffic separate, and the mistakes that quietly twist organic data.

What GA4 Counts as Organic Search

GA4 sorts every session into a channel. It uses rules in its default channel group to do this. A session goes into Organic Search when its source is on Google’s list of search sites, or when the medium is exactly organic.

That list covers far more than Google. Bing, DuckDuckGo, Yahoo, Ecosia, Baidu and Yandex all count. So the channel total means “all unpaid search engines”, not “Google”. Google’s help page on default channel groups lists the exact rules and links to the full source list.

A few nearby channels are easy to confuse with it:

• Organic Shopping: shopping sites and free listings from Merchant Center, not regular search results.
• Organic Video: sources such as YouTube, even though people “search” there.
• Organic Social: social networks.
• Paid Search: Google Ads and other paid search traffic. This never belongs in an SEO report.

Clicks from Google’s AI features, such as AI Overviews, arrive as normal Google organic visits. GA4 has no separate dimension for them. So do not expect to split them out here.

Which Channel Dimension to Use

GA4 has several channel dimensions that look alike but answer different questions. A dimension is just a way to label and group your data. Picking the wrong one is the most common reason I see two people’s organic numbers not match.

• Session default channel group: the channel that started each session. Use this for organic traffic reports.
• First user default channel group: the channel that first brought in each user. This is what the User acquisition report shows. It will be lower for organic, because returning visitors keep their first channel.
• Default channel group: the channel given credit for a key event under your attribution settings. It shows in the Advertising section and in key event analysis.

Once you create a custom channel group, you will also see Session primary channel group. That shows whichever group you have set as primary, which may not be the default one.

Building Your GA4 Organic Search Report in Traffic Acquisition

Traffic acquisition is where I always start. It is based on sessions, and it shows engagement and key events by channel. Here is how to turn it into an organic-only view.

1. Go to Reports > Acquisition > Traffic acquisition. In some properties it sits under a “Life cycle” heading.
2. Click Add filter under the report title.
3. Choose the dimension Session default channel group, set the match type to exactly matches, and pick Organic Search.
4. Click Apply. The table and charts now show organic sessions only.
5. Change the main dimension in the table to Session source to split Google from Bing and other engines.

The metrics I watch are sessions, engaged sessions, engagement rate, average engagement time per session, key events and session key event rate. Engagement rate tells you if search visitors stayed. Key events tell you if they did anything useful.

A filter like this is temporary. If you want to save the view, an Editor or Administrator can click the pencil icon, add the filter and save it as a new report. Add that report to a collection in the Library so it shows in the left menu for everyone.

A Practical Example

Say someone asks you why leads fell last month. In the filtered report, set the date range to the last 28 days and compare it with the period before. If organic sessions held steady but key events dropped, the problem is likely on the site, such as a broken form. If sessions fell first, look at rankings and Search Console.

See Which Pages Earn Organic Traffic With the Landing Page Report

Channel totals tell you how much traffic arrived. The Landing page report tells you where it arrived. For SEO choices, that is usually what you need.

1. Go to Reports > Engagement > Landing page. If it is missing, an Editor can add it back to the menu through the Library.
2. Add the filter Session default channel group exactly matches Organic Search.
3. Sort by sessions to see your top organic entry pages.
4. Click the + next to the dimension heading to add Session source / medium as a second dimension, if you want to check engines page by page.

The landing page dimension shows the path of the first page seen in a session. Use this report to spot pages that pull in searchers but have low engagement or no key events. In my experience, these are often quick wins. The ranking is already there, but the page is not doing its job.

If you are checking the effect of an algorithm change, this is the report to run before and after. Our guide on reading your June 2025 core update results covers how to set those date ranges sensibly.

Track Key Events From Organic Search

Traffic without results is a vanity number. Key events are GA4’s name for the actions you mark as important. Examples are a purchase, a lead form sent or a booked call. Google renamed them from “conversions” in March 2024.

Before organic reports can show results, you have to mark the right events. In Admin > Data display > Events, click the star next to an event to mark it as a key event. The change counts from that point on, not for past data.

Once events are marked, the Traffic acquisition and Landing page reports show key events and session key event rate for organic visitors. You can pick one key event from the dropdown in the metric column header, instead of seeing the total across all of them.

Keep the list short. I’d only mark actions that matter to the business. If a thank-you page view and a scroll event are both marked, your organic “results” will look too high and mean very little.

Link Search Console to GA4 and Publish Its Reports

GA4 shows what happened after a visitor arrived. Search Console shows what happened before the click: searches, impressions, clicks and average position in Google. Linking the two puts both in one place.

You need the Editor role on the GA4 property. You must also be a verified owner of the Search Console property. Then follow these steps.

1. In GA4, go to Admin > Product links > Search Console links.
2. Click Link, then Choose accounts and pick the Search Console property you own.
3. Click Next and pick the web data stream for the site.
4. Check the settings and click Submit.
5. Go to Reports > Library, find the Search Console collection, open its menu and click Publish. The collection is unpublished by default. That is why many people link the accounts and then cannot find the reports.

The collection holds two reports:

• Queries: Google searches with clicks, impressions, CTR (click-through rate) and average position.
• Google organic search traffic: landing pages with Search Console metrics next to GA4 metrics such as engagement and key events.

Google’s help page on Search Console integration lists the full rules and limits.

Limits to Know Before You Rely on It

• One web data stream links to one Search Console property, and the other way round too.
• Search Console metrics only combine with Search Console dimensions and the GA4 dimensions landing page, device and country.
• Data shows up about 48 hours after Search Console collects it. History goes back 16 months at most.
• The data covers Google only. Bing and other engines will not show in these two reports.
• You cannot edit a link. To change it, delete it and make a new one.

Expect Search Console clicks and GA4 organic sessions to differ. One counts clicks on Google results. The other counts sessions GA4 recorded after consent and tag loading. I treat them as two views of the same traffic, not numbers that should match.

Go Deeper With Explorations

Standard reports are good for regular checks. Explorations are better when you have a specific question. For example: which organic landing pages lead to purchases on mobile?

1. Go to Explore and start a Free form exploration.
2. Under Dimensions, import Session default channel group, Landing page + query string, Session source and Device category.
3. Under Metrics, import Sessions, Engaged sessions, Engagement rate and Key events.
4. Drag the landing page dimension into Rows and the metrics into Values.
5. Add a filter: Session default channel group exactly matches Organic Search.
6. Drag Device category into Columns to see desktop and mobile side by side.

Two other exploration types help with SEO. Path exploration shows where organic visitors go after their landing page. Segment overlap shows how many organic users also come through other channels.

One warning: explorations are limited by your data retention setting. For standard properties this is either 2 or 14 months. Standard reports are not affected. Check Admin > Data collection and modification > Data retention. I set it to 14 months on every property, so year-on-year explorations work.

Use Comparisons Instead of Rebuilding Reports

Comparisons let you see organic traffic next to other traffic in the same report, without changing filters. When you want context, they are quicker than filters.

1. Open any standard report, such as Landing page.
2. Click the comparison icon near the date range at the top right.
3. Click Create new, choose Session default channel group, set it to Organic Search and apply.
4. Add a second comparison for another channel, such as Paid Search or Direct.

Each comparison shows as its own coloured line in charts and its own row in tables. Editors can save comparisons in Admin > Data display > Comparisons so anyone on the property can use them again.

Add a date comparison too. Then you can answer questions like “did organic grow faster than paid this quarter?” on one screen.

Separate AI Assistant Referrals With a Custom Channel Group

Visitors who click links in ChatGPT, Perplexity, Gemini, Copilot or Claude are not organic search traffic in GA4. When a referrer (the site a visitor came from) is passed, they usually land in Referral. When it is not, they fall into Direct. Either way, they are mixed in with everything else.

The default channel group has no AI channel, so build one. A standard property can have two custom channel groups. They apply to past data as well as new data. You need the Editor role.

1. Go to Admin > Data display > Channel groups.
2. Copy the default channel group and give the copy a name such as “Channels with AI”.
3. Click Add new channel and name it “AI assistants”.
4. Set the condition to Source, matches regex, using a pattern like the one below.
5. Save the channel, then click Reorder and move “AI assistants” above Referral. GA4 gives traffic to the first channel that matches, so order matters.
6. Save the group. It will show as a dimension in acquisition reports and explorations.

.*(chatgpt.com|chat.openai.com|perplexity.ai|gemini.google.com|copilot.microsoft.com|claude.ai).*

Check the pattern every few months against your Referral source list, since new assistants and domains appear. AI browsers and agents are changing how these visits show up. Our pieces on Perplexity’s Comet browser and ChatGPT agent explain what to watch for.

Keep this group separate from your organic report. Don’t merge AI traffic into Organic Search. The two behave differently, and mixing them makes trends harder to read.

Common Mistakes in GA4 Organic Reporting

Most bad organic reports I see come from a handful of repeat mistakes.

• Using User acquisition for SEO totals. It credits the first channel a user ever came from. So it undercounts organic sessions from returning visitors.
• Reading “Organic Search” as “Google”. Add Session source to check the split before you report a Google trend.
• Looking for Search Console reports that are not published. Linking is not enough. The collection must be published in the Library.
• Forgetting the processing delay. Search Console data in GA4 is about two days behind, so the last couple of days always look low.
• Trusting “(not set)” landing pages. These usually come from sessions without a page view, such as sessions that started from a background event. A high share points to a tagging problem worth fixing.
• Ignoring Unassigned traffic. Sessions that match no channel rule end up there. Odd UTM tags on internal links are a common cause.
• Tagging internal links with UTM parameters. This starts a new session with the UTM source and takes credit away from organic.
• Not filtering internal traffic. On small sites, your own team searching for the brand name and clicking through pushes organic numbers up.

Sometimes organic traffic suddenly drops to near zero in GA4 while Search Console looks normal. When that happens, I check tagging and consent setup first. That pattern almost always points to measurement, not rankings.

Putting Your GA4 Organic Search Report Together

A useful GA4 organic search report does not need to be complex. Start with Traffic acquisition filtered to Organic Search. Add the Landing page report with the same filter. Mark the key events that matter. Then publish the Search Console collection so you can see searches next to results.

From there, save comparisons for quick context, use Explorations for one-off questions, and keep AI assistant visits in their own custom channel. Set those up once. Then your monthly SEO reporting is just a matter of checking the same few views.