Not Provided in GA4: Search Queries, Not Set and Practical Analysis

April 11, 2026

Author: Shusaku Yosa

“Not provided” describes the problem of organic search keywords not being supplied to analytics tools. GA4 has no setting that restores each visitor’s Google organic query and joins it to an individual conversion. Use Google Search Console (GSC) for search-query trends and GA4 for behavior after a visit.

Start by checking the field you are looking at. Session manual term is associated with manually tagged campaign information such as utm_term; it is not a hidden repository of Google organic search queries.

Distinguish the terms

Term	Meaning	Appropriate action
Not provided	Withheld organic keyword information	Analyze aggregate queries in Search Console
(not set)	A value is unavailable for a particular dimension	Check the dimension and collection conditions
utm_term / manual term	A value supplied in a campaign URL	Review URL tagging and naming conventions
Search Console query	A Google search query associated with site visibility	Analyze impressions, clicks and position

Treating every missing value as search encryption can hide genuine collection problems or an unsuitable dimension. Adding UTM parameters does not recover a visitor’s original organic query.

Investigate a page in Search Console

Open the correct website property and select a reporting period.
Filter the search-performance report to the article’s exact URL.
Review queries, impressions, clicks, CTR and average position.
Segment by country, device or search type when it changes the interpretation.
Compare the search intent with the page’s answer and record any editorial change.

Search Console anonymizes some query information and limits displayed data. Query totals can differ from page totals. A missing row is not proof that the URL is unindexed; inspect index status separately.

Combine page-level evidence

These are illustrative diagnostic patterns, not measured results.

Observation	Working hypothesis	Next check
Many impressions, few clicks	Intent, position or search-result presentation needs work	Query-specific rankings and displayed titles
Search clicks but fewer GA4 sessions	Collection, consent, navigation or scope differs	Tags, URLs, periods and hostnames
Organic visits but few qualified outcomes	The offer, audience or path may not align	Landing page, CTA, form and success measurement

Use the GA4 Landing page report to study entry pages and an appropriate session acquisition dimension to identify organic visits. Pages and screens includes pages viewed later in a journey, so it does not answer exactly the same question.

Align dates and URLs, but do not expect clicks and sessions to match. They describe different actions, and the systems have different collection rules. Query-to-page analysis supports hypotheses; it does not establish that a particular person searched a term and then registered.

Link Search Console with GA4

With the required Analytics permissions and Search Console ownership, create a Search Console link in GA4 Admin and select the intended website property and web stream. If the reports are absent, check whether the Search Console collection has been published in the report library.

The integration provides organic query and organic search traffic reports. It does not allow every GA4 dimension or conversion metric to be freely joined to each query. Check supported combinations, available history and reporting delay in the official documentation.

Use paid-search evidence carefully

An advertising keyword, an actual paid search term and an organic query are different datasets. A successful ad topic can suggest a content hypothesis, but its conversion rate is not automatically the conversion rate for organic readers.

For repeatable work, keep a worksheet containing the page URL, the question it answers, observed Search Console queries, GA4 entry metrics, the proposed change and the change date. Leave unknown information unknown. That makes an editorial decision auditable without pretending to recover private search data.