Guide

The Complete Guide to App Store Optimization (ASO)

Everything a mobile publisher needs to know about ranking higher and converting better on the App Store and Google Play — the levers, the trade-offs, and what actually works.

On this page
  1. What ASO actually optimizes
  2. The three lever categories
  3. How to prioritize an ASO programme
  4. iOS vs Google Play: the practical differences
  5. Measuring ASO
  6. Common mistakes
  7. Where to go next

App Store Optimization is the mobile equivalent of SEO: the systematic process of ranking higher on the App Store and Google Play, and converting more of the resulting traffic into installs. For most successful consumer apps, organic installs from ASO are the single largest and highest-quality acquisition channel — and unlike paid UA, the work compounds.

This guide covers every major lever a mobile publisher should understand, organized around the three stages of the funnel ASO touches: visibility (whether users see your listing), conversion (whether they install), and durability (whether the installs stick and drive the feedback loop that the store algorithms reward).

What ASO actually optimizes

The App Store and Google Play rank apps using algorithms that are similar in shape but differ in implementation. Both weight a composite of three broad signal categories:

  1. Relevance signals — how well your app's metadata matches a user's query or the context Apple/Google use to generate chart rankings. This is what keyword targeting, title, subtitle, and description copy drive.
  2. Behavioural signals — download velocity, conversion rate from impression to install, review velocity and rating, retention, and (for Google Play) crash rate. These are the metrics the algorithm uses to decide whether your app deserves the ranking its metadata suggests.
  3. Engagement signals — post-install retention and active-use patterns. Both stores increasingly factor these in via first-party OS data (iOS) and Firebase/Play Console telemetry (Android).

You don't control the algorithms, but you fully control the inputs. Everything in ASO is either surface-level (metadata and creatives you submit) or velocity-level (behaviour you drive through product quality, marketing, and operations).

The three lever categories

1. Metadata optimization

Metadata is the indexed text Apple and Google use to match your app to searches. Each field has a specific length cap, a specific weighting, and a specific review cadence.

On iOS, the fields that matter for keyword ranking are:

  • App Title (30 characters). Highest keyword weight. Typically structured as Brand: Primary Keyword or Brand — Primary Descriptor.
  • Subtitle (30 characters). Second-highest weight. Used for secondary keywords phrased as benefits.
  • Keywords Field (100 characters, comma-separated). Hidden from users but indexed. Pack with singulars, synonyms, and long-tail terms.
  • Promotional Text (170 characters). NOT indexed — purely conversion copy. Editable without app review.
  • Description (4,000 characters). Weakly indexed. Primarily a conversion surface.

On Google Play, the keyword surface differs:

  • App Title (30 characters). Highest weight, similar structure to iOS.
  • Short Description (80 characters). High weight, visible and indexed.
  • Full Description (4,000 characters). Indexed with keyword-density weighting. Aim for 1.5-3% density on your primary terms without stuffing.

There is no keywords field on Google Play. Keywords you want to rank for must appear in the title, short description, or long description naturally.

2. Creative optimization

Creatives drive the impression-to-install conversion rate — the single biggest lever for organic install volume once you have baseline visibility.

  • App icon. The first thing a user sees in search results or on the chart. A/B test shapes, colour palettes, and whether to feature a character, a letter mark, or a functional glyph.
  • Screenshots. Apple allows up to 10; Google Play 2-8. The first two carry 60-80% of conversion weight. Use them to pitch your app's hero benefit — captioned screenshots with short marketing copy consistently outperform raw UI.
  • Preview video (iOS 15-30s, Google Play 30-120s). Optional but high-leverage for games and visual products.
  • Custom Product Pages (iOS) and Custom Store Listings (Google Play). Variant pages you can link from paid ad campaigns or pre-registration funnels to match creative context to landing page.

Most apps under-invest in creative iteration. A 2x IPM lift on a winning screenshot variant can double paid UA efficiency at the same CPI — and boost organic conversion on every impression at the same time.

3. Off-page and behavioural signals

  • Star rating and review volume, weighted heavily toward recent reviews.
  • Download velocity — the rate of change in daily installs. This is what moves apps up the Free chart.
  • Uninstall rate (Google Play). Tracked in Play Console; high rates can penalize ranking.
  • Crash rate (Google Play). Same.
  • In-App Events (iOS). Limited-time events (up to 5 concurrent) that surface on your product page and in search. Use them for seasonal hooks, feature launches, and tournaments.

How to prioritize an ASO programme

For a new or under-invested app, the order of operations is roughly:

  1. Baseline your current state. Know your current keyword ranks (for all target keywords, per country), category rank, impression volume, and install conversion rate. Without baselines you can't measure change.
  2. Fix the most broken metadata first. If your title has no keyword, or your subtitle is repeating brand copy, those are disproportionately high-leverage fixes.
  3. Target a small keyword basket. 10-20 keywords you actively rank and track. Dropping to top-10 on one of these moves more needle than being ranked 50-200 on dozens.
  4. Ship an icon + first-two-screenshots test. These surfaces drive 60-80% of conversion weight — you'll know within weeks whether your visuals are underperforming.
  5. Iterate on the long tail. Once metadata and primary creatives are dialed, your ongoing work is iterating on secondary screenshots, event hooks, localizations, and the keyword basket.

At MWM we observe that most apps in the bottom two quartiles of their category have never shipped a single icon A/B test. The delta between the median and top-quartile app on creative iteration cadence is larger than the delta on budget.

iOS vs Google Play: the practical differences

DimensioniOSGoogle Play
Keywords fieldYes (100 char, hidden)No
Description keyword weightWeakStrong
Title character cap3030
A/B testing infrastructureProduct Page Optimization (native)Store Listing Experiments (native)
Creative variantsUp to 35 Custom Product PagesMultiple Custom Store Listings
Primary off-page signalDownload velocity + reviewsVelocity + reviews + retention + uninstall
In-store eventsIn-App Events (up to 5)Promotional content card

Plan separate ASO workflows per store. Title structure, keyword selection, and screenshot test cadence usually converge, but Google Play's long-description keyword strategy and iOS's keyword field usage are distinctly different problems.

Measuring ASO

The canonical ASO dashboard tracks, per country and per store:

  • Keyword rank (per target keyword) and movement day-over-day.
  • Category rank and Overall rank.
  • Impressions (Apple Analytics → Product Page Impressions; Google Play Console → Acquisition reports).
  • Conversion rate from impression to install.
  • Review velocity (new reviews per week) and rating trend.
  • Search vs. browse split — what fraction of your installs come from search, from chart, from referrer ads, and from editorial featuring.

MWM Scale tracks keyword rank, category rank, and competitive benchmarks across 150+ countries, with free tiers for publishers tracking their own app.

Common mistakes

The patterns we see repeatedly on under-performing apps:

  1. Keyword stuffing in titles. Apple and Google both reject spammy titles, and stuffed titles tank conversion. Pick one primary keyword and one brand.
  2. No localization. Every significant international market (DE, FR, ES, BR, JP, KR) should have locally-translated metadata, not auto-translated. Localized listings can double conversion in non-English markets.
  3. Static creatives for years. If you haven't updated your screenshots in 12 months, you're leaving 20-40% organic conversion on the table.
  4. Treating ASO as a one-time launch activity. It's an always-on programme. Keyword landscapes shift, competitors iterate, and you need to compound small wins.
  5. Optimizing for rank without measuring install quality. Winning a keyword that delivers low-retention users is worse than losing it. Always evaluate cohort quality alongside rank.

Where to go next

ASO compounds. Every creative iteration, every localization, every keyword you claim is a small permanent uplift on a stream that generates installs for as long as your app is live. Publishers who treat ASO as an ongoing programme — not a one-time listing optimization — tend to dominate their categories three to five years in.

Key terms

Concepts used in this guide.

FAQ

Frequently asked questions.

How long does it take for ASO changes to take effect?
For iOS metadata changes (title, subtitle, keywords field), expect initial rank shifts within 24-72 hours and full re-ranking within 7-14 days. For Google Play, changes are indexed within a few hours but rank movement typically takes 3-10 days. Creative changes (screenshots, icon) take effect on conversion immediately, though rank movement driven by improved install-rate compounds over days to weeks.
What's more important — keywords or creatives?
Both, at different stages of the funnel. Keywords determine whether users see your app at all (impression). Creatives determine whether they install it (conversion). If you're not ranking for relevant searches, fix metadata first. If you rank but aren't converting, your creatives need work. Most mature ASO programs run continuous work on both tracks.
Can ASO replace paid user acquisition?
Rarely, at scale. Organic installs from ASO are the highest-LTV users you can acquire (zero CPI, high intent), but total organic volume is bounded by category search demand plus chart placement. Most successful apps blend paid UA (to drive early download velocity and chart movement) with ASO (to compound the resulting organic visibility).
How often should I run A/B tests on creatives?
Continuously. Google Play's Store Listing Experiments and Apple's Product Page Optimization let you run concurrent tests. Best practice is to always have one screenshot or icon test live, cycling through hypotheses quarterly. Top-quartile apps ship 8-12 significant creative iterations per year.
Does ASO work the same on iOS and Google Play?
The principles are shared — ranking on relevance plus behavioural signals, conversion on creatives — but the implementation details are very different. iOS has a dedicated keywords field and is more metadata-deterministic; Google Play has no keywords field and derives keywords from full-text indexing of the description. A/B testing infrastructure differs substantially too. Plan separate ASO workflows for each store.

Keep reading

Related playbooks.