Optimising an iOS App Store Listing
The App Store gives you a small set of fields, and Apple decides how much each one counts in search. The name, subtitle and a hidden keyword field do most of the work for discovery; the screenshots, preview, rating and privacy details decide whether people install.
Some fields only change when you submit a new version, while others can be edited any day. This guide explains how the pieces fit together on iOS specifically, how to plan the three search fields as a single set of words, and how to use Apple's own tools to test and promote the listing.
What each iOS field does
Apple does not publish its ranking formula, so the notes below reflect Apple's own guidance plus what the ASO community broadly agrees on. Character limits change occasionally; confirm them in App Store Connect before you write.
| Field | Visible to users? | Used for search? | Change needs a new version? |
|---|---|---|---|
| App name | Yes, everywhere | Yes, strongly | Yes |
| Subtitle | Yes, under the name | Yes | Yes |
| Keyword field | No | Yes | Yes |
| Promotional text | Yes, at the top of the description | Not generally treated as a search field | No, edit any time |
| Description | Yes | Widely believed to have little or no effect on iOS search | Yes |
| Screenshots and app previews | Yes, and shown in search results | No, but they drive conversion | Yes, submitted with a version |
| In-app events | Yes, on the page and in search | Events can appear in search results | No, submitted separately for review |
| Category | Yes | Mainly for charts and browsing | Usually with a version |
The practical consequence is that the name, subtitle and keyword field form a single pool of search words, and every word should appear in only one of them. The description is written for people, not for the algorithm.
The fix, step by step
Step 1
Collect the terms iPhone users search
Type the start of likely terms into the App Store search box on an iPhone and note the suggestions, which reflect what people actually search. Look at the names and subtitles of the apps ranking for each term. If you run Apple Ads, the search terms report and keyword recommendations add real query data. Build a list of perhaps thirty to fifty terms, marked by how relevant each is to your app and how crowded the results look.
Step 2
Plan name, subtitle and keywords as one set
Put your brand and the single most important descriptive term in the name, a clear benefit plus one or two secondary terms in the subtitle, and the remaining useful single words in the keyword field. Check that no word appears in more than one of the three. Read the name and subtitle aloud as a stranger would: they must still describe the app plainly, because they appear in search results and they drive taps as well as rankings.
Step 3
Write the keyword field without waste
Enter single words separated by commas with no spaces, such as budget,expense,spending,savings,bills.
Leave out words already in the name or subtitle, your company name, the word app and the category name,
which Apple's guidance says are unnecessary. Avoid competitor brand names and terms unrelated to the
app, because they can lead App Review to reject the version. Use the full allowance shown in App Store
Connect for each localisation you support.
Step 4
Line up the release-bound assets
Because the name, subtitle, keywords, description and screenshots only change with a new version, gather them into one checklist for your next release. Update the screenshots to match the current interface, check that the first three frames tell the main benefit, and review the App Privacy answers in App Store Connect against what the app and its third-party SDKs actually collect. Inaccurate privacy details can cause rejections and mislead visitors who read the labels.
Step 5
Use promotional text and in-app events
Promotional text sits at the top of the description and can be changed without a release, so use it for timely messages such as a new feature, a seasonal offer or an award. If the app has time-bound activities, such as a challenge, a live session or a major content drop, create an in-app event in App Store Connect with its own image, name and short description. Events are reviewed separately and can appear on your product page and in search.
Step 6
Test icons and screenshots
Create a Product Page Optimization test in App Store Connect with one treatment that changes a single idea, such as a new first screenshot or an alternative icon. Alternative icons must be included in the app binary before you can test them. Let the test run until App Store Connect shows a confident result for your traffic, apply the winner to your default page, and record what you tested so you do not repeat it later.
Step 7
Check rankings after the release
Once the version is live, search your target terms on an iPhone set to the right country and note where you appear, then repeat weekly for a month. Watch App Analytics for impressions and conversion from App Store Search. Rankings often move for several days after metadata changes, so avoid judging on day one. Keep terms that bring impressions, swap out keyword field words that never do, and plan those swaps into the next version.
Before and after: a worked example
Harbourcast, a fictional sailing weather app, had this metadata:
Name: Harbourcast
Subtitle: The best app for sailors
Keywords: harbourcast,sailing app,weather app,best,wind,sailing,tides,marine weather,forecastProblems: the name says nothing about what the app does; "best" and "app" are wasted words; the brand is repeated in the keyword field; "sailing" appears twice and spaces are used inside phrases; the subtitle makes a vague claim rather than stating a benefit.
Name: Harbourcast: Sailing Weather
Subtitle: Wind, tide and swell forecasts
Keywords: marine,boat,yacht,gusts,knots,waves,harbour,coastal,passage,dinghy,kayak,surf,sea,portAfter the change, the name and subtitle state what the app is for, words are spread across the three fields without repeats, and the keyword field carries related single words that can combine with "sailing", "weather", "wind" and "tide". Whether each term is worth keeping is then decided by the rankings check in step 7, not by guesswork.
Custom product pages and Apple Ads
Custom product pages are extra versions of your product page, each with its own screenshots, app previews and promotional text, and its own link. They let you match the page to the reason someone arrived: a campaign about a meal-planning feature can lead to a page that shows meal planning first. Apple has expanded where custom product pages can be used over time, including options for linking them to keywords, so check App Store Connect for what your account currently offers.
Apple Ads (formerly Apple Search Ads) places your app at the top of App Store search results for terms you bid on. Even with a small budget it is useful for ASO research, because the search terms report shows real queries that led to taps and installs. Terms that convert well in ads are good candidates for your organic name, subtitle and keyword field, and you can point ad groups at relevant custom product pages.
Getting metadata through App Review
Metadata is reviewed with every version, and common rejections are avoidable:
- Trademarks and competitor names in the name, subtitle or keyword field.
- Prices or claims in the name or subtitle, such as "Free" or "Number one", which Apple's guidelines discourage in these fields.
- Screenshots that do not show the app, such as only marketing art or images of a different device's interface.
- Keyword stuffing, including long lists of unrelated terms or popular app names.
- Privacy details that do not match the app, including data collected by analytics or advertising SDKs you forgot about.
- Mentions of other platforms, such as "also on Android", in the listing text.
If metadata alone is rejected, App Store Connect usually lets you fix and resubmit the metadata without building a new binary, which is quicker than a full resubmission.
Planning a release cadence for ASO
Because the main search fields are tied to versions, teams that ship rarely get few chances to improve them. A few habits help:
- Keep a running ASO checklist in the same tracker as the release notes, so metadata changes are prepared before the build is ready.
- Change the name or subtitle in a release separate from a big keyword field rewrite when you can, so you can tell which change moved rankings.
- Use promotional text and in-app events between releases for anything seasonal, since they do not wait for a version.
- Review every localisation you support at each release, not just English (UK) or English (US). Each has its own name, subtitle and keyword field; the localisation guide covers this in depth.
For the Android side of the same app, the approach is quite different because Google Play has no keyword field and reads your descriptions. The App Audit Guide covers both stores side by side.
1. Does the App Store description affect search ranking?
Apple does not say exactly which fields count, but the widely shared experience of ASO practitioners is that the long description has little or no effect on iOS search, unlike on Google Play. The name, subtitle and keyword field are the fields that clearly matter. Write the description for people who have already opened the page: say who the app is for, what it does and why it is better, and put the most important points in the first few lines.
2. Should I use spaces or phrases in the iOS keyword field?
Use single words separated by commas without spaces after the commas. Spaces use up characters without adding anything, and the store can generally combine words from the name, subtitle and keyword field into phrases for you. A phrase is only worth entering if its words mean something different together than apart, which is rare. Check the current character allowance in App Store Connect and try to use it fully for each localisation you support.
3. Can I change my app name without releasing a new version?
Not normally. The app name, subtitle, keyword field, description and screenshots are version-level details on the App Store, so they go live when a new version is approved and released. Promotional text is the main exception: you can edit it at any time. In-app events are also managed separately from versions. Plan name and keyword changes into your release schedule, and use promotional text and events for anything that cannot wait.
4. Should I put my competitors' names in the keyword field?
No. Apple's guidelines do not allow trademarked terms, other app names or company names you do not own in your metadata, and App Review can reject the version for it. Even when such a version slips through, it can later be rejected or the terms can draw complaints from the trademark owner. If you want to appear when people search for a competitor, bidding on their name through Apple Ads is the permitted route, subject to Apple's advertising policies.
5. What is the difference between Product Page Optimization and custom product pages?
Product Page Optimization tests alternatives to your default product page on a share of your ordinary visitors, to find out which icon, screenshots or preview perform best. Custom product pages are separate versions with their own links, used to show tailored content to specific audiences such as visitors from an advert. One is for finding a better default page; the other is for serving different pages to different groups. Many teams use both.
6. How long do App Store ranking changes take after a metadata update?
There is no fixed time. Rankings for new terms often start to shift within a few days of the version going live, but they can keep moving for a couple of weeks as the store gathers data on how searchers respond to your listing. Check rankings on an iPhone in the relevant country regularly for about a month, and compare impressions from App Store Search in App Analytics, before deciding whether a change worked.
7. Do App Privacy details affect downloads?
They can. The privacy details appear on the product page, and people who care about data collection do read them, particularly for apps in sensitive areas such as health or finance. More importantly, they must be accurate: Apple requires you to declare the data your app and its third-party SDKs collect. Review them at each release, remove SDKs you no longer need, and make sure the listing and the privacy policy tell the same story.
The App Store Audit checks your iOS and Google Play listings for keyword visibility, screenshot effectiveness, review velocity and rating, and conversion from impression to install, and benchmarks you against direct competitors.
Open App Store Audit Fixes →