Most ASO guides are written for teams with budgets, agencies, and dedicated growth functions. This one is not.

This ASO playbook is built for indie iOS developers: one person, one app, limited time. Every step in this framework is ordered, actionable, and scoped to what actually moves rankings without requiring paid installs or a marketing team. Follow the steps in sequence. Each one sets up the next.

Step 1: Keyword Research

Start here. Everything else in this playbook compounds from this step.

The mistake most indie developers make is targeting head terms: broad, high-volume keywords where the top 10 is dominated by apps with hundreds of thousands of downloads. These are unwinnable in the short term. The correct approach is a tiered keyword strategy that matches keyword difficulty to your app’s current ranking authority.

Three tiers, each with a different role:

  • Foundation tier: Terms you can rank for now. Low difficulty, lower volume, but real search queries from real users. These produce early impressions and build conversion signals that help you rank for harder terms later.
  • Growth tier: Terms you are 6 to 12 weeks away from reaching. Medium difficulty, meaningful volume. This is where most of your ranking work should be focused after your first metadata sprint.
  • Target tier: Your long-term goal. High volume, high competition, likely six or more months away. Track these, but do not waste keyword field space on them until your foundation and growth tiers are producing.

Build a list of 80 to 120 terms across all three tiers before you write a single word of metadata. Pull candidates from four sources: your app’s core functionality described in plain language, competitor titles and subtitles, App Store autocomplete suggestions for your top 5 use-case terms, and related searches visible at the bottom of search results pages.

Track all of these terms before you touch any metadata. You need a baseline so you can measure what moves.

Step 2: Screenshot Optimization

Screenshots convert users. Keywords bring users to your product page. Confusing these two responsibilities is the most expensive creative mistake in app store optimization.

The first two screenshots carry the majority of conversion weight. Research consistently shows most users never scroll past frame two. This means your first screenshot has one job: communicate what the app does and why a user should care, in under three seconds, in the context of a small mobile screen.

What converts:

  • Lead with the outcome, not the feature. “Fall asleep in minutes” outperforms “Sleep Timer Mode” because the user searched for a result, not a feature label.
  • Use the minimum UI chrome needed to establish credibility. Showing the app is real matters; showing every settings menu does not.
  • Match the copy in the screenshot to the keyword the user searched. A user who found your app by searching “meditation for anxiety” responds better to a first frame that mentions anxiety than one that leads with a general wellness message.

What does not convert:

  • Distributing features across six screenshots with no hierarchy
  • Screenshot copy that requires reading to understand (if it takes more than three seconds, users bounce)
  • Generic marketing language that could apply to any app in the category

Screenshot copy is one area where AI for ASO accelerates the work significantly. Generate five different outcome framings for your first screenshot frame, test them, and let the data select the winner rather than making the decision based on internal preference.

Step 3: Ratings and Reviews

Below 20 ratings, your product page conversion rate is suppressed regardless of screenshot quality. Users assign uncertainty to apps with few ratings before they read anything else. This is not a perception problem you can design around. It is a threshold that requires actual ratings to cross.

The fix is review timing. The native review prompt should fire at moments of genuine user delight, not on app launch and not as a blanket trigger after a fixed number of sessions. Productive trigger points:

  • After a user completes a task that involved three or more steps
  • After a user returns to the app for the third time in the same week
  • After a user hits a milestone they set for themselves inside the app

Quantity matters most at the low end of the volume range. Getting from 2 ratings to 20 ratings has more conversion impact than going from 200 to 300. Do not wait to get the review prompt right. Ship a basic version and refine it.

For review responses, reply within 48 hours and be specific. Reference the actual content of the review rather than using a template response. For negative reviews, acknowledge the issue, describe what changed or what will change, and invite the user back. Every prospective user reading your reviews also reads how you respond. The response is conversion copy, not customer service.

Step 4: Localization

Localization is the highest-leverage growth lever most indie developers ignore entirely. A single English listing competes globally, but an app with localized metadata across five regions has five separate ranking surfaces in Apple’s search index.

Which locales to prioritize first:

  • English (US) is table stakes.
  • English (UK) and English (Australia) are fast wins. Translation work is minimal, but Apple treats them as separate ranking surfaces with separate keyword indexes.
  • German, French, and Japanese are the next tier if your app has a use case that crosses language markets without requiring deep cultural adaptation.

Do not localize into a language unless you can also respond to reviews in that language. A user who leaves a negative review in German and gets no response is a worse outcome than no localization at all.

When localizing copy, avoid direct translation. Adapt for search behavior. The queries users type in German App Store search are not translated versions of English queries. They reflect different vocabulary, different search habits, and different expectations. Native speaker review is not optional for localization to work.

Step 5: Market Intelligence

Most indie developers track their own keyword rankings. Fewer track what competitors are doing with their rankings, and almost none use competitor movement as a signal for their own keyword decisions.

ASO market intelligence means monitoring the keywords your competitors are ranking for that you are not, and tracking when they update their metadata. A competitor’s title or subtitle change signals that they identified a keyword cluster worth testing. Their keyword field is hidden from you, but their ranking movements are not.

Watching competitor keyword movements gives you three actionable inputs:

  1. Early signal on keyword terms gaining volume in your category, before you commit budget or sprint time to testing them yourself
  2. Evidence of which growth-tier terms are winnable at your current authority level, based on the competitive apps ranking in those positions
  3. A gap list: terms your five closest competitors rank for that your app does not appear in at all

Build a competitor monitoring list of five apps in your category and review their ranking changes weekly. When a competitor makes a visible metadata change, investigate the keyword clusters they moved into. That investigation often surfaces opportunities faster than any keyword brainstorming session.

Step 6: Using AI for ASO

AI tools have changed the speed at which several parts of the ASO workflow can run. Understanding where AI for ASO accelerates work and where it does not replace judgment is the difference between a useful tool and a shortcut to worse decisions.

Where AI accelerates ASO work:

  • Generating 20 title and subtitle variations for keyword testing in seconds instead of hours
  • Summarizing review themes across hundreds of reviews to surface the top user praise points and the top complaints, which become both screenshot copy and review-prompt timing inputs
  • Writing localization variants for metadata fields to send to a native speaker for selection, instead of starting from a blank page
  • Identifying keyword gaps from competitor visible metadata (title, subtitle, app name) at scale across a full category

Where AI does not replace judgment:

  • Choosing which keyword tier to target requires knowing your app’s current conversion authority, which requires looking at actual conversion data from your product page
  • Deciding when to push a metadata update requires understanding how Apple’s algorithm weights fresh updates, which requires experience reading ranking movement patterns
  • Selecting which screenshot variant wins requires real impression and conversion data, not an AI preference

Marteso uses AI to generate keyword suggestions ranked by estimated difficulty and relevance to an app’s existing metadata, to draft screenshot copy variants for testing, and to surface localization candidates. The judgment calls on what to accept and what to ship stay with the developer. The time cost of generating options drops from hours to seconds.

Step 7: Measuring Results

The most common failure mode in ASO is not a bad strategy. It is abandoning a working strategy because the measurement window was too short or the wrong metrics were being watched.

ASO operates on 21-day cycles. Apple’s algorithm re-evaluates keyword placements on that cadence. Making decisions after 7 days means making decisions based on noise. The signal lives in 21-day cycles, not weekly snapshots.

Three metrics that actually diagnose ASO performance:

Keyword rank velocity. How many positions did a keyword move per cycle? A term moving from unranked (position 200+) to the top 50 in one cycle is on a strong trajectory. A term stuck at position 80 after two cycles with no movement needs diagnosis: the difficulty may be higher than it appeared, the term may be too broad for your current authority, or conversion is actively dragging the ranking signal down.

Tap-through rate. From impressions to product page views. The healthy range for an indie app ranking for relevant keywords is 8% to 20%. Below 8% means the search result presentation is not matching query intent, and the fix lives in the icon, visible subtitle text, or the first screenshot visible in browse views.

Product page conversion. From page views to first-time downloads. The healthy range is 20% to 40% for apps well-matched to their ranked keywords. Below 15% with a tap-through above 10% means users arrived interested and left without installing. Screenshots and ratings volume are the most common causes.

The correct measurement timeline for this app store optimization playbook:

  • Weeks 1 to 3: collect baseline data, make no changes
  • Week 4: push first metadata sprint, document everything you changed
  • Week 4 to 7: monitor rank velocity, tap-through, and page conversion against your baseline
  • Week 8: diagnose results, adjust keyword tier, plan second sprint
  • Month 3 and beyond: one metadata sprint every 3 to 4 weeks, compounding on what worked

By month four, an app following this playbook has a tested keyword cluster, a conversion baseline it can measure against, and a sprint rhythm that compounds over time. The teams that win at ASO are not the ones with the best initial strategy. They are the ones who run the process consistently for two or more quarters without abandoning it when the first cycle’s results feel slow.

Marteso tracks keyword rank velocity, tap-through rate, product page conversion, and competitor movements in one dashboard, updated automatically from App Store Connect. You get the full ASO playbook metrics without building your own analysis. Start at app.marteso.com.