The App Store does not give founders a clean organic search volume number. That is the first thing to accept. If a tool shows a keyword volume, daily installs by keyword, or exact traffic number, it is almost always a model built from available signals, not a public Apple metric.
That does not make keyword research useless. It means the work has to be done like a founder would make any other product decision: combine the strongest signals, ignore fake precision, and look for terms where the next action is clear.
The goal is not to know the exact number of searches. The goal is to avoid wasting metadata on dead, broad, or unreachable terms while finding search language that can actually bring the right users to the page.
Start with intent, not volume
A keyword is only valuable if the person typing it wants the thing your app actually does. A high-popularity query with broad intent can waste your title, subtitle, keyword field, and Apple Ads budget. A smaller query with sharp intent can become a reliable source of installs because your product page feels made for that search.
For a cycling weather app, “weather” is too broad. “cycling wind”, “bike weather”, “wind forecast cycling”, and “cycling route weather” are closer to real buyer language. The volume may be lower, but the user has already revealed context.
This is the first filter because no popularity source can save a bad intent match. If the keyword attracts people who will bounce after seeing your first screenshots, it is not a growth keyword. It is noise.
Use popularity as a demand index
Apple Search Ads popularity is useful when available, but it is not exact organic search volume. It is best treated as a demand index. Higher usually means more search demand; lower usually means less. The problem starts when teams use it like a precise traffic forecast.
The practical move is to bucket demand: low, medium, high. Then combine that bucket with relevance, difficulty, and your current ability to rank. A medium-demand keyword where you can reach the top 5 is usually more useful than a high-demand keyword where the top results are impossible to beat.
This became even more important after the Apple Ads popularity disruption in 2025, when many teams saw old popularity reads become less stable. The lesson is not to throw away Apple Ads data. The lesson is to stop treating one Apple Ads-derived number as the whole truth.
Use autocomplete for language, not certainty
App Store autocomplete is useful because it exposes phrasing. It can reveal that users search for “photo cleaner”, “duplicate photo remover”, “storage cleaner”, and “clean up photos” even when the product team only says “media management”.
But autocomplete does not tell you exact organic search volume either. Use it to expand the candidate list, then validate candidates against live search results, competitor strength, and your own product fit.
Read the live search result
The live App Store result tells you what Apple currently believes the query means. Look at the top 10 apps. Are they the same category as yours? Do their titles directly match the phrase? Are the leaders massive brands with hundreds of thousands of ratings? Are there small apps ranking because their metadata is unusually focused?
This is where RankPal’s keyword screen should matter more than a single score. Popularity tells you there may be demand. The top results tell you whether the demand is reachable.
A live result page can also show wrong-intent traps. If you search a phrase and the top apps solve a different job than your app, that phrase may not belong in your metadata even if a tool says it has demand.
Use competitors as evidence, not a shortcut
Competitor keywords are not the private keyword fields competitors typed into App Store Connect. Those fields are not public. The strongest public signal is which keywords a competitor ranks for in live search results, by country and over time.
If three smaller competitors rank for a phrase and their screenshots are weak, their ratings are stale, or their titles only partially match the query, that is a real opening. If the top 10 is filled with category leaders with strong ratings, high conversion assets, and exact metadata, the keyword may still be worth tracking but not worth leading with.
Use paid search terms carefully
Apple Search Ads can reveal search terms that people used before tapping an ad. That is valuable because it comes from real search behavior. Still, paid search term data has its own bias: bids, match type, budget, campaign structure, and ad placement all shape what you see.
A paid term deserves organic metadata only when it also passes the ASO filters: strong relevance, reachable live results, good product-page fit, and enough evidence that the users convert after the tap.
Validate with your own App Store Connect data
Apple does not give organic installs per keyword. But App Store Connect still gives the truth layer for your own app: impressions, product page views, downloads, conversion, territory, and source type. If you update metadata and your search impressions rise but product page conversion falls, you may have reached more people with weaker intent.
If search impressions rise and conversion holds or improves, the new keyword set is probably pulling in better demand. That is the kind of loop worth repeating.
This is why keyword research should be connected to analytics. A keyword score helps choose the experiment. App Store Connect tells you whether the listing actually performed better after the experiment.
A clean keyword decision rule
Choose a keyword when four things line up: the query describes the job your app does, demand is not zero, the current top results have reachable weaknesses, and you can support the keyword in your product page with title, subtitle, screenshots, or reviews.
Skip a keyword when the only good thing about it is a big popularity number. App Store growth is won by matching intent better than the apps around you.
What to write down before changing metadata
Before editing App Store Connect, write one plain sentence: “We are targeting this keyword because...” The answer should mention the user intent, demand signal, result-page weakness, and product-page proof. If the reason is only “the score is high”, the decision is not ready.
Also write what you expect to change. Do you expect rank to improve? Search impressions to rise? Product page conversion to hold? A specific country to move first? This makes the next review much cleaner because you are comparing results against a real hypothesis, not vibes.