Apple Search Optimization

App Store search runs on a much smaller set of signals than web search, and on a metadata budget of roughly 160 characters. That makes it learnable in an afternoon — and makes every wasted character expensive.

What the term means

Apple Search Optimization is App Store Optimization applied specifically to the iOS App Store: the work of getting your app to appear when someone searches the store for what it does. Most people use it interchangeably with ASO. The reason the Apple-specific phrasing exists at all is that the two big stores work differently enough that advice for one is actively wrong for the other.

It matters more than most developers expect. Store search is where a large share of app discovery begins, and unlike advertising it does not stop working when you stop paying. It is also the part of shipping an app that engineers are least prepared for, because none of the skills transfer from building the thing.

The one difference to internalise: Google Play indexes your long description, so keyword-rich copy helps there. Apple does not. On iOS your searchable surface is the app name, the subtitle, a hidden 100-character keyword field, your developer name, your in-app purchase names and your category. That is the whole of it.

What Apple actually indexes

FieldBudgetHow to use it
App name30 charactersThe heaviest weighted field. Brand plus your single strongest phrase. Most apps waste it on brand alone.
Subtitle30 charactersWeighted close behind the name, and visible to users, so it has to read as a sentence rather than a keyword list.
Keyword field100 charactersNever shown to users. Single words, comma separated, no spaces after commas, nothing repeated from the name or subtitle.
In-app purchase namesPer itemIndexed, and routinely forgotten. Name them descriptively rather than “Pro Plan”.
Developer nameAccount levelIndexed. Occasionally worth a keyword if you are setting up a new account.
Description4,000 charactersNot indexed. Write it for conversion, not for search.

Two mechanical rules follow from this and are worth committing to memory. First, Apple combines words across all indexed fields to build phrases, so you do not need to write phrases yourself — if “quit”, “vaping” and “tracker” each appear once anywhere in your metadata, you are eligible for the combinations. Second, and following directly from that, repetition is pure waste. Every duplicated word is a word you did not cover.

Also skip articles and connectors, do not include your own category name if it is already implied, and do not use competitor brand names — that is a rejection risk with no upside.

How ranking actually works

Apple does not publish its algorithm, and anyone claiming a precise formula is selling something. But the observable behaviour across thousands of result pages is consistent enough to work from, and it splits into two stages.

Stage one: are you eligible?

Relevance decides whether you appear for a phrase at all. This is almost entirely a metadata question — do your indexed fields contain the words, and does your app genuinely relate to them. This stage is fully within your control, and it is what keyword research is for.

Stage two: where do you land?

Among the apps that are eligible, position is heavily influenced by popularity signals you cannot edit: installs, ratings volume, rating quality, engagement and retention. This is why the same metadata produces wildly different outcomes for a new app and an established one.

The practical consequence is the thing most guides skip. Perfect metadata makes you eligiblefor a phrase; it does not make you visible for one. On a page where the top ten all have tens of thousands of ratings, being eligible puts you at position 60. This is why whether a new app can rank is a different question from how difficult a keyword is, and why choosing launch keywords is a fundamentally different exercise from choosing keywords for an app that already has users.

Spending your metadata budget

You have roughly 160 characters, or about 20 to 25 distinct indexed words per localization. Treat it like a budget and allocate deliberately:

  • The name carries your single best phrase. The one term you most want to own, that you have a real chance at. “Brand — Quit Vaping Tracker” beats “Brand” for every app that is not already famous.
  • The subtitle carries the next cluster, written as something a human would read. It is on your product page and it affects whether people tap, so it cannot be a keyword dump.
  • The keyword field carries everything else as single words. Synonyms, the words people use that you would not, misspellings that are genuinely common, and the modifiers that form long tails with words already in your title.
  • Localizations multiply the budget. Each localization has its own fields. Adding a localization for a market you already sell in gives you a fresh 160 characters for that storefront — one of the highest-leverage moves available, and widely ignored.

Myths worth dropping

  • “Put keywords in the description.” Not indexed on iOS. This advice is imported from Google Play or the web and it wastes your best conversion asset.
  • “Target high-volume keywords.” Volume you cannot rank for is worth precisely nothing. A phrase with modest demand you reach position 4 for beats a huge one where you sit at 80.
  • “Low competition means opportunity.” Sometimes it means nobody searches it. The useful version of this signal is narrower: people search it, and the apps ranking are answering a different question. That gap is an opening; emptiness usually is not.
  • “Use plurals and variations to be safe.” Apple handles most pluralization on its own. Spending characters on both “tracker” and “trackers” usually buys nothing.
  • “Set it once at launch.” Result pages move, competitors change their metadata, and the terms you can win widen as you accumulate ratings. Metadata is something you revise every few releases, against evidence.

What to actually do at launch

  1. Build a candidate list from Apple’s own autocomplete rather than your imagination — it is the closest thing to free demand data the store publishes.
  2. For each candidate, look at who ranks and how strong they are, and specifically at how many of the top ten are small enough that a newcomer could displace them.
  3. Choose launch terms you can win now, not the ones you want. Write the head terms down as a destination for later rather than spending metadata on them today.
  4. Allocate the name, subtitle and keyword field with nothing repeated, then localize for every market you sell in.
  5. Capture your positions on a schedule from day one, so that when you revise the metadata you can tell whether anything actually changed.

The keyword research guide covers steps one and two in detail, including a method you can run by hand. If you would rather it were done for you, that is what GetRevuu is.

Common questions

Is Apple Search Optimization the same as App Store Optimization?

In practice, yes — people use "Apple Search Optimization" to mean App Store Optimization applied to the iOS App Store specifically, as opposed to Google Play, where the rules are meaningfully different. Both refer to getting your app found in store search. ASO is the more common term in the industry; Apple Search Optimization is what people tend to type when they are searching for how iOS in particular works.

Does Apple index my app description for search?

No. On the iOS App Store the description is not part of the search index, which catches out anyone arriving from Google Play or from web SEO habits. Your description still does real work — it converts the people who reach your page — but keywords stuffed into it will not help you rank.

How many characters do I get for App Store keywords?

A 30-character app name, a 30-character subtitle, and a 100-character keyword field that users never see. That is your entire search budget per localization. Apple also indexes your developer name, your in-app purchase display names, and your category.

Should I repeat keywords across the title, subtitle and keyword field?

No. Apple combines words across all indexed fields to form phrases, so a word only needs to appear once. Repeating it wastes characters you could have spent on a word you have not covered yet — one of the most common and most expensive metadata mistakes.

Do ratings and downloads affect App Store search rankings?

Indirectly but substantially. Apple does not publish its ranking formula, but the pattern across result pages is consistent: relevance decides whether you are eligible for a phrase at all, and popularity signals largely decide where you land among the apps that are. This is why a brand-new app with perfect metadata still cannot enter a page held by apps with tens of thousands of ratings, and why launch keyword choice has to account for it.

Stop guessing which keywords you can win.

GetRevuu scores every phrase against the live App Store and tells you whether a new app can realistically rank for it.

Start free