# ASO Agency — Lesson 21: iOS keyword field optimization: selection and QA

Outcome: Construct a reviewed keyword field while understanding counting and overlap limitations.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Build a field from your approved portfolio and save the before/after versions.

Your response:

2. Explain three inclusion or exclusion decisions.

Your response:

3. Test an accented word and record both counts.

Your response:

## Scenario challenge

Calculate UTF-8 bytes for cafe, café and 日記: 4, 5 and 6 respectively. Explain why the last two cannot be validated by assuming one byte per visible character. Then audit diary,logbook against the approved name and subtitle.

Your reasoning:

## Handover

### Original list

Include every candidate with source and status, including rejected and unresolved entries.

Your evidence and decision:

### Visible metadata

Attach the approved name and subtitle because they determine important overlap checks.

Your evidence and decision:

### Keyword proposal

Supply the exact comma-separated string, locale, byte count and console-validation status.

Your evidence and decision:

### Rationale

Explain major inclusions and exclusions with product or research evidence, not only formatting rules.

Your evidence and decision:

### Evidence gaps

Name the next check for held terms and whether it blocks release; record reviewer and review date.

Your evidence and decision:

## Submission check

- [ ] The final entries describe supported use cases.
- [ ] Byte and character differences are understood and console validation is planned.
- [ ] Tool suggestions remain distinguishable from researched strategic decisions.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com