If your organic search report is full of (not provided), GA4 is not broken. Google
is hiding individual organic search queries before they reach Google Analytics, so the
session can still be counted as Google organic search while the exact keyword is withheld.
That is frustrating, but it is not a dead end. You can still rebuild useful keyword visibility with Search Console, GA4's Search Console reports, and a landing-page analysis workflow. The key is to stop looking for a native GA4 keyword dimension that does not exist and start combining the data sources Google still gives you.
Quick answer
SEO not provided means Google Analytics knows a visit came from organic Google Search, but it does not receive the exact search query. To get useful keyword data back, connect Search Console to GA4, use the Google Organic Search Queries report, and compare query data with landing pages and conversions.
Key Takeaways
- →
(not provided)is expected behavior, not an error. Google withholds organic query data for privacy reasons. - → GA4 has no native organic keyword dimension. Keyword data requires the Search Console integration.
- → The best free fix is linking Search Console to GA4 and publishing the Search Console collection from the Reports Library.
- → Search Console caps at 1,000 top queries and keeps 16 months of data. You cannot recover every hidden keyword exactly.
- → Use query data for demand signals and landing-page data for behavior. Combine both to make better content and conversion decisions.
What does SEO not provided mean?
SEO not provided means the search engine did not pass the user's organic keyword query into Google Analytics. In older Universal Analytics reports, this appeared as (not provided) in organic keyword rows. In GA4, the same underlying issue shows up as a lack of native organic keyword detail unless you use the Search Console integration.
The visit is still tracked. You can see that the session came from Google organic search, and you can analyze landing pages, engagement, conversions, and revenue. What you cannot see directly in GA4 is the exact organic query that caused that individual session.
For SEO work, that means keyword analysis becomes probabilistic. You are not matching one person, one query, one session, and one conversion inside GA4. You are combining query-level Search Console data with page-level analytics data to make a working diagnosis.
Why Google Analytics hides organic keywords
Google's stated reason was privacy and secure search. As Google moved search activity to HTTPS, the query string was no longer passed to analytics platforms in the old referral-data pattern. The privacy logic is simple: the search query can contain sensitive personal information, so Google does not expose it at the individual analytics-session level.
That original 2011 change affected signed-in users first. Over time, organic keyword visibility in analytics tools collapsed. Today, for practical purposes, assume Google Analytics is not the place to find complete organic Google keyword data.
GA4 makes the confusion worse
GA4 also changed the reporting model. Many marketers remember Universal Analytics reports
where a keyword row existed, even if most rows were (not provided). GA4 is event-based
and does not provide a built-in organic keyword dimension that behaves like the old UA
keyword report.
That does not mean GA4 has no search-query reporting at all. The Search Console integration creates two GA4 reports: Google Organic Search Queries and Google Organic Search Traffic. The difference is that those reports are Search Console data surfaced inside GA4, not GA4 magically recovering every hidden keyword.
This distinction matters when explaining the issue to a client or executive. GA4 can help you analyze SEO performance, but query data comes through Search Console constraints.
The best ways to get useful keyword data back
You have three realistic options. Start with the free, first-party sources, then use paid tools only when the extra modeling or competitive data is worth the cost.
| Method | Cost | Best for | Main limitation |
|---|---|---|---|
| Search Console in GA4 | Free | Seeing queries, clicks, impressions, CTR, and average position near GA4 reports | Search Console dimensions and retention limits apply |
| Landing page inference | Free | Connecting query intent to page behavior and conversions | Infers keyword intent rather than proving exact session keywords |
| Paid SEO tools | Paid | Competitive research, keyword universe expansion, modeled recovery | Third-party estimates are not first-party conversion attribution |
Method 1: Search Console in GA4
This is the best free fix for most sites. After you link a GA4 web data stream with a Search Console property, GA4 shows a Google Organic Search Queries report with search queries and Search Console metrics for the linked property.
Use this report to answer:
- → Which queries are driving impressions?
- → Which queries earn clicks?
- → Which terms have high impressions but low CTR?
- → Which query themes are attached to pages that should be refreshed?
The key mindset shift: Search Console query data is pre-click search performance. GA4 behavior data is post-click site performance. You need both.
Method 2: Landing page inference
The landing page method is the practical workaround when you care about conversions. Start with a page that receives Google organic traffic in GA4. Then open Search Console and filter Performance data to that same landing page. The query list tells you which searches most likely drove visibility and clicks.
This does not recover the exact query behind every conversion. It gives you a defensible keyword cluster for that page. Use it to decide whether to rewrite a title, expand a section, add an FAQ, or create a supporting article.
Method 3: Paid keyword modeling tools
Tools such as Keyword Hero, Semrush, and Ahrefs can model hidden keyword attribution, show the broader keyword universe, or estimate the organic keywords a page ranks for. Treat them as decision support, not a replacement for Search Console and GA4. If a tool says a page likely ranks for a term, verify it in Search Console before acting on it.
How to connect Search Console to GA4
You need owner or edit-level access to the right properties before you start. The GA4 property must have a web data stream, and the Search Console property must represent the same site.
- 1 Open GA4 and go to Admin.
- 2 In the property settings, find Search Console links.
- 3 Choose the Search Console property you want to connect.
- 4 Choose the GA4 web data stream for the same site.
- 5 Submit the link.
- 6 Open Reports > Library.
- 7 Find the Search Console collection and publish it if it is not already visible.
- 8 Open the Google Organic Search Queries and Google Organic Search Traffic reports.
Common miss: The Search Console collection is unpublished by default. If you linked Search Console but still cannot find the Queries report, go to Reports Library and publish the collection. This is the most common reason teams think the setup did not work.
After the link is active, do not expect instant historical data across every GA4 report. Search Console data is available 48 hours after collection, and Search Console keeps the last 16 months of data. If you need longer trend history, export and store it on a schedule.
Use the landing page method when query data is incomplete
The most useful SEO workflow is usually page-first, not keyword-first.
Start in GA4
- 1 Go to organic traffic reports and isolate Google organic sessions.
- 2 Find landing pages with meaningful traffic, engagement, leads, or conversions.
- 3 Export the landing pages that matter.
Then go to Search Console
- 1 Open the Performance report and filter to one landing page at a time.
- 2 Review the Queries tab and sort by clicks, impressions, CTR, and average position.
- 3 Group similar queries into intent clusters.
How to interpret the page-query map
- → High impressions, low CTR: rewrite the title tag and meta description, or better match the dominant query intent.
- → High clicks, low engagement: check whether the intro answers the query quickly enough.
- → Good traffic, weak conversions: inspect the offer, CTA, internal links, and next-step path.
- → Many similar question queries: add an FAQ or a clearer how-to section.
- → Queries outside the page's core topic: split the content or create a supporting article.
Limits to know before you trust the data
Search Console is the best free source for Google organic query data, but it has hard limits.
| Limit | What it means for you |
|---|---|
| 1,000 top queries max | Long-tail-heavy sites miss detail on low-frequency queries |
| 16 months data retention | Export regularly if you need longer trend history |
| Search Console dimensions only | Cannot combine every GA4 audience or conversion segment with query rows directly |
| 48-hour data lag | Do not compare today's GA4 conversions with today's Search Console queries and expect a match |
| Rare queries withheld | Very low-frequency queries are anonymized for privacy — they will not appear even inside the 1,000 limit |
The practical takeaway: use Search Console for query visibility, GA4 for site behavior, and exports or a data warehouse when you need durable history beyond 16 months.
What to do after you recover the keyword clues
Once you can see query patterns again, do not stop at reporting. Use the data to improve pages.
- → Pages ranking for the right query but failing to win clicks need better titles, clearer angles, or a stronger answer in the opening section.
- → Pages getting clicks but weak engagement need a tighter intro, better structure, and stronger alignment with query intent.
- → Pages getting traffic but no leads need better internal paths, CTAs, and proof that the next step is worth taking.
A good next step is an SEO content audit . Build a list of pages with high impressions, low CTR, or weak conversion behavior, then decide whether each page needs a title refresh, section expansion, FAQ coverage, consolidation, or a new supporting article. If you are also troubleshooting why traffic is not converting to leads, the conversion leak guide covers that side in detail.
(not provided) is annoying because it removes easy keyword attribution. But it also pushes you
toward a better SEO workflow: query data for demand, landing-page data for behavior, and
conversion data for business impact.
Not sure which pages are worth fixing first?
Use the audit to connect query data, landing-page behavior, and AI visibility gaps before you spend time rebuilding the wrong content.
Frequently asked questions
What does (not provided) mean in Google Analytics?
It means Google Analytics recorded organic search traffic but did not receive the exact search query. Google created the (not provided) token after secure search changes meant organic query terms were no longer passed for affected visits.
Why does Google Analytics not show keywords?
Google Analytics does not show most organic Google keywords because the query is withheld for privacy and secure-search reasons. GA4 also does not include a native organic keyword report like many people remember from Universal Analytics.
How do I see organic keywords in GA4?
Connect Search Console to GA4, publish the Search Console collection from the Reports Library if needed, then open the Google Organic Search Queries report. That report displays search queries and Search Console metrics for the linked property.
How do I connect Search Console to GA4?
In GA4, go to Admin, open Search Console links, choose the matching Search Console property, select the correct web data stream, and submit the link. Then check Reports Library and publish the Search Console collection if it is hidden by default.
Can I recover not provided keywords exactly?
Not completely. You can recover useful keyword visibility, but not perfect session-level keyword attribution for every organic visitor. Search Console, landing-page inference, and paid tools can show strong keyword clues, but each has limits.
What is the difference between Search Console and GA4 keyword data?
Search Console shows Google Search performance before and at the click: queries, impressions, clicks, CTR, and position. GA4 shows what users did after they arrived on your site. The best SEO analysis combines both instead of expecting one report to answer everything.
(not provided) is not something you fix inside GA4 with one hidden setting. It is a
privacy-driven reporting limitation. The practical fix is to connect Search Console, use
query and landing-page reports together, and turn those clues into page improvements. You
will not recover every keyword, but you can recover enough signal to make better SEO
decisions.
Use the AI Visibility Audit to identify which pages are worth fixing based on real query and behavior data, then use the findings to rebuild only the pages that truly have an intent, structure, or visibility problem. If your SEO is not working more broadly, start with that diagnostic framework before investing in new content.