App Store keyword search volume is how often users type a given term into App Store search — and Apple has never published it. There is no official number. What exists instead are three usable signals: Apple's own popularity index (a 5–100 score inside Apple Search Ads), the demand-ordered autocomplete suggestions in the store's search bar, and modeled popularity scores from ASO tools. Every “12,400 searches per month” figure you've ever seen for an App Store keyword was an estimate built on some mix of those three.
That's not a reason to ignore volume — it's a reason to read it correctly. This guide covers what each signal actually measures, how to check them (including free options), and how to combine volume with difficulty so you spend your 160 indexed characters on keywords that can actually produce installs.
What is App Store keyword search volume?
It's the demand side of every keyword decision: how many people are searching the term you're thinking of ranking for. Roughly 65% of App Store downloads start with a search, so the difference between optimizing for a term nobody types and a term thousands type per day is the difference between ASO that works and ASO theater.
The complication is measurement. Apple exposes exactly one demand signal, and only to advertisers: the Apple Search Ads popularity index, a relative score from 5 to 100 attached to every keyword in an Apple Search Ads account. It isn't a count — a popularity of 40 doesn't mean 40,000 searches — and it compresses hard at the bottom of the range, where a 5 can mean anything from near-zero to a few hundred monthly searches. But it is Apple's own ranking of relative demand, which makes it the calibration target for every serious estimate in the industry.
Why don't ASO tools agree on search volume?
Because they're all modeling different proxies. One tool leans on Apple Search Ads data pulled across client accounts. Another weighs autocomplete positions across markets. Others fold in panel data from SDKs, or signals from the search results themselves. Different inputs, different models, different numbers — which is why the same keyword can show “2,900/mo” in one tool and “8,100/mo” in another and neither is lying. They're disagreeing about a number neither has seen.
The practical takeaway: use volume estimates comparatively, not absolutely. “Keyword A has roughly triple the demand of keyword B” is reliable across every decent tool. “Keyword A gets exactly 4,400 searches” is not, from anyone.
How do you check App Store search volume for free?
Three ways, in ascending order of effort:
- Read autocomplete order. Type your seed keyword into App Store search on a device and watch the suggestions. Apple orders them by search demand, so the suggestion list is a live, free demand ranking — the phrases at the top are the phrases people actually type. Do this per storefront: suggestions in the German store reflect German demand, not translated American demand.
- Use a free popularity score. AppDrift's free keyword difficulty checker shows a popularity score (0–100) next to the difficulty score for any keyword, computed from live store data — no signup, and it works for iOS and Android in any of 150+ storefronts.
- Open an Apple Search Ads account. You don't have to spend anything meaningful: create a campaign draft and the keyword planner shows the official popularity index for every term you add. If a keyword matters enough to build your title around, it's worth thirty minutes to see Apple's own number.
There's now a fourth official source: App Store Connect publishes a monthly market-wide Search Term Rank report with genre-level popularity scores, plus impressions and installs per search term for your own app — our guide to App Store Connect's keyword analytics covers how to access both.
What is a good search volume for a keyword?
The honest answer: there is no good volume in isolation, because volume you can't rank for is worth exactly zero installs. A term with huge demand and a top ten full of apps with hundreds of thousands of ratings will never show your app to anyone. The metric that matters is winnable demand — volume × your realistic chance of reaching the visible ranks.
A practical framework for most indie and small-studio apps:
- Popularity under ~20: usually too little demand to justify title/subtitle characters, unless the term converts exceptionally (e.g., a niche with rabid intent).
- Popularity ~30–60 with difficulty under 60: the sweet spot. Real demand, beatable competition. Our difficulty study across iOS and Android keywords found most of the winnable inventory for smaller apps lives here.
- Popularity 70+: head terms. Only worth targeting directly if you already have the review mass to compete — otherwise target their long-tail variants and let combined-phrase indexing do the work.
Where you currently rank changes the math too. A keyword where you sit at position 11–30 is already half-won: you're indexed and close, so a stronger placement in your title or subtitle can push you onto page one. Check any keyword's live position with the free rank checker before deciding whether it deserves better placement.
Search volume vs. keyword difficulty: which matters more?
Difficulty, for most apps, most of the time. Volume tells you the size of the prize; difficulty tells you whether you can touch it. The classic failure mode in App Store keyword research is stuffing metadata with high-volume head terms (“fitness”, “photo editor”) where the app has no chance of cracking the top 50, while ignoring mid-volume phrases it could own in a month.
The workflow that works: shortlist keywords by demand, then kill everything your app can't plausibly rank for, then spend your indexed characters on what survives. Since title and subtitle words are indexed automatically, make sure you're not wasting keyword-field characters repeating them — the keyword space calculator measures your utilization and flags the waste for free.
How does AppDrift measure keyword popularity?
Honestly, and with stated limits. For every keyword, AppDrift scrapes the live store results and computes two numbers: a difficulty score (0–100, from the strength of the apps actually ranking) and a popularity score (0–100). On iOS, popularity is derived from the review mass across the result set — sustained review flow across ranked apps tracks sustained search demand. On Android it's derived from install counts, because Google exposes installs and hides review recency. The two platforms' scores are therefore not comparable to each other, and we say so in the product rather than pretending otherwise.
Inside AppDrift's keyword rank tracking, both scores sit beside every tracked keyword and update with your daily rank checks — so the volume/difficulty tradeoff is visible at the moment you decide what to push next, not in a separate research tab. The weekly ASO Autopilot plan then does that prioritization for you: it flags keywords ranked 11–30 with beatable difficulty as your highest-ROI pushes.
The bottom line
Nobody outside Apple knows true App Store search volume — including every tool selling you a precise number. What you can know: relative demand (autocomplete order, popularity indexes), your competitive odds (difficulty), and your current position (rank). Those three, read together, answer the only question that matters: which keywords deserve my 160 characters this month? Estimate humbly, compare relatively, and put your characters where demand and winnability overlap.
