Your app ranks in the top 15 for several keywords you care about. Installs are flat. You’re not sure what to change because by every ranking metric you can see, the work is holding.
This is one of the most common situations indie developers run into six months after launch, and it’s confusing because ranking success and download growth are two different problems. Mixing them up is how you spend weeks updating metadata when the real issue is on your product page, or redesigning screenshots when the real issue is that nobody’s finding you at all.
The App Store gives you enough data to tell them apart. Most developers never look at it this way.
The funnel has two distinct failure points
App Store growth happens in two stages:
Discoverability: Does Apple surface your app for the searches users are running?
Conversion: When users see your app in results, do they tap it? And once they’re on your product page, do they install?
Keyword optimization works on the first stage. It affects whether Apple indexes your app for relevant searches and whether your app appears prominently enough to be seen. If that stage is broken, no amount of screenshot polish will help. Nobody’s arriving to convert.
But if the first stage is working and the second stage is broken, keyword work won’t help either. You’re already being found. Users just aren’t installing.
Both problems look identical from the downloads line on a chart. You have to dig one level deeper to see which one you’re dealing with.
How to read the funnel in App Store Connect
Three metrics in App Store Connect let you calculate conversion at each stage:
Impressions: How many times your app appeared in search results, on category pages, in featured sections, or on other apps’ product pages.
Product Page Views: How many users tapped through to your full listing after seeing it.
Downloads: How many users installed.
From those three numbers, you can derive two conversion rates.
Tap-through rate (Product Page Views divided by Impressions): This tells you how compelling your app looks in search results before users arrive at your page.
Install rate (Downloads divided by Product Page Views): This tells you how well your product page closes once users are there.
Both rates will vary by traffic source, device type, and category, so don’t get too attached to absolute benchmarks. What matters more is the diagnosis these numbers make possible.
The four states, and what each one means
Low impressions, reasonable conversion rates: This is a ranking problem. Apple isn’t surfacing your app. The fix lives in keyword expansion, metadata updates, and potentially localization to reach more search surfaces.
Strong impressions, low tap-through rate: Users see your app in search results but don’t tap. This is a search result presentation problem. Your app icon, title, and subtitle are the only signals visible before a tap. If those aren’t earning attention, changing your screenshots won’t help.
Strong impressions, strong tap-through rate, low install rate: Users arrive on your product page and leave without installing. The fix lives in your screenshots, your description, or the mismatch between the keyword that brought them and what they find when they get there.
Low impressions and low conversion at both stages: Both problems exist. Fix the ranking problem first. Conversion optimization has no leverage when traffic is minimal.
Why the subtlety matters
Most indie developers default to “update the keywords” whenever downloads are low. Sometimes that’s right. Often it’s a wasted release cycle.
If your app is collecting 40,000 impressions per month but converting to 600 installs, that is not a keyword coverage problem. You have strong search visibility. You have a conversion problem, and the fix is a product page change, not a metadata change.
If your app is collecting 800 impressions per month from a handful of low-competition keywords, that is a visibility problem. More keyword surface area is the right answer. Redesigning screenshots at that point is optimizing something only 800 people will see.
The funnel tells you which lever matters. Pulling the wrong lever is worse than doing nothing, because it uses up a version release and a 21-day observation window you could have spent on the actual problem.
What breaks tap-through rate
If your impression-to-page-view rate is weak, start with the subtitle.
Your subtitle appears directly under your title in most search result layouts. It’s indexed by Apple and visible before the user taps. Most developers write subtitles that describe what the app does. Users respond better to subtitles that describe what they get.
“Track your runs” describes the app. “Know exactly how your training is trending” describes the result. The second one earns more taps from someone who searched “running tracker.”
The app icon is the other visible element in search results. It’s also the most expensive thing to test: a redesign takes real time and a 21-day wait before you have meaningful data. If you suspect the icon is the issue, flag it as a future test. Start with the subtitle because you can ship it in the next metadata update.
What breaks install rate
If your page-view-to-install rate is weak, start with the first screenshot.
The first screenshot is the most important real estate on your product page. It’s visible above the fold on nearly every device. Users who aren’t sure whether to install will make that decision based on one or two screenshots before scrolling further.
The job of the first screenshot is not to showcase a feature. It’s to confirm that this is exactly what the user came looking for.
If your keyword bet is “meditation timer for anxiety,” the first screenshot should show a timer with context around calm and focus, not a general wellness dashboard. The gap between what the search implied and what the screenshot shows is felt immediately, even if users can’t name it. They just leave.
Also check your screenshots against the keywords actually driving your impressions. If your strongest traffic is coming from narrow, specific searches and your screenshots are pitched at a broad general audience, that mismatch is costing you installs.
The one-change rule applies here too
The same discipline that governs metadata testing applies to conversion optimization.
Don’t update the subtitle, the icon, the first screenshot, and the description in the same release. You will not be able to tell what moved the rate. Pick one hypothesis, change one element, wait 21 days, read the conversion metrics, then decide what to change next.
The instinct when downloads are flat is to fix everything at once. The result is a version history with no usable signal. You spend the next quarter making similar changes and wondering if they’re working.
One change. Three weeks. Read the funnel. Repeat.
Putting it together
Before your next metadata update, look at your funnel for the past 30 days:
- Check impressions. Are they growing, flat, or declining?
- Check tap-through rate. Are users engaging with your search listing?
- Check install rate. Are users converting from your product page?
If impressions are healthy and both conversion rates are strong, you have neither a ranking problem nor a conversion problem. Something else is limiting growth, perhaps seasonal patterns, category dynamics, or product-market fit at a deeper level.
If impressions are strong and conversion is broken, your keyword work is doing its job. Stop changing metadata and fix the product page.
If impressions are weak, that is your starting point. Everything else is secondary until more users are seeing your app.
The funnel gives you a map. Most developers are navigating without one.