ASO for New App Launches: The 30-Day Metadata Foundation
Most founders treat app store optimization as something they'll "get to after launch." That's backwards. The metadata you submit on day one gets indexed, cached, and ranked immediately — and changing it later costs you the indexing momentum you built, however small, in those first weeks.
This guide gives you a concrete 30-day sequence: what to finalize before your app goes live, what to test in the first two weeks post-launch, and how to iterate based on real signal rather than guesswork. It applies to both the Apple App Store and Google Play, with platform-specific notes where the mechanics differ.
Why the First 30 Days Are Different
When your app first publishes, both stores treat it as a new listing with no behavioral signals — no installs, no ratings, no retention data. Keyword indexing starts immediately, but ranking is heavily influenced by early conversion rates on impressions. The store algorithms essentially ask: "When we show this app, do people install it?"
That means your metadata and creative assets need to be tight on day one, not six weeks later after you've squandered your new-listing window. App store conversion optimization is not a post-launch audit — it's a pre-launch deliverable.
On Google Play, indexing works more like web SEO: text fields are crawled and weighted similar to how Google Search processes page content. On the App Store, Apple's algorithm is more opaque, but keyword field selection remains the primary lever for indexing outside your app name and subtitle.
Pre-Launch: What to Lock In Before You Submit
These elements should be finalized before you submit for review. Changing them after launch restarts your keyword indexing and can trigger an additional review cycle.
App name (title) The single highest-weighted metadata field on both platforms. Include your primary keyword naturally — not as a stuffed suffix. "MyPace: AI Fitness Tracker" outperforms "MyPace" and "MyPace - Fitness, Nutrition, Habits & Community" (too diluted).
Subtitle (App Store) / Short description (Google Play) The subtitle is indexed by Apple and visible on the search results card. Keep it under 30 characters and treat it as a secondary keyword slot, not a tagline.
Keyword field (App Store only) 100 characters, no spaces after commas, no repetition of words already in your title or subtitle. Use the full 100. Don't waste characters on brand names of competitors or terms with zero volume — but also don't optimize only for high-volume terms you can't rank for at launch.
Long description (Google Play) Google indexes this field. Apple does not. For Google Play, treat the first 167 characters (the visible "above the fold" portion) as a conversion copy block, and use the remaining space to naturally integrate supporting keywords. Write for humans first; the indexing follows.
Screenshots and preview video These are the primary conversion driver once someone taps into your listing. On the App Store, approximately 60–70% of users never scroll past the first three screenshots. Lead with your value proposition, not a feature list. For a thorough guide to deep linking and strategic marketing, you'll also want your screenshots to reflect the destination users land on when following a deep link from ads — consistency there improves paid UA conversion as well.
Category selection Choose your primary category based on where your actual competitors rank, not where you ideally want to be positioned. A fitness app that competes with habit trackers might outperform in Health & Fitness vs. Lifestyle — pull the category leaderboards and check before you submit.
| Metadata Field | App Store Indexed? | Google Play Indexed? | Character Limit |
|---|---|---|---|
| App Name / Title | ✅ Yes | ✅ Yes | 30 (iOS) / 50 (GP) |
| Subtitle / Short Description | ✅ Yes | ✅ Yes | 30 (iOS) / 80 (GP) |
| Keyword Field | ✅ Yes | ❌ N/A | 100 (iOS only) |
| Long Description | ❌ No | ✅ Yes | 4,000 |
| Developer Name | ✅ Yes | ✅ Yes | — |
| Screenshots / Video | ❌ Not indexed | ❌ Not indexed | Conversion asset |
Days 1–7 Post-Launch: Establish Your Baseline
Your first priority after going live is not optimization — it's measurement. You cannot iterate without a baseline.
Set up the following immediately:
- App Store Connect Analytics — impressions, product page views, conversion rate (installs ÷ product page views), and source breakdown.
- Google Play Console — store listing conversion report, traffic acquisition report.
- A keyword tracking tool — AppFollow, AppTweak, or MobileAction. Track your 10–15 target keywords daily. Rankings in the first week will look erratic; that's normal.
In this window, do not change your metadata. Let the indexing settle. Changing your keyword field or subtitle in week one throws off your baseline and makes it impossible to attribute any ranking movement to the right variable.
What you should do: start soliciting your first ratings. Reach out directly to beta users, waitlist members, and early adopters. The App Store's prompt (SKStoreReviewRequestAPI) can be triggered after a meaningful action — a completed workout, a delivered order, a finished onboarding flow. Don't trigger it at app open; that's noise. Even a handful of early ratings signals to both stores that real humans are using the app.
Days 8–21: First Iteration Cycle
By day eight you have roughly a week of conversion data. Now you can make your first informed changes.
Screenshot A/B testing Both platforms offer native testing: App Store Connect's Product Page Optimization (PPO) and Google Play's Store Listing Experiments. Run one test at a time, change one element (first screenshot, screenshot order, or preview video presence), and let it run for at least 7–10 days before reading results. In our engagements, the first screenshot frame — specifically whether it leads with a lifestyle visual vs. a UI screenshot — is typically the highest-variance element for new apps.
Keyword refinement Pull your keyword ranking report. Identify terms where you're ranking in positions 11–50 — these are your "near-page-one" opportunities. Swap out keywords where you're ranking below 100 with no movement; that's a signal the term is either too competitive or semantically misaligned.
Description copy for Google Play If your Play Store conversion rate is underperforming relative to your App Store rate (controlling for traffic quality), rewrite the first 167 characters of your long description. This is frequently the culprit on Play — founders copy-paste their App Store promotional text, which isn't written for Google Play's UI or indexing behavior.
Need help building this out? Our mobile app marketing team handles ASO, paid UA, and creative asset development as one integrated engagement — not three separate vendors.
Days 22–30: Close the Loop and Set Your Ongoing Cadence
The goal by day 30 isn't a "finished" ASO setup — that doesn't exist. The goal is a documented baseline, at least one completed experiment, and a repeatable 30-day iteration cadence.
Document the following before the month closes:
- Current conversion rate (store listing views → installs) per platform
- Top 10 ranking keywords and current positions
- Which screenshot variant is winning or leading
- Ratings count and average rating
These become your Month 2 starting point. Treat your ASO like a product sprint: one hypothesis, one change, measure, repeat.
A few things that typically fall off the radar in the first month that you should not skip:
Localization: If your app targets markets beyond English-speaking users, submit localized metadata for at least your top two or three geographies. Both stores rank apps separately by locale, and a US-optimized listing running in Spanish-speaking markets is leaving organic installs on the table.
Reply to your first reviews: Both stores surface developer responses visibly. Responding to your first five to ten reviews — especially any critical ones — signals active support and influences the sentiment of subsequent reviews more than most founders expect.
App category re-evaluation: After 30 days of data, revisit whether your category is serving you. If your top-ranking keywords align more naturally with a different category's ecosystem, a category change is worth testing. It's one of the lower-risk metadata changes because it doesn't reset keyword indexing.
Common First-Launch ASO Mistakes
The same errors show up consistently across new app launches:
- Stuffing the app name with five keywords and a slogan. The algorithm picks up on keyword density, but users see a wall of text and don't tap.
- Identical metadata across platforms. The App Store and Google Play have different indexing rules, different UI presentation, and different user behavior. Your metadata should be platform-specific, not copy-pasted.
- Skipping the keyword field entirely or partially. Every unused character in the iOS keyword field is an indexing opportunity you're surrendering.
- Setting and forgetting screenshots. Creative assets should be tested, not assumed. First-impression conversion is the biggest lever on organic installs and also improves paid UA efficiency.
- Optimizing for volume over reachability. New apps cannot rank for "fitness app" or "food delivery" — the competition depth is too steep. Target mid-tail terms where you can realistically reach page one in 60–90 days, then build outward.
FAQ
How long does it take for ASO changes to show ranking impact?
On the App Store, keyword changes typically reflect in rankings within 24–72 hours. Google Play indexing can take three to seven days. Conversion-driven ranking improvements (from better screenshots or copy) take longer to manifest because the algorithm needs sufficient impression volume to register the conversion rate shift.
Should I optimize for the App Store and Google Play differently?
Yes. On the App Store, the keyword field and app name are your primary indexing levers; the description is not indexed. On Google Play, the description is crawled and weighted, making it a significant optimization surface. Creative asset behavior also differs — Google Play users interact with screenshots differently than App Store users, so test them independently.
How many keywords should I track for a new app?
Start with 15–25 keywords across three priority tiers: five core high-intent terms (even if you rank low), ten mid-tail terms where you have a realistic shot at page one, and five brand-adjacent or niche terms where competition is thin. Expand the list as you accumulate ranking data.
When should I start paid user acquisition alongside ASO?
Running Apple Search Ads on your core keywords from day one is generally worth it — even at a small budget — because installs from Search Ads contribute to keyword ranking velocity. This is one of the few cases where paid and organic ASO directly reinforce each other. For Meta or TikTok UA, wait until you have a converting store listing; sending paid traffic to an unoptimized product page just burns budget.
Does the number of ratings affect keyword rankings?
Ratings volume and average rating are confirmed ranking factors on both platforms. They affect overall app ranking more than individual keyword positions, but a significant rating deficit relative to category competitors creates a ceiling on how high you can rank for competitive terms. Prioritize getting your first 25–50 ratings in the first 30 days.
Can I change my app name after launch without hurting rankings?
Yes, but do it carefully. Changing the app name resets keyword indexing for the words you remove. If a term in your current name has built any ranking momentum, removing it costs you that position. Make name changes deliberately and only when the keyword case is clear — not for rebranding reasons alone.
If you're building your ASO foundation from scratch or auditing a listing that hasn't been touched since launch, the sequenced approach above is where to start. It's not complicated — but it does require doing things in the right order and being disciplined about what you change and when.
If you'd rather have a team that's shipped 15+ apps handle the metadata strategy, keyword research, creative testing, and UA alongside your organic ASO, talk to us at Semnexus. Or skip the contact form and book a 30-minute call directly — we'll tell you exactly where your listing is leaving installs on the table.
