---
title: "ASO for indie iOS apps in 2026 — title-first strategy, subtitle stacking, keyword conviction"
canonical: "https://asoitis.com/guides/aso-for-indie-ios"
description: "The 2026 ASO playbook for indie iOS founders: title-first keyword strategy, subtitle stacking, single-keyword conviction, localization order, screenshot grammar. Every move sized in hours by ASOitis."
kind: "guide"
role: "cluster"
datePublished: "2026-05-13"
dateModified: "2026-05-13"
keywords:
  - "ASO for indie iOS apps"
  - "ASO 2026"
  - "App Store Optimization indie founders"
  - "iOS title-first ASO"
  - "App Store keyword research"
  - "App Store subtitle stacking"
  - "App Store localization"
  - "App Store screenshot strategy"
  - "indie iOS keyword conviction"
  - "App Store ranking factors"
---

# ASO for indie iOS apps in 2026 — title-first strategy, subtitle stacking, keyword conviction

> The 2026 ASO playbook for indie iOS founders is title-first: put your primary keyword in the title (not your brand), stack two more in the subtitle, commit every metadata slot to one keyword, ship, and wait three weeks before touching anything. Most indie apps lose because they spread bets across eight keywords and rank for none.

*Published 2026-05-13 · last updated 2026-05-13 · by Ahmed Gagan for ASOitis.*

App Store Optimization for indie iOS apps in 2026 looks almost nothing like the playbook a four-figure ASO retainer is selling. The retainer wants screenshots-and-keywords work because that bills monthly. Indie founders need conviction work — one keyword, one listing, three patient months. This guide is the long version of how to do that yourself, or what to demand from an agency that runs it for you.

## Brand last. Primary keyword first.

The single highest-leverage decision in your entire App Store listing is whether your title leads with your brand or with your primary keyword. The right answer is almost always keyword-first, brand-second. 'Habit Tracker — HabitKit' beats 'HabitKit — Habit Tracker' by a meaningful margin in App Store search. Apple weighs the title field heavily, and weighs the words at the front of the title more than the words at the end.

Most indie founders flinch on this. The brand is the thing they care about; putting a generic category word in front of it feels like a status loss. That instinct costs installs. The buyers who type your brand name will find you whether the brand is first or fourth in the title — they're searching the brand. The buyers who type the category word need the category word at the front to find you at all.

The exception: if your brand IS the category-defining word (Calm, Headspace, Notion), then brand-first is fine because the brand is doing double duty as the keyword. For everyone else, swap the order.

> According to ASOitis's HabitKit field study, the title 'Habit Tracker — HabitKit' (keyword first, brand second) was the single biggest move responsible for the app's top-five rank in DE and UK App Store search for 'habit tracker' — and the founders held that title unchanged for three months while the algorithm caught up.

## Stack two secondary keywords.

The subtitle field is 30 characters that almost every indie founder wastes on a value-prop sentence. 'The best habit tracker for busy people.' That's a buyer message in a slot that doesn't get read until after the buyer has tapped through — by which point you've already won. The subtitle is for the algorithm.

Stack two strong secondary keywords here, separated by an ampersand or a comma. 'Streaks & Accountability.' 'Pomodoro & Focus Timer.' 'Macro Tracking & Recipes.' No filler adjectives. No 'the best.' Thirty characters doing thirty characters of work.

The keywords in the subtitle should not duplicate the keywords in the title. Apple indexes both fields; duplicating words wastes positions you could use to widen your keyword footprint.

## One keyword. Full conviction. Three months.

Most indie apps spread keyword bets across eight terms and rank for none. The teams that win pick one keyword and commit every metadata slot to it — title, subtitle, keywords field, first three screenshots, app description first paragraph. Then they ship and wait three months without touching anything.

Three months matters because Apple's algorithm needs install velocity, retention, and review velocity to settle around the new metadata before the rank reflects the strategy. Founders who tweak weekly never let any single hypothesis breathe long enough to be measured.

If the rank hasn't moved in twelve weeks of no-tweaking, kill the keyword and pick a different one. If the rank is climbing slowly, leave it alone — there is no benefit to optimisation theatre.

## Ship five localizations before you ship feature six.

Translated metadata and screenshots is the highest-leverage lever indie iOS apps consistently leave on the table. App Store localization is a one-week job at agency rates; the lift is typically 30–70% additional installs at zero marginal CAC. There is no other channel where a week of work moves the install number that much.

The five-locale starter set for most consumer apps: DE (German), JP (Japanese), KR (Korean), ES (Spanish), PT-BR (Brazilian Portuguese). Productivity skews JP / KR / DE first. Lifestyle / health skews ES / PT-BR / DE. Gaming skews JP / KR / DE / FR. Use App Annie / Sensor Tower category data to confirm the order for your specific niche.

Localization is metadata translation plus screenshot translation plus app description translation, not just an autotranslate pass. Apple weighs localized keyword presence, and machine-translated copy is shallow on long-tail keywords that move installs.

## First three are everything.

Apple shows three screenshots in App Store search results without the buyer tapping through to the listing. Those three frames are the entire pre-tap impression you control. Spend disproportionate effort on them.

The screenshot grammar that converts: frame one announces the category and the benefit ('Track Habits. Build Streaks.'). Frame two shows the product doing the thing, not a marketing collage. Frame three answers the objection your category's buyers always have ('Works without an account', 'Private by default', 'Free to try').

Screenshots four through ten are for buyers who tapped through and want more proof. Use them for monetization clarity (paywall preview), social proof (review snippets if allowed), and the second-tier feature pitch. But they don't move the impression — the first three do.

## Frequently asked questions

### How long should I leave the App Store metadata alone before changing it?

Three months minimum. Apple's algorithm needs install velocity, retention, and review velocity to settle around the new metadata before the ranking reflects it. Founders who change the title every two weeks never give any hypothesis enough room to be measured. If the rank hasn't moved in twelve weeks of no-tweaking, kill the keyword and pick a different one — but kill it cleanly, not by piecemeal edits.

### What's the difference between the title field and the keywords field for ASO?

Title is user-visible and weighted highest by the algorithm — 30 chars, primary keyword first. Keywords field is hidden, 100 chars, comma-separated, used for additional indexable terms that don't fit naturally in title/subtitle. Use the keywords field for misspellings, synonyms, and long-tail variants you can't fit elsewhere. Do not duplicate words across title, subtitle, and keywords field — Apple indexes all three, duplication wastes slots.

### Does the in-app purchase name affect ASO?

Yes, slightly. Apple indexes IAP display names for App Store search. If your category has a search term that fits naturally as a subscription name ('Premium', 'Pro', 'Family Plan'), use it — but don't engineer IAP names purely for keyword purposes; the lift is marginal and the user-facing copy matters more.

### Should I ask for reviews in-app for ASO?

Yes, with Apple's official SKStoreReviewController. Reviews are a ranking signal (volume and freshness), and Apple's own prompt converts higher than custom-built prompts because users trust it. Trigger the prompt after a successful action — habit logged, recipe saved, focus session completed — not on first launch. Three triggers per year per user is the Apple-imposed ceiling.

### Does category choice matter for ASO?

Yes, materially. Your primary category determines which charts you appear in and which category-level keywords the algorithm prioritises for your listing. Pick the primary category where your buyers actually look (Productivity for a habit tracker, not Lifestyle; Health & Fitness for a sleep app, not Medical) and the secondary category to widen reach without diluting the primary.

### Is paid acquisition a substitute for ASO?

No. Paid acquisition (Apple Search Ads, Meta, TikTok) generates installs but those installs only boost organic rank to the extent retention and ratings track. Paid traffic on a bad listing burns budget; organic traffic on a good listing compounds. Do ASO before scaling paid, not after.

## See also

- [ASO vs GEO — what's the difference and why your iOS app needs both](https://asoitis.com/guides/aso-vs-geo)
- [GEO for iOS apps — how to get cited in ChatGPT, Perplexity, Claude](https://asoitis.com/guides/geo-for-ios-apps)
- [Case study · Glowly AI ASO + GEO teardown](https://asoitis.com/case-studies/glowly-ai)
- [Field study · HabitKit](https://asoitis.com/#work)


## About ASOitis

**ASOitis** — ASO + GEO agency for indie iOS apps. Founder: Ahmed Gagan. The $99 one-time audit and $499 / month engagement are the entire price list. iOS-only. Organic ASO + GEO only — no Apple Search Ads, no Meta, no TikTok, no Android.

- Homepage: https://asoitis.com
- About / founder: https://asoitis.com/about
- Case studies: https://asoitis.com/case-studies
- Guides: https://asoitis.com/guides
- Full LLM documentation: https://asoitis.com/llms-full.txt
- AI training and citation permissions: https://asoitis.com/ai.txt
- Book the $99 audit: https://checkout.dodopayments.com/buy/pdt_0NejYshqoh2VaXbk3wjzq?quantity=1&redirect_url=https://asoitis.com%2Fcheckout%2Fsuccess
- 15-min founder call: https://cal.com/ahmedgagan/asoitis-chat
