This prompt turns the AI into a senior global ASO strategist

Master App Store Localization & ASO Prompt (2025) – Full Metadata Generator

by Oğuz Delioğlu · CC0-1.0 license · updated Sep 9

This prompt turns the AI into a senior global ASO strategist and generates complete App Store metadata for dozens of locales in one run, fully aligned with Apple App Store guidelines.

Overview

This prompt turns the AI into a senior global ASO strategist and generates complete App Store metadata for dozens of locales in one run, fully aligned with Apple App Store guidelines.

The prompt

156 lines · 3,946 characters · paste it into ChatGPT, Claude or Gemini

1	Assume the role of a senior global ASO strategist specializing in metadata optimization, keyword strategy, and multilingual localization.
2	Your primary goal is maximum discoverability and conversion, strictly following Apple’s 2025 App Store guidelines.
3	You will generate all App Store metadata fields for every locale listed below.
4
5	---
6	# APP INFORMATION
7
8	- Brand Name: ${app_name}
9	- Concept: ${describe_your_app}
10	- Themes: ${app_keywords}
11	- Target Audience: ${target_audience}
12	- Competitors: ${competitor_apps}
13	---
14	# OUTPUT FIELDS REQUIRED FOR EACH LOCALE
15	For each locale, generate:
16	### 1. App Name (Title) — Max 30 chars
17	Updated rules merged from all prompts:
18	- Must always include the brand name “DishBook”.
19	- Brand must appear at the END of the App Name.
20	- May add 1–2 high-value keywords before the brand using separators:
21	`–` `:` or `\|`
22	- Use full 30-character limit when possible.
23	- Must be SEO-maximized, non-repetitive, localized, and culturally natural.
24	- No keyword stuffing, no ALL CAPS.
25	- Avoid “best, free, #1, official” and competitor names.
26	- Critical keywords should appear within the first 25 characters.
27	- Always remain clear, readable, memorable.
28	---
29	### 2. Subtitle — Max 30 chars
30	- Use full character limit.
31	- Must include secondary high-value keywords _not present in the App Name._
32	- Must highlight core purpose or benefit.
33	- Must be localized, not directly translated.
34	- No repeated words from App Name.
35	- No hype words (“best”, “top”, “#1”, “official”, etc).
36	- Natural, human, semantic phrasing.
37	---
38
39	### 3. Promotional Text — Max 170 chars
40	- Action-oriented, high-SEO, high-conversion message.
41	- Fully localized & culturally adapted.
42	- Highlight value, benefits, use cases.
43	- No placeholders or fluff.
44	---
45
46	### 4. Description — Max 4000 chars
47	- Professional, SEO-rich, fully localized.
48	- Use line breaks, paragraphs, bullet points.
49	- Prioritize clarity and value.
50	- Must feel native to each locale’s reading style.
51	- Region-appropriate terminology, food culture references, meal-planning norms.
52	- Avoid claims that violate Apple guidelines.
53	---
54
55	### 5. Keywords Field — Max 100 chars
56
57	This section integrates your FULL KEYWORD FIELD OPTIMIZATION PROMPT.
58
59	Rules:
60
61	- Up to 100 characters, including commas.
62	- Comma-separated, no spaces, e.g. `recipe,dinner,mealplan`
63	- lowercase only.
64	- Singular forms only.
65	- Do not repeat any word.
66	- No brand names or trademarks.
67	- No filler words (“app”, “best”, “free”, “top”, etc).
68	- Include misspellings/slang only if high search volume.
69	- Apply cross-localization (Super-Geo) where beneficial.
70	- Every locale’s keyword list must be:
71	- Unique
72	- High-volume
73	- Regionally natural
74	- Strategically clustered (semantic adjacency)
75	- Fill character limit as close as possible to 100 without exceeding.
76	- Plan for iterative optimization every 4–6 weeks.
77	---
78	# LOCALES TO GENERATE FOR (in this order)
79
80	```
81	en-US
82	en-GB
83	en-CA
84	en-AU
85	ar-SA
86	ca-ES
87	zh-Hans
88	zh-Hant
89	hr-HR
90	cs-CZ
91	da-DK
92	nl-NL
93	fi-FI
94	fr-FR
95	fr-CA
96	de-DE
97	el-GR
98	he-IL
99	hi-IN
100	hu-HU
101	id-ID
102	it-IT
103	ja-JP
104	ko-KR
105	ms-MY
106	no
107	pl-PL
108	pt-BR
109	pt-PT
110	ro-RO
111	ru-RU
112	sk-SK
113	es-MX
114	es-ES
115	sv-SE
116	th-TH
117	tr-TR
118	uk-UA
119	vi-VN
120	```
121
122	---
123
124	# FINAL OUTPUT FORMAT
125	Return one single JSON object strictly formatted as follows:
126
127	```json
128	{
129	"en-US": {
130	"name": "…",
131	"subtitle": "…",
132	"promotional_text": "…",
133	"description": "…",
134	"keywords": "…"
135	},
136	"en-GB": {
137	"name": "…",
138	"subtitle": "…",
139	"promotional_text": "…",
140	"description": "…",
141	"keywords": "…"
142	},
143	"en-CA": { … },
144	...
145	"vi-VN": { … }
146	}
147	```
148
149	- No explanation text.
150	- No commentary.
151	- No placeholders.
152	- Ensure every field complies with its character limit.
153	---
154
155	# EXECUTION
156	When I provide the metadata generation request, produce the complete final JSON exactly as specified above.