When you connect Google Analytics 4 (GA4) to SEO Gets, you unlock a whole new layer of insight: what happens after users land on your site from search. You'll see sessions, engagement rate, key events, and revenue (if you're tracking it)—all alongside your Google Search Console data.
The GA4 connection is read-only. SEO Gets can view your data but never modify your GA4 properties.
What GA4 data you'll see
Once connected, SEO Gets pulls these metrics from GA4 for each landing page:
Sessions — How many visits started on that page from organic search
Engagement rate — The percentage of sessions that were meaningful (not bounces)
Key events — Conversions or important actions you've set up in GA4
Revenue — Purchase value attributed to those sessions (if you track e-commerce)
GA4 is page-based, not query-based
Here's the key distinction: GA4 data tells you what happens after someone lands on your site, not which query brought them there.
Google Search Console shows you queries and impressions. GA4 shows you behavior and outcomes. They're two halves of the same story—GSC reveals how people found you, and GA4 reveals what they did next.
For more on this, see Why don't my GA4 metrics apply to queries?
Why your numbers won't match GA4 exactly
SEO Gets intentionally filters your GA4 data to show only SEO-relevant traffic—organic search from engines like Google, Bing, DuckDuckGo, and Yahoo, plus referral traffic from AI search tools like ChatGPT, Gemini, Perplexity, and Brave.
This means:
SEO Gets shows filtered traffic—organic search plus select AI/referral sources
GA4's default view shows all traffic, including paid campaigns, social, email, and direct visits
The numbers will differ, and that's intentional. You're seeing a cleaner, SEO-focused view without the noise. For the full breakdown of what gets filtered, see Why doesn't my GA4 data match what I'm seeing in SEO Gets?
Working with GA4 data in the dashboard
Once your GA4 property is linked, open the GA4 dashboard to explore your data. Here's what you can do:
Filter your GA4 data
Open the Filter menu on the GA4 dashboard to narrow the data. The menu includes:
Page & Content Group, Country, Device, and Source / Medium — filter by any of these dimensions
Key Events — include or exclude specific key events
GA4 Presets — one-click source/medium filters for Organic, LLMs, Referral, and Social Media
Priority Pages, Compare Filters, and Saved Filters
To filter by key event, choose Filter → Key Events. In the Filter by Key Events dialog, select the events you want from the list of your GA4 key events, choose Include or Exclude, and click Apply. The list reflects key events with data in your selected date range, and only events you've marked as key events in GA4 appear in it.
Clicking a table row still works: click a landing page to see all metrics filtered to that page, click a country to focus on that region, or click a key-event row to toggle that event in the active filter.
Basic filters in GA4 work by clicking table rows—just like in GSC views. The dashboard updates automatically to show filtered data across all widgets.
Compare time periods
Use the date picker to compare performance over time. Available comparison modes include:
Previous Period — Compare against the immediately preceding period
Year Over Year — Compare against the same period last year
Previous Month — Compare against the previous month
Custom — Pick specific date ranges to compare
Year Over Year comparisons are helpful for spotting seasonal trends or measuring growth against the same period last year.
Export your data
Click Export to CSV to download your GA4 data. You can choose which columns to include—Date, Landing Page, Country, Device, Event Name, and Source/Medium—so you only export what you need.
Current limitations
Here's what GA4 in SEO Gets doesn't support yet:
Editing GA4 key events — The GA4 connection is read-only, so you can't mark or unmark events as key events from SEO Gets. Set your key events in GA4 itself; once marked, they become available to filter in the dashboard.
Query-level metrics — GA4 attributes sessions to landing pages, not search queries. If you need query-level data, use GSC analytics instead.
How to connect GA4
Linking GA4 takes about 30 seconds per site:
Go to Settings → Data Source for the site you want to connect
Under Google Analytics 4, select the corresponding property
For step-by-step instructions with screenshots, see Link GA4 property.
Troubleshooting
If something looks off with your GA4 data, start by checking these common issues:
If your GA4 metrics are showing zero—or the panel stays empty—this is usually a connection or access issue:
GA4 property not linked — Go to Settings → Data Source → Google Analytics 4 and confirm the property is selected. If it shows "Connect GA4," you'll need to link it first.
Wrong Google account — Make sure the Google account connected in Settings → My Google Accounts has access to the GA4 property you're trying to view. If someone else set up the connection, their account needs access—not just yours.
Multiple GA4 properties — If you have more than one GA4 property for the same site, check that you've selected the correct one. It's easy to link the wrong property by mistake.
No matching traffic in the date range — SEO Gets only shows organic search and select referral traffic. If your site had no organic traffic in the selected date range, metrics will show as zero. Try broadening the date range to check.
For step-by-step connection help, see Link GA4 property.
If you see revenue in GA4 but not in SEO Gets, the most common cause is where that revenue is being tracked:
Revenue on an unrelated hostname — If your checkout or booking happens on a completely separate domain (like a third-party booking platform), GA4 attributes that revenue to that hostname—not your main site. Cross-domain tracking in GA4 does not bring revenue from unrelated domains into SEO Gets for your main site.
Revenue on a subdomain — If you connected the sc-domain property, revenue attributed to subdomains of your primary domain—such as checkout.yoursite.com—will come through in SEO Gets.
Revenue from non-organic traffic — SEO Gets filters to organic search and select referral sources only. Revenue from paid campaigns, social, email, or direct traffic won't appear in your dashboard.
Processing delay — GA4 can take 24–48 hours to process revenue data. If the transaction is recent, it may not have appeared yet.
For more detail, see Why doesn't GA4 revenue show in SEO Gets?
If your GA4 data looks fine in the main dashboard but vanishes or drops significantly when you apply a content group filter, the issue is almost always how the filter is written:
Your regex includes the full URL — GA4 stores URL paths only, not full URLs. If your content group regex includes https:// or your domain name (like ^https://yoursite.com/blog), it won't match anything.
Fix: Write regex patterns that match the path only. Use ^/blog instead of ^https://yoursite.com/blog.
For a full walkthrough, see Why can I see my GA4 data in the dashboard but not in the filtered view?
This is expected—SEO Gets intentionally filters your GA4 data to show only SEO-relevant traffic:
SEO Gets shows filtered traffic — organic search plus select AI/referral sources like ChatGPT, Gemini, and Perplexity.
GA4 shows all traffic — including paid campaigns, social, email, and direct visits.
The numbers should differ. If you want to verify SEO Gets numbers in GA4 directly, you can apply a matching source/medium filter. See Why doesn't my GA4 data match what I'm seeing in SEO Gets? for the exact filter values.
We filter out (not set) source/medium as poor quality data—if you're seeing that in your GA4 reports, it won't appear in SEO Gets.
SEO Gets shows the key events you've marked in GA4, but only for the SEO traffic we track — organic search plus selected AI/referral sources. An event that only fires on paid, social, email, or direct traffic won't appear in SEO Gets at all.
Event fires on traffic outside our scope — If the event mostly fires on non-organic traffic, check the session source/medium in GA4 to confirm. See Why doesn't my GA4 data match what I'm seeing in SEO Gets? for the exact sources we include.
Same primary domain, different subdomain — If your conversion, booking, or signup happens on a subdomain like checkout.yoursite.com, the key event will appear in SEO Gets when you've connected the sc-domain property, because it shares your primary domain.
Unrelated third-party hostname — If your conversion happens on a completely separate domain (like a booking platform or payment processor), GA4 attributes that key event to that hostname, not your primary domain. Cross-domain tracking in GA4 does not bring those events into SEO Gets for your main site.
Event isn't marked as a key event in GA4 — Only events marked as key events in GA4 appear in SEO Gets. Mark the event in GA4, and it becomes available to filter in the dashboard.
To check where a key event is attributed, go to GA4 → Reports → Landing page and add a hostname filter. If the hostname is unrelated to your primary domain, that's why it's not showing in SEO Gets.
To control which key events show, use Filter → Key Events and choose the events to include or exclude. You can't change which events are key events in GA4 from SEO Gets — the connection is read-only.
The site-level key events total and the detailed Key Events card count different things, so the two numbers aren't supposed to match.
Dashboard key events total — This is a count of key event occurrences across all your key events. SEO Gets sums the GA4 key events metric across the selected date range.
Detailed Key Events card — This card counts active users (distinct people) who triggered a key event, broken out by event name. When you filter to a single event, its header shows the active users for that event.
Here's a real example: filtering generate_lead shows 16 key events, while the dashboard total shows 37. That's because 16 distinct users triggered generate_lead, while the dashboard's 37 counts every key event occurrence across all your events. Neither number is wrong—they're just answering different questions.
Filters don't change the calculation. Applying a filter (like clicking a landing page, country, or event row) reruns the GA4 queries and narrows the result set—it doesn't create a new attribution model. The detailed card always reports active users; the site-level total always sums key event occurrences.
One more surface difference: the SEO Analytics dashboard restricts GA4 data to SEO-relevant sources (organic search plus select AI and referral sources), while the GA4 dashboard does not apply that source filter. So the same key event can show different—but both correct—totals depending on which dashboard you're looking at.
If your GA4 data dropped right after you switched your site to a new hostname, such as moving from yoursite.com to www.yoursite.com, while Google Analytics kept collecting traffic, the hostname change is usually the cause. SEO Gets filters GA4 data by hostname based on the site property currently selected in Search Console, not the GA4 property itself.
When that property is a URL-prefix property, for example https://www.yoursite.com, SEO Gets matches its hostname exactly. Switching from the non-www to the www version changes what we match against, so rows for the old hostname stop appearing even though GA4 is still collecting them.
Confirm the Search Console property for the site now points to your current hostname, such as the www version.
Go to Settings → Data Source → Google Analytics 4 and check the property shown under Select GA4 Property.
Select the GA4 property that corresponds to your site again if it is not already selected.
Reconnecting your Google account in My Google Accounts only refreshes OAuth access and does not change the hostname filter. Use that path only if the Google account or GA4 access itself needs reconnecting.
SEO Gets does not automatically remap old-hostname history. Rows recorded under your previous hostname are not moved to the new one, so older data may stay absent even after you reconnect.
If you use a domain (sc-domain) Search Console property, SEO Gets matches your whole domain instead of one exact hostname, so it picks up traffic across protocols and subdomains.
Still stuck? If you've checked these issues and something still looks off, reach out to support with your site name and GA4 property ID, and we'll help you troubleshoot.