---
title: Using extra localizations to add keywords on the US App Store
slug: aso-us-storefront-extra-localizations
summary: The US App Store indexes several localizations (incl. Spanish Mexico), so English keywords placed in those localizations' title/subtitle also rank in the US.
domain: mobile-apps
tags: [aso, localization, metadata, app-store, us]
related: [aso-metadata-fields-and-keyword-placement, aso-keyword-selection-criteria, aso-international-localization-opportunities]
sources: [yt:ytAKZDh5eHU]
updated: 2026-10-23
---

# Using extra localizations to add keywords on the US App Store

## TL;DR
- The US App Store on iOS indexes **multiple localizations** (Steve: nine, including Spanish (Mexico); the list has expanded to e.g. Vietnamese, Russian, Portuguese).[^1]
- Writing **English** title/subtitle/keywords into e.g. the Spanish (Mexico) localization helps your **US** rankings.[^2]
- App Masters has used Spanish (Mexico) this way for years; their own app shows US and Spanish (Mexico) localizations both in English, split across target keywords.[^1][^2]
- US + Spanish (Mexico) title and subtitle together fit roughly **6–10 keywords** — the size of Steve's keyword shortlist.[^3]
- Other storefronts overlap too (e.g. Canada: English + French; UK also indexes other localizations).[^1][^2]

## Details
Steve P. Young (February 2026) presents this as a beginner-level but still valid trick.[^1] How to apply:

1. Look up Apple's table of which localizations each storefront supports (he says it's easy to find by searching for it).[^1]
2. Split your shortlist: put the strongest terms in the US title/subtitle, the next tier in the Spanish (Mexico) title/subtitle — avoid repeating the same words so you cover more terms.[^2]
3. Use the extra keyword fields of those localizations for further long-tail terms.

## Disagreements / caveats
- The exact list of localizations indexed per storefront has changed over time (Steve notes it "expanded"); verify against Apple's current documentation.
- Editorial note (not from the source): using a localization for keywords in a language its users don't speak means real Mexican-Spanish users see English metadata; weigh this if that market matters.

## See also
- [[aso-metadata-fields-and-keyword-placement]]
- [[aso-international-localization-opportunities]] — localizing for real non-US markets

[^1]: yt:ytAKZDh5eHU @ 03:36 — Steve P. Young
[^2]: yt:ytAKZDh5eHU @ 04:41 — Steve P. Young
[^3]: yt:ytAKZDh5eHU @ 07:37 — Steve P. Young