Troubleshooting

Why your app isn't showing up in App Store search (and how to actually check)

"My app doesn't show up in search" is six different problems wearing one coat. Each has a different fix, and the wrong fix wastes a release cycle: devs rewrite descriptions that search never reads, chase ratings for terms they're not indexed under, and wait for metadata changes they checked too early. Work through the six causes in order. Each one ends with the exact check that confirms or clears it.

1. You're outside the top 200 — which means you don't rank for that term at all

App Store search returns a finite result set — roughly 200 apps per term. Position 201 isn't "low"; it's nonexistent. No amount of scrolling by a motivated user will ever reach you, because the list ends. This is the first thing to establish, because it splits the problem in two: apps ranked 50–200 have a position problem (fixable with incremental gains), while apps outside the 200 have an indexing problem (cause #2), and the treatments are completely different.

Check it: search your target term and find your app's exact position — or confirm it's absent from all ~200 results. If you're at #87, skip to cause #4. If you're absent, the next cause is yours.

2. You're not indexed for that word

Apple builds its search index from a short list of fields: your app name, your subtitle, and your 100-character keyword field — plus secondary signals like category and in-app purchase names. Your description is not indexed for search. Neither are your screenshots' captions or your promotional text. If the phrase you want to rank for doesn't appear (as words Apple can combine) across your name, subtitle and keyword field, you are not in the index for it, and no rating count on earth will put you there — ratings only sort apps that are already indexed (see cause #4 for the proof). Two mechanics matter here:

Check it: write out your name + subtitle + keyword field. Circle every target term whose words don't fully appear in that combined text. Those terms are unwinnable until the metadata changes — no other cause on this page matters for them.

3. Exact-match names are beating you structurally

When an app's name is the search term, it starts with a relevance advantage that popularity has to work hard to overcome. This is measurable, not folklore. On October 21, 2026, an app named Podcast App (309,545 ratings) ranked #2 for "podcasts", ahead of Spotify (42,671,055 ratings) at #3 — an app with 0.7% of the giant's ratings winning on name alone. The same week, an app actually called Habit Tracker held #1 for 8 of 10 habit-category keywords we measured. If your term's top 5 is full of apps named after the term, you're not losing a popularity contest; you're losing a naming contest that was decided before ratings were counted.

Check it: look at the top 5 names for your term. If three or more are near-exact matches for the query, either get the term's core word into your name or subtitle, or pick a longer-tail variant where the exact-match slots are empty.

4. Ratings gravity — real, but gated

Among apps that are indexed and relevant, Apple sorts heavily by ratings count, rating velocity and tap/download conversion. This is why incumbents are sticky. But gravity has a gate: relevance first. In our October 21 habit-category study, Finch — 766,051 ratings, the most of any app measured — didn't appear in the top 200 at all for 6 of 10 habit keywords, because its metadata doesn't claim those terms. Meanwhile HabitKit, with 2,494 ratings, held #2 for "habit tracker". The practical read: compare yourself only against the apps in your term's top 10. The number that matters is the weakest top-10 incumbent's ratings count — that's the gravity bar you actually have to clear, and on mid-tail terms it is often a few hundred ratings, not millions.

Check it: list the ratings counts of your term's current top 10. If the #10 app has fewer ratings than you, gravity isn't your problem — relevance is (causes #2–#3). If the floor is 50× your count, the term is defended; attack a softer one (cause #5).

5. You're fighting in the wrong result set

Rankings aren't computed inside your category — they're computed per search term, against every app claiming that term, including giants from adjacent categories (in travel search, a general journaling app with 118,643 ratings competes directly with travel journals). Two consequences. First, your category page position tells you nothing about your search position. Second, terms differ wildly in how defended they are: on October 21, the top 10 for "streak tracker" included apps with 6 and 53 ratings — Apple also gives new and small apps test impressions on mid-tail terms, so those result sets churn and admit newcomers in a way head terms never do. The strategic move isn't to push harder on a defended term; it's to find the adjacent term whose top 10 is held by apps your size.

Check it: for each candidate term, note how many of the top 10 have under 1,000 ratings. Terms with two or more are open doors. Terms with zero are fortresses — park them and revisit after your ratings grow.

6. You changed your metadata yesterday — and checked this morning

Metadata changes are not instant. A new version's name, subtitle and keyword field have to be indexed, and rank movement after an indexing update plays out over days, not minutes. Checking two hours after a release and concluding "it didn't work" is the most common self-inflicted wound in ASO. The related trap: checking the wrong storefront. Rankings are per-storefront and per-language; your US result says nothing about Germany, and a subtitle localized for one market doesn't index in another. Give a change at least 48 hours, then measure in the storefront you actually targeted — and keep measuring weekly, because the honest answer to "did it work?" is a trend, not a single reading.

Check it: note the date of your last metadata change and re-check the same terms after 48 hours in the target storefront. If positions haven't moved at all, the cause is back at #2 or #3 — the change didn't alter what you're indexed for.

Sources. Rank and ratings figures (Spotify, Podcast App, Finch, HabitKit, the "streak tracker" top 10) were pulled live from Apple's public iTunes Search API on October 21, 2026, US storefront; the full habit dataset is published in our companion study. Indexing mechanics (indexed fields, keyword-field length, stemming) reflect Apple's documented App Store search model. Ranks are snapshots and fluctuate.

Run the checks in this article — free

Every "check it" box above is the same operation: your app, your keyword, your exact position in the top 200 — plus the top 5 apps outranking you. RankBlob does it in about 10 seconds, in your browser, with no account and no API key.

Check my ranks — free
Sources & independence
RankBlob · Instant App Store keyword rank checking for indie developers · Data: Apple iTunes Search API (public)
RankBlob is not affiliated with Apple Inc.