How to Find App Store Keywords That Actually Drive Downloads

Most indie builders write down a handful of terms they think describe their app, paste them into App Store Connect's keyword field, and move on. The list looks reasonable. It is almost always wrong - not because the words are irrelevant, but because relevance alone is not enough. A keyword you and your app are perfectly matched for is useless if nobody searches it, and a keyword with enormous search volume is useless if every result is a major publisher with ten thousand reviews. The missing step is working all three signals together: volume, competition, and relevance, in that order of importance.

This is not a research sprint you do once before you launch. The App Store's index updates as competitor apps enter and exit, as seasonal patterns shift, and as your own app earns reviews and authority. The builders who stay ranked treat keyword research as a monthly check, not a one-time task.

Open the App Store on your phone or in a simulator, tap the Search tab, and start typing the root word for your app's core action. Do not hit enter - just watch the autocomplete suggestions appear. Write down every one of them. Then delete a letter, type a different root, and repeat. You are not speculating here: every autocomplete suggestion is a real query that real users have typed enough times for Apple's index to surface it. No tool gives you more direct signal about what your users actually type.

The autocomplete list usually reveals two or three phrases you had not considered - often longer, more specific queries (people typing 'habit tracker for students' instead of just 'habit tracker') where the competition is far thinner. Those long-tail terms are where new apps with no review history can actually rank on day one.

For each high-interest keyword on your list, search it in the App Store and open the top three results. Read their titles, subtitles, and the first three lines of their descriptions carefully. The title and subtitle are where Apple weights keyword relevance most heavily, so the words those top-ranked apps choose to put there are a direct signal about which terms the index is rewarding. This is not copying - it is reading the scoreboard.

Once you have a list of thirty or so candidate keywords from autocomplete and competitor research, score each one so you can prioritize. You do not need a paid tool for this pass - a simple three-column spreadsheet works fine. The three columns are: estimated volume (high, medium, low, based on how broadly the autocomplete surfaced it and how many competing apps target it), competition level (high, medium, low, based on the top results' review counts), and relevance (does a user who types this actually want what your app does?). Only terms with medium-to-high volume, medium-or-lower competition, and direct relevance make the shortlist.

The goal is not the longest keyword list - App Store Connect gives you 100 characters for the keyword field, and you have to fit them all in. The goal is the most precisely targeted shortlist you can build in that space.

The mechanical part of this process - pulling autocomplete suggestions, reading competitor metadata, building the scoring spreadsheet - is exactly the kind of repetitive structured research Claude Code is fast at. From the desktop app, you can describe your app in a paragraph, give it your target category, and ask it to draft an initial keyword list with volume and competition notes. It cannot query Apple's private ranking data, but it can reason about relative search intent, generate root term variations, and draft a scored table you then verify by hand against the live App Store.

The verification step is not skippable. Claude Code's volume estimates are inferences, not measured data. Every keyword that makes your final 100-character field should be one you have seen in live autocomplete yourself, or that appears in the metadata of an app you know is actually ranking. Treat the Claude Code pass as a draft you check, not a finished answer.

App Store Connect gives you three places to put keywords: the title (30 characters), the subtitle (30 characters), and the keyword field (100 characters). Apple's index reads all three, but it weights them differently: title first, subtitle second, keyword field third. The terms you are most confident about - your primary category term and the term with the highest intent match for your core user - belong in the title. The second tier goes in the subtitle. Everything else, including related long-tail variants and plurals, goes in the 100-character field.

Keywords are part of a metadata update, which triggers an App Review. That means you should not be swapping keywords daily. The right cadence for most indie apps is once per major version update - which you are already submitting for review anyway, so the keyword refresh adds no extra wait time. Review your keyword field every time you bump the version number, run the autocomplete pass again for any terms you are not sure about, and look at whether any of the top-ranked competitors for your key terms have changed. New competitors entering a category you are ranking in is the main signal to act on between updates.