Download your lesson workbook · Open the assignment tool →
Your ASO learning objective
Draft an App Store name, subtitle and keyword field that communicate the product and preserve the reasoning behind term placement.
- Step 1Write clear visible metadata
- Step 2Map approved candidates to fields
- Step 3Check overlap, lengths and evidence
Give each field a clear job
Keep the app identity recognizable in the name, and use the subtitle to clarify the core benefit or job. A field-length limit is a constraint, not a target that must always be filled. Start with coherent wording, then examine which approved candidates it covers. Do not sacrifice clarity merely to fit another term.
Apple’s product-page guidance gives the app name and subtitle 30-character limits. The keyword field has a separate compact format. Apple’s search guidance describes a 100-character limit, while the App Store Connect reference specifies 100 bytes; the Workbench displays both and applies a conservative byte check. Verify the final entry in the console, especially for non-ASCII text.
Map approved candidates and inspect overlap
Assign each approved term to its intended field. In the fictional example, “hiking journal” fits the name “Trail Notes: Hiking Journal”; “photo journal” is covered by “Your photo journal”; and “walking diary” contributes words to the keyword field. This is a teaching proposal, not a claim that these are optimal commercial terms.
Use the builder to assemble words from approved candidates assigned to the keyword field. It de-duplicates those words but leaves you in control of the final text. Review overlap with the visible name and subtitle in light of Apple’s guidance. Do not delete a word from a readable subtitle merely because a machine found it elsewhere; reconsider the field roles first.
Validate wording and provenance together
Read the visible copy aloud and compare its promise with the released product. Then inspect lengths, bytes, source references, locale and decision reasons. Keep the earlier wording in draft A and the proposal in B. A clean character count cannot tell you whether a trademark is appropriate, a benefit is accurate or the audience understands the phrase.
Worked example: Trail Notes
This fictional hiking-journal app and its review samples are the teaching project. Treat the example as a reasoning exercise you can adapt to your own evidence.
- Original draftTrail Notes Best Hiking Maps — a title implying unverified superiority and navigation.
- Revised proposalTrail Notes: Hiking Journal, with a supporting subtitle and a separately reviewed keyword field.
- Why it changesThe revised name identifies the product job and avoids unsupported promises. Candidate coverage remains a review aid, not a ranking guarantee.
Your ASO assignment
- Preserve your current App Store metadata in draft A and write the proposal in B. Assign every approved candidate to a field.
- Build the keyword field from approved candidates, then review the resulting words and cross-field overlap manually. Record any changes to the generated draft.
- Resolve every approved-candidate evidence gap and inspect both character and UTF-8 byte counts before previewing a transfer to Listing Studio.
Your handover and assessment criteria
Your work is ready for review when each deliverable below can be understood without a verbal explanation. Include the source or product reference, the decision owner and any unresolved evidence gap. If a reviewer cannot verify a claim, record the missing evidence before treating the proposal as approved.
- Deliverable 1Approved name, subtitle and proposed keyword field
- Deliverable 2Candidate-to-field mapping with placement reasons
- Deliverable 3Length checks, locale and remaining evidence gaps
Check your understanding
All candidate words appear somewhere in the draft. Does that prove the app will rank for the complete phrase?
Read the interpretation
No. The tool checks word presence within fields, not indexing, phrase interpretation, competitive strength or ranking. Keep those questions separate from metadata completeness.
Record your progress
Mark this lesson complete after checking your assignment against the handover criteria. Progress stays in this browser, separately from your tool project.
Sources and further reading
Platform references checked 30 September 2026.
App Store keyword research guide · Check final metadata fields