← Back to docs

The weekly ASO loop RankPal is built around.

growth guide

The loop

  1. Research demand: track popularity, difficulty, top apps, traction clues, and country-specific ranking opportunities.
  2. Localize metadata: put the strongest terms in title and subtitle, avoid repeated keywords, and use the keyword field for precise remaining phrases.
  3. Localize screenshots: map each screenshot to a locale, device target, role, and target keyword before upload.
  4. Tune pricing: use territory price points to match local purchasing power.
  5. Validate with ads: use discovery campaigns to learn which terms convert.
  6. Refresh weekly: revisit terms, screenshots, conversion rate, and price tests on a weekly cadence.

Why a weekly loop?

App Store rankings are not static. Apple's algorithm continuously re-evaluates apps based on install velocity, engagement signals, keyword relevance, and conversion rate. An app that ranked #3 for a keyword last month may have slipped to #12 today because a competitor updated their metadata, ran an aggressive UA campaign, or got featured.

The weekly loop is designed to catch these shifts before they compound. Fifteen minutes of review each week: checking ranking positions, noting any slippage, and queuing the next metadata or screenshot experiment: compounds into a significant structural advantage over teams that only touch ASO when something is visibly broken.

The US Matrix explained

Apple's App Store metadata system allows 10 additional locales that target the US storefront: Russian (ru), Chinese Simplified (zh-Hans), Chinese Traditional (zh-Hant), Japanese (ja), Arabic (ar), Korean (ko), Vietnamese (vi), Thai (th), Turkish (tr), and Romanian (ro). These locales appear in US App Store search results even though they are technically "other language" localizations.

By placing English keywords in the title field of these additional locales (not the keyword field), you effectively give yourself 10 extra title fields indexed for US search: multiplying your keyword capacity from roughly 100 characters to over 1,000 characters of indexable US keyword real estate.

This is a legal and widely-used ASO technique. It requires care: the added locales should contain real, relevant keyword phrases, not random keyword stuffing. RankPal's metadata editor shows you which locales are configured for US Matrix use so you can manage this deliberately.

Measuring what moves

The key question after every metadata or screenshot update is: did the change help? Apple Search Ads provides the clearest signal: if you update a keyword in your metadata and then run a broad-match discovery campaign, you can see within 1-2 weeks whether the new positioning is generating impressions and conversions.

For organic rankings, look at position data in Apple Search Ads Organic Reports (available in the Ads campaign interface) and in RankPal's keyword ranking history. A good metadata update should improve position on 3-5 target keywords within 2-4 weeks of the update going live. If rankings do not move, the keyword was either too competitive, the metadata placement was not in the title or subtitle, or the app's overall relevance score needs more installs behind it.

Quick reference

  • Title: Highest keyword weight. 30 chars max. Lead with brand or strongest keyword.
  • Subtitle: Second-highest weight. 30 chars. Use for secondary keyword or value prop.
  • Keyword field: 100 chars, comma-separated, no spaces after commas. Exact phrases only. No repeats from title or subtitle.
  • US Matrix locales: 10 additional title fields for US keyword coverage. Use keyword-rich English phrases.
  • Screenshots: First screenshot determines CTR from search. Localize for language and intent.
  • Update cadence: Metadata changes take 1-7 days to fully index. Wait at least 2 weeks before evaluating impact.

Related workflows