The short answer
To do ASO, define who the app is for, record its current performance by storefront, research the words those people use, map a focused keyword set to the app name, subtitle, and keyword field, improve screenshots and trust signals, publish one coherent change, then measure visibility, conversion, and user quality before iterating.
App Store Optimization is not a one-time metadata rewrite. It is a learning loop across two connected jobs:
- Discovery: helping the App Store understand which searches are relevant to the app.
- Conversion: helping the right person understand and choose the app when it appears.
According to Apple’s App Store search overview, search considers text relevance across the app name, subtitle, keywords, and primary category, along with user behavior such as downloads, ratings, and reviews. Apple does not publish a formula or guarantee a rank. That makes ASO an evidence-led product and marketing process, not a keyword trick.
1. Record a baseline
Choose one app, storefront, and comparable date range. Save the current app name, subtitle, private keyword field, icon, first screenshots, rating, release version, and any Apple Ads activity. Then record:
- important keyword positions
- impressions
- product-page views
- first-time downloads
- conversion rate
- activation, revenue, and retention where available
A global total can hide a strong result in one country and a weak result in another. Keep the baseline market-specific so the next change has a fair comparison.
2. Define one user, problem, and promise
Write a plain-language positioning sentence before opening a keyword tool:
This app helps [specific user] achieve [specific outcome] when [situation], without [main frustration or alternative].
For example: “This app helps university students begin a focused study session without configuring a complicated productivity system.” That sentence suggests both search intent and screenshot content. “Productivity for everyone” does neither.
The position is a filter. If a keyword attracts a person the app does not serve, popularity will not make it useful.
3. Build a focused keyword set
Collect language from user interviews, support messages, reviews, competitor listings, App Store suggestions, Apple Ads search terms, and keyword tools. Group candidates by intent:
- Category: what the app is, such as “study timer”
- Problem: what the user wants to fix, such as “stop procrastinating”
- Outcome: what the user wants, such as “focus while studying”
- Feature: a capability they seek, such as “focus widgets”
Do not aim for the longest spreadsheet. A small, coherent cluster is easier to express in metadata and easier to evaluate after release. The keyword research playbook covers the field-by-field process in more depth.
4. Qualify each keyword
Score every candidate on three questions:
- Relevance: does the app genuinely satisfy the search intent?
- Opportunity: is there enough demand to matter?
- Feasibility: can this app credibly compete with the results already ranking?
Relevance comes first. A broad, popular term can create impressions without qualified downloads. A smaller term that precisely matches the product can lead to better conversion, activation, and revenue.
Inspect the actual apps ranking for each query. Compare their promise, screenshots, rating, pricing, and audience. A keyword difficulty score is useful context, but it cannot tell you whether your product is the right answer.
5. Map keywords to the right metadata fields
Give every field a distinct job:
- App name: brand plus the clearest category or purpose when space allows.
- Subtitle: add an audience, outcome, or differentiator instead of repeating the name.
- Private keyword field: cover relevant terms not already used in the visible metadata.
- Primary category: choose the most accurate category, not simply the one that looks easier.
Apple currently limits the app name and subtitle to 30 characters each. The private keyword field accepts up to 100 bytes. Apple recommends comma-separated terms without spaces after commas, avoiding duplicates, irrelevant terms, competing app names, and protected trademarks.
Read the visible name and subtitle as copy, not as a database row. A person scanning search results still needs to understand the app. Promotional text can support conversion, but Apple says it does not affect search ranking.
6. Make the product page earn the download
Keyword visibility only creates an opportunity. The icon, screenshots, app preview, rating, reviews, price, and product promise decide whether the right person continues.
Give the first three screenshots separate jobs:
- Recognition: show the problem or outcome the user searched for.
- Mechanism: demonstrate how the app creates that outcome.
- Reason to believe: show useful proof, depth, or a credible differentiator.
Use specific captions that describe an action or benefit. “Start a 25-minute study session” is stronger than “Boost your productivity.” Review the full App Store screenshot guide, then inspect recurring themes in ratings and reviews. Those themes often reveal objections the listing should answer or product problems the listing cannot fix.
7. Localize the strategy by market
Do not translate one English keyword list into every language and call it localization. Search language, competitors, category expectations, screenshots, and trust concerns can change by country.
Start with the markets that already show demand or fit the product. Repeat the positioning and keyword research in the local language, adapt the visible promise, and measure that storefront separately. The storefront-by-storefront localization guide explains how App Store Connect localizations and storefront coverage interact.
8. Publish one coherent hypothesis
Before changing anything, write:
I believe [specific issue] limits [visibility or conversion] for [audience and storefront] because [evidence]. We will change [coherent set of elements] and judge it using [metric and decision rule].
“One change” means one idea, not necessarily one field. A new position may require the app name, subtitle, and first screenshot to work together. Avoid unrelated changes that make the result impossible to interpret.
9. Measure the whole funnel
After release, compare the same storefront and source against the baseline. Do not stop at rank:
| If this is weak | Investigate next |
|---|---|
| Relevant impressions | Keyword relevance, metadata coverage, and competitive feasibility |
| Product-page views | Whether the visible search result matches the query |
| Downloads or conversion | Screenshots, reviews, price, and clarity of the promise |
| Activation or retention | Traffic quality, onboarding, and whether the product delivers the promise |
| Revenue | Audience fit, value communication, and monetization timing |
Use App Analytics in App Store Connect to monitor impressions, downloads, conversion, and sources. Remember that Apple Ads activity can also appear in App Store search data, so record when paid campaigns are running.
10. Keep, revise, or reject the idea
Give the change enough time and traffic to become informative. Low-volume apps may need several weeks. Seasonality, featuring, paid campaigns, product releases, and rating changes can all affect the comparison.
Then make an explicit decision:
- Keep the change when the target metric improves without damaging user quality.
- Revise it when the signal is promising but the message or audience is still unclear.
- Reject it when the evidence contradicts the hypothesis.
Add the result to the next baseline. ASO compounds when each release answers a question; it stalls when every release restarts the guesswork.
Where an ASO tool helps
You can do the strategic work manually, but a tool makes repeated keyword research and rank monitoring faster. Astro is one focused option for Apple developers: it tracks keyword performance across Apple platforms and provides keyword popularity data sourced from Apple Search Ads.
Use a tool to collect and compare evidence, not to outsource the decision. A popularity or difficulty score cannot know your product’s positioning, user quality, or which promise the app can honestly keep.
For a deeper system that connects ASO with Apple Ads, custom product pages, activation, and retention, continue with the complete iOS ASO guide.
Frequently asked questions
How do you do ASO?
Define the app’s audience and position, establish a storefront baseline, research relevant intent, map a focused keyword cluster to the name, subtitle, and keyword field, improve screenshots and trust signals, publish one coherent change, then measure visibility, conversion, and user quality before repeating.
How long does ASO take to work?
Metadata can appear after release, but a useful decision depends on enough impressions and downloads. A higher-volume app may see a directional signal quickly; a low-traffic app may need several weeks. Do not call a result from a few observations.
Which ASO metrics matter?
Track relevant keyword positions, impressions, product-page views, first-time downloads, conversion rate, activation, revenue, and retention by storefront and source. Rankings are diagnostic evidence, not the business outcome.