Metadata rules
App Store metadata rules: title, subtitle, keywords, and description
How to use each iOS metadata field without wasting character limits, repeating terms, or making the listing read like keyword spam.
Quick answer
- The iOS metadata fields have different jobs: title and subtitle must rank and persuade; keywords expand relevance; description mostly supports conversion.
- Apple documents a 30-character app name, a 30-character subtitle, and a 100-character keyword field.
- Promotional text should not be treated as an ASO keyword field because Apple says it does not affect search ranking.
- Metadata changes need review discipline because irrelevant, trademarked, competitor, offensive, or misleading keywords can cause rejection.
The App Store metadata field map
Good metadata is compact because iOS gives you very little room. The title and subtitle are visible to users and influence relevance. The keyword field is hidden but constrained to 100 characters. The description has more room, but it should not be used as a keyword dump.
The cleanest approach is to assign each field a job before writing copy. Otherwise the same words get repeated across title, subtitle, category, and keyword field, wasting limited relevance space.
| Field | Limit or rule | Best role |
|---|---|---|
| App name | 2 to 30 characters | Brand plus the highest-confidence category or use-case term. |
| Subtitle | Up to 30 characters | Specific value proposition or secondary search intent. |
| Keywords | 100 characters total | Relevant terms not already present in title, subtitle, or category. |
| Promotional text | Visible above description | Fresh launch, seasonal, or offer copy; not search ranking keywords. |
| Description | Long-form product explanation | Conversion, objections, trust, feature clarity, and web search snippets. |
How to write the title and subtitle
The title should still read like a real app name. A title packed with unrelated terms may look desperate, dilute the brand, and run into review risk. Use the title for the most defensible term that describes the app people are actually searching for.
The subtitle should not repeat the title. Apple recommends using the subtitle to explain the app value in more detail and avoid generic claims. In practice, that means concrete user language like "Meal plans and groceries" is stronger than "The best food app."
- Use one clear primary keyword in the title when it fits naturally.
- Use the subtitle for a complementary term or outcome, not a synonym repeated for density.
- Write the title and subtitle as visible copy first, then check keyword coverage second.
- Localize the title and subtitle with native phrasing, especially when category language differs by country.
How to use the 100-character keyword field
Apple says keywords are limited to 100 characters total and terms should be separated by commas with no spaces after commas. Apple also says to avoid repeating words already included in app name, subtitle, or category, plus generic filler, unnecessary plurals, special characters, and irrelevant terms.
A strong keyword field is usually a compressed list of relevant discovery terms. It is not a sentence. It is also not a place to borrow competitor names, protected brands, celebrity names, or misleading terms.
Metadata review checklist before submission
- No title or subtitle exceeds 30 characters.
- The keyword field is 100 characters or less.
- Commas are used efficiently, with no spaces after commas unless part of a phrase.
- No duplicated words from title, subtitle, or category are repeated in the keyword field.
- No competitor names, unauthorized trademarks, celebrity names, or irrelevant terms are present.
- Promotional text is written for conversion, not keyword ranking.
- Each localization has native keyword intent, not a literal English translation.
Sources used
The guide above is based on current Apple developer, App Store Connect, and Apple Ads documentation checked on May 21, 2026.
Product note
A safer way to scale metadata edits
After you have decided the ASO strategy, LocalizeASO can turn it into draft metadata across locales and flag field-limit issues before you push changes to App Store Connect.
- Import keyword sets from CSV, Astro ASO, or manual research.
- Generate title, subtitle, keyword field, and screenshot copy per locale.
- Review field limits and publish-ready localizations before pushing to App Store Connect.
LocalizeASO