Metadata Localization

Definition

Metadata Localization is the process of translating and culturally adapting an app's structured metadata (title, subtitle, keywords, description) for international markets. It differs from simple translation: transcreation adapts messaging, value propositions, and cultural references for local audiences. It also accounts for language-specific character count variations, character encoding issues, and platform-specific technical constraints. Metadata localization is the highest-impact localization effort because it directly affects search visibility, app store discovery, and conversion rate.

How It Works

Transcreation vs. Literal Translation

Literal Translation (❌ Avoid):

English Title: "Snap! Photo Editor for Everyone"
Machine Translation: "Chasni! Editor Fotoğrafu herkes için" (Turkish, awkward phrasing)

Transcreation (✅ Best Practice):

English Title: "Snap! Photo Editor for Everyone"
Turkish Transcreation: "Fotoğraf Düzenle - Herkes İçin Snap!" (reordered, cultural context)

Transcreation asks: "What would a native speaker say to convey this value proposition?" rather than "How do I translate each word?"

Character Count Challenges Across Languages

Languages vary dramatically in character efficiency:

English: 1 character = ~0.5 words of meaning

• "Task manager" = 12 chars, ~2 words, ~3 words of meaning

German: 1 character = ~0.3 words of meaning (compounds are long)

• "Aufgabenverwaltung" = 19 chars, 1 word, ~3 words of meaning
• ~30% more characters needed for equivalent English meaning

CJK (Chinese/Japanese/Korean): 1 character = 1-3 words of meaning

• Chinese "任务管理" = 4 chars, ~2 words, "task management"
• ~60% fewer characters needed than English

Spanish: 1 character = ~0.45 words (slightly more efficient than English)

• "Gestor de tareas" = 15 chars, ~3 words of meaning

Platform implications:

• Apple App Title: 30 characters. Works fine for English/CJK. German needs creative abbreviation ("Aufgaben Manager" instead of "Aufgabenverwaltung").
• Google Play Title: 50 characters. More generous; supports German easily.
• Apple Subtitle: 30 characters. German nearly impossible; CJK highly efficient.

Messaging and Value Proposition Adaptation

Different cultures prioritize different app values:

US/English-speaking markets:

• Productivity focus: "Get things done faster"
• Efficiency/time-saving: "Save 2 hours daily"
• Individualism: "Achieve your goals"

German/Northern Europe:

• Engineering/quality: "Engineered for precision"
• Trust/security: "Your data is safe"
• Detail-orientation: "Advanced customization options"

CJK markets (China, Japan, Korea):

• Harmony/group: "Collaborate with your team"
• Aesthetic design: "Beautiful, intuitive design"
• Reputation: "Trusted by 10M+ users"

Example — Productivity App Description:

English (US-focused):

"Crush your to-do list and achieve more every day. Get alerts, prioritize, and
dominate your tasks. The #1 productivity app for ambitious people."

German transcreation (quality + engineering focus):

"Intelligente Aufgabenverwaltung mit präzisen Benachrichtigungen. Professionelle
Priorisierung für anspruchsvolle Arbeit. Von Ingenieuren entwickelt, für Profis gemacht."

Japanese transcreation (aesthetic + harmony focus):

"美しく整理された毎日へ。チームで協力し、すべてのタスクを優雅に管理。信頼される10万人のユーザー。"
(Beautiful daily organization. Collaborate with your team, elegantly manage all tasks. Trusted by 100K users.)

QA for Localized Metadata

Localization QA checklist:

1. Spelling and grammar — hire native speaker, not machine
2. Terminology consistency — use same word for same concept throughout (e.g., "task" vs. "job" vs. "assignment")
3. Character limits — every field must fit within platform limits
4. Encoding issues — test special characters (accents, umlauts, Arabic marks) render correctly on device
5. Placeholders and variables — if English uses %s or {name}, ensure translations also use placeholders correctly
6. Screenshot caption text — ensure translated captions match UI language and don't look auto-generated
7. Formatting — check for URL links, line breaks, and formatting in translated strings
8. Tone and voice — ensure translated version matches brand tone (formal, casual, playful, etc.)
9. Screenshot and icon appropriateness — review all visuals for cultural sensitivity

Apple's Dual-Locale Strategy

Apple allows (and sometimes requires) defining metadata for up to 36 locales. Important quirk:

Primary Locale: The metadata users see in their region (e.g., Australia sees "English (Australia)" metadata if provided)

Fallback Locale: If no primary locale exists, Apple shows English (US) metadata (or another fallback)

Strategic implication:

• If you support English (US) but not English (Australia), Australian users see English (US) metadata
• If you want to optimize separately for Australia (regional keywords, Australian spellings), you must create a distinct English (Australia) localization
• This is often not worth the effort; most teams optimize English (US) once and share globally

Formulas & Metrics

Localization Quality Index:

Quality = (Native Speaker Approval % × 0.50) +
          (Character Fit % × 0.20) +
          (Keyword Inclusion % × 0.20) +
          (Formatting Errors × -0.10)

Target: 95%+ for all localizations.

Translation Cost Efficiency:

Cost per Download = Total Localization Cost / Expected Downloads from Locale

Used to validate ROI on localization (compare to marketing cost-per-install).

Best Practices

1. Hire transcreators, not translators — a translator converts words; a transcreator adapts messaging. Pay more, get better results.

1. Create a terminology glossary — define how key terms (your app's core features, brand concepts) translate consistently across languages.

1. Test character limits during translation — don't translate and then discover the German title is 35 characters (too long for Apple's 30-char limit).

1. Account for expansion during translation — allocate only 60-70 characters for a 30-character English subtitle; that's the headroom needed for German.

1. Use style guides — document capitalization, formatting, brand name handling for each language (e.g., "All titles in French start lowercase unless a proper noun").

1. Quality assurance on-device — don't assume localized text looks right. Test on actual iPhone/Android device to see rendering, truncation, line breaks.

1. Version control your localizations — track which metadata version is live for each locale; enable rollback if needed.

1. Localize incrementally — start with title, subtitle, keywords (highest impact). Add full description later.

Examples

English Title (30 chars) → German Adaptation Challenge:

Subtitle Adaptation (30 chars):

Dependencies

Influences (this term affects)

• Conversion Rate — localized messaging increases CVR by 10-40% on average
• App Title — localization directly affects title optimization
• Screenshot — screenshot text must match metadata language
• Localization Strategy — strategy defines which metadata to localize

Depends On (affected by)

• Localization Strategy — scope of localization (Tier 1/2/3)
• Keyword Localization — keywords inform metadata keywords
• Transcreation skill and native speaker availability
• Platform character limits

Platform Comparison

Related Terms

• Keyword Localization
• Localization Strategy
• App Title
• Subtitle
• Full Description
• Screenshot
• CJK ASO
• Right-to-Left (RTL) ASO

Sources & Further Reading

• Phrase: Localization Best Practices for App Store Optimization
• OneSky: Character Limits by Language and Platform
• SplitMetrics: Transcreation for International ASO
• AppTweak: Metadata Character Count Guidelines by Language