# ASO Agency — Lesson 12: How to build an ASO keyword map

Outcome: Turn research into a map connecting intent, product evidence, metadata and validation.

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

## Your ASO assignment

1. Build a map for five intent clusters.

Your response:

2. Write a plain-language rationale for the top two priorities.

Your response:

3. Ask a colleague to identify any promise they cannot verify in the app.

Your response:

## Scenario challenge

Hand your map to someone unfamiliar with the app. Ask them to explain the main promise and one rejected term. If they can only repeat a score, improve the rationale before proceeding to metadata production.

Your reasoning:

## Handover

### Candidate history

Supply the original library with provenance and rejections, not just the final winning rows.

Your evidence and decision:

### Approved map

Record intent, evidence, locale, priority and proposed field role for every selected concept.

Your evidence and decision:

### Decision rationale

Explain important inclusions and exclusions, especially attractive terms displaced by relevance or readability.

Your evidence and decision:

### Open questions

Name missing evidence, its owner and whether it blocks the current draft or only future expansion.

Your evidence and decision:

### Version and review

Freeze a dated approved version and define when product or market changes trigger reconsideration.

Your evidence and decision:

## Submission check

- [ ] Each target has both an audience reason and product evidence.
- [ ] The proposed listing communicates a coherent product identity.
- [ ] The map records how contradictory future evidence will be handled.

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

www.asoagency.com