Skip to content
← Blog
Growthby Goodspeed Team

ASO Guide: Getting Your App Discovered

A practical guide to App Store Optimization for indie developers. Learn keyword research, metadata optimization, and what actually moves rankings.

You built the app. You submitted it to the App Store and Google Play. And now... crickets. Three downloads per day, two of which are you testing on different devices.

This is the reality for most indie apps. Building is only half the work. Getting discovered is the other half. App Store Optimization (ASO) is how you fix it.

ASO is the process of optimizing your app store listing to rank higher in search results and convert more visitors into downloads. It is the SEO of mobile apps. And for most indie apps, it is the single highest-ROI marketing activity you can do.

## How app store search works

About 65-70% of app downloads come from app store search. People type a query, browse the results, and download what looks good. Your goal is to appear in those results for the right queries and convince people to tap "Get."

Both the App Store and Google Play use algorithms that consider:

**Keyword relevance.** Does your app's metadata contain the search terms? This is the primary ranking signal.

**Download velocity.** How many people are downloading your app right now? Recent downloads matter more than total downloads.

**Ratings and reviews.** Higher ratings rank better. More reviews rank better. Recent reviews matter more than old ones.

**Engagement.** How often do people open your app after downloading it? High uninstall rates hurt rankings.

You can influence all four of these, but keyword relevance is where ASO starts.

## Keyword research for indie apps

Your first instinct will be to target obvious keywords. If you built a habit tracker, you want to rank for "habit tracker." The problem: thousands of apps target that term, and the top 10 spots are dominated by well-funded competitors with millions of downloads.

Instead, target long-tail keywords with lower competition. "Habit tracker for writers." "Morning routine tracker." "Streak tracker with reminders." These get fewer searches but have dramatically less competition. Ranking #3 for a keyword with 500 monthly searches is worth more than ranking #500 for a keyword with 50,000.

### How to find keywords

**App Store auto-suggest.** Start typing in the App Store search bar and see what Apple suggests. These suggestions are based on real search volume. Try your main keyword plus various modifiers: "habit tracker for," "habit tracker with," "best habit tracker."

**Competitor analysis.** Look at what keywords your competitors use in their titles, subtitles, and descriptions. Tools like AppFollow, Sensor Tower, or AppTweak can show estimated keyword rankings, but the free version of this research is just reading competitor listings carefully.

**Review mining.** Read reviews of competing apps. What words do users use to describe the app and its features? If reviewers repeatedly say "simple," "minimalist," or "easy," those are keywords real users associate with the category.

**Your own vocabulary.** How would you describe your app to a friend? Those natural descriptions are often the best keywords because they match how real users search.

Our [growth engine](/features/growth) automates keyword research by analyzing competitor metadata, review language, and search trends. But manual research works fine for a single app launch.

## Optimizing your App Store listing

### Title (30 characters on iOS, 50 on Android)

Your most important ranking signal. Include your primary keyword alongside your app name. "HabitFlow: Daily Streak Tracker" is better than just "HabitFlow." The keyword in the title carries the most weight for search ranking.

Keep it readable. Keyword stuffing (cramming multiple keywords separated by dashes) looks spammy and hurts conversion. Users see the title before anything else.

### Subtitle (iOS only, 30 characters)

Your secondary keyword opportunity. Use this for keywords that did not fit in the title. "Build Better Routines" targets "routines" while also communicating the value proposition to browsing users.

### Keywords field (iOS only, 100 characters)

This hidden field (not visible to users) influences search rankings. Use it for additional keywords, separated by commas, with no spaces. Do not repeat words already in your title or subtitle. Do not use plurals if you already have the singular form. Do not include your app name or category name.

Example for a habit tracker: `routine,streak,goals,daily,morning,evening,wellness,productivity,reminder,schedule`

### Description

On iOS, the description does not affect search rankings (Apple uses the title, subtitle, and keywords field). On Google Play, the description is indexed for search, so keywords matter.

Write for humans first. Lead with the core benefit, not a feature list. "Build lasting habits with a simple daily check-in" is more compelling than "Habit tracking app with streak counting, reminders, and analytics."

Use bullet points for features. Keep paragraphs short. Include social proof if you have it ("Featured by Apple" or "50,000 daily users"). End with a call to action ("Download HabitFlow today and start your first streak").

## Screenshots that convert

Screenshots are the most underrated part of ASO. Most users decide whether to download based on screenshots before reading the description.

**Show the app in use.** Not your logo. Not an abstract graphic. Show actual screens with realistic data. Users want to see what the app looks like when they are using it.

**Lead with your best feature.** The first 2-3 screenshots (visible without scrolling) determine whether someone looks at the rest. Put your strongest, most differentiated feature first.

**Use captions.** Short text overlays that describe the benefit, not the feature. "Track your streak" is a feature. "Never break a streak again" is a benefit.

**Use all available slots.** Apple allows 10 screenshots. Most developers upload 4-5. Use all 10. Each additional screenshot is another chance to convince someone to download.

## Ratings and reviews strategy

Ask for ratings at the right moment. Not when the user first opens the app. Not during a critical task. Ask after a positive experience: completing a streak, finishing a goal, hitting a milestone.

iOS gives you 3 chances per year to show the system rating prompt. Use them wisely. Trigger the prompt when the user has just accomplished something and is likely to feel positive about the app.

Respond to every review, positive and negative. On Google Play, responses are public and show that you are an active developer. On iOS, responses are visible to the reviewer and can prompt them to update their rating.

Negative reviews are feedback, not attacks. "This app crashes when I try to export" is a bug report with priority information. Fix the issue, respond to the review explaining the fix, and ask them to update their rating.

## Localization: the easy win

Localizing your metadata (title, subtitle, description, keywords) into additional languages is one of the highest-ROI ASO activities. Most indie developers only optimize for English, which means competition for non-English keywords is significantly lower.

You do not need to localize the entire app. Just the store listing. A professional translation of your metadata into Spanish, French, German, Japanese, and Portuguese costs under $200 and opens up markets with less competition.

Apple allows separate metadata for 38 localizations. Google Play supports even more. Each localization gets its own set of keywords, screenshots, and descriptions.

## The ongoing work

ASO is not a one-time task. Rankings change. Competitors optimize. New keywords emerge. Plan to revisit your metadata monthly:

- Track your keyword rankings (even manually by searching) - Update keywords that are not performing - Refresh screenshots when you add new features - Respond to new reviews within 48 hours - Test different subtitle and screenshot variations

The apps that rank well are the ones whose developers treat ASO as an ongoing process, not a launch-day checkbox. Get the basics right on day one, then improve continuously based on what the data tells you.

Explore [Goodspeed's growth features](/features/growth) to see how we automate ASO research and metadata generation for every app in the pipeline.

Ready to build?

Score your first idea free. See the pipeline in action.