GA4 for SEO reporting: the setup that answers real questions

TL;DR: GA4’s default setup does not answer SEO questions out of the box. Organic Search now includes Google’s AI Overviews and AI Mode by definition, while a separate AI Assistants channel (added May 13, 2026) tracks ChatGPT, Gemini, and Claude referral traffic. Link Search Console for query-level data, build a landing page exploration that isolates real entry pages from thank-you and confirmation pages, and know when data thresholding is hiding rows from you. This guide walks through the exact setup.

---

Table of contents

1. Why your default GA4 reports don’t answer SEO questions
2. How GA4 defines organic search, and why that changed in 2026
3. Linking Search Console to GA4: setup and limits
4. The two reports the Search Console link enables
5. Building a landing page exploration that isn’t lying to you
6. Fixing the skewed landing pages report
7. Attribution models and what they do to organic credit
8. Data thresholding: the rows GA4 hides from you
9. Referral exclusions and cross-domain measurement
10. Tracking AI assistant traffic separately from AI Overviews
11. Custom channel groups and the Data API
12. Building a monthly SEO reporting dashboard in GA4
13. GA4 vs Search Console vs third-party tools for SEO reporting
14. Common GA4 SEO reporting mistakes
15. Frequently asked questions
16. Key takeaways

---

Why your default GA4 reports don’t answer SEO questions

You open GA4, click Reports, then Acquisition, and you get a channel breakdown that mixes Organic Search sessions with a landing page column that is often wrong. You don’t get search queries. You don’t get click-through rate. You don’t get a clean view of which pages actually earn organic entries versus which ones just happen to load first in a session.

None of that is a bug. GA4 was built as an events-based measurement platform first and a marketing-channel report second. The reports SEO teams actually need, query performance, landing page accuracy, channel-level attribution for organic, all require deliberate setup: linking Search Console, building explorations, and understanding two data-quality mechanics (thresholding and sampling) that quietly remove rows from what you see.

A thread in r/SEO titled “The new Landing Pages report in GA4 is skewed” captures the practitioner complaint directly: internal pages, like order confirmations or thank-you pages, show up attributed to organic search sessions because GA4’s landing page dimension reflects the first page of the session, not necessarily the page a searcher actually clicked into from a results page. If your reporting workflow treats GA4’s default Landing Page report as ground truth, you inherit that skew.

This guide covers the setup that fixes it: what changed in GA4’s organic definition in 2026, how to link and use Search Console data, how to build a landing page exploration that filters out the noise, and where thresholding will silently hide the rows you’re trying to report on.

How GA4 defines organic search, and why that changed in 2026

Google Analytics Help’s default channel group documentation defines Organic Search as the channel “by which users arrive at your site/app via non-ad links in organic-search results, including Google’s AI Overviews and AI Mode.” Technically, a session gets classified as Organic Search when the source matches Google’s internal list of designated search sites, or when the medium exactly matches “organic.”

That inclusion of AI Overviews and AI Mode inside Organic Search matters for your reporting. It means a click from an AI Overview citation on Google shows up in the same bucket as a click from a classic blue link. You cannot separate AI Overview traffic from traditional organic traffic using GA4’s channel dimension alone; you need Search Console’s Search Appearance filter for that split, and even then Search Console groups AI Overview clicks under broader search-appearance categories rather than a clean standalone row.

On May 13, 2026, Google Analytics shipped a separate default channel: AI Assistants. According to Google’s own release notes, this channel is triggered when a session’s medium exactly matches “ai-assistant” and the referrer matches a documented list of AI assistant sources, currently including ChatGPT, Gemini, and Claude. Critically, the release notes specify that AI Assistants “excludes Google’s AI Overviews and AI Mode,” which stay classified as Organic Search.

Search Engine Journal’s coverage of the launch, written by senior news writer Matt G. Southern, adds useful context: before this update, all AI chatbot referral traffic landed in GA4’s generic Referral channel, indistinguishable from any other unrecognized inbound link. Southern’s piece also notes that Google had already published guidance in August 2025 for building manual custom channel groups with regex patterns to isolate AI referrers, meaning some SEO teams were already doing this work by hand before the native channel existed. The native AI Assistants channel frees up one of GA4’s two custom channel group slots if you had used one for that purpose.

The practical takeaway: as of August 2026, GA4 gives you two default channels relevant to AI-driven search, Organic Search (which absorbs AI Overviews and AI Mode) and AI Assistants (which captures standalone chatbot referrals). Neither report separates AI Overview clicks from classic organic clicks within Organic Search itself. For that split, pair GA4 with the Search Console integration covered next, and see how to track ChatGPT and Perplexity traffic in GA4 for the referrer-level detail this section doesn’t cover.

Linking Search Console to GA4: setup and limits

Search Console has query-level data. GA4 does not, natively. Linking the two properties pulls a limited slice of Search Console data into GA4’s report library, but the link comes with real constraints you need to plan around before you build a reporting workflow on top of it.

To create the link, per Google’s support documentation, you need Editor role on the GA4 property and verified ownership status in Search Console (you can verify during the linking flow itself if you haven’t already). Once linked:

• A web data stream can link to only one Search Console property.
• A GA4 property can have only one data stream linked to a Search Console property.
• Search Console metrics can be broken down only by Search Console’s own dimensions plus three GA4 dimensions: landing page, device, and country. You cannot cross Search Console data with GA4’s channel, source/medium, or event dimensions.
• Time-series charts are not supported in the Search Console reports.
• Data retention is capped at 16 months, matching Search Console’s own retention limit, not GA4’s longer retention for standard event data.
• Search Console data appears in GA4 roughly 48 hours after Search Console collects it.

One more detail that trips people up: your data availability start date depends on setup order. If you create the GA4 data stream before verifying the site in Search Console, data starts from the verification date. If you verify the site first and link later, data starts from the stream creation date. If you’re setting this up for a new property, verify Search Console first, then link, to avoid losing a data-collection window.

The two reports the Search Console link enables

The link enables exactly two pre-built reports, both living under Library > Search Console in GA4’s report navigation, and both unpublished by default (you have to add them to a collection to see them in the left nav):

1. Google Organic Search Queries. Shows the actual search queries driving impressions and clicks, alongside Search Console’s native metrics: clicks, impressions, click-through rate, and average position. This is the report SEO teams have wanted since GA4 launched: real query data inside the same interface as session and conversion data.
2. Google Organic Search Traffic. Combines landing pages with Search Console metrics, drillable by country and device. This is closer to a blended report, showing which pages earn impressions and clicks from Google organic search specifically, filtered to Search Console’s definition of organic rather than GA4’s broader session-based one.

The Queries report is the one that matters most for content teams doing keyword-level analysis, because it is the only place inside GA4 where query strings exist at all. Everything else in GA4’s standard reporting works from channel, source, medium, and campaign dimensions, none of which include the actual search term.

Two caveats worth internalizing. First, click-through rate in this report displays as a fraction (0.0588 rather than 5.88%), which throws off exports if you’re piping this into a spreadsheet without reformatting. Second, because the report can only cross Search Console dimensions with landing page, device, and country, you cannot filter Queries data by GA4 audience segments, custom events, or conversions. If you need to know which queries led to a demo request, you’re back to Search Console’s own interface or the Search Console API, not this GA4 report. See Google Search Console data analysis: queries most people never run for the query-decay and cannibalization checks that live entirely in Search Console’s own tools.

Building a landing page exploration that isn’t lying to you

The standard Landing Page report under Engagement mixes every channel together and applies GA4’s session-based landing page definition, which is the first page viewed in a session regardless of how the user actually arrived there mid-funnel through internal redirects, app-to-web handoffs, or client-side routing quirks. For SEO reporting, you want a version filtered to organic-only sessions with the noise removed.

Build this as a Free-form exploration, one of GA4’s six exploration techniques, alongside Funnel, Path, Cohort, Segment Overlap, and User Explorer:

1. Create a new exploration and select Free-form.
2. Add Session default channel group as a dimension, and filter it to Organic Search (and AI Assistants, if you want AI-driven referrals in the same view).
3. Add Landing page + query string as a second dimension rather than plain Landing page, so parameterized URLs don’t collapse into a single row and hide UTM-driven distortion.
4. Add Sessions, Engaged sessions, Average engagement time, Key events, and Total revenue (if ecommerce applies) as metrics.
5. Apply an exclusion filter on landing page to drop known internal paths: checkout confirmations, thank-you pages, login redirects, anything that structurally cannot be the entry point of an organic search click but keeps appearing as one due to a session boundary quirk.
6. Segment by device category and, if you linked Search Console, cross-reference the highest-session landing pages against the Search Console Queries report to confirm the query-to-page match makes sense.

This exploration takes 15 minutes to build once and becomes your reusable SEO landing page source of truth, distinct from the default report every stakeholder outside SEO is looking at.

flowchart TD
    A["Stakeholder asks: which pages drive organic traffic?"] --> B{"Using default Landing Page report?"}
    B -->|Yes| C["Mixed with all channels, session-based landing page definition"]
    C --> D["Confirmation and thank-you pages appear as organic entries"]
    D --> E["Report looks skewed, trust in GA4 drops"]
    B -->|No, using SEO exploration| F["Filter: Session default channel group = Organic Search"]
    F --> G["Dimension: Landing page + query string"]
    G --> H["Exclusion filter removes internal/confirmation paths"]
    H --> I["Cross-check against Search Console Queries report"]
    I --> J["Accurate organic landing page report"]

Fixing the skewed landing pages report

The r/SEO thread on skewed landing pages isn’t an isolated complaint. It reflects a structural fact about how GA4 assigns the landing page dimension: it’s tied to the session’s first pageview event, not to a verified “this is where the search click landed” signal. Three fixes reduce the damage:

• Exclude non-entry paths explicitly. Build the exclusion filter described above and maintain it as your site adds new confirmation, redirect, or gated-content flows.
• Cross-reference against Search Console. The Google Organic Search Traffic report ties landing pages to Search Console’s click data, which is closer to “a searcher clicked this exact URL” than GA4’s session-first-page logic. When the two reports disagree sharply on a page’s organic volume, trust Search Console’s version for that page.
• Watch for redirect chains. If a page 301-redirects before rendering, GA4 sometimes records the landing page as the post-redirect URL rather than the URL Google indexed and ranked, especially with client-side redirects. Audit your top 20 organic pages by checking their indexed URL in Search Console against the URL showing up as the GA4 landing page; a mismatch there usually points to a redirect or canonicalization issue worth fixing at the source, not just in reporting. For a broader framework on separating real ranking damage from reporting noise, see Google core update recovery: the diagnostic playbook and your traffic dropped and there was no announced update.

Attribution models and what they do to organic credit

GA4’s Attribution reports offer three models, per Google’s attribution models documentation: data-driven attribution, which uses machine learning to distribute conversion credit across touchpoints based on your account’s own data; paid and organic last click, which assigns 100% of a conversion’s value to the last channel a user clicked through before converting; and Google paid channels last click, which credits only the last Google Ads touchpoint.

“Paid and organic last click” and “last non-direct click” are, per Google, two names for the same model. Under this model, if a user’s path was Display, then Social, then Paid Search, then Organic Search, Organic Search gets 100% of the credit as the final non-direct touchpoint. Direct visits are excluded from receiving credit unless the entire conversion path consists only of direct visits.

Google deprecated the older single-touch and rules-based models (first click, linear, time decay, position-based) in November 2023, leaving data-driven attribution as the model most GA4 properties now report against by default in the standard Conversions and Advertising reports. That matters for SEO reporting specifically: data-driven attribution splits credit across every touchpoint in a path using a machine-learned model unique to your property’s data, which means the “organic search drove this conversion” figure you see in GA4’s default reports is a modeled estimate, not a last-click count. If you’re reporting organic’s contribution to a board or client who expects last-click logic (the way most legacy SEO reporting worked), switch the report’s comparison model explicitly to “paid and organic last click” rather than assuming the default view uses it. See share of answer: the metric replacing share of voice for how attribution modeling problems compound when AI answer engines remove the click entirely.

Data thresholding: the rows GA4 hides from you

Thresholding is different from sampling, and conflating the two leads to wrong conclusions about missing data. Google’s documentation on data thresholds explains that GA4 withholds rows under two conditions: when a report or exploration includes demographic data (or audiences built on demographic data), and when it includes search query information, meaning the Search Console Queries report specifically, if a query row doesn’t have enough total users behind it.

The thresholds are system-defined; Google’s documentation states plainly that “you can’t adjust them.” No specific row or user-count minimum is published, which makes thresholding frustrating to diagnose: you’ll see a query or a demographic breakdown suddenly show fewer rows than you expect, with no error message explaining why. The only documented remedy is expanding the date range, which increases the total user count behind a given row and can push it back over the visibility threshold.

For SEO reporting specifically, this means your long-tail query analysis in the Search Console Queries report will systematically under-report low-volume queries, not because they didn’t happen, but because GA4 is withholding rows it judges too small to report safely. If you need complete long-tail query visibility, pull that data from Search Console directly (or the Search Console API), where thresholding doesn’t apply the same way, rather than from the GA4 integration.

Referral exclusions and cross-domain measurement

Two related settings affect whether GA4 correctly classifies a session as organic versus referral, and both are easy to misconfigure.

Referral exclusion list. This list tells GA4 which domains should never be counted as referral sources, appending an ignore_referrer parameter to events from matching traffic. Google’s referral exclusion documentation notes that self-referrals (your own domain and subdomains) are excluded automatically, so you generally don’t need to add your own domain manually. The common real use cases are third-party payment processors your users are redirected to and back from, and any domain you operationally control that isn’t your primary site, such as a separate email or authentication subdomain. GA4 allows up to 50 exclusion entries per data stream, matched with OR logic.

Cross-domain measurement. If your funnel spans multiple domains (a marketing site on one domain, a checkout or app on another), cross-domain measurement lets GA4 treat a single user’s activity across both domains as one continuous session rather than a fresh session with a referral from your own other domain. Per Google’s documentation, GA4 handles self-referral suppression automatically once you’ve configured your domains under cross-domain measurement, which means a separate referral exclusion entry for your own second domain is usually redundant once cross-domain measurement is set up correctly.

Get these wrong and you inflate referral traffic with what is actually organic-driven, cross-domain user behavior, muddying any channel-level SEO report you build on top of session or user counts.

Tracking AI assistant traffic separately from AI Overviews

Given that AI Overviews stay bucketed inside Organic Search while standalone AI assistants get their own channel, your reporting needs two separate questions answered, not one:

1. How much of my Organic Search channel’s growth or decline is attributable to AI Overview citations specifically, versus classic blue-link clicks? Search Console’s Search Appearance dimension is the only place to filter for this; GA4’s channel dimension cannot make the distinction.
2. How much standalone traffic am I getting from ChatGPT, Gemini, Claude, and any other assistant Google recognizes going forward? The native AI Assistants channel, live since May 13, 2026, answers this without custom configuration, assuming your traffic volume clears GA4’s thresholding minimums.

If you were running a manual custom channel group with regex patterns to catch AI referrers before the May 2026 update, per Search Engine Journal’s coverage of the launch, you can now retire that custom channel and reclaim the slot, since the native default channel does the same classification automatically and more completely. For the full setup on separating AI referral sources at the UTM and referrer level, see how to track ChatGPT and Perplexity traffic in GA4, and for the broader diagnostic on why you might rank well on Google but see nothing from AI engines, see why you rank on Google but are invisible in ChatGPT and Perplexity.

Custom channel groups and the Data API

Even with the native AI Assistants channel covering the most common cases, custom channel groups remain useful for edge cases: a niche AI tool not yet on Google’s recognized list, an internal referral pattern specific to your business, or a channel breakdown that groups sources differently than Google’s default logic for reporting purposes. GA4 properties get a limited number of custom channel group slots, and with the AI Assistants default now handling chatbot classification natively, most teams have at least one slot free for something else.

For teams building reports outside GA4’s own interface, the GA4 Data API exposes the same channel logic programmatically. The defaultChannelGroup dimension in the API schema is documented as being “based primarily on source and medium,” with values including Direct, Organic Search, and the other default channels. Combine it with landingPage (the page path tied to a session’s first pageview) and sessionSource / sessionMedium to rebuild the same organic-filtered, noise-excluded landing page report described earlier, but pipe it into your own dashboard, spreadsheet, or BI tool instead of GA4’s exploration interface. This is the route to take if your SEO reporting needs to sit alongside rank-tracking or content-performance data from other systems in one place. See the 9 SEO KPIs that still matter when clicks are disappearing for what to build into that combined dashboard beyond raw session counts.

Building a monthly SEO reporting dashboard in GA4

Once the underlying setup is correct, the actual monthly report is a small, repeatable set of views:

• Organic sessions and engaged sessions trend, filtered to the Session default channel group = Organic Search, with AI Assistants shown as a separate line rather than folded in.
• Top landing pages by organic sessions, from your custom exploration, cross-checked against the Google Organic Search Traffic report for click-level confirmation.
• Top queries by clicks and impressions, from the Google Organic Search Queries report, watching for thresholding gaps in the long tail.
• Key events by landing page, so organic traffic gets tied to outcomes, not just visits.
• Attribution comparison: data-driven credit versus last-non-direct credit for your primary conversion event, reported side by side so stakeholders see the range rather than a single number presented as fact.

Save this as a GA4 Collection with the relevant reports and explorations pinned together, so it’s a two-click destination each month rather than a rebuild. If you’re reporting against content that was refreshed or pruned recently, layer in publish and update dates from your CMS so page-level organic trend changes can be tied back to specific edits; see content refresh vs new content: where to spend your next $10k and content pruning: how to delete your way to more traffic for how to structure that comparison.

GA4 vs Search Console vs third-party tools for SEO reporting

No single tool answers every SEO reporting question on its own. Here is what each one is actually built for.

Reporting need	GA4 (native)	GA4 + Search Console link	Search Console (standalone)
Search query data	✗ Not available	✓ Via Queries report, thresholded	✓ Full query data, no thresholding
Session and engagement metrics	✓ Native strength	✓ Same data	✗ Not available
Landing page accuracy	✗ Session-based, prone to skew	~ Better via cross-reference	✓ Click-verified landing URL
Conversion / key event attribution	✓ Data-driven and last-click models	✗ Not crossable with Search Console dims	✗ Not available
AI Overview vs classic organic split	✗ Both bucketed as Organic Search	~ Via Search Appearance filter in linked data	✓ Search Appearance dimension
Standalone AI assistant referral traffic	✓ Native AI Assistants channel (since May 2026)	✓ Same channel	✗ Not available
Historical data retention	Configurable, longer-term	Capped at 16 months	Capped at 16 months
Time-series charting on query data	✗ Not supported in linked reports	✗ Not supported	✓ Fully supported

The practical pattern: use GA4 for session, engagement, and conversion behavior; use Search Console (either standalone or through the link) for query and click-level truth; use the two together, cross-referenced, for landing page accuracy, since neither one alone is reliable for that specific question.

Common GA4 SEO reporting mistakes

• Treating the default Landing Page report as SEO-accurate. It mixes every channel and uses session-based logic that misattributes internal pages as organic entries.
• Assuming AI Overview traffic is separable from classic organic in GA4’s channel dimension. It isn’t; both live inside Organic Search. Only Search Console’s Search Appearance filter makes that split.
• Reporting the default attribution view as last-click. Since November 2023’s deprecation of the older rules-based models, most properties report against data-driven attribution by default, which is not the same math as last-click.
• Not knowing why a query row disappeared. Thresholding removes low-user rows from the Search Console Queries report silently. Widen the date range before assuming the query volume genuinely dropped to zero.
• Skipping the exclusion filter on the landing page exploration. Confirmation, checkout, and redirect pages will keep polluting organic landing page counts until you filter them out explicitly and maintain that filter as the site changes.
• Setting up the Search Console link after building reporting habits around the default reports. Retrofit is more work than doing it during initial GA4 setup for a new property; see the first 90 days of a new site in 2026 for where this fits in an early setup checklist.

Frequently asked questions

Does GA4 show which keywords drive organic traffic?

Not natively. GA4 has no query dimension on its own. Linking Search Console adds a Google Organic Search Queries report under Library, which shows real search terms with clicks, impressions, CTR, and average position, but only when the two properties are linked and the report is published to your navigation.

Why does GA4’s Landing Page report show pages that shouldn’t be organic entry points?

GA4 assigns the landing page dimension based on the first pageview event in a session, not on click-verified entry data. Redirects, internal navigation quirks, and session-boundary issues can cause confirmation or thank-you pages to appear as if they were organic entry points. Build a filtered exploration with an exclusion list, and cross-reference against Search Console’s landing page data, to correct for it.

Does GA4 separate AI Overview traffic from regular organic search?

No. Google’s default channel grouping documentation places AI Overviews and AI Mode traffic inside the Organic Search channel, alongside classic search results. GA4’s channel dimension cannot split them apart. Use Search Console’s Search Appearance dimension for that separation.

What is the AI Assistants channel in GA4, and when did it launch?

AI Assistants is a default channel Google Analytics introduced on May 13, 2026, which classifies referral traffic from recognized AI chatbots, including ChatGPT, Gemini, and Claude, using an “ai-assistant” medium value. It explicitly excludes Google’s AI Overviews and AI Mode, which remain classified as Organic Search.

Can I still build a custom channel group for AI traffic if I want more control?

Yes. GA4 supports a limited number of custom channel groups per property using source, medium, and campaign rules, including regex patterns. With the native AI Assistants channel now covering the most common cases automatically, most teams that previously used a custom slot for this purpose can retire it and use that slot elsewhere.

How do I link Search Console to GA4?

You need Editor role on the GA4 property and verified site ownership in Search Console (verification can happen during the linking flow). Go to Admin, find Search Console Links under the property column, and follow the linking flow. Each data stream can link to only one Search Console property, and each GA4 property supports only one link per Search Console property.

What data does the GA4-Search Console integration NOT give me?

You cannot cross Search Console metrics with GA4 dimensions beyond landing page, device, and country. There are no time-series charts on the linked reports. Data retention caps at 16 months, matching Search Console’s own retention limit rather than GA4’s longer window for standard events.

Why is Search Console query data appearing in GA4 with a delay?

Google’s documentation states Search Console data appears in Analytics approximately 48 hours after Search Console itself collects it. This is a fixed processing lag on Google’s side, not a configuration issue you can adjust.

What is data thresholding in GA4, and how is it different from sampling?

Thresholding withholds specific rows from a report or exploration when the underlying data includes demographic information or search query information and the row doesn’t have enough total users behind it, based on a system-defined, non-adjustable minimum. Sampling is a separate mechanic where GA4 calculates results from a subset of data rather than the full dataset at high volumes. Both can make numbers look incomplete, but the causes and fixes differ.

How do I get thresholded query rows to show up again?

Google’s documentation lists one remedy: expand the date range. A wider window increases the total user count behind a given row, which can push it back above the visibility threshold. There’s no manual override.

Should I use data-driven attribution or last-click for reporting organic search’s contribution?

It depends on the audience. Data-driven attribution, GA4’s current default in most standard reports, models credit across the full path using machine learning specific to your account, and is generally the more accurate reflection of how channels actually contributed. If you’re presenting to stakeholders who expect a last-click framing (common in legacy SEO reporting), explicitly select the “paid and organic last click” model in the comparison view instead of assuming the default matches their expectation.

What happened to first click, linear, time decay, and position-based attribution in GA4?

Google deprecated these rules-based attribution models in November 2023. Data-driven attribution and the two last-click variants (paid and organic last click, Google paid channels last click) are the models currently available in GA4’s Attribution reports.

Do I need to add my own domain to the referral exclusion list?

Usually not. GA4 automatically excludes self-referrals from your own domain and subdomains. The list exists mainly for third-party domains genuinely outside your control that your users pass through and return from, such as payment processors.

What is cross-domain measurement, and when do I need it?

Cross-domain measurement stitches a single user’s session across multiple domains you control, such as a marketing site and a separate checkout or app domain, so GA4 doesn’t record a new session with a self-referral when the user crosses from one to the other. You need it any time your conversion funnel legitimately spans more than one domain.

How many exclusion domains can I add to a GA4 data stream?

Up to 50 entries per data stream, matched with OR logic, per Google’s documentation.

What exploration type should I use to build a clean SEO landing page report?

A Free-form exploration. Filter the Session default channel group dimension to Organic Search (and AI Assistants if relevant), use Landing page + query string rather than plain landing page, and apply an exclusion filter for known non-entry paths like confirmation and redirect pages.

Can I pull GA4’s channel and landing page data into an external dashboard?

Yes, through the GA4 Data API. The defaultChannelGroup, landingPage, sessionSource, and sessionMedium dimensions are documented in Google’s API reference and let you rebuild your filtered SEO reporting outside GA4’s own interface, useful for combining it with rank-tracking or CMS data in one dashboard.

Why does GA4’s CTR in the Search Console Queries report look like a strange decimal?

Click-through rate in that report displays as a fraction (for example, 0.0588 rather than 5.88%). Reformat it when exporting, or you’ll misread performance by two orders of magnitude in a spreadsheet.

Is GA4 alone enough for SEO reporting, or do I still need Search Console?

You still need Search Console. GA4, even with the link active, cannot cross query data with most of its own dimensions, has no time-series charting on that data, and applies thresholding that Search Console’s own interface doesn’t apply the same way. Use GA4 for session, engagement, and conversion behavior, and Search Console for query and click-level truth.

What should I check first if my organic numbers suddenly look wrong?

Check three things in order: whether the change lines up with the May 2026 AI Assistants channel launch reclassifying traffic that used to sit in Referral, whether a redirect or canonicalization change shifted which URL GA4 records as the landing page, and whether thresholding is hiding rows rather than volume actually dropping. Widen the date range as a first diagnostic step before assuming the traffic is gone.

Key takeaways

GA4’s default reports were never built to answer SEO-specific questions on their own. Organic Search now includes AI Overviews and AI Mode by definition, while the AI Assistants channel launched May 13, 2026 isolates standalone chatbot referrals like ChatGPT, Gemini, and Claude. Link Search Console for the query data GA4 doesn’t natively have, but plan around its 16-month retention cap, 48-hour lag, and the limited set of dimensions it can cross with GA4 data. Build a filtered landing page exploration instead of trusting the default report, watch for thresholding silently withholding low-volume query rows, and confirm which attribution model your organic-contribution numbers are actually using before you present them.

Start with the Search Console link and the custom exploration described above. Those two changes fix the majority of what makes GA4’s SEO reporting feel unreliable, and they take under an hour to set up on a property that doesn’t have them yet.