# ASO Agency — Lesson 16: ASO metadata strategy: allocate keywords across fields

Outcome: Translate a keyword portfolio into readable field roles for each store.

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

## Your ASO assignment

1. Create separate iOS and Play field-role tables.

Your response:

2. Draft one coherent set of fields for your primary market.

Your response:

3. Record three wording tradeoffs and their reasons.

Your response:

## Scenario challenge

A reviewer adds journal to the iOS name after the keyword field was approved. Identify the dependent checks and explain why reviewing only the edited field can leave avoidable duplication elsewhere.

Your reasoning:

## Handover

### Field plan

Name the store, locale and communication role of each field before giving the final strings.

Your evidence and decision:

### Approved strings

Preserve exact text, punctuation and version so counts and reviews refer to the same proposal.

Your evidence and decision:

### Coverage matrix

Show where important concepts appear and why intentional exclusions or repetitions remain.

Your evidence and decision:

### Validation

Record field counts, current platform reference and unresolved console checks.

Your evidence and decision:

### Change implications

Explain which other fields need rechecking if a visible name or subtitle changes.

Your evidence and decision:

## Submission check

- [ ] Each field serves a clear communication or discovery role.
- [ ] The draft preserves necessary qualifiers.
- [ ] Excluded candidates remain documented instead of being forced into copy.

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

www.asoagency.com