// ASO capability · Metadata Optimisation

Metadata rewritten as a release, not a copy pass.

Every title, subtitle, keyword field, short and long description is treated as a shippable artifact with a diff, a projection and a rollback plan — never a document lost in a Slack thread.

• App Store + Google Play• Client-owned accounts• Measured releases
// Metadata release diff
Before · v4.2.1
Title
Restly — Sleep & Calm
Subtitle
Meditation for a better you
Keyword field
calm,mindful,sleep,rest,zen,quiet,peace,dream
After · v4.3.0 candidate
Title
Restly: Sleep Meditation
Subtitle
Guided sleep & breathwork daily
Keyword field
breathwork,anxiety,journal,guided,nap,unwind,bedtime,relax
Projected impressions +34% · install rate hold
3–4
Releases per wave
Per app, per market
100%
Diffed
Before ↔ after, always
0
Silent edits
Everything reviewed
8
Locales max/wave
Beyond that we stagger
// How we think about it

Principles this practice runs on.

These aren't slogans — each principle maps to a decision we make weekly inside the release wave.

Principle · 01

Diffs, not documents.

We never hand over a wall of copy. Every change ships as a diff — old value, new value, projected impact, rollback line.

Principle · 02

Rewrite for the field, not the store.

Title, subtitle, and keyword field each play a different game. We write for each field's real ranking behaviour, not for a generic 'app description'.

Principle · 03

Every release is reversible.

If a wave doesn't compound, we roll to the previous version within one release. Nothing we ship is one-way.

// Inside the wave

The 90-day cadence for this practice.

Every practice is scheduled through the same four-beat wave. Here is what those beats look like inside this one.

Diagnose · Weeks 1–2

Baseline all fields

Screenshot every metadata field, per store, per market, before we touch anything. That baseline becomes the read line.

Baseline archive
Ship · Weeks 3–8

Draft, review, release

Diffs proposed, reviewed against the keyword architecture, released in staged windows to protect existing rankings.

Release diff pack
Read · Weeks 9–10

Impression + install read

We separate impression movement from install-rate movement — a good metadata release moves both, or we rewrite.

Read report
Compound · Weeks 11–13

Codify winners

Field-by-field, we lock the shapes that worked and open the next brief with clear no-go zones.

Metadata playbook
// Inputs we need
  • Current metadata across every market
  • Brand voice guardrails
  • Release calendar access
// Outputs you get
  • Release-ready diff pack per market
  • Projected impression movement per diff
  • Rollback line for every field
  • Locked metadata playbook per wave
// Tools we run
App Store ConnectPlay ConsoleAppTweakStudio diff tool

We bring the stack. You never buy or manage tools to work with us.

// Questions

Questions we get about this practice.

Do you write in local languages yourself?+

For our core markets, yes. Beyond that we work with vetted native writers who follow our field-by-field brief — never a generic translator.

How often do you rewrite metadata?+

Three to four times per 90-day wave per app, sequenced so no two markets rewrite in the same week.

Can we approve every diff?+

Yes — every diff goes to your decision owner before release. Nothing ships silently.

// Continue reading
// Free audit

Want us to run this practice on your app first?

45-minute audit. You leave with a written read of where this practice would move the needle in your category.

30 seconds. No commitment.