You cannot fully unlock (not provided) keywords inside Google Analytics itself, in GA4 or the old Universal Analytics. Google began encrypting search queries in 2011, and by 2013 most sites saw 95%+ of organic keywords hidden, per Search Engine Watch. The real fix is linking Google Search Console, which still records the actual query behind every click.
That single fact trips up a lot of people who go digging through GA4's settings looking for a hidden report or a checkbox to flip. There isn't one. What follows is where the label came from, why GA4 handles it differently than the old Universal Analytics did, and the specific steps that actually recover usable keyword data today.
(not provided) exists because Google began encrypting search queries for privacy, starting with signed-in users on October 18, 2011. Bounteous tracked 117 websites in the two weeks after that rollout and found organic keywords going dark at an average rate of 9.13%, ranging from 3.82% to 28.33% depending on the site. Google made the encryption universal on September 23, 2013, and Search Engine Watch reported that many sites then saw 95% or more of their keywords replaced with the (not provided) label almost overnight.
The change had nothing to do with Analytics directly. Google switched signed-in search, then all search, over to HTTPS so the query itself wouldn't leak to the site a searcher clicked through to. Analytics still recorded that a visit came from Google organic search. It just lost the referrer string that used to carry the actual term. Search Engine Land's Danny Sullivan framed the fuller 2013 move partly as a response to concerns about government surveillance of search activity, and Google has given no sign it plans to reverse course.
Universal Analytics carried the (not provided) label for the rest of its life, right up until Google stopped processing UA data on July 1, 2023. When GA4 replaced it, Google didn't bring the label along. It removed the keyword column entirely, which is the subject of the next section.
No. GA4 has no keyword report and no (not provided) label, because it never had a query column to begin with. Ahrefs puts it plainly in its own analysis of the issue: there is no (not provided) in GA4 because there is no keyword column to put it in. The underlying problem, that Google Search hides the query from the referring site, is identical to what Universal Analytics dealt with. GA4 simply stopped pretending it could show you anything close to it natively.
Open GA4's default Acquisition or Traffic acquisition reports and you'll see channel groupings like Organic Search, source and medium, and even the specific search engine. What you won't see anywhere in a stock GA4 property is the search term itself. That gap is exactly why linking Search Console matters more in GA4 than it did in Universal Analytics: there's no built-in placeholder left pointing you toward the fix. You don't need Analytics 360 for any of this either; it works on free GA4 the same way it works on the enterprise tier.
GA4's Acquisition reports can't reveal search keywords on their own, and the same referrer-hiding problem shows up elsewhere in Analytics too. Our guide on how to find backlinks in Google Analytics covers a similar workaround for referral data that GA4 doesn't surface directly.
In GA4, go to Admin, then Product links, then Search Console links, and connect the Search Console property that matches your verified domain. Once linked, two reports become available in your reports library: Google Organic Search Queries, which lists the actual search terms alongside clicks, impressions, CTR, and average position, and Google Organic Search Traffic, which maps that same query data to landing pages. Google's own documentation confirms both reports pull directly from your linked Search Console property.
If you're unclear on what each tool actually measures before connecting them, our comparison of Google Search Console vs Google Analytics breaks down which metrics live in which platform.
Two limits carry over from Search Console itself. Data only goes back 16 months, matching Search Console's own retention window, so linking today won't backfill years of old queries. And query rows below a low volume threshold get grouped or dropped for privacy, the same behavior you'd see inside Search Console directly. For the deeper keyword-research side of Search Console beyond just recovering GA4 data, see our guide to Google Search Console for keyword research.
The Search Console web interface caps exports at 1,000 rows, but the Search Analytics API, the Looker Studio connector, and Bulk Data Export all return far more. The API supports pagination up to roughly 50,000 rows a day per property, and Google's Bulk Data Export feature, added in February 2023, schedules a full daily export straight into BigQuery with no row cap at all.
For most sites, the UI's 1,000-row cap only becomes a real problem once you're diagnosing a large content library or an ecommerce catalog. A local service business with a few dozen ranking pages rarely needs more than what the Performance report already shows. If you outgrow it, Looker Studio's free Search Console connector is usually the fastest fix, since it needs no code and refreshes daily, while Bulk Data Export is the right call once you want years of history warehoused in BigQuery for deeper analysis.
Cross-reference the Search Console Pages report with the Performance report's query breakdown for that one URL, or use GA4's Google Organic Search Traffic report, which already joins landing page and query data for you. Filter by the page you care about, and Search Console shows every query that earned an impression or a click on it, ranked by clicks. That tells you which terms are actually driving a page's organic sessions even when GA4's own Landing page report only shows you the URL, not the search term.
This landing-page-first approach earns its keep on pages where the query report alone doesn't explain the traffic. It's the same instinct behind measurable wins like growing Zluri's organic traffic by 45%: find what's already earning clicks at the page level before deciding whether a page needs a rewrite or a brand-new URL entirely, rather than guessing.
Paid tools like Keyword Hero and Semrush's Organic Traffic Insights combine your Search Console data with machine-learning matching to estimate a keyword for sessions GSC alone doesn't fully explain, but neither one, nor any free tool, unlocks every hidden query. They're worth the cost mainly when you want automatic keyword-to-session mapping inside a dashboard you don't want to build by hand.
| Method | Cost | Row or keyword limit | Best for |
|---|---|---|---|
| Search Console Performance report (UI) | Free | 1,000 rows in the interface | Quick checks on your top queries |
| Search Console + Looker Studio or API | Free | Up to about 50,000 rows a day | Full-catalog analysis without writing code |
| Search Console Bulk Data Export (BigQuery) | Free (BigQuery usage may apply at scale) | No cap | Long-term warehousing and historical trend analysis |
| Ahrefs Webmaster Tools | Free for verified sites | No 1,000-row cap | Teams already using Ahrefs for the rest of their SEO stack |
| Keyword Hero / Semrush Organic Traffic Insights | Paid | Varies by plan | Automating keyword-to-session mapping at scale |
Treat every option in that table as a way to read data Google already collects inside Search Console. None of them, including the paid ones, restores the literal query for a search Google chose not to share. Any tool promising to unlock 100% of not provided keywords is overselling a statistical estimate as certainty.
Once your query data is flowing again through Search Console, roll it into your broader Google Analytics SEO reporting setup so keyword, landing page, and conversion data live in one place instead of three separate tabs.
What does (not provided) mean in Google Analytics? (not provided) is the label Google Analytics shows in place of an organic search keyword when Google's encrypted search hides the actual query from the site the visitor clicked through to. It first appeared after Google began encrypting search in 2011 and covered the large majority of organic keywords in Universal Analytics from 2013 onward.
Why did Google hide keyword data from Analytics? Google encrypted search primarily to protect user privacy, starting with signed-in users in October 2011 and expanding to all searches by September 23, 2013. Search Engine Land's Danny Sullivan noted the fuller 2013 rollout was also framed partly as a response to concerns about government surveillance of search activity.
Does GA4 show (not provided) keywords? No. GA4 removed the keyword column entirely rather than carrying the (not provided) label forward, so there is nothing to unlock inside GA4 itself. The same underlying limitation, that Google Search doesn't pass the query to the destination site, still applies.
How do I connect Google Search Console to GA4? In GA4, go to Admin, then Product links, then Search Console links, and connect the verified Search Console property that matches your GA4 web data stream. Once linked, the Google Organic Search Queries and Google Organic Search Traffic reports become available in your reports library.
Why does Search Console only show 1,000 rows of keyword data? That 1,000-row cap is a limit of the Search Console web interface, not the underlying data. The Search Analytics API and the Looker Studio connector can return up to roughly 50,000 rows a day, and Bulk Data Export to BigQuery removes the cap entirely.
Can I get more than 1,000 keywords out of Search Console? Yes. Connect Search Console to Looker Studio using its built-in connector for a free, no-code export well beyond 1,000 rows, or set up Bulk Data Export to BigQuery, which Google added in February 2023 for uncapped daily exports.
How do I match hidden keywords to a specific landing page? Filter the Search Console Performance report by that single URL to see every query tied to it, or use GA4's Google Organic Search Traffic report, which already joins landing pages with the query data pulled from your linked Search Console property.
Are paid tools like Keyword Hero worth using for not provided data? They can help if you want keyword-to-session mapping automated inside a dashboard, since tools like Keyword Hero and Semrush's Organic Traffic Insights use machine learning to estimate a likely keyword for sessions Search Console alone doesn't fully explain. They add a convenience layer over Search Console data rather than a separate source of hidden information.
Is there a way to unlock 100% of not provided keywords? No. Google does not release the underlying query for every search, and no free or paid tool can recover data Google has chosen not to share. Search Console plus its exports get you the closest, most complete, and most accurate picture available.
Stop searching GA4's settings for a hidden (not provided) toggle. It doesn't exist, and it never will, because GA4 was built without a keyword column from day one. Link Search Console today so you start capturing real query data going forward, then decide whether the 1,000-row UI cap is actually a problem for your site before reaching for the API or a paid tool. If you want a second pair of eyes on whether your GSC and GA4 setup is capturing everything it should, get a free SEO audit from Rankite and we'll check your tracking end to end.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.
