Search Everywhere: GA4 for SEO: Setup, Reports and Explorations
Set up GA4 for SEO measurement, use the right reports and explorations, build Looker Studio dashboards, export to BigQuery and avoid common pitfalls.

This post is Chapter 16 of Search Everywhere: The Practical Guide to SEO, AEO and GEO, the free online edition. Chapter and appendix references link to the matching post.
Search Console tells you what happens before the click. Google Analytics 4 (GA4) tells you what happens after it: which visitors engage, which convert, and which channels bring them. For SEO, AEO and GEO, GA4 answers three questions:
- How much traffic and value does organic search bring?
- Which pages and topics engage and convert visitors?
- How much traffic comes from AI assistants, and how does it behave?
This chapter covers the setup that makes those answers reliable, then the reports and explorations that answer them.
How GA4 thinks
GA4 is built around events. Every interaction (a page view, a scroll, a click, a form submission, a purchase) is an event with parameters. Some events are collected automatically, some with enhanced measurement (scrolls, outbound clicks, site search, video engagement, file downloads), and others you define yourself.
Key concepts:
- Session: a group of interactions within a time window, started by a
session_startevent. - Engaged session: a session that lasts longer than 10 seconds, has a key event, or has at least two page views. Engagement rate is the share of sessions that were engaged; it replaced bounce rate as the main quality metric (bounce rate in GA4 is simply the inverse of engagement rate).
- Key events: events you mark as important, such as a contact form submission, a booking or a download. (GA4 renamed “conversions” to “key events” in 2024; “conversions” now refers to key events imported into Google Ads.)
- Channel groups: rules that classify traffic into channels such as Organic Search, Direct, Referral, Organic Social and Paid Search.
Setup for SEO measurement
1. Install the tag correctly
webocreation.com/ loads GA4 through Google Tag Manager (container GTM-M7RQBC visible in the page source). That is a good setup. Check that:
- The Google tag fires on all pages, once.
- There is no duplicate hard-coded GA4 tag in the theme.
- Consent Mode v2 is configured if you have visitors from the EEA or UK, so that data is modelled correctly when users decline cookies.
2. Define key events
For a services and content site, sensible key events are:
| Key event | How to capture |
|---|---|
generate_lead |
Contact form submission (thank-you page view or form submit event) |
book_call |
Click on the Calendly link, or Calendly’s embed event |
file_download |
Enhanced measurement catches .zip downloads; for GitHub-hosted downloads, track outbound clicks to the download URL |
newsletter_signup |
Newsletter form submission |
purchase |
For book sales or paid extensions, if sold on-site |
For the free extensions, downloads are the main value event. Because many of webocreation.com/’s downloads are hosted on GitHub, configure a GTM trigger on clicks to github.com/* URLs ending in .zip and send a file_download event with the extension name as a parameter.
3. Create custom dimensions for content analysis
Content analysis is much richer when page views carry metadata. Push these to the data layer from WordPress and register them as event-scoped custom dimensions:
content_category(primary category: OpenCart, HubSpot, Webflow…)content_authorpublish_date(year or year-month)content_type(tutorial, extension download, service page, guide)word_count_band(under 1,000; 1,000–2,000; over 2,000)
<script>
window.dataLayer = window.dataLayer || [];
dataLayer.push({
content_category: 'OpenCart',
content_author: 'Rupak Nepali',
publish_date: '2026-11',
content_type: 'tutorial'
});
</script>
With these in place you can answer questions like “Do OpenCart tutorials convert better than HubSpot tutorials?” or “How much traffic comes from content published before 2020?” directly in GA4.
4. Track AI assistant traffic
AI assistants send visitors when users click citations. These usually arrive as referral traffic with a recognisable source, such as chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com or claude.ai. Some arrive without a referrer and appear as Direct; for example, links opened from some mobile apps may lose the referrer. ChatGPT also adds utm_source=chatgpt.com to many of its outbound links, which helps.
Create a custom channel group so AI traffic is reported as its own channel rather than being buried in Referral:
- Admin › Data display › Channel groups › Create new channel group (copy the default).
- Add a new channel named AI Assistants.
- Condition: Source matches regex:
.*(chatgpt|openai|perplexity|gemini\.google|bard\.google|copilot\.microsoft|bing\.com/chat|claude\.ai|anthropic|you\.com|phind|deepseek|meta\.ai|mistral|grok|x\.ai).*
- Move the AI Assistants channel above Referral in the list, because rules are evaluated in order.
- Save, and select it as the primary channel group if you want it in standard reports.
Note that traffic from Google’s AI Overviews and AI Mode arrives as normal Google organic traffic, not as a separate source, so this channel captures third-party assistants only.
5. Link Search Console
Admin › Product links › Search Console links. Once linked, enable the Search Console reports in the Library (Reports › Library) to see “Queries” and “Google organic search traffic” collections inside GA4. These combine landing page data from Search Console with engagement and key event data from GA4.
6. Filter internal and bot traffic
- Define internal traffic by IP address (Admin › Data streams › Configure tag settings › Define internal traffic) and activate the filter.
- GA4 excludes known bots automatically, but spam registrations and fake form submissions (a problem the case study site has written about) inflate lead events. Captchas such as Turnstile protect data quality as well as the site.
Reports for SEO
Organic search overview
Reports › Acquisition › Traffic acquisition, with the primary dimension set to Session default channel group. Filter to Organic Search to see sessions, engaged sessions, engagement rate, key events and revenue.
Landing pages
Reports › Engagement › Landing page. Add a filter for Session default channel group = Organic Search. Sort by sessions and look at engagement rate and key events per landing page. Pages that attract organic traffic but have low engagement may not match intent; pages with high engagement but few key events may need better calls to action.
AI Assistants channel
With the custom channel group in place, Traffic acquisition shows AI Assistants alongside other channels. Compare:
- Volume and growth month over month.
- Engagement rate and average engagement time. AI-referred visitors often arrive with a specific purpose and engage well.
- Key event rate.
- Landing pages: which pages AI assistants send people to. These are your most-cited pages, and the list often surprises site owners.
Illustrative example. Channel comparison for a site like webocreation.com/, last 90 days. Figures are illustrative; your own GA4 export would replace them.
Channel Sessions Engagement rate Key events Key event rate Organic Search 58,200 54% 1,420 2.4% Direct 11,900 49% 310 2.6% Referral 4,300 58% 160 3.7% AI Assistants 1,850 66% 92 5.0% Organic Social 1,200 41% 14 1.2%
AI landing pages (illustrative) Sessions Top source Cloudflare Turnstile for OpenCart 4 310 chatgpt.com OpenCart 3 to 4 upgrade guide 240 perplexity.ai ShoppingGPT guide 190 chatgpt.com Cloudflare OWASP ruleset explained 150 copilot.microsoft.com In this pattern, AI Assistants is small but has the highest engagement and key event rates. That is common: visitors who click a citation have already been told the page answers their question.
Explorations
Explorations (the Explore section) allow ad-hoc analysis beyond standard reports. Three are particularly useful for SEO.
Free-form: content performance by category
- Dimensions:
content_category(custom), Landing page. - Metrics: Sessions, Engaged sessions, Key events.
- Filter: Session default channel group = Organic Search.
This shows which topics bring the most valuable organic traffic, which feeds your content strategy.
Path exploration: what happens after an organic landing
Start from a landing page (for example the Turnstile tutorial) and see the next pages visitors go to. Do they reach the service page, the download, the books page? If almost everyone leaves after one page, internal links and calls to action need work.
Funnel exploration: from content to lead
Build a funnel: organic landing on a tutorial › view of a service page › contact form view › generate_lead. Identify where most visitors drop off.
Looker Studio dashboards
Looker Studio (formerly Data Studio) connects to GA4 and Search Console for free and lets you build dashboards that combine them. A useful SEO dashboard has four pages:
- Overview: organic clicks, impressions, sessions and key events over time, with year-over-year comparison.
- Content: top landing pages with Search Console clicks and CTR alongside GA4 engagement and key events, filterable by category.
- Queries: top queries, question queries and branded vs non-branded split.
- AI visibility: AI Assistants sessions by source and landing page, plus manually entered AI citation tracking data (Chapter 24) from a Google Sheet.
BigQuery export
GA4 offers a free daily export of raw event data to BigQuery. Combined with the Search Console bulk export (Chapter 17), it allows analyses the interface cannot do, such as joining query data with landing-page conversion data over long periods. A simple query to count sessions from AI assistants by landing page:
SELECT
(SELECT value.string_value FROM UNNEST(event_params) WHERE key = 'page_location') AS landing_page,
traffic_source.source AS source,
COUNT(DISTINCT CONCAT(user_pseudo_id,
CAST((SELECT value.int_value FROM UNNEST(event_params) WHERE key = 'ga_session_id') AS STRING))) AS sessions
FROM `project.analytics_XXXXXXX.events_*`
WHERE _TABLE_SUFFIX BETWEEN '20260801' AND '20261031'
AND event_name = 'session_start'
AND REGEXP_CONTAINS(traffic_source.source, r'chatgpt|perplexity|gemini|copilot|claude')
GROUP BY landing_page, source
ORDER BY sessions DESC;
Note that traffic_source in the export is first-user acquisition; for session-level source, use the collected_traffic_source fields or session-scoped parameters, depending on your export version.
Common GA4 pitfalls for SEO
- Self-referrals: if your payment gateway, booking tool or subdomain appears as a referral, add it to the list of unwanted referrals (Admin › Data streams › Configure tag settings › List unwanted referrals).
- Unassigned traffic: often caused by malformed UTM parameters or missing
session_startevents. Check your UTM conventions. - Thresholding: when Google signals is enabled, GA4 may hide rows with small numbers. Switch reporting identity to “Device-based” in Admin › Reporting identity if thresholding hides data you need.
- Data retention: the default retention for exploration data is 2 months. Raise it to 14 months (Admin › Data retention).
- Comparing GA4 sessions with Search Console clicks: they will never match. Clicks are counted by Google; sessions are counted by your tag, and are affected by consent, ad blockers, and redirects.
Key takeaways
- Set up GA4 with clean key events (leads, bookings, downloads) and content metadata as custom dimensions.
- Create a custom AI Assistants channel to separate traffic from ChatGPT, Perplexity, Gemini, Copilot and Claude, and place it above Referral.
- Google AI Overview and AI Mode traffic appears as normal Google organic traffic.
- Use landing page reports, explorations and Looker Studio to connect content with outcomes.
- For deeper analysis, export GA4 and Search Console data to BigQuery.
Previous: Google Search Console, Report by Report
Next: The Rest of the Google SEO Toolbox
All chapters: Search Everywhere: The Practical Guide to SEO, AEO and GEO






