How to Find Not Provided Keywords in Google Analytics
If you've ever dug into your Google Analytics traffic sources and found a wall of (not provided) where your organic keyword data should be, you're not alone. Since 2013, Google has encrypted search queries for users signed into Google accounts, replacing actual keyword data with this frustrating placeholder. Understanding why this happens — and what you can actually do about it — is essential for any web developer or site owner trying to make sense of organic traffic.
Why Google Analytics Shows "(Not Provided)"
When a user searches on Google while logged into their Google account, their query is sent over a secure HTTPS connection. As a result, the keyword they used doesn't get passed along in the referral data to your analytics platform. Google Analytics receives the visit but has no keyword to report — so it logs it as (not provided).
Over time, this has ballooned. For most websites, (not provided) now accounts for 85–99% of all organic keyword data in Google Analytics. This isn't a bug you can fix on your end — it's a deliberate privacy and infrastructure decision by Google.
What You Can Actually Recover: The Real Methods
You can't undo Google's encryption, but you can reconstruct a meaningful picture of what keywords are driving traffic using a few reliable approaches.
1. Google Search Console (The Most Direct Method)
Google Search Console (GSC) is the most authoritative source for organic keyword data because it comes directly from Google's index. Under Performance > Search Results, you'll find:
- Queries — the actual search terms users typed
- Clicks — how many times each query sent a visitor to your site
- Impressions — how often your pages appeared in search results
- CTR — click-through rate per query
- Average position — where you ranked for each term
GSC data isn't perfect — it samples data, rounds small numbers, and limits history to roughly 16 months — but it's as close to the real keyword picture as you'll get without a paid tool.
2. Linking Google Search Console to Google Analytics (GA4)
In GA4, you can link your Search Console property directly. Once connected, you gain access to the Search Console collection inside GA4, which includes reports like:
- Queries — shows organic search terms alongside landing page performance
- Google organic search traffic — breaks down sessions by query and page
This integration lets you cross-reference keyword data with on-site behavior metrics like engagement rate, conversions, and session duration — something you can't do inside Search Console alone.
To link them: go to GA4 Admin > Property Settings > Search Console Links, then follow the prompts to connect your verified GSC property.
3. Landing Page Analysis as a Proxy 🔍
When keyword-level data isn't available, landing page data becomes your next best signal. The logic: if you know which pages receive organic traffic, and those pages are optimized for specific keywords, you can infer what terms are likely driving that traffic.
In GA4, navigate to Reports > Acquisition > Traffic Acquisition, filter by Organic Search, then break down by Landing Page. Pair this with your GSC query data filtered to those same URLs to build a keyword-to-page map manually.
This isn't exact, but it's a practical workaround used regularly by SEO professionals.
4. Third-Party SEO Tools
Platforms like Ahrefs, SEMrush, Moz, and Similarweb estimate organic keyword rankings and traffic using their own crawl data and clickstream modeling. These tools can show:
- Keywords your pages rank for
- Estimated traffic volume per keyword
- Competitor keyword comparisons
- SERP feature visibility (featured snippets, People Also Ask, etc.)
The tradeoff: these are estimates, not actual Analytics data. Accuracy varies by site size, niche, and how frequently the tool crawls your domain.
Factors That Affect How Much Data You Can Recover
Not every site owner will get the same results from these methods. Several variables affect how complete your keyword picture ends up being:
| Factor | Impact on Data Recovery |
|---|---|
| GSC verification status | Must be verified to access any query data |
| Site traffic volume | Low-traffic sites see more data sampling and suppression |
| GA4 vs. Universal Analytics | GA4 has better native GSC integration |
| Brand vs. non-brand traffic mix | Branded queries often dominate, obscuring informational terms |
| International traffic | GSC data may vary by country/language segment |
| Third-party tool budget | Paid tools provide broader keyword coverage than free tiers |
What "(Not Provided)" Can Still Tell You
Even the placeholder itself carries information. A sharp rise in (not provided) sessions tied to a specific landing page suggests that page gained organic visibility for something — your job is to use GSC to find out what. A drop in those sessions points to ranking loss or click-through decline, again traceable through Search Console's performance filters.
🔎 Treating (not provided) as a starting signal — rather than a dead end — is what separates analysts who work around it from those who give up on organic keyword insight entirely.
The Variables That Make This Personal
How useful these methods are for you depends heavily on your specific situation: whether you're running a content-heavy blog or a product-driven e-commerce site, whether you've already linked GSC to GA4, how much of your traffic comes from branded versus informational queries, and whether your budget allows for third-party tooling.
A developer running a small portfolio site will piece together keyword data very differently than a team managing a high-traffic SaaS platform. The methods above are the same — but which combination actually fills the gap, and how much effort it justifies, comes down to what you're trying to measure and why.