App Store Optimization (ASO): the complete guide for iOS developers

ASO is how people find your app in App Store search and decide to download it. This guide explains how Apple's search works, what you control, and a practical 30-day plan to improve it.

October 11, 202613 min readBy the Appsium team

You can build a great iOS app and still get almost no downloads, because nobody finds it. App Store Optimization (ASO) is the work of making your app easy to find in App Store search and convincing once someone lands on your product page. It costs nothing but time, and every improvement keeps working while you sleep.

This is the pillar guide. It covers how App Store search works, which fields Apple actually reads, what moves people to tap Get, and how to measure it all. Where a topic deserves a deep dive, you'll find a link to a dedicated guide.

What ASO is (and what it isn't)

ASO has two halves that feed each other:

  • Discovery. Showing up when people search for the problem your app solves. This is mostly about the words in your metadata and how relevant Apple thinks your app is for a query.
  • Conversion. Turning a search result or product page view into a download. This is about your icon, screenshots, preview video, ratings and the first lines of text people read.

They are linked. Apple says search results are based on text relevance and user behavior, such as downloads and ratings (Apple, App Store search). A listing that converts well sends better signals, which can help it rank, which brings more impressions to convert.

The ASO flywheel
Relevant metadata title, subtitle, keywords More impressions you appear in more searches Strong product page icon, screenshots, ratings More downloads and better user signals ASO discovery + conversion
Discovery and conversion reinforce each other. Improving only one half leaves results on the table.

ASO is not keyword stuffing, buying fake reviews or copying a competitor's name into your keywords. Those tactics break the App Review Guidelines (see 2.3.7 on metadata and the Section 3 introduction on manipulated reviews) and can get an update rejected or worse.

How App Store search works

Apple doesn't publish its ranking algorithm, but it does tell developers what goes into it. According to Apple's search guidance, results are based on:

  1. Text relevance: matches between the search query and your app name, subtitle, keyword field and primary category.
  2. User behavior: downloads, ratings and reviews, and other signals Apple doesn't list in detail.
From a search query to a download
User searches "rain sounds" 1. Match (text relevance) App name Subtitle Keyword field Category, developer name 2. Rank (relevance + behavior) #1 strong match, many downloads #2 strong match, fewer signals 3. Convert: icon, screenshots, rating, title → product page → Get Each download feeds back into the behavior signals in step 2
A simplified model based on Apple's published search guidance. The exact weights are not public.

A few practical consequences follow from this:

  • If a word isn't in an indexed field, you are unlikely to rank for it. Writing "white noise" in your description is not the same as having it in your subtitle or keyword field.
  • Relevance gets you into the race; behavior decides the order. A brand-new app can match a popular term perfectly and still sit far down the list behind apps with years of downloads and ratings.
  • Apple adds context on top. Search results can show tags generated from your metadata, In-App Event cards, promoted in-app purchases and, if you set them up, custom product pages assigned to specific keywords.
Target words you can realistically win For a new app, a mid-volume phrase that describes exactly what you do ("rain sounds for sleep") usually beats a huge generic term ("sleep"), where established apps hold the top results. Win the specific terms first, then broaden.

The metadata fields you control

Everything you write for the App Store lives in App Store Connect. Some fields feed search directly; others exist only to persuade. Here is how they compare, based on Apple's App information and platform version references.

FieldLimitUsed for search?Change without a new version?
App name30 charactersYesNo
Subtitle30 charactersYesNo
Keyword field100 bytesYes (hidden from users)No
Primary / secondary categorypicked from a listYesNo
Promotional text170 charactersNo, per AppleYes
Description4,000 charactersNot listed by AppleNo
What's New4,000 charactersNoWith each version
Screenshotsup to 10 per sizeNo (conversion)No
App previewsup to 3, 15–30 sNo (conversion)No

The three highlighted rows are where discovery happens, and together they give you only about 160 characters to describe your app to the search engine. That scarcity is why every word matters. Two dedicated guides go deeper:

Don't repeat yourself across fields Apple's guidance is to avoid repeating words that are already in your app name, subtitle or category inside the keyword field. Each indexed word only needs to appear once, so spread your vocabulary across the three fields.

Conversion: what makes people tap Get

Ranking puts you in front of people. Conversion decides whether they download. In search results, most of your listing is visual: the icon, the name and subtitle, the star rating and the first screenshots or preview video. Many people decide right there, without opening your product page.

Pages that convert

  • Lead with the main benefit in the first two or three screenshots
  • Use short, large captions that read at thumbnail size
  • Show the real app in use, as guideline 2.3.3 requires
  • Keep the icon simple and distinct from the top competitors
  • Use the subtitle to say what the app does, in plain words

Pages that leak downloads

  • A splash screen or login page as the first screenshot
  • Tiny captions or feature lists nobody can read in search
  • An icon that looks like the category leader's
  • A subtitle that is a slogan with no information
  • Few or no ratings, or old complaints left unanswered

Here's how two listings for the same kind of app can look side by side in search. Same category, very different first impression:

Same query, two first impressions
Noisy
The best app ever made
★★★★☆ 12
Get
Welcome Sign in Settings
Driftly: Rain & Sleep Sounds
White noise for deep sleep
★★★★★ 2.4K
Get
Fall asleep in minutes 40+ calming sounds Mix your own
Illustrative mockups. The right listing tells you what it does before you open it: keywords in the name and subtitle, social proof and benefit-led screenshots.

Ratings and reviews

Ratings do double duty. Apple says ratings and reviews can influence search ranking, and the star average and count sit right in the search result, where they shape the decision to download.

Three habits make the biggest difference:

  1. Ask at the right moment, with the system promptUse StoreKit's review request (AppStore.requestReview(in:), or requestReview in SwiftUI) after a moment of success, not at launch. The system shows the prompt at most three times per 365 days per user, so don't waste it on a first session.
  2. Reply to reviewsYou can respond to reviews in App Store Connect. A calm, helpful reply to a complaint is read by every future visitor who scrolls to it.
  3. Never buy or force ratingsApps must not force people to rate the app to unlock features (guideline 3.2.2), and manipulated or incentivized reviews can lead to removal from the Apple Developer Program.

When you ship a version that fixes a big problem, App Store Connect lets you reset the overview rating on release. Use it sparingly: it can't be undone, and Apple notes that having few ratings may discourage downloads. Written reviews stay visible either way.

Screenshots and app previews

You can upload up to 10 screenshots per device size and localization, and up to three app preview videos of 15 to 30 seconds each (Apple, app preview specifications). Only the first few are visible in search results, so treat them like a billboard, not a manual.

  • Screenshot 1 states the core promise ("Fall asleep in minutes").
  • Screenshots 2–3 prove it with the features people care about most.
  • The rest handle objections: privacy, offline use, widgets, pricing model, awards.

Required sizes change as Apple ships new devices, so check the current list before you design. Our screenshot size guide keeps them in one place, and the upcoming screenshot guide covers design in depth.

How does your listing score today?

Paste any App Store link and get a free ASO score with concrete fixes for the title, subtitle, screenshots and ratings.

Get your free ASO score

Localization: the most underused lever

Apple's localization page describes the App Store as available in 175 regions and 50 languages. Every language you add gives you a fresh name, subtitle and keyword field to work with, and a product page that speaks to people in their own words.

175App Store regions, per Apple
50languages for App Store metadata, per Apple
~160characters of indexed text per language (name + subtitle + keywords)

Localization is not translation. Search terms differ from country to country, and a literal translation of your English keywords often misses what people actually type. Research each market's terms, then write metadata for them. Remember the keyword field is measured in bytes, so languages with non-Latin scripts fit fewer characters into the same 100 bytes.

The App Store localization guide covers how to choose markets and adapt screenshots.

Measuring ASO

You can't improve what you don't measure. App Store Connect's App Analytics gives you the core numbers for free:

MetricWhat it tells youWhich half of ASO
Impressions (from App Store Search)How often your app was seen in search resultsDiscovery
Product page viewsHow many people opened your pageDiscovery
Conversion rateShare of visitors who downloadedConversion
Downloads by sourceSearch vs browse vs web referrer vs app referrerBoth
Ratings over timeWhether recent versions please usersBoth

Track your position for your most important search terms each week, and log every metadata change with its date. Without a change log, you'll never know which edit moved the numbers.

For visual assets you can run real experiments. Product Page Optimization lets you test up to three alternate versions of your icon, screenshots and preview videos against your original page, for up to 90 days. Text fields like the name and subtitle can't be A/B tested this way, so change them one at a time and compare periods.

Change one thing at a time If you change the name, subtitle, keywords and screenshots in the same release, you won't know which one helped or hurt. When you can, isolate text changes from visual changes.

A 30-day ASO plan

Here's a realistic month for a solo developer or small team. It assumes an app that's already live; if you haven't launched yet, use the ASO launch checklist instead.

30 days, four focused weeks
Week 1 Research Baseline analyticsCompetitorsKeyword list Week 2 Metadata Name + subtitleKeyword fieldSubmit version Week 3 Visuals + ratings Screenshot setPPO testReview prompt Week 4 Measure Rank + conversionPick a localePlan next loop
Each week has one goal. Repeat the loop every month or with every release.
  1. Days 1–3: Record a baselineExport impressions, product page views, conversion rate and downloads by source for the last 30 days. Write down where you rank today for 10–20 terms that describe your app.
  2. Days 4–7: Study competitors and build a keyword listSearch your main terms and note who ranks in the top results. Collect the words they use in names and subtitles. For each candidate keyword, weigh relevance to your app, search volume, and how strong the apps already ranking are.
  3. Days 8–12: Rewrite name, subtitle and keyword fieldPut your most valuable phrase in the name, your second tier in the subtitle and everything else in the keyword field, with no repeats. Submit a new version.
  4. Days 13–20: Fix the first three screenshotsRewrite captions around benefits, make them readable at thumbnail size, and start a Product Page Optimization test if you have enough traffic.
  5. Days 15–20: Tune your review promptMove the prompt to a moment of success and reply to the most recent critical reviews.
  6. Days 21–30: Measure and decideCompare rankings and conversion with your baseline. Keep what worked, revert what didn't, and pick one new localization or keyword cluster for next month.

ASO compounds. One good month won't transform an app, but twelve months of small, measured improvements usually will. Start with the fields that carry the most weight: your title and subtitle.

Frequently asked questions

How long does ASO take to show results?

Metadata changes only take effect once a new version is approved and live, and rankings then need time to settle. Plan to judge a change over a few weeks of App Analytics data rather than a few days.

Does the app description affect App Store search ranking?

Apple's search guidance lists the app name, subtitle, keywords and category as the text used for relevance, not the description. Write the description for people who are deciding whether to download.

Is ASO a one-time task?

No. Competitors, search trends and your own app change over time, so treat ASO as a loop: research, update metadata with each release, measure in App Analytics and repeat.

Can a tool guarantee a top ranking?

No. Apple decides rankings using relevance and user behavior that nobody outside Apple controls. Good tools help you choose better keywords and build a stronger product page, which improves your odds.

See how your App Store page scores — free.

Paste your App Store link and get an ASO Score with the fixes that matter most. Then let Appsium research keywords, write metadata in every language and design your screenshots.