Guide · 8 min read
ASO With Zero Reviews: How to Rank a New App When Nobody Knows It Exists
Every new app starts from the same position: zero installs, zero reviews, zero ranking history — and an algorithm that weighs all three. The App Store doesn't reward potential; it rewards evidence of demand. The good news is that the same algorithm weighting that disadvantages new apps is also more sensitive to small signals at launch than at any other point in an app's lifecycle. Getting that window right is the entire cold-start problem.
Target keywords where zero reviews is not a death sentence
The biggest mistake new apps make at launch is going after primary, short keywords immediately — phrases like "meditation" or "budget tracker" where every incumbent has thousands of reviews and years of ranking history. Competing there with zero reviews produces page-5 placement and near-zero impressions, which means you can't build install velocity even if every other signal is right. The structural advantage available to new apps is in the long tail: 3–5 word phrases where the total search volume is lower but the competition pool is thin enough that 15 installs creates a visible relative signal.
Long-tail phrases like "anxiety breathing exercise timer," "meal log app no subscription," or "GTD task app Apple Watch complication" are not targeted by apps with 100,000 reviews because the traffic volume doesn't justify their attention. But for a new app, ranking top-3 on five such phrases generates real impressions from users whose search intent matches precisely what your app does. Conversion rates on long-tail queries are higher than on head terms for exactly this reason: the user already described what they want and you answered it. See the long-tail ASO keyword strategy guide for the combination method — function + format + audience + constraint — that generates candidate phrases systematically.
The practical test for whether a keyword phrase is worth targeting at launch: type it into App Store search and note the autocomplete and first five results. If all five apps have four-figure review counts, the phrase is too competitive for a cold start. If three of the five are apps you haven't heard of with review counts under 200, it's worth targeting. This observation takes 30 seconds per phrase and is more reliable than any keyword tool at the low-volume end of the curve, where tool data is thin and direct observation is the only credible signal.
App Store subtitle: the 30-character field that matters most before you have reviews
Your 30-character subtitle is the highest-ROI metadata field for a new app with no ranking authority. Apple indexes it for search and users read it in results — which means it must do two jobs simultaneously: match a phrase users actually search, and read naturally enough that users click through. The subtitle is not the place for a brand tagline; it's the place for a compressed statement of your app's specific function and differentiating constraint. "Budget tracker, no subscription" outperforms "Financial freedom starts here" on every metric that matters at launch.
The 100-character keyword field should not repeat any words already in the title or subtitle — Apple indexes those fields separately, and duplication wastes characters that could carry additional keyword surface. Use the keyword field for vocabulary variations, alternate category terms, and adjacent queries that would read awkwardly in a public-facing field. No spaces between keywords (commas only), no articles or prepositions, no competitor brand names. Every character is search-indexed real estate. For the exact interaction between subtitle, promotional text, and keyword field — including which field gets indexed where and how changes affect ranking velocity — see the subtitle vs promotional text guide.
Conversion rate is a ranking signal — and screenshots are your only social proof before reviews land
Conversion rate — the share of App Store page visits that result in an install — is a direct input to Apple's ranking algorithm. For new apps without reviews, download history, or editorial features, it's the primary quality signal the algorithm has access to. A screenshot set that converts 10% of listing visitors tells Apple that users who encountered your app found it credible. A set that converts 3% from the same impression pool tells it something different. Before reviews exist, the argument for why a user should install lives entirely in your screenshots.
The first screenshot carries the most weight because it's visible in search results before a user taps your listing. For a new app with no star rating displayed, the first screenshot must establish benefit without social proof to lean on. Lead with a specific functional outcome ("Every expense logged in under 10 seconds") rather than a feature category label ("Expense Tracking"). One concrete claim beats any feature noun at converting a browse into a tap. Export at the correct dimensions for each device class before submitting — the App Store screenshot sizes guide has every required resolution — and preview the full set at actual search-row display size in the screenshot editor before submitting.
The 72-hour launch burst: why your first installs are the most valuable you'll ever get
The App Store algorithm gives disproportionate ranking weight to install velocity in the first days after a new listing appears. The "New" sections in category charts exist specifically to surface this velocity signal — and the window is narrow. The first 72 hours after launch carry more ranking influence than any equivalent 72-hour period later in the app's lifetime. A concentrated burst of 200 installs on launch day produces a measurably larger ranking effect than 200 installs spread evenly across the following six weeks.
This makes your launch-day audience — email subscribers, community members, friends who agreed to install, communities where you've announced — the most strategically important install source you'll ever have. Coordinate them to install within a 24-hour window, not spread across a week. Users who install in this burst are also your best candidates for early reviews: they came with intent and are most likely to experience the core loop quickly enough to be prompted. See the indie app launch checklist for the 6-week pre-launch sequence for building this coordinated audience before go-live.
Zero to 30 reviews in 30 days: the sequenced approach
Apple limits apps to three review prompts per device per year using SKStoreReviewController. For a new app, those three opportunities are finite and irreplaceable — spending one before a user has experienced real value is unrecoverable. Fire the first prompt after the core-loop completion the app exists for: not at onboarding, not on third open — after they've logged the first workout, closed the first budget cycle, or exported the first design. That moment of demonstrated value is the highest-probability trigger for a 5-star response.
Reply to every review you receive in the first 30 days, including 1-star ones. Replies are publicly visible on the App Store listing and signal developer engagement to both users and the algorithm. A thoughtful, specific response to a critical review regularly generates follow-up positive reviews from users who notice the responsiveness — the social proof of visible accountability is real. Once in-app prompts are firing correctly, supplement with a direct review link (using the itms-apps:// review URL format) in your launch email. Removing one step in the path from intent to completed review measurably increases review volume. For category-specific prompt timing benchmarks, see the review prompt timing guide.
Cold-start on Google Play: retain first, rank second
Google Play's cold-start mechanics differ from the App Store in one critical respect: the algorithm weighs Day-3 and Day-7 retention much earlier and more aggressively for new listings. An app that gets 500 installs and retains 3% at Day 7 triggers a negative quality signal that can actively suppress ranking — more aggressively than simply having fewer installs. For Play Store cold starts, getting the right users (ones who stay) matters more than getting many users quickly. Retention-oriented onboarding is more urgent at launch on Play than on iOS.
Unlike the App Store, Google Play has no keyword field. The short description (80 characters) and the long description (4,000 characters) carry the full indexing load. Write the long description to answer the queries users type into Play search as complete, natural sentences rather than keyword lists — semantic interpretation applies to Play Store search in 2026. The "Similar apps" shelf on competitor product pages is also a Day-1 discovery channel that requires no paid promotion: apps with overlapping category, description vocabulary, and audience signals appear there from the moment a listing is live. For visual asset specifications, the Play Store feature graphic size guide covers the 1024×500 banner format with design guidance for apps without established brand recognition.
Cold starts are won in metadata and the first 72 hours
Everything above costs nothing except time: picking the right long-tail keywords, writing a subtitle that functions as a search phrase, and coordinating your launch audience to install within the same window. The installs needed to bootstrap the algorithm out of cold-start territory are almost always already in your network — the constraint is coordination and timing, not volume.
What strong screenshots add is conversion rate leverage on every impression those first installs generate. A first screenshot that converts 10% of listing visitors instead of 3% multiplies the ranking signal from each coordinated install. Preview your screenshot at actual search-row display size in the editor before submitting — what reads clearly at design canvas resolution often loses its central claim at the 150px width of an App Store search row.
Preview your screenshots at App Store display size →
Frequently asked questions
does having zero reviews hurt your app store ranking
Yes — review count and rating are both ranking signals. Their weight is heaviest for high-volume head keywords where every ranked app has four-figure review counts. The practical response is to target keywords where your zero reviews don't represent a structural disadvantage relative to the apps already ranking for that phrase, then run a sequenced review acquisition campaign in the first 30 days to build review velocity as quickly as possible.
how long does it take for a new app to appear in app store search
A new app typically appears in App Store search within 24–72 hours of approval. The initial ranking will be low for competitive keywords, but the "New" category charts surface velocity rather than cumulative signals and can show your app within hours of approval. Keyword field and subtitle indexing happen in this same window — the metadata submitted at launch is searchable from day one.
how many downloads do you need to rank on the app store
There is no published minimum. The App Store ranks apps relative to other apps targeting the same keyword — so the download count that matters is relative, not absolute. For long-tail keywords (3–5 word phrases), 15–50 installs from engaged users can produce top-5 ranking. For primary head keywords like "meditation" or "photo editor," the same 50 installs is invisible against apps with millions of cumulative downloads.
how to get your first app store reviews fast
The highest-converting method is the native SKStoreReviewController prompt fired after the first core-loop completion — not at onboarding. Supplement with direct review deep-links (<code>itms-apps://</code> format) in your launch email, and reply to every early review to signal engagement. Aim for 30 reviews in the first 30 days as the minimum threshold for meaningful ranking credibility on competitive keywords.
can a new app rank against established apps with thousands of reviews
On primary head keywords — no, not without paid install campaigns. On long-tail, specific-intent keywords — yes, regularly. Apps with thousands of reviews don't target 3–5 word phrases where search volume is low, because the volume doesn't justify their ASO attention. That gap is the structural opening available to new apps: specific-function, constrained-audience phrases where the ranking competition consists of other small apps, not category leaders with dominant review counts.