Module 2: Keyword Strategy and Metadata for iOS

Step 1 – The 3 Core iOS Keyword Fields (and What Really Indexes)

In iOS ASO today (2025–2026), most of your keyword visibility comes from three metadata fields:

1. App Name (Title)

• Limit: 30 characters (including spaces)
• Indexed for search: Yes
• Weight: Highest among on‑metadata fields
• Visible to users in search results and product page.

1. Subtitle

• Limit: 30 characters
• Indexed for search: Yes
• Weight: High, but generally a bit lower than the App Name
• Also visible in search results.

1. Keyword Field (App Store Connect)

• Limit: 100 characters, comma‑separated list
• Not visible to users, but fully indexed
• No spaces needed after commas; spaces count toward the limit.

Other fields and their current role (as of early 2026):

• Promotional Text: Not used for keyword indexing; used for time‑sensitive messaging.
• Description: In most markets, Apple still does not reliably index the description for keyword ranking the way Google Play does. You should still write it well for conversion, but do not rely on it for ranking.
• In‑App Events, Custom Product Pages, and Screenshots: Mainly affect conversion and relevance signals, not traditional keyword indexing.

Key takeaway: For iOS keyword strategy, this module focuses on App Name, Subtitle, and Keyword Field, because these are the fields you can intentionally structure to rank for specific searches within strict character limits.

Step 2 – Rules and Constraints You Must Follow

Before designing any keyword strategy, you must respect Apple’s current guidelines and technical limits.

Character and formatting rules

• App Name & Subtitle
• Max 30 characters each.
• Avoid truncation: if your title is too long, it will be cut off in search results.

• Keyword Field
• Max 100 characters.
• Use commas to separate keywords.
• No spaces after commas (wastes characters).
• No need to repeat your brand name here.

Content policy constraints (high‑level)

Apple’s App Store Review Guidelines (continuously updated; current version as of 2026) enforce:

• No keyword stuffing or repeating the same word in unnatural ways.
• No competitor brand names or trademarks you don’t own or have rights to.
• No misleading terms (e.g., claiming features you don’t have, or using unrelated high‑traffic keywords).
• No special characters or emojis used purely to attract attention (unless part of your brand and compliant with guidelines).

Practical implications

• You must prioritize ruthlessly: 160 total characters (30 + 30 + 100) is very small.
• You should not copy Google Play titles directly; iOS limits are stricter.
• You should not repeat the same keyword across fields unless it is your brand or absolutely essential for clarity.

In the next steps, you’ll learn how to use these limited characters to cover as many relevant searches as possible.

Step 3 – Combinatorial Indexing: How Apple Builds Phrases

Apple’s search algorithm combines words from your App Name, Subtitle, and Keyword Field to form searchable phrases. This is often called combinatorial indexing.

What this means

If your metadata contains:

• App Name: `CalmMind: Sleep`
• Subtitle: `Meditation & Relax`
• Keyword Field: `anxiety,breathing,relax,sleep tracker`

Apple can potentially match searches like:

• `sleep meditation`
• `relax sleep`
• `anxiety sleep`
• `breathing meditation`

…even if you never wrote those exact 2–3 word phrases in one place.

Why repetition usually wastes characters

Because Apple can combine words across fields:

• If `meditation` is in your Subtitle, you usually don’t need `meditation` again in the Keyword Field.
• If `sleep` is in your App Name, you don’t need `sleep` again in Subtitle just for ranking (you might still use it if it’s essential for user clarity).

Exceptions: When repetition can be okay

• Brand name: repeating your brand in App Name and Subtitle can help clarity and brand recall.
• Critical core intent: if your app absolutely depends on a single core keyword (e.g., `VPN`), you might keep it in App Name and Subtitle for user understanding, even if it’s technically redundant for indexing.

Key principle:

> Use each unique word once across the three fields (except brand and essential clarity words) to maximize the number of distinct terms Apple can combine.

Step 4 – Good vs. Bad Keyword Structures

Let’s compare two approaches for a habit tracker app.

Scenario

Target concepts: `habit`, `tracker`, `routine`, `daily`, `productivity`, `goals`, `planner`, `reminder`.

#### Bad structure (too repetitive)

• App Name: `Daily Habit Tracker`
• Subtitle: `Habit Tracker & Habit Reminder`
• Keyword Field: `habit,habit tracker,tracker,habit reminder,reminder,daily habits`

Problems:

• `habit` appears 5+ times.
• Using multi‑word phrases like `habit tracker` and `habit reminder` in the Keyword Field wastes characters because Apple can combine `habit` + `tracker` anyway.
• Many potential new concepts (e.g., `routine`, `goals`, `planner`, `productivity`) are missing.

#### Better structure (maximizing unique coverage)

• App Name: `HabitFlow: Daily Tracker`
• Subtitle: `Build routines, reach goals`
• Keyword Field: `productivity,planner,reminder,streaks,habit,routine,focus`

Why this is better:

• `habit` appears only once (Keyword Field) and once as part of the brand concept `HabitFlow`.
• `tracker`, `daily`, `routines`, `goals` are covered in App Name + Subtitle.
• Keyword Field adds new concepts: `productivity`, `planner`, `reminder`, `streaks`, `focus`.
• Apple can now build combinations like `habit planner`, `productivity tracker`, `daily routine`, `goal tracker`, etc.

You’ve increased the number of unique words Apple can mix, without exceeding character limits.

Step 5 – Design a Non-Repetitive Keyword Set

You’re working on an iOS app: a language learning app focused on Spanish and French for beginners.

Task

You want to rank for concepts like:

• `spanish`
• `french`
• `learn`
• `language`
• `vocabulary`
• `grammar`
• `beginner`
• `lessons`
• `practice`

1. Draft 3 fields on paper or in a notes app:

• App Name (≤ 30 chars)
• Subtitle (≤ 30 chars)
• Keyword Field (≤ 100 chars, comma‑separated, no spaces)

1. Rules for yourself:

• Use each non‑brand word only once across all three fields.
• Make App Name and Subtitle readable and appealing to humans.
• Put more utility words (like `vocabulary`, `grammar`, `beginner`) in the Keyword Field.

1. After drafting, ask:

• Did I repeat any generic keyword (e.g., `learn`, `language`) across multiple fields? Can I remove the repetition?
• Can Apple form key phrases like `learn spanish`, `french grammar`, `spanish vocabulary`, `language lessons` from the words I used?

Spend 3–4 minutes creating your own set before moving on. In the next steps, you’ll see how to refine this using data from Apple Search Ads and ASO tools.

Step 6 – Keyword Research Workflow with Apple Search Ads & ASO Tools

Modern iOS keyword strategy relies heavily on data, not guesses. Two main sources today:

1. Apple Search Ads (ASA) – especially Search Match and keyword suggestions.
2. Third‑party ASO tools – e.g., AppTweak, AppFollow, AppRadar, MobileAction, Sensor Tower, etc.

Using Apple Search Ads (ASA)

ASA is Apple’s official ads platform. Even if you have a small or zero budget, it’s useful for research:

1. Create a test campaign (if you have access):

• Use Search Match: Apple automatically matches your app to relevant queries.
• After a few days, export the Search Terms report.

1. Analyze the report:

• Look at search terms with impressions > 0 and reasonable tap‑through rate (TTR).
• These terms show real user demand and some level of relevance to your app.

1. Use Popularity / Search Volume:

• ASA shows a Popularity score (0–100 in many tools; in the ASA UI it’s a bar).
• Prioritize keywords with higher popularity but still relevant and attainable (not overly generic like `games`).

Using ASO tools (2025–2026 capabilities)

Most modern ASO tools provide:

• Estimated search volume / popularity for each keyword.
• Difficulty / competition score.
• Keyword suggestions based on seed terms.
• Competitor analysis: which keywords similar apps rank for.

Practical workflow:

1. Start with a seed list (10–30 obvious keywords).
2. Use ASO tools + ASA search terms to expand to 50–100 candidate keywords.
3. For each keyword, note:

• Relevance (High / Medium / Low)
• Popularity (from ASA or ASO tool)
• Difficulty / competition

1. Shortlist ~20–30 high‑relevance keywords with a mix of high, medium, and long‑tail volume.

You’ll use this shortlist to fill your App Name, Subtitle, and Keyword Field strategically.

Step 7 – Prioritize Keywords Like a Pro

Imagine your habit tracker app again. From ASA and an ASO tool, you collected this simplified data:

| Keyword | Relevance | Popularity (0–10) | Difficulty (0–10) |

|----------------|-----------|-------------------|-------------------|

| habit tracker | High | 9 | 9 |

| habit app | High | 7 | 7 |

| daily routine | High | 6 | 6 |

| productivity | Medium | 8 | 8 |

| goal tracker | High | 7 | 6 |

| streaks | Medium | 4 | 4 |

| planner | Medium | 6 | 7 |

| reminder app | Medium | 5 | 6 |

Task

1. Rank these keywords for inclusion in your 3 fields, considering:

• Relevance must be High or Medium (ignore low).
• You want some easier wins (moderate popularity, lower difficulty).
• Remember combinatorial indexing: you don’t need the exact phrase `habit tracker` if you already have `habit` and `tracker`.

1. Decide which belong in:

• App Name: usually 1–2 core concepts + brand.
• Subtitle: 2–3 supporting concepts that read well as a tagline.
• Keyword Field: remaining high‑value words, single terms, not phrases.

1. Write down your choices. Ask yourself:

• Did I avoid wasting characters on full phrases like `habit tracker` when I could use `habit,tracker` separately?
• Did I balance big, competitive terms with more specific, winnable ones?

This exercise mirrors what ASO managers do in real teams when turning keyword research data into concrete metadata.

Step 8 – Localizations and Regional Keyword Strategies

Apple lets you create localized metadata (App Name, Subtitle, Keywords, Description, Screenshots) for many storefronts.

Why localization matters

• Users in different countries search in different languages and with different habits.
• Even within the same language, US vs. UK vs. Australia may use different terms (e.g., `calorie counter` vs. `calorie tracker`).
• Localized keywords can unlock entirely new markets without changing your core product.

Important details (as of 2026)

• You can set separate keyword fields for each supported language in App Store Connect.
• Some language pairs share indexing (e.g., US English with Spanish (Mexico) in some cases), but Apple’s behavior can change; do not rely on undocumented hacks.
• It’s safer to explicitly localize key languages instead of assuming cross‑language indexing.

Practical localization workflow

1. Identify priority markets by revenue or installs (e.g., US, UK, Germany, Japan, Brazil).
2. For each target country, answer:

• What is the primary language in App Store Connect?
• Do I have app content (UI, support) in that language? If not, focus on English‑speaking users there.

1. Run local keyword research:

• Use ASO tools with country‑specific search volume.
• For non‑English markets, work with native speakers or professional translators; avoid direct machine translation of keywords.

1. Adapt your metadata:

• Keep brand consistent (e.g., `HabitFlow`).
• Translate and culturally adapt generic terms (e.g., `routine`, `goals`, `planner`) to what people actually search.

Example: A `budget planner` app might localize to German with keywords like `Haushaltsbuch`, `Finanzen`, `Budget`, instead of direct translations that users don’t actually use.

Localization is not only language translation; it’s matching local search behavior.

Step 9 – Template for Structuring Metadata (Pseudo-Formula)

Use this pseudo‑template to plan your metadata. It’s written in a JSON‑like style to make it easy to reuse in projects or documentation.

```json

{

"app_name": {

"max_chars": 30,

"structure": "<Brand>: <Core keyword or benefit>",

"example": "HabitFlow: Daily Tracker",

"notes": [

"Include brand + 1 main generic keyword (e.g., 'tracker', 'meditation', 'budget')",

"Avoid stuffing multiple commas or keyword lists",

"Prioritize clarity and click-through over stuffing"

]

},

"subtitle": {

"max_chars": 30,

"structure": "<2–3 supporting concepts in natural phrase>",

"example": "Build routines, reach goals",

"notes": [

"Use 2–3 additional high-value concepts not fully covered in title",

"Write as a human-readable promise or benefit",

"Avoid repeating the exact same generic words from title unless needed for clarity"

]

},

"keyword_field": {

"max_chars": 100,

"format": "comma-separated, no spaces",

"structure": "<single words, no phrases>",

"example": "productivity,planner,reminder,streaks,habit,routine,focus",

"notes": [

"Do not repeat generic keywords already used in title/subtitle",

"Focus on single terms that can combine into many long-tail queries",

"Avoid competitor brand names and irrelevant high-volume terms"

]

}

}

```

Use this as a checklist each time you create or revise iOS metadata.

Step 10 – Check Your Understanding: Keyword Field

Answer this question to test your understanding of how to structure the keyword field.

Step 11 – Review Key Terms

Flip these cards (mentally or with a partner) to reinforce the main concepts from this module.