How to Check Organic Traffic in GA4 (Step by Step)

Open GA4 and go to Reports → Acquisition → Traffic acquisition. The row labelled Organic Search is your organic traffic. That's it. Everything else in this article is about making that number useful: which pages earned it, whether it's growing, and why it will never match Search Console.

I check this report on our own Shopify store blogs most mornings, and I've walked a lot of merchants through it after they installed GA4, saw a wall of cards, and closed the tab. GA4 is not hard. It's just badly signposted.

How do you check organic traffic in GA4?

Four clicks, start to finish:

1. Sign in at analytics.google.com and pick the correct property from the dropdown at the top. If you run a Shopify store and a separate marketing site, these are usually two properties. Grabbing the wrong one is the single most common reason someone tells me their traffic "collapsed".
2. In the left sidebar, click Reports (the bar-chart icon), then Acquisition, then Traffic acquisition.
3. Set your date range in the top right. Default is the last 28 days. I'd start with Last 90 days so seasonality doesn't fool you.
4. Read the Organic Search row. The columns you care about are Sessions, Engaged sessions, Average engagement time, and Key events.

A note on the two similarly named reports. User acquisition tells you how people first found your site ever. Traffic acquisition tells you how they arrived in this particular session. For "how much traffic did search send me last month", you want Traffic acquisition. Almost always.

One thing that trips people up: Organic Search in GA4 is not Google-only. Bing, DuckDuckGo, Yahoo, Ecosia and a long tail of others all land in that bucket. For most Shopify blogs Google is 85–95% of it, but if you sell into markets where Bing has real share, the gap between GA4 and Search Console will be wider than average.

How do you filter GA4 to only organic search?

Reading one row in a table is fine for a headline number. To actually work with organic traffic you want the rest of the report filtered down to it.

Click Add comparison + at the top of any report. Set the condition to Include → Session default channel group → exactly matches → Organic Search, then Apply. Now every report you navigate to keeps that comparison alive: Pages and screens, Landing page, Demographics, Tech. This is the fastest way to answer "which blog posts do people find through search" without building anything.

If you want a stricter cut, swap the dimension for Session source / medium and match google / organic. That isolates Google only, which is the apples-to-apples version when you're comparing against Search Console.

Save the comparison by clicking the bookmark icon next to the report title if your role allows it. Otherwise it resets when you leave, and you'll be rebuilding it every Monday.

How do you see which pages get your organic traffic?

Sessions by channel is a vanity number on its own. The useful view is organic sessions by landing page, because that tells you which article is actually doing the work.

With the Organic Search comparison still applied, go to Reports → Engagement → Landing page. You'll get a list of entry URLs with sessions, engagement rate, and key events, filtered to organic. Sort by Sessions descending.

Here's what that looked like for a home-fragrance store we worked with. Their blog had 34 posts. Filtered to organic, three posts accounted for 61% of all organic blog entries; eighteen posts had fewer than 10 organic sessions in 90 days. That's not a traffic problem, it's a distribution problem, and you can only see it in the landing-page view. They cut new publishing in half and spent the time expanding the three winners into proper guides with internal links to their collections. Organic blog sessions went from roughly 1,400/month to 3,900/month over the following two quarters.

If you want the same diagnosis without touching GA4, our Blog Potential Analyzer crawls your Shopify blog and flags which posts have the structure and depth to earn search traffic and which are thin filler. It's a decent sanity check before you decide what to rewrite.

How do you compare organic traffic between date ranges?

Click the date range in the top right. Toggle Compare on, and pick Preceding period or Same period last year. GA4 will show both numbers plus the percent change under each metric.

Which one you pick matters more than people think. Preceding period is the right choice for "did last month's changes work". Same period last year is the right choice for anything seasonal, which for ecommerce is basically everything. A candle store comparing November to October will always look like a genius.

Two practical cautions. First, GA4 fills in yesterday's data over the following 24–48 hours, so a rolling 7-day comparison always shows a fake decline on the last day. End your ranges two days back. Second, if you migrated from Universal Analytics, you have no comparable pre-2023 data, and GA4's session definition is different anyway. Don't try to bridge that gap; start your trend line where GA4 starts.

How do you build an organic-only exploration in GA4?

Standard reports get you 80% of the way. When you need two dimensions at once, use an exploration.

Go to Explore in the left sidebar and choose Blank. Then:

1. Under Variables, click + next to Dimensions and import Landing page + query string, Session default channel group, and Session source / medium.
2. Click + next to Metrics and import Sessions, Engaged sessions, Average engagement time per session, and Key events.
3. Drag Landing page + query string into Rows. Drag your metrics into Values.
4. At the bottom of the Settings column, under Filters, add: Session default channel group → exactly matches → Organic Search.
5. Set Show rows to 100 or 250, set your date range, and rename the tab something like "Organic landing pages".

Now you have a saved, reusable organic-only report you can export to CSV or Sheets. Add Session source / medium as a second row dimension if you want to see how much of each page's traffic comes from Bing versus Google. Explorations are stored per-user by default, so share them explicitly if your team needs access.

For a fuller tour of GA4's reporting model, including events and key events setup, see our GA4 guide for bloggers. If you just want the short Shopify-specific version, we keep a walkthrough of checking blog traffic in GA4 in the help centre.

How do you connect Search Console to GA4?

Linking the two puts query data inside GA4, which saves a lot of tab-switching.

You need Edit access on the GA4 property and verified owner status on the Search Console property. Then: Admin → Product links → Search Console links → Link. Choose the Search Console property, choose the web data stream to associate it with, review, submit.

That's only half the job, and the half everyone forgets is the second one. The Search Console reports stay unpublished until you enable them: Admin → Data display → Reports (this opens the Library), find the Search Console collection, click the three-dot menu, and hit Publish. Now Reports → Search Console → Queries and Google organic search traffic appear in the sidebar.

On the Shopify side, make sure GA4 is actually collecting in the first place. In your Shopify admin go to Settings → Apps and sales channels → Google & YouTube → Settings, and connect your Google account and GA4 property there. The old Online Store → Preferences analytics field is legacy and doesn't handle GA4 properly. If you'd rather control the tag yourself, Settings → Customer events → Add custom pixel lets you drop a GA4 pixel in with full consent-mode control, but only do that if you're comfortable writing the event mapping yourself. Running both at once double-counts everything.

Why don't GA4 and Search Console numbers ever match?

Because they measure different things at different points in the journey. Expecting them to agree is like expecting your till receipts to match your footfall counter.

Search Console counts a click the moment someone clicks your result on Google. GA4 counts a session only if the page loaded, the tag fired, and the visitor didn't block or decline it. Every gap between those two events is lost data. In our own properties GA4 organic sessions typically run 10–30% below Search Console clicks, and I treat anything inside that band as normal.

What differs	Search Console	GA4	Trust which one
Unit measured	Clicks on a Google result	Sessions that fired the tag	GSC for search demand, GA4 for on-site behaviour
Search engines covered	Google only	All organic engines (Google, Bing, DDG, Yahoo…)	GSC for Google-specific work
Blocked / bounced-before-load visits	Counted	Missing	GSC — it doesn't depend on your tag
Consent banners and ad blockers	Unaffected	Suppresses 5–25% of sessions	GSC for volume, GA4 for direction
URL attribution	Grouped to the canonical URL	Recorded as the actual landing URL	GSC when you have canonical/variant URLs
One click, multiple sessions	Still one click	Can become 2+ (30-min timeout, midnight rollover)	GA4 inflates here; GSC is cleaner
Query data	Full (with anonymised long tail)	Only via the linked Search Console reports	GSC always
Conversions / revenue	Not available	Full attribution	GA4 always
Data freshness	1–3 day lag	Same day, finalised in 24–48h	GA4 for speed

The short version of how I use them: Search Console answers "is Google sending me more people, for which queries, at what position". GA4 answers "what did those people do once they arrived". Use GSC clicks as your organic volume number in reports to stakeholders. Use GA4 for engagement rate, landing-page performance, and revenue attribution. Don't average them, and don't try to reconcile them line by line — you'll lose a day and learn nothing.

If your organic numbers are flat in both tools, the problem is upstream of measurement. Our guide on how to increase blog traffic covers the content and internal-linking fixes that actually move the line, and blog analytics for Shopify stores goes deeper on tying blog sessions to revenue.

What should you actually check every month?

Five numbers, ten minutes:

• Organic sessions, this month vs same month last year (Traffic acquisition, Compare on).
• Top 10 organic landing pages and their movement (Landing page report, Organic comparison applied).
• Engagement rate on those pages. Below ~45% on an informational post usually means the intro doesn't match the query.
• Key events from organic sessions. If a post drives 800 sessions and zero events, it has no path to anything you sell.
• Search Console clicks for the same window, as your reality check on volume.

Anything beyond that is analysis, not reporting, and it should be triggered by a question rather than a calendar.

FAQ

Where is organic traffic in GA4?

Organic traffic lives in Reports → Acquisition → Traffic acquisition, in the row labelled Organic Search under the Session default channel group dimension. Set your date range in the top right, then read the Sessions column. If you want Google only rather than all search engines, switch the report's primary dimension to Session source / medium and look for google / organic.

Why is my GA4 organic traffic lower than Search Console clicks?

Search Console counts every click on your Google result. GA4 only counts sessions where the page finished loading and your tag fired, so visitors who bounce instantly, block trackers, or decline consent never register. A gap of 10–30% is normal. Search Console also covers only Google, while GA4's Organic Search includes Bing and others, which pushes in the opposite direction.

How do I see blog traffic specifically in Google Analytics?

Apply an Organic Search comparison, then go to Reports → Engagement → Landing page. In the search box above the table, type your blog path (on Shopify that's usually /blogs/) to filter the list to blog entries only. That gives you organic sessions per post. For a repeatable version, build a free-form exploration with Landing page as the row dimension and the same path filter.

Can I see which keywords bring organic traffic in GA4?

Not natively. GA4 has no keyword dimension of its own. Link Search Console under Admin → Product links → Search Console links, then publish the Search Console collection in Admin → Data display → Reports. The Reports → Search Console → Queries report then shows queries, clicks, impressions and average position inside GA4, sourced entirely from Search Console.

How far back does GA4 keep organic traffic data?

Standard GA4 properties default to a 2-month event-data retention window, extendable to 14 months under Admin → Data collection and modification → Data retention. Change it to 14 months today if you haven't. Aggregated standard reports like Traffic acquisition retain longer, but explorations and custom breakdowns are capped by that retention setting, so old cohort analysis simply won't be available.

Does GA4 count Shopify checkout pages as organic traffic?

Checkout sessions inherit the source of the session that started them, so a visitor who arrived from Google and later checked out stays attributed to Organic Search. Problems appear when a payment provider redirects back and starts a new session, showing up as referral traffic. Add the provider's domain to your unwanted referrals list in your data stream's tagging settings to prevent it.

Pick one thing from this article and do it this week: apply the Organic Search comparison, open the Landing page report, and find out which three posts are carrying your blog. If you'd rather have that read back to you automatically, run your store through the Blog Potential Analyzer.