Most indie developers treat ASO as a ranking problem. Rank higher, get more impressions, watch downloads grow.
The model is incomplete.
Between impressions and downloads, there are two conversion steps that most developers never measure. Both can fail silently while rankings improve. You can spend weeks optimizing keywords and end up with more visibility and no more installs.
Here is how to find the actual problem.
The conversion chain most developers skip
Every App Store download starts as an impression. After that, two things have to happen:
- The user has to tap your listing (impression to product page view)
- The user has to decide to install (product page view to download)
Each step is its own conversion rate. App Store Connect tracks both. Most developers never separate them.
For Pi Digits, using Marteso’s analytics pull from the past 30 days:
- Impressions: 1,847
- Product page views: 312 (tap-through rate: 16.9%)
- First-time downloads: 89 (page conversion: 28.5%)
- End-to-end: 4.8% of impressions became installs
Walk through that chain: for every 100 users who saw the app in search results, 17 tapped in. Of those 17, about 5 installed. If rankings double the impressions but tap-through stays at 16.9%, downloads roughly double. But if tap-through drops to 8%, a doubling of impressions produces no gain at all.
Rankings get you impressions. What happens to them is the conversion problem.
Tap-through rate: the metric search results control
Tap-through rate is impressions divided by product page views. It measures how many users who saw the app in search results decided to click in.
What users see in search results before they tap:
- App icon
- App name and the start of the subtitle (often truncated)
- Star rating and review count
- The first screenshot in some browse views
If any of these create a mismatch with the search query, the user scrolls past. Tap-through falls without any change in keyword rankings.
The most common tap-through killers for indie apps:
- An icon that looks generic next to more polished competitors in the same results page
- A subtitle that repeats the title instead of adding qualifying context
- A review count of 0, 1, or 2 (users read this before they read anything else)
- A first screenshot that shows UI chrome instead of communicating what the app does
Benchmarks vary by category, but a tap-through rate below 8% in a competitive search context usually signals a mismatch between what users searched for and what your listing communicates at a glance. Check what your top competitors show in search results for the same queries. If their icon, name, and first screenshot create a clearer intent signal than yours, that is the gap.
Product page conversion: where promising rankings die quietly
Once a user taps in, the next conversion step runs on the product page itself.
A 28.5% product page conversion rate for Pi Digits means roughly 7 in 10 users who tapped in chose not to download. That is not unusually bad. Most apps convert between 20% and 40% of page visitors. But there is real room to move that number, and the levers are different from keyword work.
What most directly affects product page conversion:
Screenshots. The first two screenshots are visible before any scrolling on mobile. If they do not show the user what they get and why it matters within three seconds, the session ends. Screenshots that show feature lists or UI navigation convert worse than screenshots that lead with the outcome the user came to find.
Ratings. The psychological gap from 2 ratings to 20 ratings is larger than any other range. Below that threshold, users assign uncertainty to the product before reading anything else. Even a 5.0 average on 2 ratings converts worse than a 4.5 average on 50.
Description opening. Most users read 2 sentences, if that. The description does not rescue a weak first impression from screenshots, but a clear opening line can close a hesitant user who almost tapped back.
The 10-minute audit
Open App Store Connect Analytics. Set the window to 30 days. Pull these three numbers:
- Impressions divided by product page views: tap-through rate
- Product page views divided by first-time downloads: page conversion rate
- Total impressions divided by first-time downloads: end-to-end conversion rate
Then ask where the gap is largest.
If tap-through is below 8% and page conversion is above 25%, the problem is before the tap. Your icon, visible subtitle text, or first screenshot is not matching the search query. Fix what users see in results before touching the product page.
If tap-through is above 12% and page conversion is below 15%, the problem is on the product page. Users are interested enough to investigate but not converting. Focus on screenshot order and rating volume before rewriting any metadata.
If both are low, start with tap-through. A product page cannot convert users who never land on it.
The adjustment keyword work alone cannot make
Keyword optimization addresses one question: do the right users see your app? Conversion optimization addresses what happens after they do. Both questions are required.
A rank of #5 with a 6% tap-through rate and a 15% product page conversion produces fewer installs per 1,000 impressions than a rank of #12 with a 16% tap-through and a 30% page conversion. The lower-ranked app installs more often.
Rankings are a prerequisite. They are not the outcome.
Before the next metadata update, pull the three numbers above. They will tell you whether the next round of work should go into keyword research or into the product page. Most indie developers skip this check entirely and wonder why better rankings did not move the download count.
The ranking might not be the problem.
Related: How to Read Your App Store Connect Data to Know If Your ASO Is Actually Working