App Store Optimization: The Complete Guide
App Store Optimization (ASO) is the practice of improving an app's visibility and conversion rate in the Apple App Store and Google Play so more people find it, tap it, and install it without paid ads, learn more in this comprehensive guide.
It works on two levers: ranking higher for the searches your users make, and turning more product-page views into downloads.
This guide covers both stores end to end: how their algorithms rank apps, how to research keywords, what to put in every metadata field, how to test creatives, and how to measure results. It also covers a newer question every app marketer now faces: how to get your app recommended by AI assistants like ChatGPT, Gemini, and Perplexity.
The short answer, if you only have a minute:
Put your most important keyword in the app name/title, and use every character of the fields each store indexes.
Treat your icon and first three screenshots as your ad: most visitors decide from them without scrolling.
Keep your rating above 4.0 and reply to reviews; ratings affect both ranking and conversion.
A/B test creatives with Apple's Product Page Optimization and Google Play's store listing experiments.
Localize for your top markets, not just translate.
Build off-store signals (press, reviews, a strong website) so search engines and AI assistants cite your app.
Measure impressions, conversion rate, and keyword rankings monthly, and iterate.
What to expect in this App Store Optimization guide
App Store Optimization is the process of improving an app's store listing so it ranks higher in store search and browse, and converts more visitors into installs. It is often called "SEO for apps," and the comparison holds: you research what people search for, match your listing to that intent, and earn trust signals that push you up the results.
ASO has two jobs:
Visibility: getting your app in front of people through search results, category charts, featured placements, and recommendations.
Conversion: persuading the people who see your app to install it, through your icon, screenshots, video, ratings, and copy.
Why ASO matters
Search is the main way people find apps. According to Apple, 70% of App Store visitors use search to discover apps, and almost 65% of downloads happen directly after a search. If you don't rank for the terms your users type, most of them will never see you.
ASO also compounds. Organic installs cost nothing per user, and a better conversion rate makes every paid campaign cheaper too, because paid traffic lands on the same product page. Better organic rankings bring more installs, which improve the ranking signals, which bring more installs.
ASO vs. SEO
ASO | SEO | |
Where it happens | App Store, Google Play | Google, Bing, AI search |
Goal | Installs | Visits, leads, sales |
Main text signals | Title, subtitle, keyword field, descriptions | Page title, headings, body copy |
Main trust signals | Ratings, reviews, downloads, retention | Backlinks, authority, engagement |
Conversion assets | Icon, screenshots, preview video | Page design, calls to action |
The two work together. Google indexes Play Store listings, and a strong website helps both web search and AI assistants understand and recommend your app (more on that below).
How the App Store and Google Play rank apps
Both stores rank apps on two kinds of signals: relevance (does your metadata match the search?) and quality and popularity (do people install, keep, and rate your app?). Neither store publishes its algorithm, so the factors below combine official guidance with what ASO practitioners consistently observe.
Ranking factor | Apple App Store | Google Play |
App name / title | Strongest text signal | Strongest text signal |
Subtitle / short description | Subtitle indexed, second strongest | Short description indexed |
Hidden keyword field | Yes, 100 characters | None |
Long description | Not confirmed as indexed | Indexed; natural keyword use matters |
Screenshot caption text | Observed as indexed since June 2025 | Not indexed for search |
Install volume and velocity | Yes | Yes |
Conversion rate from search | Yes | Yes |
Ratings and reviews | Yes | Yes |
Retention and engagement | Yes | Yes, strongly weighted |
Technical quality | Crashes hurt reviews and retention | Android vitals thresholds can cut visibility |
What's different about Apple
Apple indexes a small set of fields: the app name, subtitle, keyword field, and (per SplitMetrics and other ASO researchers) text in screenshot captions since around June 2025. Apple hasn't confirmed the screenshot change, so treat it as a bonus signal, not a replacement for the keyword field. The description is written for humans; Apple's own product page guidance warns against stuffing it with keywords.
What's different about Google Play
Google Play reads your listing more like a web page. The title, short description, and full description are all indexed, and Google's language understanding looks for natural, relevant use of terms rather than repetition. Google also leans heavily on quality: apps whose user-perceived crash rate exceeds 1.09% or ANR rate exceeds 0.47% may be excluded from recommendations, and apps that break the per-device threshold can get a warning on their listing (Android Developers Blog).
The ranking flywheel
Relevance gets you into the results. Conversion and retention decide how high you stay. An app that ranks for a keyword but converts poorly for it will slide down; one that converts well will climb. That's why the rest of this guide gives creatives, ratings, and testing as much weight as keywords.
How to do keyword research for ASO
Good ASO keywords are relevant to what your app does, searched often enough to matter, and winnable given your app's current strength. Pick relevance and intent first, volume second: ranking #3 for a specific term beats ranking #80 for a generic one.
Step-by-step process
List your product language. Write down how you'd describe the app to a friend: its core job, features, and the problems it solves.
Mine store autocomplete. Type seed terms into the App Store and Google Play search bars. Autocomplete suggestions reflect real, frequent searches.
Study competitors. Note the words competitors use in their names, subtitles, and short descriptions, and which terms they rank for in an ASO tool.
Read reviews. Users describe your app (and your competitors') in their own words. Those phrases are often long-tail keywords nobody is targeting.
Check popularity and difficulty. Apple Ads shows a search popularity score for iOS terms; ASO tools such as AppTweak, Sensor Tower, data.ai, AppFollow, and MobileAction estimate volume and difficulty for both stores.
Score and shortlist. Rate each term on relevance, volume, and difficulty. New apps should start with lower-competition long-tail terms and move to broader ones as they gain installs and ratings.
Map keywords to fields. Put the highest-value term in the title, the next tier in the subtitle or short description, and the rest in the keyword field (iOS) or description (Google Play).
Keyword types to cover
Head terms: short, high-volume, very competitive ("budget", "meditation").
Long-tail terms: more specific and easier to win ("budget planner for couples", "sleep meditation for kids").
Feature terms: what the app does ("receipt scanner", "offline maps").
Problem terms: what the user wants solved ("stop overspending", "fall asleep fast").
Brand terms: your own name, and common misspellings of it.
How Apple combines keywords
Apple combines words across the name, subtitle, and keyword field into phrases. If your name contains "Budget" and your keyword field contains "planner", you can rank for "budget planner" without typing the full phrase. So never repeat a word across fields, and use single words separated by commas rather than full phrases (AppLaunchFlow).
Metadata optimization: every field, both stores
Metadata is the text on your listing. On both stores the title carries the most ranking weight, so it should hold your brand plus your single most important keyword. Here is every text field, its limit, and whether it affects search.
Field | Store | Limit (characters) | Indexed for search? | Can change without an app update? |
App name | App Store | 30 | Yes, strongest | No |
Subtitle | App Store | 30 | Yes | No |
Keyword field (hidden) | App Store | 100 | Yes | No |
Promotional text | App Store | 170 | No | Yes |
Description | App Store | 4,000 | Not confirmed | No |
Title | Google Play | 30 | Yes, strongest | Yes |
Short description | Google Play | 80 | Yes | Yes |
Full description | Google Play | 4,000 | Yes | Yes |
App name / title (30 characters)
Use the format Brand: Main Keyword or Brand - Main Keyword, for example "Lumo: Budget Planner". Keep the brand short so the keyword fits. Google Play bans performance claims ("#1", "Best"), promotional words ("Free", "No Ads"), emojis, and all caps in titles; Apple rejects generic or misleading names.
Subtitle (iOS, 30 characters)
Use the subtitle for your next-best keywords, phrased as a benefit a human would want to read: "Track spending, save more" rather than "budget money finance tracker".
Keyword field (iOS, 100 characters)
Separate terms with commas and no spaces: planner,expense,savings,bills,receipt.
Don't repeat words already in your name or subtitle.
Skip plurals, the word "app", category names, and competitor trademarks.
Use every character. Short words beat long ones when they're equally relevant.
Short description (Google Play, 80 characters)
This is the first text people see on your Play listing, and it's indexed. Lead with your core benefit and a primary keyword: "Plan your budget, track expenses, and save money with smart monthly goals."
Description (4,000 characters)
On iOS, write for people. The first sentence shows before the "more" tap, so make it your value proposition. On Google Play, write for people and search: work your main keywords naturally into the opening lines and a few times in the body, with headings and short bullet lists. Google warns against repetitive keyword blocks.
A reliable structure for both:
One-line value proposition.
Three to five key features, each as a short bullet.
Social proof (awards, press, user counts), attributed.
Pricing or subscription details, stated plainly.
A closing call to action.
Promotional text (iOS, 170 characters)
Promotional text sits above the description and can be changed any time without a new release. Use it for seasonal offers, new features, and events.
Creative optimization: icon, screenshots, and video
Creatives decide conversion. Most visitors judge an app from the icon and the first few screenshots in search results, without opening the full page or reading a word of the description.
Asset | App Store | Google Play |
Icon | 1024 × 1024 px source; no text-heavy designs | 512 × 512 px, 32-bit PNG, up to 1 MB |
Screenshots | Up to 10; first 1–3 show in search when no preview video | 2–8 per device type; at least 4 at 1080 px+ recommended |
Video | Up to 3 app previews, up to 30 seconds, autoplay muted | 1 YouTube video; first 30 seconds autoplay |
Feature graphic | None | 1024 × 500 px, required for video and promo placements |
Sources: Apple, Google Play Console Help.
Icon
One simple, bold shape that reads at small sizes.
A color that stands out from the top competitors in your category (search your main keyword and look).
No words or tiny details; they become noise at thumbnail size.
Test variants. Icon changes can move conversion more than any other single asset.
Screenshots
Sell the outcome in screenshot one. Show your core value with a short, bold caption: "Save $200 a month" beats "Dashboard".
One benefit per screenshot. Order them by what matters most to users.
Make captions readable at thumbnail size. Aim for five words or fewer, large type, high contrast.
Put keywords in captions (iOS). Since mid-2025, ASO researchers have observed Apple indexing caption text, so natural keyword use can add a small ranking lift.
Show real UI. Both stores require screenshots that reflect the actual app experience.
Include social proof such as an award, rating, or press quote, if you have one.
Localize captions and, where it matters, the UI shown.
Preview video
Videos autoplay without sound, so the first three seconds must show the app doing something valuable, with captions instead of narration. On Google Play, Google asks that at least 80% of the video show the real user experience. Test video on vs. off: in some categories, a strong static screenshot converts better than an autoplaying video.
New in 2026: App Store visual search results
Apple is adding new creative assets, Product Page Headers and landscape Search Results Visuals, rolling out with iOS 27 from July 2026 (AppTweak). If your app is eligible, design these as carefully as your first screenshot; they're the first thing searchers will see.
Ratings and reviews
Ratings affect both ranking and conversion, and reviews now shape the AI summaries both stores show. Aim for a 4.5-star average and treat anything below 4.0 as urgent: it lowers conversion and signals low quality to the algorithms.
How to earn more (and better) ratings
Ask at the right moment. Prompt after a success, such as a completed workout, a saved goal, or a finished level, never on launch or after an error.
Use the native prompts. On iOS, SKStoreReviewController can show the system prompt up to 3 times in 365 days (Apple). On Android, use the Google Play In-App Review API, which lets users rate without leaving the app.
Don't gate reviews. Asking "Do you like the app?" and only sending happy users to the store breaks both stores' policies.
Fix what reviews complain about. Recurring complaints are your product roadmap and your fastest ranking win.
Respond to reviews
Both stores let you reply publicly. Apple recommends prioritizing low-star reviews and those about bugs in the current version, and replying to older reviews when an update fixes their issue. Keep replies short, specific, and human. Users can update their rating after a good reply.
Recency matters
Google Play's displayed rating is weighted toward recent ratings, so improvements show up quickly (Play Console Help). Apple lets you reset your summary rating with a new version, but written reviews stay visible, so use it only after a release that fixes the main complaints.
AI review summaries
Apple now shows LLM-generated review summaries on product pages in the US and several other English-language storefronts, and Google Play's Gemini-powered Ask Play feature answers user questions using your metadata and reviews. Both mean the themes in your reviews are now copy on your listing. The best way to influence them is to fix the problems people write about and encourage satisfied users to leave detailed reviews.
Conversion rate optimization and A/B testing
Both stores offer free, native A/B testing, and it's the only reliable way to know which icon, screenshots, or copy convert best. Opinions, even expert ones, are often wrong about creatives.
Apple Product Page Optimization | Google Play store listing experiments | |
What you can test | Icon, screenshots, app previews | Icon, feature graphic, screenshots, video; descriptions in localized tests |
Variants | Up to 3 treatments vs. original | Variants vs. current listing |
Tests at once | 1 | 1 default-graphics or up to 5 localized |
Max length | 90 days | Auto-completes after 6 months |
Confidence | Results reported at 90%+ confidence | Configurable confidence and minimum detectable effect |
Notes | New creatives need App Review; icon tests need icons in the binary | Target metric: install clicks, opens, or pre-registrations |
Sources: Apple Product Page Optimization, Play Console Help.
How to run a good ASO test
Start with a hypothesis. "A caption leading with savings will beat one leading with features" is testable; "try new screenshots" isn't.
Test one big change at a time. Icon first, then first screenshot, then screenshot order, then video.
Test big differences. Small tweaks rarely reach significance on moderate traffic.
Run for at least 7 days, covering full weekday and weekend cycles, even if a winner appears early.
Apply winners and keep a log of every test, result, and lesson so learning compounds.
Conversion rate benchmarks
Conversion rates vary widely by category, store, and traffic source, so benchmark against yourself. Track product page conversion rate (page views to installs) and, on iOS, impression-to-install rate from search, then aim to beat your own baseline with each test. Branded searches convert far higher than generic ones, so segment them before judging a creative.
Custom product pages, in-app events, and promotional content
These features let you show different audiences different listings and keep your app fresh in search, without shipping a new build. They're among the most underused tools in ASO.
Apple custom product pages
You can publish up to 70 extra versions of your App Store product page, each with its own screenshots, app previews, and promotional text (Apple). Since late 2025 you can also assign keywords to a custom product page so it appears in search for those terms instead of your default page.
Use them to:
Match a page to each major use case ("budget for students", "budget for couples").
Send each paid campaign to a page that mirrors its ad creative.
Rank a tailored page for keyword clusters your default page can't serve well.
Each keyword can map to only one page, so plan clusters before you build.
Apple in-app events
In-app events are timely experiences, such as challenges, premieres, live events, or major updates, that show on your product page, in search results, and in editorial selections. You can have up to 10 published at a time, each lasting up to 31 days and promoted up to 14 days early. Event names (30 characters) and descriptions (50 and 120 characters) are separate text that can surface in search, so write them with keywords in mind.
Google Play promotional content
Promotional content (formerly LiveOps) is Google's equivalent: offers, time-limited events, and major updates shown on your listing and sometimes on the Play home page and in search. Run a steady calendar of it; fresh, relevant content gives Google more reasons to surface your app.
Google Play custom store listings
Custom store listings let you tailor your Play listing by country, by traffic from a specific ad campaign, or for users who previously uninstalled. In August 2026 Google also added targeting by monetization behavior, such as non-buyers, one-time buyers, and lapsed buyers (AppTweak).
Localization: rank in every market you serve
Localizing your listing is one of the highest-return ASO tasks, because each language gets its own title, subtitle, keywords, and screenshots, and competition is often lower outside English.
Localize, don't just translate
Research keywords per market. Direct translations often miss how people actually search. Use local autocomplete and ASO tools for each country.
Adapt creatives. Translate captions, and where relevant show local currency, examples, and culturally familiar imagery.
Prioritize by opportunity. Start with markets where you already get organic installs, or where your category is growing and competitors haven't localized.
Localize the app, too. A localized listing that opens into an English-only app earns bad reviews.
Cross-localization on the App Store
Each App Store storefront indexes keywords from more than one localization. In the US, for example, Apple also indexes Spanish (Mexico), and several other locales, alongside English (US) (AppTweak). That gives you extra keyword fields for your US ranking.
Two rules apply:
Keywords aren't combined across localizations. "bus" in English (US) and "metro" in Spanish (Mexico) won't rank you for "metro bus", so keep phrases together in one locale.
Keep the secondary locale useful to real speakers of that language. Use its keyword field for extra terms, but don't fill a visible title or subtitle with English words that make the listing confusing.
Google Play localization
Google Play offers machine translation of your listing in Play Console, a quick way to start, but review it with a native speaker. Localized store listing experiments let you test descriptions and graphics in up to five languages at once.
ASO for AI search: GEO and off-store signals
App discovery no longer happens only inside the stores. People ask ChatGPT, Gemini, Perplexity, and Siri "what's the best app for...", and those assistants answer with a short list. Generative engine optimization (GEO) for apps is the work of making sure your app is on that list.
Why it matters now
In June 2026, Google's Gemini app gained the ability to recommend and install Android apps directly, with embedded Play Store cards (AppTweak).
Google Play's Ask Play chatbot answers questions on app listings using your metadata and reviews.
In an analysis of more than 125,000 ChatGPT app recommendations, app store pages made up about 47% of cited sources, and about 60% for games (AppTweak, May 2026). Your store listing is the single biggest input AI assistants read about your app.
What AI assistants look for
Assistants match apps to a task, not a keyword. They favor apps with a clear, consistent identity, evidence they do the task well, recent updates, and validation from trusted third parties.
[embed: node/b503bac5-74ff]
Each surface reinforces the others: assistants trust an app more when its store listing, website, and outside mentions all describe the same job.
How to optimize for AI recommendations
Define one core intent. Say plainly, everywhere, what job your app does and for whom: "Lumo is a budgeting app for couples who share expenses." Secondary use cases support it but shouldn't dilute it.
Write descriptions that answer questions. Put a clear, factual summary in your first sentence, and name features, platforms, pricing, and audience explicitly. LLMs quote plain statements more readily than slogans.
Build an owned web presence. A fast, crawlable website with a feature page, pricing, FAQ, and changelog gives AI engines a source to cite. Add SoftwareApplication or MobileApplication structured data with rating, price, and operating system.
Earn third-party mentions. "Best apps for..." roundups, review sites, Reddit threads, and press coverage are what assistants lean on for validation.
Keep everything consistent. Your app name, category, and core claim should match across both stores, your site, and your social profiles.
Keep reviews detailed and positive. Reviews feed both store AI summaries and assistant answers.
Measure share of voice. Regularly ask the main assistants the questions your users would ask, and track how often, and how favorably, your app appears.
Integrate with the assistants themselves
Platform features let assistants act inside apps: Apple's App Intents power Siri and Spotlight actions, and Android's App Actions do the same for Google's assistant. Apps that expose their key actions give assistants another reason to suggest them.
How to measure ASO: the KPIs that matter
Measure ASO as a funnel: impressions, then product page views, then installs, then retained users. Each stage points to a different fix, so track all of them, not just downloads.
KPI | What it tells you | Where to find it | If it's weak, work on |
Keyword rankings | Whether you're visible for target searches | ASO tools (AppTweak, Sensor Tower, AppFollow, etc.) | Metadata, keyword choice |
Impressions | How often your app is seen in the store | App Store Connect Analytics, Play Console | Rankings, featuring, events |
Product page views | How many people tap into your listing | App Store Connect, Play Console | Icon, first screenshots, title |
Conversion rate | Share of page views (or impressions) that install | App Store Connect, Play Console | Screenshots, video, ratings, copy |
Organic installs by source | Split of search, browse, and referral installs | App Store Connect (source type), Play Console (acquisition reports) | The weakest channel |
Average rating and review volume | Trust and quality signal | Both consoles | Product fixes, prompt timing |
Retention (day 1, 7, 30) | Whether installs stick, a ranking input | Your analytics, consoles | Onboarding, product quality |
AI share of voice | How often assistants recommend you | Manual prompt checks, AEO/GEO tools | Web presence, third-party mentions |
Reporting cadence
Weekly: keyword rankings for your top 20–50 terms, rating trend, new reviews.
Monthly: impressions, conversion rate, and organic installs by source, compared with the prior month and the same month last year.
Per release or test: before-and-after conversion and ranking changes, logged with what you changed.
Isolate branded search when reporting. Brand searches are driven by marketing and PR, so mixing them with generic searches hides whether ASO itself is working.
ASO checklist
Use this checklist for a launch or a quarterly listing audit.
Keywords and metadata
Keyword list researched, scored, and mapped to fields
Title includes brand plus the top keyword, within 30 characters
iOS subtitle uses next-best keywords as a readable benefit
iOS keyword field uses all 100 characters, no repeats, no spaces after commas
Google Play short description leads with the core benefit and a keyword
Descriptions open with a clear value proposition; Play description uses keywords naturally
Creatives
Icon is simple, distinctive, and tested
First screenshot sells the main outcome; captions readable at thumbnail size
Screenshot captions include relevant keywords (iOS)
Preview video shows value in the first 3 seconds, captioned
Google Play feature graphic uploaded (1024 × 500)
Ratings and conversion
Native rating prompts triggered after positive moments
Low-star and bug reviews answered
A/B test running on at least one store
Custom product pages or custom store listings set up for top audiences
In-app events or promotional content scheduled
Reach and measurement
Listing localized for top markets, including cross-localization on iOS
Android vitals below the crash and ANR thresholds
Website with FAQ and structured data; consistent app description everywhere
KPI dashboard reviewed monthly
Common ASO mistakes
Keyword stuffing. It gets rejected by Apple, penalized by Google, and reads badly to users.
Wasting characters. Repeating words across iOS fields, or leaving the keyword field half empty.
Chasing only head terms. New apps rarely rank for them; long-tail wins come first.
Screenshots that show settings screens. Show outcomes, not menus.
Setting and forgetting. Algorithms, competitors, and store features change every few months; review metadata at least quarterly.
Ignoring technical quality. Crashes lower ratings and, on Google Play, can directly cut visibility.
Judging tests too early. Stopping at day two often crowns a false winner.
Treating ASO as separate from product. Retention and reviews are ranking signals; the best ASO lever is often a better app.
Frequently asked questions about ASO
What does ASO stand for?
ASO stands for App Store Optimization: improving an app's store listing so it ranks higher in App Store and Google Play search and converts more visitors into installs.
How long does ASO take to work?
Metadata changes usually affect rankings within a few days to two weeks after the update goes live. Conversion gains from creative tests show within a test's run, typically 7–30 days. Compounding gains from ratings, retention, and off-store authority build over months.
Is ASO different for iOS and Android?
Yes. The Apple App Store indexes a small set of fields, including a hidden 100-character keyword field, and doesn't confirm indexing the description. Google Play has no keyword field but indexes the full description and weights app quality (Android vitals) and engagement heavily.
Which is the most important ASO factor?
The app title is the strongest text ranking signal on both stores. For overall growth, conversion rate matters as much: the icon and first screenshots decide whether impressions become installs.
Does the app description affect App Store rankings?
Apple hasn't confirmed that the iOS description is indexed, and most practitioners treat it as a conversion asset. On Google Play, the description is indexed and matters for rankings.
How often should I update my app's metadata?
Review it at least quarterly, and whenever you ship a major feature, see a ranking drop, or enter a new market. Promotional text (iOS) and promotional content (Google Play) can change as often as you like.
Can paid ads improve organic ASO?
Indirectly. Paid installs raise download velocity, which can lift rankings, and Apple Ads data shows which keywords convert. But ads don't replace good metadata or creatives.
Do I need an ASO tool?
You can start with free sources: store autocomplete, Apple Ads popularity scores, App Store Connect, and Play Console. Paid tools and services such as BrightLake.ai, AppTweak, Sensor Tower, AppFollow, and MobileAction add keyword volume estimates, rank tracking, and competitor data, which become worth it as you scale.
How do I get my app recommended by ChatGPT or Gemini?
Give your app one clear core purpose, state it consistently on both stores and your website, earn mentions in third-party "best apps" lists and reviews, and keep ratings and reviews strong. Store pages are the most-cited source AI assistants use for app recommendations.
Comments