About 12 minutes reading · 23 minutes practice
You will produce: A seed library with provenance, product support, intent and explicit status.
Collect by source and meaning
Seed collection is discovery work. Include product capabilities, user jobs, problems, outcomes, category language and customer expressions. Keep the source beside each candidate. Separate terms you observed from terms you brainstormed or generated with assistance. An attractive phrase deserves investigation, but its existence in a spreadsheet does not establish demand or relevance.
Normalize without erasing intent
Trim formatting and remove exact duplicates while preserving meaningful variants. “Walking diary” and “walk tracker” may overlap linguistically but imply different expectations. Record language and storefront before normalization. Do not aggressively merge singulars, plurals or spelling variants based on an assumed indexing rule; preserve the research evidence and make allocation decisions later.
Make exclusions part of the library
An exclusion list prevents rejected ideas from returning every meeting. Record why a term is unsuitable: unsupported feature, wrong audience, ambiguous meaning or unresolved brand concern. Rejection is a strategic result, not wasted research. Keep the original candidate and rationale so new product capabilities can trigger a deliberate reconsideration rather than a forgotten assumption.
Quick check · pick a response
Make the call before you scroll.
Go deeper: practical decisions and tradeoffs
Collect concepts before forcing field formatting
A seed library is a research inventory, not the final iOS keyword field. Keep natural phrases such as walking diary, hiking memories and private journal intact while you investigate meaning. Record the source type: interview, support conversation, product terminology, competitor listing or an analyst hypothesis. Different sources establish different things. A customer phrase can support language relevance; it does not independently establish demand. Keeping concepts intact makes it easier to understand intent before later splitting or allocating terms for a specific store.
Normalize without destroying useful distinctions
Create a normalized comparison form for case, whitespace and obvious duplicates, but preserve the original phrase. Do not merge different meanings merely because their strings look similar. “Trail log” and “training log” may serve distinct jobs. Store the locale with each candidate and avoid combining translated words into one language-neutral row. If two sources support the same concept, link both to a canonical research entry instead of copying rows that inflate the apparent breadth of the library. Version the library so rejected ideas can be traced later.
Use status as a decision history
Give each candidate a status such as new, needs intent review, shortlisted or rejected. A rejection should include a reason and the evidence that would justify reopening it. “Unsupported navigation function” is useful; “bad keyword” is not. Assign the next research action to uncertain candidates. This turns a large list into a manageable queue. Before handing it to a copywriter, distinguish researched candidates from brainstorms, because attractive unverified terms often reappear in drafts when status is unclear.
Platform references for this work: Apple — App Store search · Google Play — Metadata policy
Your turn · two-minute exercise
Try the scenario. Make your case.
You receive 2,000 tool-exported terms without locale or provenance. Design a triage process that first restores context, then deduplicates and reviews intent. Explain why immediately pasting the highest-score terms into metadata would skip necessary decisions.
Autosaved on this browser. Your work is private and does not sync between devices.
Your step-by-step procedure
Create columns for candidate, locale, source, intent, supporting feature and status.
Import customer language and product terminology before broad brainstorming.
Deduplicate formatting variants while preserving meaningful query differences.
Add explicit exclusions and questions for unresolved candidates.
Completed example · use the reasoning
A research-ready seed library
Gabriel’s take: A long keyword list is not research. Sometimes it is just a long list.
Constructed teaching material, not a client result. Adapt the evidence and product facts before using it for your app.
Walking journal
Interview phrase; supported; investigate demand
Trip diary
Review phrase; supported; investigate intent
GPS navigation
Competitor phrase; unsupported; exclude
Photo log
Team idea; plausible; needs user-language evidence.
Your turn · repair the decision
Make the call. Then compare.
Add “offline maps” to the library without pretending it is a valid target.
Autosaved on this browser. Your work is private and does not sync between devices.
Explore the supporting case and interpretation
Trail Notes collects “walk diary,” “hiking journal,” “route planner” and “private travel memories.” The route-planner candidate stays in the sheet with an exclusion because planning is unsupported. Private travel memories is marked unvalidated language rather than discarded merely for lacking a score. The library now records what the team knows, what it suspects and what it has ruled out.
Candidate: Walking diary
Origin: Interview language
Status: Inspect local results
Candidate: Hiking memories
Origin: Product benefit workshop
Status: Validate user wording
Candidate: Offline navigation
Origin: Competitor observation
Status: Reject: unsupported function
A good seed library can be small. Thirty traceable entries with clear next actions are more useful than several thousand terms collected without context. In the example, walking diary has language evidence but still needs search inspection. Hiking memories has product relevance but weaker customer-language evidence. Offline navigation is retained in the rejection history to prevent repeated discussion. None of these statuses claims search volume, difficulty or a guaranteed ranking opportunity.
Build a handover someone can use
Original candidates
Preserve the unedited phrase, locale and source reference so the origin is recoverable.
Normalized index
Link duplicate expressions to a canonical concept while retaining meaningful variants and sources.
Decision status
Label researched, unresearched and rejected entries explicitly, with reasons and review dates.
Research queue
Assign a concrete next check to each unresolved candidate, such as local result inspection or product verification.
Handoff boundary
State that the library is a research input and identify the separate approved shortlist for drafting.
Your ASO assignment
Use your own app and evidence, or work through the teaching case. Keep your observations separate from assumptions and explain the reasoning behind your decisions.
Build something · track your work
Your assignment checklist
Tick each item after you have produced the work. Reading it does not count. The strategy deck will survive.
0 of 3 tasks checked.
Autosaved on this browser. Your work is private and does not sync between devices. Course completion is recorded separately.
Assess your work
- Every candidate has a source or is labeled as a brainstorm.
- The sheet preserves market and language context.
- Excluded terms include reasons that another analyst can evaluate.
Common mistakes to catch
- Presenting AI-generated phrases as observed customer searches.
- Deleting rejected terms without retaining the rationale.
Sources and further reading
Platform references reviewed 29 September 2026. These sources support platform capabilities and constraints; the teaching frameworks, assignments and illustrative cases are original course material.
- Apple — App Store search — Search presentation, relevant keywords and metadata guidance.
- Google Play — Metadata policy — Accurate, relevant metadata and prohibited presentation.
Your ASO lesson notes
Use this space for your assignment, evidence and handover. Your notes save automatically in this browser. Download a copy to take with you.
Notes stay on this device and are not submitted to ASO Agency.
Complete your assignment with the ASO Keyword Research Workbench.
Loading your progress…
Progress is saved only in this browser. It does not sync across devices. Mark a lesson complete after doing its exercise.