How to Do ASO for a New iOS App

The central idea: Build ASO into launch preparation so a new app starts with deliberate metadata, realistic keywords, conversion assets and a tracking baseline.

Key facts

• Apple says 70% of App Store visitors use search to discover apps and almost 65% of downloads happen directly after a search; that discovery context matters for “how to do aso for a new ios app.”
• Apple says search relevance can use the app title, subtitle, keywords and primary category, alongside user behavior such as downloads, ratings and reviews.
• The iOS keyword field is limited to 100 characters, while app names and subtitles are limited to 30 characters each.
• Apple's Product Page Optimization can compare up to three treatments against the original page, and a test can run for up to 90 days.

Primary references checked for “how to do aso for a new ios app” include Apple App Store Search, Apple Ads — App Store discovery/search statistics, App Store Connect acquisition analytics.

ASO has two outputs: visibility and conversion

Metadata and keyword work influence whether the app can appear for relevant searches. Creative and positioning influence whether the user downloads after seeing the result. Ratings, reviews, product quality and user behavior connect the two over time.

A mature ASO workflow therefore tracks at least: target keyword set, rank by storefront, search impressions, product-page conversion, screenshot/icon tests, review themes and the date of every material listing change.

The objective is not maximum keyword count. It is a coherent match between query, listing and product.

Step-by-step: How to Do ASO for a New iOS App

1. Build a keyword map before the first submission.

For “how to do aso for a new ios app,” use the U.S. storefront consistently and save the exact query, date and result set. Relevance is the first filter; after that, compare brand strength, ratings and result quality to judge whether the term is realistically contestable.

2. Choose realistic terms for a zero-review app.

For this aso workflow, reproduce the flow from a clean install with no developer-only assumptions. If a reviewer needs a credential, special state or explanation, provide it directly in App Review Information and verify that the credential still works.

3. Create screenshots that answer the same intent as the metadata.

When working on “how to do aso for a new ios app,” treat the listing as part of the product funnel. The promise in the title/subtitle and first screenshots should match the first-use experience. A higher rank for a mismatched promise can actually create worse conversion and retention.

4. Save the launch baseline before changing anything.

Capture the baseline before making the change and annotate the release date. Without a dated before/after state, normal App Store volatility can be mistaken for the effect of your work.

What to measure

Common mistakes

• Launching with generic category keywords only. Confirm the bottleneck with a relevant baseline before acting.
• No baseline rank checks. Confirm the bottleneck with a relevant baseline before acting.
• Screenshots that do not match search intent. Confirm the bottleneck with a relevant baseline before acting.
• Changing metadata before enough data exists. Confirm the bottleneck with a relevant baseline before acting.

Execution plan