ASOGrade Guide

Single Keywords vs. Keyword Phrases: Which Strategy Wins

When to target one-word, high-competition terms versus multi-word phrases in App Store metadata, and how the keyword field's word-indexing rules change the calculation.

The keyword field indexes words, not phrases

The App Store keyword field is a set of comma-separated words, each indexed independently rather than as a fixed phrase. Entering 'budget,tracker,weekly' covers searches for 'budget tracker', 'weekly budget', 'weekly tracker', and any other combination of those three words, without needing to spell out every phrase variant explicitly.

This changes how to think about single words versus phrases: you're rarely choosing between one or the other in the keyword field itself, since individual words there recombine automatically. The real choice is which individual words earn a spot in your limited 100 characters, and separately, whether your subtitle (which is read as a literal phrase, not word-indexed) should target a broad single word or a specific multi-word phrase.

Single, broad words: high popularity, high difficulty, real but distant upside

A single broad word like 'fitness' or 'budget' typically carries high popularity and high difficulty simultaneously — lots of search demand, and a ranking set dominated by the most established apps in the category. For a new or mid-stage app, targeting one of these as a primary ranking goal is usually not realistic in the near term.

That doesn't mean broad terms have no place. Including the core category word somewhere in your metadata matters for basic relevance signaling and for the (smaller, but real) share of installs that come from any ranking at all on a very high-volume term, even outside the top few positions.

Multi-word phrases: where accessible ranking usually lives

A specific phrase like 'weekly budget planner' or 'ADHD habit tracker' has lower absolute search volume than the broad single-word version, but the ranking set competing for that specific intent is typically far less entrenched, since fewer apps have built metadata precisely targeting the narrower phrase.

This is where most of the accessible, near-term ranking opportunity lives for apps below the top tier of established players. A portfolio of well-chosen specific phrases, each capturing a smaller but real slice of demand at a low difficulty, often out-produces a single broad term you can't realistically rank for.

The subtitle is the field where phrase construction matters most directly, since it's read as connected text rather than word-indexed like the keyword field. A subtitle written as a coherent phrase covering two or three specific terms ('Weekly Budget & Bill Planner') does double duty as both a phrase-level ranking signal and legible, convert-worthy copy.

Frequently asked questions

Should I enter multi-word phrases in the keyword field with commas, or as one entry?
Enter the individual words, comma-separated, without spaces inside a phrase. 'Budget planner' should be entered as 'budget,planner' — this indexes both words independently and covers more combinations than trying to preserve the phrase as a single unit.
Is a specific long-tail phrase ever worth more than a broad single word?
In terms of realistic installs generated, often yes for apps that can't rank top-5 for the broad term. A portfolio of accessible specific phrases with real popularity typically produces more actual installs than a broad term you rank 40th for.
Does the subtitle behave the same word-indexing way as the keyword field?
No. The subtitle is indexed as the literal text you write, which is why it needs to read as a coherent phrase rather than a comma-separated word list the way the keyword field does.

Related resources

More guides

Apply this in your own keyword research

Score App Store keywords by popularity and difficulty across 109 storefronts — the tool behind every strategy in this guide.

Start keyword research