App Store Metadata Localization Prompt
Draft App Store metadata for selected locales from verified app facts, with explicit field limits and review notes.
What this prompt does
Reusable app brief
Use your actual brand, supported features and chosen locales.
Localized metadata
Draft natural local wording while keeping app facts consistent.
Reviewable output
Return structured fields, length checks and unresolved facts for review.
What to provide & what you get
- Input
- Your app’s brand, verified features, audience, requested locales and current App Store Connect field constraints.
- Expected output
- A JSON draft for each requested locale, with metadata fields, counts, assumptions and localization review notes.
How to use
- Supply the app facts, brand and only the locales you need; confirm current field limits in App Store Connect.
- Run the prompt to draft JSON and review the stated counts with a real character or byte counter.
- Have a fluent reviewer check each locale and validate all fields in App Store Connect before submission.
Check the result: Parse the JSON, recompute field lengths and verify every product claim. Treat all keyword-demand estimates as unknown unless backed by supplied data.
Copy. Paste. Run.
v1.0.0-gas1Edit the inputs below, then copy into your AI tool with the requested source material.
Before you start
- Your app’s brand, verified features, audience, requested locales and current App Store Connect field constraints.
Worked example · Editorial fixture
Two locales for the same offline notes app
Original fictional inputs and a prepared editorial answer. This reusable prompt was not run against the fixture. Use the files and case-specific checks to review your own result.
Example input
Fictional app: TidyNote. F1: plain-text notes saved on one device. F2: local search. F3: text export. No account, sync or collaboration. Locales: en-US and fr-FR. Approved keyword data: NONE. Draft constraints: name/subtitle 30 characters; promotional text 170; description 4000; keywords 100 UTF-8 bytes.
Prepared output
{
"locales": [
{
"locale": "en-US",
"name": "TidyNote",
"subtitle": "Offline notes and text export",
"promotional_text": "Keep a short note on your device, find it by word, and export a text copy.",
"description": "TidyNote stores plain-text notes on one device. Search saved notes and export a text copy. There is no account, cloud sync, or collaboration.",
"keywords": "offline,notes,text,search,export",
"counts": {
"name": {
"characters": 8,
"utf8_bytes": 8
},
"subtitle": {
"characters": 29,
"utf8_bytes": 29
},
"promotional_text": {
"characters": 74,
"utf8_bytes": 74
},
"description": {
"characters": 141,
"utf8_bytes": 141
},
"keywords": {
"characters": 32,
"utf8_bytes": 32
}
},
"review_notes": [
"Fictional app; no keyword-demand research supplied.",
"French wording needs fluent review; counts do not establish App Review acceptance."
]
},
{
"locale": "fr-FR",
"name": "TidyNote",
"subtitle": "Notes hors ligne et export",
"promotional_text": "Gardez vos notes sur votre appareil, recherchez un mot et exportez une copie texte.",
"description": "TidyNote conserve des notes en texte brut sur un seul appareil. Recherchez une note et exportez une copie texte. Sans compte, synchronisation cloud ni collaboration.",
"keywords": "notes,hors ligne,texte,recherche,export",
"counts": {
"name": {
"characters": 8,
"utf8_bytes": 8
},
"subtitle": {
"characters": 26,
"utf8_bytes": 26
},
"promotional_text": {
"characters": 83,
"utf8_bytes": 83
},
"description": {
"characters": 165,
"utf8_bytes": 165
},
"keywords": {
"characters": 39,
"utf8_bytes": 39
}
},
"review_notes": [
"Fictional app; no keyword-demand research supplied.",
"French wording needs fluent review; counts do not establish App Review acceptance."
]
}
]
}What to check in this case
- Recomputed all five fields for both locales with Python: character counts and UTF-8 bytes are in metadata.json.
- Keep the same three features and exclusions in both languages. No search-volume or acceptance claim is supported.
- French localization still needs a fluent reviewer. Keyword byte limits and interface validation matter separately from wording.
References: Apple: app information · Apple: version fields and keyword bytes
Keep in mind
- A draft does not establish keyword search volume, ranking gains or App Review acceptance.
- Generated character counts and translations require independent checks before submission.



