Most ASO advice is either too vague to act on ("optimize your keywords!") or buried in 10,000-word guides that assume you have a team and a budget. This is neither.
These are 15 specific, actionable tips for indie iOS developers — things you can check, fix, or implement in your next App Store update. They're ordered roughly by impact, starting with the highest-leverage changes.
1. Put your primary keyword in your title — as early as possible
The title is the highest-weighted field in Apple's algorithm. A keyword in position 1 of your title carries more ranking power than the same keyword in your subtitle, and significantly more than in your keyword field.
If your title is your app name with no category keyword, you're invisible to anyone who doesn't already know your name. Fix: add a dash or colon after your brand name and include your primary keyword. "Navi — Habit Tracker" outranks "Navi" for "habit tracker" every time.
2. Stop wasting your subtitle on taglines
"Your productivity companion" is not a subtitle. It's a wasted 30 characters of the second-highest-weighted search field in Apple's algorithm.
Every word in your subtitle is indexed for search. Use it for your second most important keyword — one that doesn't appear in your title. "Daily Goals & Streaks" after "Habit Tracker: Navi" adds "daily," "goals," and "streaks" to your indexed keyword set. A tagline adds nothing.
3. Remove every duplicate word from your keyword field
Apple indexes each word once — from whichever field it first appears in. If "focus" is in your title and also in your keyword field, the keyword field instance contributes zero ranking power. You've wasted those characters.
Run your title, subtitle, and keyword field through the free keyword checker. Most apps find 3–6 duplicates on the first audit. Each duplicate you remove and replace with a new term expands your search footprint.
4. Use commas not spaces in your keyword field
Spaces count toward your 100-character keyword field limit. Commas don't.
focus,timer,productivity,habit = 30 characters, 4 keywords indexed
focus timer productivity habit = 30 characters, but only 3 separators, and you've used spaces that could have been more keywords
Write focus,timer,productivity not focus, timer, productivity. That single space after each comma costs you characters across the whole field — potentially 5–10% of your total budget on long fields.
5. Fill your keyword field to 100 characters exactly
Every character under 100 is a keyword you're not targeting. Most apps submit keyword fields at 70–80 characters and leave meaningful ranking opportunity unused.
Count your field character by character before submitting. App Store Connect shows the character count live. If you're at 87, find 2–3 more relevant terms to fill the remaining 13.
6. Fix your ratings before spending time on keywords
Below a 4.0 average rating, keyword optimization hits a ceiling. Apple's algorithm weights rating quality, and apps with low ratings rank lower for competitive keywords regardless of metadata quality.
If your rating is under 4.0, implement SKStoreReviewRequest to prompt users after a positive in-app moment — 3rd completed session, completing a goal, returning after 3+ days away. Get your rating above 4.0 before investing heavily in keyword strategy.
7. Prompt for ratings at the right moment
Apple allows 3 native review prompts per user per 365 days. Most apps either never prompt or prompt immediately after download — the worst possible moment, before the user has experienced any value.
The highest-converting prompt moments:
- After completing a meaningful action for the 3rd time
- After returning to the app following 3+ days of absence (signals habit formation)
- After the user achieves a goal or milestone
Use the native SKStoreReviewController — not a custom review screen. The native prompt converts at a higher rate because users trust it.
8. Change your subtitle without a new binary
Most App Store metadata changes require submitting a new app version. The subtitle is an exception — it can be changed independently in App Store Connect without a new binary submission.
This makes the subtitle the easiest field to experiment with. Change your subtitle, wait 4–6 weeks, check whether rankings moved. If the new keyword performed well, keep it. If not, try another. No binary review cycle required.
9. Don't put your app name or developer name in the keyword field
Apple automatically indexes your app name and your developer name. Putting them in the keyword field wastes characters on coverage you already have for free.
Same applies to your category name if it's already in your title. Every character spent on already-indexed words is a character not spent on new keywords.
10. Target keywords where you can actually rank
"Productivity" has hundreds of apps in the top results with 100,000+ ratings. A new indie app will not rank for "productivity" regardless of how well it's optimized.
Find the competition tier where your app can compete. Look at the apps currently ranking in positions 3–10 for your target keyword. What are their rating counts? If they're all above 5,000, you need a more specific variant — "productivity timer for focus" or "deep work pomodoro" — where the top results have 200–1,000 ratings.
11. Wait 6 weeks before evaluating keyword changes
Apple's indexing takes 2–4 weeks after a metadata update. Many developers change keywords, check rankings two weeks later, see no movement, and revert — before the changes were even indexed.
Give every keyword change at least 6 weeks before deciding if it worked. Set a calendar reminder when you submit. Don't touch the metadata again until the evaluation window closes.
12. Set up keyword rank tracking before you make changes
You can't know if a change worked without a baseline. Before your next metadata update, set up per-keyword rank tracking in Astro, AppFollow, or ASOdesk. Record your current positions. After the 6-week window, compare.
Without a baseline, "my ranking improved" is a feeling. With tracking, it's a measurement.
13. Check your non-English keyword fields
Open App Store Connect. Look at your app's metadata for Germany, Japan, France, Brazil, South Korea. How many have a filled keyword field? How many have a researched subtitle?
If the answer is "none" or "same as English," you're invisible to every non-English search in those markets. Japan is the third-largest App Store market by revenue. Germany is the largest in Europe. A blank keyword field in those locales means zero organic search presence there — not low presence, zero.
14. Localize, don't translate
If you do add non-English metadata, use keyword research tools set to the target country to find what users actually search in each language — not a translation of your English keywords.
"Productivity" translated to German is "Produktivität." But German App Store users might search "Zeitmanagement," "Aufgabenliste," or "Gewohnheiten App" far more often. Translation gives you the literal equivalent. Research gives you what users type. Only one of those moves rankings.
15. Revisit keywords every 3–6 months
Search behavior changes. Competitors update their metadata. New keyword opportunities emerge as your app's category evolves. A keyword field set once in 2023 is working with outdated data.
The minimum maintenance cadence is every 6 months: pull fresh keyword data, check which of your current terms still have the right volume-to-competition ratio, and refresh any that have become too competitive or too low-volume to be worth the characters.
The highest-leverage starting point
If you do only one thing from this list: run your current title, subtitle, and keyword field through the free keyword checker. It takes 30 seconds and shows you duplicates and character waste instantly. Most apps find something to fix on the first check.
For the full research — keyword data by market, competitor gap analysis, and paste-ready metadata — LocalizeRank starts at $49 for 5 markets.