11 New App Store Connect Languages in 2026: New ASO Opportunities for India and Local Markets
Apple made one of its most important localisation changes in recent years on 31 March 2026, when App Store Connect gained support for localised metadata in 11 additional languages. The new list includes Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu, taking the total number of supported App Store localisations to 50. Ten of these additions have direct relevance to India, where a single English-language product page often cannot reflect the linguistic habits of users across different states and regions. For app publishers, this change creates new App Store optimisation opportunities because names, descriptions, keywords, screenshots and other product-page elements can now be adapted for audiences that previously had to rely mainly on English or another supported language. The practical value goes beyond translation: ASO teams can now match search vocabulary, product positioning and visual communication more closely to local user expectations.
What Changed in App Store Connect in 2026
Apple’s March 2026 update introduced Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu as supported metadata languages. Apple specifically highlighted India when announcing the change, which is understandable given the composition of the new language group. Before the update, Hindi was already available, but many other widely used Indian languages could not be selected as dedicated App Store metadata localisations. The change therefore gives publishers much more freedom to prepare product pages for audiences whose preferred language is not English or Hindi. Apple also released corresponding localised App Store badges, allowing the same language to be carried into selected marketing materials outside the store listing.
The current App Store localisation reference illustrates the scale of the change particularly clearly in India. English (U.K.) remains the default language for the Indian storefront, while Apple now lists Bangla, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu and Urdu as additional supported languages. Hindi is the only language in that group that was supported before the 2026 expansion, which means the update added ten new India-relevant metadata options at once. The language displayed to an individual user can depend on several factors, including the storefront, device language settings, the localisations supplied by the developer and the app’s primary language.
The eleventh addition, Slovenian, shows that the update is not exclusively about India. Apple currently lists Slovenian as an additional supported language for Slovenia, where English (U.K.) remains the default. Urdu also extends the relevance of the change beyond India because Apple lists it as an additional supported language in Pakistan. This is important for ASO planning: a localisation should not automatically be treated as synonymous with one country. Language, storefront and user settings interact with each other, so the same metadata can potentially support users in more than one geographical market where Apple makes that language available.
Why Metadata Localisation Matters for App Store Search
Localised metadata matters because language is directly connected with how users formulate searches. Apple states that App Store search considers text relevance, including matches with an app’s name, subtitle, keywords and primary category, alongside behavioural signals such as downloads, ratings and reviews. A company that previously relied on English keywords for India can therefore build language-specific keyword sets that better reflect how users describe the same need in Tamil, Telugu, Marathi or another supported language. This does not mean that translating a high-volume English keyword will automatically improve rankings. It means that ASO teams finally have dedicated metadata fields in which they can test terminology that reflects real local search behaviour.
The available space still needs to be used carefully. An App Store app name can contain no more than 30 characters, and the subtitle is also limited to 30 characters. Apple limits the keyword field and recommends using specific terms related to the app’s actual features rather than broad expressions, repeated words or competitor names. Promotional text should not be treated as an additional keyword field because Apple explicitly states that it does not affect App Store search ranking. These limits make local keyword research more valuable. A short phrase that communicates the right intent in English may have a different length, word order or common form in an Indian language, so literal translation is rarely the strongest ASO method.
Metadata localisation should also be separated from localisation of the app itself. Apple treats the languages added in App Store Connect as product-page metadata, while languages supported inside the app are managed separately during development. An app can therefore have a Tamil product page without automatically having a Tamil user interface. From an ASO perspective, that distinction is important because the store listing should set accurate expectations. If screenshots, captions and descriptions imply that the entire product is available in a language that is not actually supported after installation, an initial improvement in product-page engagement can turn into disappointment, weaker retention or negative reviews. Localisation works best when the listing accurately represents the experience a user will receive.
Building an ASO Strategy for India’s Multilingual Audience
The 2026 change makes it less useful to treat “India localisation” as one task. India can now be approached as a collection of language audiences within the same storefront. An app with strong usage in Tamil Nadu may have a different localisation priority from one whose largest audience is concentrated in Maharashtra, Gujarat, Karnataka or Punjab. A company does not need to publish all ten newly available Indian languages at the same time. A more practical approach is to compare existing users, downloads, customer enquiries, regional marketing activity and the locations in which the product already has meaningful demand, then select the languages that correspond most closely to those signals.
This prioritisation also protects localisation quality. Preparing ten additional sets of names, subtitles, descriptions, keywords and visual captions creates significantly more work than maintaining one English listing. If every language is added at once without adequate review, small errors can spread across many product pages. A staged approach allows teams to put more effort into terminology, cultural context and quality control. For example, an app receiving strong organic demand from Maharashtra could reasonably prioritise Marathi, while an app with an established user base in Karnataka might test Kannada first. The order should come from actual business and user data rather than from a generic list of language popularity.
Search vocabulary deserves separate research for every selected language. People do not necessarily translate English product terminology word for word when they search. Some categories may retain familiar English terms, some may use local-language equivalents, and others may combine the two. Transliteration can also appear in everyday usage. The correct choice depends on the product category and audience rather than on a universal ASO rule. Keyword research should therefore include existing search data where available, customer-support language, competitor category terminology, user interviews or reviews, and checks by native speakers who understand the subject. The aim is to identify phrases people genuinely use, not simply produce grammatically correct translations.
Localising Names, Keywords and Screenshots Without Losing Intent
The app name and subtitle require particular care because they are highly visible and have strict length limits. A brand name will usually remain unchanged, while the descriptive part around it may need adaptation. Trying to reproduce an English subtitle word for word can waste limited space or produce wording that feels unnatural. The better question is what a local user should understand within the first few seconds: the core function, the category or the main reason the app is relevant to the search. Because Apple includes the title and subtitle among the signals used for text relevance, these fields should communicate meaning first rather than act as containers for as many search terms as possible.
The keyword field should then complement the visible metadata rather than repeat it. Apple advises developers not to duplicate terms already present in the app name, subtitle or category and prohibits irrelevant terms, competing app names and unauthorised protected names. For a new Indian-language localisation, this makes keyword selection a process of allocating limited space to additional search intentions. A finance app, learning service, photo editor or travel tool may each require a different balance between broad category language and narrower feature-specific phrases. Local search terms should describe functions that really exist in the product. Adding popular but unrelated words may bring irrelevant visibility and can also create App Review problems.
Screenshots deserve the same level of localisation as written metadata because search visibility alone does not create downloads. Apple allows localised screenshots and app previews, and these visual elements can appear both on the product page and in search results. Caption text can be rewritten around the needs of a Tamil-, Gujarati- or Telugu-speaking audience, while examples shown inside the images can be adjusted where appropriate. At the same time, visuals should remain truthful. If the interface itself is still English, presenting a completely translated fictional interface in the screenshots can create the wrong expectation. A more transparent approach is to localise explanatory captions while showing the product as users will actually see it after installation.
Measuring Local ASO Performance and Scaling Beyond India
Publishing new localisations should be treated as the beginning of an ASO test rather than the end of a translation project. Before changing a major language set, teams should record a baseline for the metrics they already follow. Apple recommends using App Analytics in App Store Connect to review indicators such as impressions, conversion rate and downloads, with source-type filtering available for closer analysis of search performance. If a new localisation produces more impressions but conversion does not improve, the problem may lie in the product-page message, visual presentation or mismatch between keywords and user intent. If both visibility and conversion improve, the language may justify further investment in content and in-app support.
Measurement should also account for the fact that ASO results are influenced by more than metadata. Apple says search results consider behavioural factors such as downloads, ratings and reviews in addition to text relevance. A new keyword set therefore cannot be evaluated in isolation from product quality, brand demand, paid acquisition or changes in user feedback. An app entering a new language audience with few reviews and limited recognition may need time to establish stable performance. The useful comparison is not simply whether a localised keyword ranks immediately, but whether the new listing increases relevant visibility and turns a reasonable proportion of that visibility into product-page engagement and downloads.
The language expansion also creates opportunities to think beyond a single-country ASO plan. Slovenian now gives publishers a dedicated localisation for users in Slovenia, while Urdu is supported for both India and Pakistan according to Apple’s current storefront reference. The wider lesson is that localisation strategy should begin with Apple’s actual language-to-storefront mapping rather than an assumption based only on national borders. Some languages can contribute to more than one market, while others have highly concentrated value. This makes language prioritisation useful for smaller teams: instead of translating every listing everywhere, they can identify the localisations where existing demand, product relevance and available resources form the strongest combination.
A Practical 2026 Rollout Plan for ASO Teams
A sensible first stage is an audit of the existing listing. Record the current app name, subtitle, keyword set, description, screenshots, search performance and main sources of downloads. Then compare this information with the regions and languages already visible in customer data. The 2026 additions should be considered where there is evidence of an audience that could benefit from them. For an India-focused app, that may mean ranking Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu and Urdu by commercial relevance and localisation readiness. Hindi should be reviewed at the same time because it remains part of Apple’s supported Indian language set even though it was not one of the 11 additions announced in March.
The second stage is to launch a manageable number of localisations and review each one as a complete product page. App Store Connect allows developers to enter localised descriptions and keywords and to provide localised app information such as the name. Apple notes that when a new language is added, several properties and screenshots may initially inherit content from the primary language, while the description and keywords require their own entries. This makes quality assurance essential before submission. Names should fit the character limit, keyword choices should reflect actual search intent, captions should match the screenshots and every product claim should remain consistent with the app itself. Apple states that the new localised metadata can be added with the next version submission.
The final stage is continuous refinement based on evidence. Compare search impressions, downloads and conversion behaviour after localisation, check whether local users understand the product page, and revise language that performs poorly instead of assuming the first translation is permanent. A localisation that generates little relevant demand may be deprioritised, while one that brings qualified users can justify better screenshots, deeper in-app language support and additional regional marketing. Apple’s 2026 language expansion does not guarantee higher rankings or downloads, but it removes an important limitation that previously prevented many local audiences from receiving dedicated metadata. For ASO teams, the strongest opportunity is therefore precision: matching the right language, search intent and product message to audiences that can now be addressed directly in App Store Connect.
