How the keyword simulator works
A walkthrough of every column, number, and action in the Keyword Coverage Simulator, written for people already inside the product who want to understand what they're looking at.
The layout
A toolbar at the top holds the drafts menu and Save. Under it, three headline numbers. Below those, your listing on the left and the keyword coverage table on the right. Whichever draft is open drives every number you see.

Live listing
Your current App Store / Play Store metadata for the active country. It's the baseline every draft is compared against, and each field shows its live value under the input with a Restore link.
Your listing
Editable fields: title, subtitle, keyword field on iOS; title, short description, full description on Android. Each shows its character count against the store limit. The numbers and the coverage table update as you type.
Drafts menu
Open it from the toolbar: the live listing, "New draft from live", and your saved drafts with their change against live. Picking a draft loads it into the editor.
Reading the coverage ledger
Next to the editor, every tracked keyword in the active country is listed with its status. The chip is purely structural: it tells you whether your metadata's tokens match the keyword's tokens, not whether you'll rank for it.
- coveredLive and draft both contain the keyword. No change.
- gainedDraft contains the keyword, live doesn't. You'd start being indexed for it.
- lostLive contains the keyword, draft doesn't. A wording change cost you eligibility.
- not coveredNeither version contains the keyword. Tracked but unaddressed.
Coverage is a literal regex match against your title, subtitle, keyword field (iOS), short description (Android), and description. Same logic the App Store uses to decide whether you're eligible to appear in a search, not where you'll rank.

TMS: the headline number
TMS (Total Market Searches) is the middle of the three headline numbers. It's the sum of monthly searches for every keyword your draft covers, across all your tracked keywords for the active country.
Read it as a ceiling, not a forecast. TMS measures the size of the search pool you're eligible for, not how many of those searches you'll actually capture. Capturing them depends on where you rank, your conversion rate, and how much paid placement Apple or Google injects above you.
Next to it you see the change against live: +12,400 means your draft would expand the eligible pool by that many monthly searches; −3,100 means you'd shrink it.

Untapped reach & AI fill
In the coverage table, tick the keywords you don't cover yet. A bar appears above the table with the monthly searches those keywords add (MaxReach) and a Generate button.
Two ways to fill the gaps
- Edit fields by hand. Just type the missing terms into the title, subtitle, keyword field, or description. The ledger reclassifies as you type.
- Let AI do it. With keywords selected, click Generate. AI proposes two variants: AMEND (preserve all existing tokens, add the gaps) and REWRITE (full restructure, may drop low-value tokens). Both are auto-saved as new drafts so you can compare them against each other and against your manual edit.
On iOS, AMEND respects the 100-character keyword-field limit and avoids duplicates against your title and subtitle (Apple penalises repetition). If a target keyword can't fit, the AI reports it as skipped with a reason.

Saving and comparing drafts
Drafts are explicit-save: typing in the editor doesn't automatically persist anything. Three actions create or update saved rows:
- Save writes the current draft into the active simulation card (or creates a new one if you started from LIVE).
- Save as new always creates a new card, leaving the active one untouched. Use this to fork a variant.
- Rename / Duplicate / Delete sit on each saved draft in the drafts menu.
Switching between saved drafts reloads the editor with that card's draft and recomputes the ledger against today's tracked keywords and volume data, not a frozen snapshot. So a draft saved two weeks ago will show different numbers if your tracked keywords or volume signals have moved since.

What "reach" actually means
Three things the simulator's reach numbers are, and one thing they aren't:
- Are: the monthly search volume of each keyword in the active country.
- Are: summed into TMS only over keywords your metadata's tokens actually match.
- Are: useful for prioritisation: bigger gaps deserve attention before smaller ones.
- Aren't: install forecasts. Indexing makes you eligible; ranking captures the searches.
The simulator can prove your draft is eligible to appear for a keyword. It can't tell you which slot you'll land in. That depends on competitor strength, conversion, install velocity, and ranking signals measured elsewhere in the product (the ASO Score, keyword rank charts, competitor matrix).
Common workflows
"What's the biggest gap I'm missing?"
In the coverage table, tick the 3-5 uncovered keywords with the most searches. Click Generate. Compare the AMEND variant's TMS gain against the REWRITE variant's. Save whichever reads naturally.
"Will this rewrite cost me reach?"
Paste your candidate copy into the editor. Watch the ledger for any lost chips. If the lost keywords carry meaningful MaxReach, your rewrite shrinks the eligible pool, even if it reads better.
"A/B copy for the next release"
Save three drafts: current copy, AMEND variant, manual rewrite. Switch between them in the drafts menu, which shows each draft's change against live. Take the winner into App Store Connect or Play Console yourself; nothing is published from the simulator.
Reasonable questions
Why does the same draft sometimes show different TMS values?
Volume figures refresh weekly (Sunday 05:00 UTC). If a snapshot job ran between two saves, the same draft can produce a slightly different TMS, which is useful signal in itself. It tells you the underlying market shifted, not your copy.
Why is my keyword still listed as uncovered when I added it to the description?
The simulator's coverage is a contiguous-token regex match (e.g. {photo editor}). On iOS, Apple does compose tokens across the title and keyword field, but our simulator doesn't credit cross-field composition yet. Workaround: add multi-word phrases as a single comma-segment in the keyword field on iOS, or as a contiguous phrase in your description on Android.
Does the simulator publish anything to the stores?
No. Nothing leaves the simulator. To ship a draft, copy the field text into App Store Connect or Google Play Console yourself.
Can I share a saved draft with a teammate?
Not yet: saved drafts are per-user. If you need shared review, copy the description text into your team's tool. We're tracking the request.
How should I read the +X searches/month figure in a small market?
Volume comes from the same search data on the App Store and Google Play, in every market. Small markets simply have fewer searches, so many long-tail keywords there show low, close-together numbers. In those markets, compare keywords against each other to decide what to cover first.
Open the simulator
Numbers are clearer when you read them on your own listing.
Open ASOScanPick an app, then Keywords, then Simulator.