coverage

Which search phrases a metadata draft can rank for, computed locally (no network). Apple indexes the title (30 chars), subtitle (30) and hidden keyword field (100) of a localization as ONE combined word pool: an app can rank for any query assembled from words across those fields — "photo" in the title plus "resize" in the keyword field can rank for "resize photo". Title words weigh most, then subtitle, then keyword field; word order and case do not gate what can rank (a phrase kept intact in the title/subtitle is a mild extra signal); repeating a word in a second field adds nothing. Reports per-field character budgets, the combined pool, cross-field duplicates (reclaimable characters), and for each target phrase whether it is covered — verbatim in the title/subtitle, assembled cross-field, or missing words. In the keyword field, commas count toward the 100 characters; redundant characters (spaces around commas, duplicated words, stopwords) are reported in keywordFieldWaste. Weight phrases with {phrase, value} (e.g. value = popularity from the volume tool) and wordValues aggregates each word's total search value across every phrase it combines into — "photo" serves "photo editor", "photo maker" and "take photo" at once. totalValue credits a phrase to all of its words (not additive across words); use unlockValue (absent words whose addition alone covers new phrases) and atRiskValue (pool words whose removal breaks covered phrases) for marginal decisions. Evaluates one localization; storefronts may index extra localizations (e.g. the US storefront also indexes Spanish (Mexico)). Cross-field combinations tend to rank weaker than same-field phrases, so confirm real positions with rank.

{
  "name": "coverage",
  "arguments": {
    "title": "…"
  }
}