Google Search Console Hidden Query Estimator

Free, no signup. Search Console never shows you every query — it anonymizes a share of clicks and impressions below its privacy threshold. Upload your GSC performance export and an Ahrefs or Semrush keyword export, and this tool estimates which of your ranking keywords plausibly explain the gap, page by page.

Search Console export limit: the UI can return only about 1,000 representative rows, and privacy-anonymized queries are omitted. Treat every analysis as a view of the exported sample, not the complete query set.

or paste CSV text
or paste CSV text
or paste a GSC Queries CSV / Google Search Console CSV Analyzer curve JSON

A Queries CSV is fitted into an impression-weighted curve; a Workbench {"curve":[…]} export is used as-is. Both are estimates, not actual hidden-query attribution.

Example data — replace with your own, then press Find hidden queries

Runs entirely in your browser — nothing you paste is uploaded or stored. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Hidden Query Finder? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 

Worked example

Say a page's GSC export shows 142 clicks and 4,800 impressions, but the Queries export only lists two visible queries for it, totalling 92 clicks:

Page,Clicks,Impressions,CTR,Position
https://example.com/blog/best-running-shoes,142,4800,3.0%,5.2
Query,Page,Clicks,Impressions,CTR,Position
running shoes for flat feet,https://example.com/blog/best-running-shoes,58,1900,3.1%,6.1
best running shoes 2026,https://example.com/blog/best-running-shoes,34,1100,3.1%,4.8

Your Ahrefs export shows the same page also ranking for two keywords that never appear as a visible GSC query:

Keyword,URL,Position,Volume
best running shoes for overpronation,https://example.com/blog/best-running-shoes,7,880
cushioned running shoes review,https://example.com/blog/best-running-shoes,11,320
running shoes for flat feet,https://example.com/blog/best-running-shoes,6,590

The tool computes 142 − 92 = 50 hidden clicks on this page, then allocates that 50 across the two candidate keywords by estimated volume × CTR-for-position — giving the higher-volume, better-ranking keyword the larger share, each labeled with a confidence tier and a plain-language reason.

The directly observed coverage is 92 ÷ 142 = 64.8% visible-query click coverage. The remaining 35.2% is measurable as a gap, but its query strings are not recoverable from Search Console; candidate allocation is a separate modeled layer.

Sample report

Pressing Try an example loads this page plus a second page with no hidden clicks, and renders:

Example data — captured by running this page's own analyzer against the "Try an example" dataset

200
total clicks
75%
visible-query click coverage
25%
estimated hidden click share
50
estimated hidden clicks
1,800
estimated hidden impressions
26.1%
estimated hidden impression share
1 / 2
pages with hidden clicks
ahrefs
keyword source detected
https://example.com/blog/best-running-shoes 50 hidden clicks (35.2%) · 1,800 hidden impressions · 2 candidates
best running shoes for overpronationMedium confidence
ahrefs · position 7.0 · volume 880 · ~43 estimated clicks (85.9% of hidden share)
Ranks position 7 for this URL with search volume; allocated a share of the hidden clicks by estimated CTR.
cushioned running shoes reviewLow confidence
ahrefs · position 11.0 · volume 320 · ~7 estimated clicks (14.1% of hidden share)
One of several candidates for this page; allocation is a rough proportional split, not a precise attribution.
  • Only 1 of 2 pages has hidden clicks — the second page's visible queries already add up to its full click total, so there's no gap to explain and no candidates are shown for it.
  • The higher-volume, better-ranking keyword takes the larger share (85.9% vs. 14.1%) — not an even split — because allocation is proportional to estimated volume × CTR-for-position, not headcount. See how confidence tiers are assigned ↓.
  • Site-wide hidden click share (25%) can differ a lot from one page's share (35.2%) — always read the per-page row for a specific page, not just the rollup.
  • Visible coverage and hidden share are complements — the example exposes 150 of 200 clicks in visible query rows, so visible-query click coverage is 75% and the remaining 25% is the hidden gap.

How to use it

  1. In Search Console, go to Performance → Search results, and export the Pages tab and the Queries tab (or a combined page × query export if your workflow produces one) as CSV.
  2. Export your site's organic keywords report from Ahrefs (Site Explorer → Organic keywords) or Semrush (Organic Research → Positions), including Keyword, URL, Position, and Volume columns.
  3. Upload or paste both into the boxes above and press Find hidden queries. No files handy? Click Try an example to see it run on sample data.
  4. Read the site rollup for the overall visible-vs-hidden click share, then work down the per-page table — expand a page to see which keywords are the likely candidates and why.
  5. Use Export CSV to pull every page/candidate row into a spreadsheet.

How it works

  1. Per page, hidden share = totals minus visible queries. For every page in your GSC pages export, the tool sums the clicks/impressions of every visible query attributed to that page and subtracts from the page's own totals. Whatever is left is the hidden click/impression share GSC didn't break out.
  2. Candidates come from your SEO-tool export. Every Ahrefs/Semrush keyword ranking for that page's URL (matched after normalizing both URLs) that doesn't already match a visible GSC query — checked with exact, stemmed, and small-edit-distance matching so near-duplicate phrasing doesn't create false candidates — becomes a hidden-query candidate.
  3. Scored by volume × CTR-for-position. Each candidate's raw score is its search volume multiplied by an estimated click-through rate for its ranking position, using a CTR-by-position curve blended from published aggregate CTR studies (Default organic CTR by position — a blend of published aggregate CTR studies; intentionally conservative. Users should override with a curve fit from their own GSC Queries export whenever possible.).
  4. Hidden clicks allocated proportionally. A page's hidden click total is split across its candidates in proportion to their raw scores — not claimed in full by each one.
  5. Confidence tiers, not certainty. A single unambiguous candidate is marked high confidence; a top-10 ranking with real volume competing against other candidates is medium; everything else is low. Every row states its reasoning.

Every number here is a modeled estimate, not a Search Console disclosure. Google never reveals which specific queries are hidden — this tool infers plausible candidates from public ranking and volume data you already have.

Limitations

This is an estimate, not ground truth: it can only surface candidates that exist in your SEO-tool export, so a hidden query with no third-party rank tracking (or one your tool doesn't track) will never appear. The CTR-by-position curve is a published-study blend, not your site's own curve, so absolute click estimates are directional. If your GSC export has no Page column on the queries side, the tool falls back to treating the visible query set as site-wide — a coarser but honest approximation rather than falsely calling a query "hidden" for a page it may not belong to. And GSC's privacy threshold itself is undocumented and can change, so the size of the true hidden share is unknowable — only the gap between totals and visible rows is measurable.

Frequently asked questions

What does Google Search Console actually hide?

Below a certain volume of impressions and clicks, Google anonymizes individual queries for privacy reasons — usually because the query is rare enough (or contains something identifying) that surfacing it could expose what a specific person searched for. The page-level and site-level totals in GSC still include that hidden traffic; only the per-query breakdown omits it. That is why a page’s Top pages clicks/impressions routinely exceed the sum of its visible Top queries rows.

How does this tool guess what the hidden queries are?

It takes every keyword your SEO-tool export (Ahrefs or Semrush) says a page ranks for, drops the ones that already appear as a visible GSC query for that page, and treats the rest as candidates. Each candidate is scored by estimated volume × CTR-for-its-ranking-position, then the page’s hidden click/impression delta is allocated across candidates proportional to that score. It is a plausibility estimate built from public ranking + volume data, not a disclosure of real Search Console data — GSC never reveals the actual hidden queries.

Why do some pages show no candidates even though they have hidden clicks?

That happens when no row in your SEO-tool export matches that page’s URL, or when the URL matches but every keyword found there also already appears as a visible GSC query (so there is nothing left over to explain the gap). The hidden click/impression numbers are still shown — there is just no keyword-level guess to attach to them.

What do the confidence tiers mean?

High confidence is a page with exactly one plausible candidate keyword — the hidden share almost certainly belongs to it. Medium confidence is a candidate ranking in the top 10 with real search volume, competing against other candidates for the same hidden share. Low confidence is everything else: multiple candidates splitting a rough proportional allocation, or a keyword ranking outside the top 10. Treat low-confidence rows as directional, not decisive.

Which CSV formats does it accept?

GSC exports from either the "Pages" or "Queries" tab of the Search Console Performance report (uploaded separately or together), and organic-keyword exports from Ahrefs or Semrush (Keyword, URL/Landing Page, Position, Volume/Search Volume columns). The format of each file is detected automatically from its header row — you do not need to tell the tool which is which.

Is any of my data uploaded anywhere?

No. All parsing and scoring happens in your browser with plain JavaScript — the CSVs never leave your machine, and nothing is sent to our server or stored. Close the tab and the analysis is gone.

Feature requests for Hidden Query Finder

Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.

Loading…

➕ Request a feature

New requests are reviewed before they appear here.

À propos de l’outil

Estimez les requêtes que Google Search Console masque dans les exports en rapprochant les données GSC, Ahrefs ou Semrush et la courbe CTR choisie.

Fonctionnalités

  • Import des exports GSC et SEO au format CSV.
  • Déduction de candidats à partir des écarts de clics et d’impressions par page.
  • Allocation transparente selon le volume estimé et la position.
  • Niveaux de confiance, exemples de calcul et export CSV des résultats.

Fonctionnement

L’outil soustrait les requêtes visibles des totaux de chaque page, puis estime le delta masqué. Il exclut les requêtes déjà visibles, score les candidats par volume estimé multiplié par le CTR de leur position et répartit le delta selon ce score. Tout est traité dans le navigateur.

Limites

  • GSC ne révèle jamais les requêtes réellement masquées ; les candidats sont des estimations plausibles.
  • Les positions, volumes et courbes CTR de tiers peuvent être incomplets ou datés.
  • Les clics masqués sont répartis proportionnellement et ne constituent pas une attribution précise.

Questions fréquentes

Que masque réellement Google Search Console ?

Les exports peuvent agréger des requêtes à faible volume ou protéger certains termes ; ils ne permettent pas de retrouver les chaînes exactes.

Les résultats sont-ils des données GSC révélées ?

Non. Ce sont des candidats inférés à partir des totaux, des rangs et des volumes fournis.

Que signifient les niveaux de confiance ?

Ils résument la quantité et la cohérence des données disponibles ; une confiance élevée reste une estimation.

Mes données sont-elles téléversées ?

Non. Les fichiers et les calculs restent dans votre navigateur.