Keyword Research for App Store Listings

Keyword research for UAE apps fails when it copies global volume charts and ignores how people actually type in Dubai. Users mix English brand names with Arabic category words, search “delivery near me” style intents without neighbourhood SEO tricks, and use fintech jargon (“IBAN,” “salary transfer,” “open bank account UAE”) that never appears in a US seed list.

This is a working method to build an EN + AR keyword system you can ship into titles, subtitles, keyword fields, and Play descriptions—and re-score monthly.

Principles before tools

1. Relevance beats inflated volume. Ranking for a huge generic term that attracts tire-kickers destroys CPI and retention.
2. Language is a dimension, not a translation step. “تحويل فلوس” and “money transfer UAE” may share intent but differ in competition and creative.
3. Brand vs non-brand split. Protect brand terms; grow category and job-to-be-done terms.
4. Store-specific packing. Apple’s 100-character keyword field is a compressed index; Play wants natural prose.

No guide should invent exact monthly search volumes for UAE queries—those numbers differ by tool and model. Use tools directionally; validate with your own impression reports in App Store Connect and Play Console.

Build the seed universe

Sources that work in the GCC

• Store autocomplete on real UAE App Store and Play accounts (language + region set correctly).
• Competitor titles and subtitles for Careem-class, bank, BNPL, grocery, and niche rivals in your category.
• Support, CRM, and WhatsApp logs — phrasing like “card not working in Mall of the Emirates” reveals long-tail pain (use carefully; don’t promise mall-specific features you lack).
• Apple Search Ads search match discovery and Google UAC search term insights where available.
• Arabic native speakers on your team—not only bilingual marketers who think in English first.

Seed categories to label

Score and prioritize

Create a sheet with columns: keyword, language, store priority (Apple/Play/both), intent, difficulty (relative), current rank if any, mapped field (title / subtitle / keyword field / short desc / long desc), owner, next test date.

Scoring rubric that stays honest:

• Intent fit (0–5): would a user who installs from this query find value in week one?
• Business value (0–5): LTV or strategic importance (e.g., salary accounts vs one-off coupon hunters).
• Winnability (0–5): based on your reviews, creative strength, and current rank—not fantasy.

Ship the top of the matrix into live fields; park low intent high volume terms.

Apple packing technique

• Deduplicate stems; Apple often matches variants.
• Prefer unique terms not already in title/subtitle.
• Include common misspellings only when evidence shows volume and they don’t waste budget.
• Local market terms: UAE, Dubai when truly relevant—avoid stuffing every emirate.
• Arabic Apple localization uses Arabic keyword opportunities in Arabic metadata; do not transliterate randomly if Arabic script is the user behaviour.

Google Play narrative technique

Write short and long descriptions for humans first. Then ensure primary keywords appear early in short description and naturally in the first paragraphs of long description. Repeat for Arabic. Bullet benefits; avoid keyword walls that read like 2014 SEO spam—Play users and reviewers notice.

Competitor teardown workflow (half day)

1. List 8–12 rivals visible for your head terms in UAE stores.
2. Capture title, subtitle/short desc, first three screenshots, rating, and rough category.
3. Note gaps: no Arabic, outdated UI, missing trust badges, weak seasonal presence.
4. Steal structure, not lies—never claim features you don’t ship.

Validation loop

After metadata ships, watch for 2–4 weeks:

• Impressions and conversion by source (Search vs Browse).
• Rank trackers (AppTweak, etc.) on a fixed list—direction, not daily panic.
• Qualitative: do new reviews mention the promise in your subtitle?

If impressions rise but CVR falls, you attracted the wrong query class—tighten relevance in creatives and subtitle, don’t only chase more rank.

UAE-specific pitfalls

• English-only research for apps with Arabic UI.
• Transliterated Arabic that nobody types.
• City stuffing (“Dubai Abu Dhabi Sharjah…” in title) that looks spammy and burns characters.
• Copying US finance slang when locals search “exchange house,” “WPS,” or bank brand + “app.”
• Ignoring brand misspellings for your own name on Apple keywords.

Deliverables checklist

• ☐ EN keyword universe (≥50 solid terms, prioritised)
• ☐ AR keyword universe built with native review
• ☐ Apple keyword field drafts per locale
• ☐ Play short/long description outlines mapped to keywords
• ☐ Competitor gap notes
• ☐ Monthly refresh ritual on calendar

Tools accelerate collection; judgment on intent is the moat. When the matrix is real, move to titles, subtitles, and descriptions—the next guide turns research into storefront language.

Field mapping examples (EN + AR thinking)

When a DIFC-based remittance app maps research into live fields, the discipline looks like this:

• Apple title: brand + one corridor or category anchor if characters allow.
• Subtitle: the job users hire you for (“Send money home with clear AED fees”)—not a second title.
• Keyword field: unique stems such as corridor names, remit, transfer, exchange, carefully chosen UAE-relevant modifiers, and Arabic locale equivalents in the Arabic localization—not a dump of the English list.
• Play short description: human sentence with the primary phrase early.
• Play long description: narrative sections for corridors, speed expectations, and trust—keywords appear as language people speak.

For a grocery marketplace, the same method swaps corridors for cuisine or fulfilment promises (tonight, dark store, meal kit) and Arabic food-category language from autocomplete rather than dictionary translations of English marketing.

Research rituals that keep the matrix alive

Weekly (15 minutes): skim ASA search terms and Play console query insights; flag new stems that converted installs with acceptable retention.

Monthly (90 minutes): re-run autocomplete on top 10 seeds in EN and AR; refresh competitor title table; drop dead seasonal terms after White Friday or Ramadan.

Quarterly: rebuild difficulty scores after major product launches (new city coverage, new banking feature) because winnability changes when proof improves.

Put the ritual on a shared calendar. Keyword research that only happens at launch is how listings rot while paid UA invents new language the store never learns.

Working with incomplete volume data

UAE query volumes in third-party tools are models. When two tools disagree, prefer: (1) your own impression trends after a metadata change, (2) ASA relative strength indicators, (3) qualitative frequency in support chats. Document uncertainty. Boards should see directional demand, not fake precision to three decimal places. That honesty keeps ASO credible next to performance marketing numbers.

Handoff package for writers and designers

Research is unfinished until creative teams receive top phrases to express (not necessarily to cram), phrases to avoid (misleading, trademark, off-product), an Arabic must-use and never-use list, and a seasonal parking lot. Without that package, designers invent lifestyle slogans that fight your keyword strategy on the product page.

Related guides

• Write App Titles, Subtitles, and Descriptions
• Screenshots and Preview Videos That Convert
• Apple App Store vs Google Play ASO
• Arabic Localization for App Stores
• ASO for UAE Apps: Start Here
• Meta Ads for UAE Businesses: Start Here

---

Part of the Dubai Marketing Playbook by Shabang — practical marketing for UAE businesses.