Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Decisions first
For landing-page SEO decisions, use Landing page plus query string with Session default channel group = Organic Search and session-scoped outcomes. For key-event credit, use event-scoped traffic dimensions and disclose the property's attribution model. Connect Search Console for aggregate query-page visibility, but never claim those queries identify individual GA4 users or sessions.
- Choose user, session, or event scope before choosing metrics.
- Organic Search in GA4 includes unpaid search traffic under Google's channel rules, including Google's AI search experiences as currently classified.
- Carry canonical landing-page context to the CRM only after a consented known-user event.
Choose the attribution question and scope
Use first-user scope for acquisition, session scope for how visits began, and event scope for credit assigned to key events. Mixing them in one sentence creates claims the data does not support.
Google defines Session default channel group as the channel by which users arrived when they initiated sessions, using paid and organic channels last click. Event-scoped Default channel group describes channels credited for key events under the property's attribution model, whose default is data-driven. First user default channel group describes the user's initial acquisition.
A report saying organic search generated sessions should use session-scoped fields. A report saying organic search received key-event credit should use event-scoped fields and name the attribution model. A report saying organic search acquired new users should use first-user dimensions. These totals can all be correct and different.
| Question | Dimension family | Example outcome |
|---|---|---|
| How was the user first acquired? | First user | New users |
| How did this visit begin? | Session | Sessions and engagement |
| Which channel receives key-event credit? | Event-scoped | Key events or revenue |
| Which queries exposed the page? | Search Console | Impressions and clicks |
Build the organic landing-page view
Filter Session default channel group to Organic Search and break sessions and qualified outcomes down by Landing page plus query string, then normalize page identity in a governed derived field.
Include sessions, engaged sessions, engagement rate, key-event sessions or relevant session outcomes, and revenue only where collection and governance are reliable. Segment by device or country when it changes the decision, not by default. Use a comparable date window and annotate tracking or consent changes.
Normalize redirects, host, trailing slash, and canonical aliases through an identity table that preserves effective dates. Do not erase query parameters indiscriminately; some distinguish products, locales, searches, or experiments. Keep the raw landing value for diagnosis.
Bridge Search Console without inventing user-level keywords
Use Search Console to explain aggregate page-query exposure and GA4 to explain onsite outcomes. Compare them at canonical page and reporting-window level with source labels intact.
Search Console clicks do not need to equal GA4 sessions. Consent, blockers, timezones, redirects, repeated clicks, canonical attribution, invalid-traffic processing, and product definitions all create legitimate differences. Set a diagnostic tolerance based on the site's history rather than a universal ratio.
Never attach a Search Console query to a GA4 user, session, contact, or deal. Instead, say that a landing page received visibility from a query cluster and that organic landing sessions for that page produced a stated number of key events under a stated scope.
- GSC query-page impressions and clicks
- GA4 organic landing sessions
- GA4 session outcomes
- Event-scoped key-event credit
- CRM identified outcomes
- Coverage and unknowns
Turn attribution into page decisions
Prioritize pages by the combination of search opportunity, qualified onsite behavior, commercial consequence, and confidence—not by last-click revenue alone.
High impressions with weak organic landing engagement may indicate intent or page-experience mismatch. Stable sessions with falling key-event rate points first to the offer, form, tracking, or audience mix. Modest traffic with strong qualified outcomes can justify deeper cluster coverage and internal links.
Report data freshness, attribution model, key-event definitions, consent or tagging changes, unknown acquisition, and the share of revenue that can be matched to a landing page. SearchHandled reads a connected GA4 property today and labels measured analytics separately from Search Console evidence; it does not collapse them into a fictional single-source truth.
Continue the workflow
Reconcile one 28-day organic landing-page report in the GA4 UI and Data API, document the chosen scopes, then bridge it to aggregate Search Console page-query evidence.
- Google Analytics integration: connect the operational read-only data source
- Search Console vs analytics: understand collection and scope differences
- Pipedrive SEO attribution: carry consented landing-page context into pipeline reporting
Questions teams ask
- Which GA4 dimension should SEO reports use?
Use Session default channel group for how sessions began, First user dimensions for acquisition, and event-scoped channel dimensions for key-event attribution. Choose based on the question.
- Does GA4 Organic Search include Google AI traffic?
Google's current default-channel documentation says Organic Search includes unpaid search results, including Google's AI Overviews and AI Mode. Other AI assistants may be classified separately under AI Assistant.
- Can GA4 show the Search Console keyword for a session?
No reliable user-level join should be claimed. Search Console query performance is aggregate; compare it with GA4 at a canonical landing-page and time-window level.
Primary sources
The SearchHandled Editorial Team prefers first-party documentation and names the limits of each source. Links were checked on the access date.
- Google Analytics Help: Default channel groupAccessed August 29, 2026
- Google Analytics Help: Traffic acquisition reportAccessed August 29, 2026
- Google Analytics Help: Scopes of traffic-source dimensionsAccessed August 29, 2026
- Google Analytics Help: Link Search Console and Google AnalyticsAccessed August 29, 2026 · Search Console and Analytics use different scopes and will not produce identical totals.
- Google for Developers: Google Analytics Data API overviewAccessed August 29, 2026
- Google Search Console Help: Performance report: clicks, impressions, CTR, and positionAccessed August 29, 2026

