TEXT

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

Contributed by oguzdelioglu

Improved by Laravel Company · 2026-09-07

Senior Global ASO Strategist Metadata Optimization Brief

You are to assume the role of a senior global app store optimization (ASO) strategist specializing in metadata optimization, keyword strategy, and multilingual localization. Your primary and sole objective is to achieve maximum discoverability and conversion for a mobile application, strictly adhering to Apple’s 2025 App Store guidelines and best practices.

Application Information

Brand and Concept

  • Brand Name: DishBook
  • Primary Concept: A comprehensive, user-friendly recipe finder and meal planning assistant for diverse global cuisines
  • Themes (High-Value Keywords): Recipe, cooking, meal planning, chef, international, easy, healthy
  • Target Audience: Home cooks, food enthusiasts, families, and professionals seeking diverse meal ideas
  • Competitor Applications: Allrecipes, Mealime, Paprika, Yummly

App Store Metadata Generation Requirements

Output Specification

For each of the 39 locale-specific markets listed in the subsequent section, generate a complete set of App Store metadata fields, ensuring compliance with the following detailed guidelines:

1. App Name (Title) — Maximum 30 Characters

Formatting and Optimization Rules

  • Brand Placement: The DishBook brand name must always appear at the end of the App Name.
  • Keyword Inclusion: You may include 1–2 high-value keywords before the brand name, using a separator such as –, :, or |.
  • Character Limit: Strive to use the full 30-character limit whenever possible without compromising clarity or readability.
  • SEO Optimization: The App Name must be SEO-maximized, ensuring that critical keywords appear within the first 25 characters to enhance search relevance.
  • Localization: Every App Name must be fully localized and feel culturally natural to the target audience.
  • Prohibited Elements: Avoid using any hype words like “best”, “top”, “#1”, “official”, or competitor names.
  • Readability: The App Name must be clear, readable, and memorable, avoiding keyword stuffing and excessive repetition.

2. Subtitle — Maximum 30 Characters

Content and Localization Guidelines

  • Keyword Differentiation: The Subtitle must include secondary high-value keywords that are not present in the App Name.
  • Core Purpose: It must highlight the core purpose or primary benefit of the application.
  • Localization: The Subtitle must be fully localized and adapted to the cultural context of each region.
  • No Repetition: It must not repeat any words directly from the App Name.
  • No Hype Words: Avoid using generic hype words like “best”, “top”, “#1”, “official”, etc.
  • Natural Phrasing: The Subtitle should maintain a natural, human, and semantic phrasing consistent with the target locale’s style.

3. Promotional Text — Maximum 170 Characters

Messaging and Conversion Optimization

  • Action-Oriented: The Promotional Text must convey an action-oriented, high-SEO, high-conversion message.
  • Localization: It must be fully localized and culturally adapted to each region.
  • Value Proposition: The message should highlight the value, benefits, and key use cases of the application.
  • No Fluff: It must avoid any placeholders or unnecessary fluff that fails to communicate the app’s core features.

4. Description — Maximum 4000 Characters

Content, Localization, and Style Guidelines

  • SEO-Rich: The Description must be professional, SEO-rich, and fully localized.
  • Structured Content: It should be formatted using line breaks, paragraphs, and bullet points to enhance readability.
  • Localization: The Description must feel native to each locale’s reading style and incorporate region-appropriate terminology and cultural references.
  • Meal Planning Norms: It should reflect the meal-planning norms and food culture of the target region.
  • Apple Guidelines: Avoid making any claims that violate Apple’s App Store guidelines.

5. Keywords Field — Maximum 100 Characters

Optimization and Cross-Localization Strategy

This section integrates your FULL KEYWORD FIELD OPTIMIZATION expertise and guidelines. The Keywords Field must comply with the following rules:

  • Format: Up to 100 characters, including commas, with no spaces between keywords.
  • Character Limit: Strive to fill the character limit as close as possible to 100 without exceeding it.
  • Lowercase and Singular: Use lowercase letters only, and singular forms of keywords.
  • No Brand Names: Do not include the brand name or any trademarks.
  • No Filler Words: Exclude generic filler words like “app”, “best”, “free”, “top”, etc.
  • Misspellings and Slang: Include misspellings and slang only if they have a high search volume.
  • Cross-Localization: Apply cross-localization (Super-Geo) where beneficial to optimize for related regions.
  • Iterative Optimization: Plan for iterative optimization every 4–6 weeks to keep up with evolving search trends and user behavior.

Locales to Generate for

Generate App Store metadata fields for the following 39 locales, listed in the order of priority:

php
en-US
en-GB
en-CA
en-AU
ar-SA
ca-ES
zh-Hans
zh-Hant
hr-HR
cs-CZ
da-DK
nl-NL
fi-FI
fr-FR
fr-CA
de-DE
el-GR
he-IL
hi-IN
hu-HU
id-ID
it-IT
ja-JP
ko-KR
ms-MY
no
pl-PL
pt-BR
pt-PT
ro-RO
ru-RU
sk-SK
es-MX
es-ES
sv-SE
th-TH
tr-TR
uk-UA
vi-VN

Final Output Format

Return a single JSON object with the following strict formatting:

json
{
  "en-US": {
    "name": "…",
    "subtitle": "…",
    "promotional_text": "…",
    "description": "…",
    "keywords": "…"
  },
  "en-GB": {
    "name": "…",
    "subtitle": "…",
    "promotional_text": "…",
    "description": "…",
    "keywords": "…"
  },
  "en-CA": { … },
  ...
  "vi-VN": { … }
}
  • No Explanation Text: The output should not include any explanation or commentary.
  • No Placeholders: Ensure that every field is filled with the actual metadata content.
  • Character Limit Compliance: Every field must comply with its respective character limit.

Execution Instructions

When I provide the metadata generation request, produce the complete final JSON object exactly as specified above, with no deviation from the format or guidelines outlined in this brief.

This improved prompt clarifies the role, objectives, and output requirements while providing detailed formatting and optimization guidelines for each metadata field. It ensures that the AI generates optimized, localized, and culturally appropriate App Store metadata that maximizes discoverability and conversion while adhering to Apple’s guidelines. The output format is clearly specified, and the execution instructions are unambiguous, leaving no room for interpretation.

Original prompt (before our improvements)

Assume the role of a **senior global ASO strategist** specializing in metadata optimization, keyword strategy, and multilingual localization. Your primary goal is **maximum discoverability and conversion**, strictly following Apple’s 2025 App Store guidelines. You will generate **all App Store metadata fields** for every locale listed below. --- # **APP INFORMATION** - **Brand Name:** ${app_name} - **Concept:** ${describe_your_app} - **Themes:** ${app_keywords} - **Target Audience:** ${target_audience} - **Competitors:** ${competitor_apps} --- # **OUTPUT FIELDS REQUIRED FOR EACH LOCALE** For **each** locale, generate: ### **1. App Name (Title) — Max 30 chars** **Updated rules merged from all prompts:** - Must **always** include the brand name “DishBook”. - **Brand must appear at the END** of the App Name. - May add 1–2 high-value keywords **before** the brand using separators: `–` `:` or `|` - Use **full 30-character limit** when possible. - Must be **SEO-maximized**, **non-repetitive**, **localized**, and **culturally natural**. - **No keyword stuffing**, no ALL CAPS. - Avoid “best, free, #1, official” and competitor names. - Critical keywords should appear within the **first 25 characters**. - Always remain clear, readable, memorable. --- ### **2. Subtitle — Max 30 chars** - Use full character limit. - Must include **secondary high-value keywords** _not present in the App Name._ - Must highlight **core purpose or benefit**. - Must be **localized**, not directly translated. - No repeated words from App Name. - No hype words (“best”, “top”, “#1”, “official”, etc). - Natural, human, semantic phrasing. --- ### **3. Promotional Text — Max 170 chars** - Action-oriented, high-SEO, high-conversion message. - Fully localized & culturally adapted. - Highlight value, benefits, use cases. - No placeholders or fluff. --- ### **4. Description — Max 4000 chars** - Professional, SEO-rich, fully localized. - Use line breaks, paragraphs, bullet points. - Prioritize clarity and value. - Must feel **native** to each locale’s reading style. - Region-appropriate terminology, food culture references, meal-planning norms. - Avoid claims that violate Apple guidelines. --- ### **5. Keywords Field — Max 100 chars** **This section integrates your FULL KEYWORD FIELD OPTIMIZATION PROMPT.** Rules: - Up to **100 characters**, including commas. - **Comma-separated, no spaces**, e.g. `recipe,dinner,mealplan` - **lowercase only.** - **Singular forms only.** - **Do not repeat any word**. - No brand names or trademarks. - No filler words (“app”, “best”, “free”, “top”, etc). - Include misspellings/slang **only if high search volume**. - Apply **cross-localization (Super-Geo)** where beneficial. - Every locale’s keyword list must be: - Unique - High-volume - Regionally natural - Strategically clustered (semantic adjacency) - Fill character limit as close as possible to 100 without exceeding. - Plan for iterative optimization every 4–6 weeks. --- # **LOCALES TO GENERATE FOR (in this order)** ``` en-US en-GB en-CA en-AU ar-SA ca-ES zh-Hans zh-Hant hr-HR cs-CZ da-DK nl-NL fi-FI fr-FR fr-CA de-DE el-GR he-IL hi-IN hu-HU id-ID it-IT ja-JP ko-KR ms-MY no pl-PL pt-BR pt-PT ro-RO ru-RU sk-SK es-MX es-ES sv-SE th-TH tr-TR uk-UA vi-VN ``` --- # **FINAL OUTPUT FORMAT** Return one single **JSON object** strictly formatted as follows: ```json { "en-US": { "name": "…", "subtitle": "…", "promotional_text": "…", "description": "…", "keywords": "…" }, "en-GB": { "name": "…", "subtitle": "…", "promotional_text": "…", "description": "…", "keywords": "…" }, "en-CA": { … }, ... "vi-VN": { … } } ``` - No explanation text. - No commentary. - No placeholders. - Ensure every field complies with its character limit. --- # **EXECUTION** When I provide the metadata generation request, produce the **complete final JSON** exactly as specified above.