Keyword Indexation on iOS: How the App Store Reads Your Metadata

October 21, 2026

Keyword Indexation on iOS: How the App Store Reads Your Metadata

Keyword Indexation on iOS: How the App Store Reads Your Metadata

App listing and keyword analytics on cover

On iOS, keyword indexation comes down to a small set of fields that Apple reads when it decides which searches your app can appear for. Your app name, subtitle and the hidden keyword field make up a 160-character budget per localization. Every word you place there is a chance to rank. Every wasted character is a search you hand to a competitor.

This guide explains what gets indexed, how to spend the budget, what Apple does not show you, and how to verify that your changes worked.

Apptenium
Track Your App’s Keyword Visibility
Apptenium combines keyword tracking and ASO scanning to help you monitor app visibility and performance across major app stores.
Explore Apptenium

TL;DR

  • Apple’s indexed metadata budget is 160 characters per localization: 30 for the app name, 30 for the subtitle and 100 bytes for the keyword field.
  • Don’t repeat words across fields, and skip plurals, filler words and spaces after commas. They consume space and add nothing.
  • App Store Connect does not report organic search terms, so you have to combine Apple Ads data with rank tracking to see what is working.
  • Custom product pages let you attach specific keywords to tailored page versions, which extends your reach past the default listing.
  • Treat indexation as a loop: write, ship, measure rank and conversion, then revise.

Table of Contents

What keyword indexation means on iOS

Indexation is the process by which the App Store decides that your app is relevant to a query. If a word is not indexed for your app, you will not rank for it, no matter how good your product is. If it is indexed, ranking then depends on relevance, competition and how well your page converts.

This is different from Google Play, where the long description is read as a ranking signal. On the App Store, the description is written for people. The fields that drive indexation are short, structured and, in one case, invisible to users. That makes iOS both more constrained and more predictable once you understand the rules.

Apple states that keywords help determine where your app displays in search results, so they deserve deliberate choices rather than a last-minute brainstorm before submission.

The fields that count

Here is the practical map of what you control.

Field Limit Visible to users Notes
App name 30 characters Yes Your strongest placement. Lead with your brand, then one or two high-value terms
Subtitle 30 characters Yes Reads as a short value statement. Combine with name keywords, don’t repeat them
Keyword field 100 bytes No Comma-separated terms. No spaces, no repeats

The limits above come from Apple’s platform version information reference, which also warns against plurals, filler words such as “the” and “to”, and repeating words already in your name or category.

Two details trip people up:

  1. Commas count toward the 100 characters. A space after a comma is pure waste, so write budget,tracker,expenses and never budget, tracker, expenses.
  2. Words combine across fields. Your name, subtitle and keyword field are read together for multi-word searches. If your name contains “Budget” and your keyword field contains “planner”, the app can still be a candidate for “budget planner”. You do not need the phrase written out anywhere.

That second point is the biggest lever. Once a word appears in one field, it is covered. Spending it again in another field is the most common indexation mistake we see.

How to spend the 160 characters

Start with a list of candidate terms, then place each one exactly once.

Step 1: Build a candidate list

Collect terms from your own product vocabulary, from the way users describe the problem in reviews, and from the listings of apps that rank above you. Group them into clusters by intent: what the app does, who it is for, and what outcome it produces.

Step 2: Balance reach and competition

Apple’s own guidance on search notes that broad, functional terms such as “social” may bring plenty of traffic but are very competitive for smaller apps, while more specific terms often convert better because they match clear user intent. For a new or mid-sized app, that argues for building organic traction on specific terms first and moving to the head terms later.

A simple scoring approach helps:

  • Relevance: would a user who searches this term be happy to land on your app? If not, drop it.
  • Popularity: is anyone actually searching for it?
  • Difficulty: can an app with your ratings and install volume realistically compete?

Keep terms that are relevant, reasonably popular and winnable. Park the rest.

Step 3: Assign terms to fields

Put the highest-value term in the name, since it carries the most weight. Use the subtitle for a second cluster, written so that it still reads naturally to a human. Fill the keyword field with everything else, in singular form, with no repeats.

How keywords are assigned across metadata fields

Step 4: Check the draft

Before you submit, run a quick audit:

  • Does any word appear in more than one field?
  • Are there plurals you can collapse into singulars?
  • Are there filler words, spaces after commas or trailing commas?
  • Is the subtitle still a sentence a real person would want to read?

If you want a fast way to check, the free ASO tools on our site include a scanner and a word frequency tool that flag repeated terms in your listing.

A worked example

Imagine a habit-tracking app called “Streaklane”. A first draft might look like this:

  • Name: Streaklane: Habit Tracker
  • Subtitle: Daily Habit Tracker & Goals
  • Keywords: habit, habits, tracker, goal, goals, daily routine, planner

The problems are plain once you list them. “Habit” and “tracker” appear in the name and again in the subtitle, then again in the keyword field. “Habits” and “goals” are plurals. There is a space inside “daily routine”. Roughly half of the keyword field is duplicated.

A tighter version:

  • Name: Streaklane: Habit Tracker
  • Subtitle: Daily Goals & Routine Planner
  • Keywords: streak,reminder,journal,productivity,self,improvement,checklist,motivation,wellness,challenge

The name and subtitle together cover “habit tracker”, “daily goals”, “routine planner” and combinations of them. The keyword field is now spent entirely on new terms. The example is illustrative, but the pattern holds for any app: every word placed once, every character working.

What Apple does not show you

This is where many teams get stuck. App Store Connect analytics reports conversion rate, defined as downloads and pre-orders divided by unique device impressions, and data only appears once an app reaches a threshold of five first-time downloads. It does not tell you which organic search terms drove those installs. Apple’s developer forums confirm the gap: there is no way to see the exact queries behind organic installs.

Two consequences follow.

First, be skeptical of any tool that claims to show you your exact organic search terms. Those figures are estimates built from models, not official Apple data. Estimates are still useful for direction, but treat them as such.

Second, you need a deliberate way to learn what works. The reliable approaches are tracking your rank for a defined keyword set over time, and using Apple’s own paid search data as a discovery channel.

Use Apple Ads to find terms worth indexing

Apple Ads is the only place Apple gives you real search-term data. Its Search Match feature automatically matches your ads to relevant searches, which surfaces terms you may not have considered. Apple also provides Search Popularity scores from 1 to 5 for keywords. Apple reports that ads at the top of search results deliver an average conversion rate above 60%, a sign of how strong intent is on the App Store.

The workflow many professional marketers use:

  1. Run a discovery campaign with Search Match on a modest budget.
  2. Review the search terms that produced taps and installs.
  3. Move the winners into manual campaigns.
  4. Fold the best performers into your name, subtitle or keyword field at your next version.

Apple’s keyword best practices for ads describe the same idea: keywords determine how your ad is matched to searches, and using them well uncovers growth opportunities. If your wider growth plan also depends on being found in web search and AI answer engines, a specialist such as AI search optimization services can cover that side while you focus on the store.

Custom product pages as a keyword extension

You can create up to 70 custom product pages per app, each with its own screenshots, previews, promotional text and keywords. Each page is localizable and shareable through its own URL.

For indexation, the useful part is that a custom product page can carry its own approved keywords. That lets you align a page’s messaging with a specific search intent, for example a page about budgeting for freelancers that is shown for freelancer-related searches. Apple notes that custom product pages must be approved before users see them, so plan for review time.

Don’t treat this as a loophole that replaces the core 160 characters. Think of it as a way to match message to intent once your base metadata is solid.

Localization multiplies the budget

The 160-character limit applies per localization. If your app is available in several storefronts, each localization has its own name, subtitle and keyword field. Some storefronts also read more than one language, so a secondary localization can sometimes add indexed terms for a market. Check which languages each storefront supports before relying on this, and test the effect on rank rather than assuming it.

For English-language apps aimed at the US, the safe baseline is to fill the US English localization completely and well. Extra localizations are an optimization, not a substitute.

Measure whether indexation worked

Changing metadata without measuring is guesswork. After each update, check three things.

Rank for your target set

Track a fixed list of keywords: the ones you placed deliberately, the ones you already ranked for, and a few competitor-owned terms. Look at position, not just presence. A term can be indexed and still sit on page ten.

Conversion rate

Ranking gets impressions, but the page has to convert them. Apple’s product page optimization tests let you split-test icons, screenshots and previews, reporting an estimated lift in conversion rate. Tests can run for up to 90 days, and Apple advises against releasing a new app version mid-test because it can skew the results.

Downstream value

More installs are only a win if they produce revenue, subscriptions or ad income. Marketers who manage ASO in isolation tend to end up with disconnected dashboards that never show how a keyword change affected the business. Connecting listing work to monetization data is what turns ASO from a checklist into a strategy. Our app analytics view is built for exactly that link between downloads, revenue and ad performance.

Common indexation mistakes

  • Repeating words across fields. Once is enough.
  • Stuffing the name. A name that reads like a list of keywords hurts conversion, and conversion feeds back into ranking.
  • Using plurals and filler words. They burn bytes without adding coverage.
  • Chasing only head terms. Your app may sit buried beneath stronger competitors for years.
  • Changing everything at once. You will not know which edit mattered. Change one cluster per release when you can.
  • Ignoring competitors. Their metadata shows you which terms the market considers valuable, and which gaps remain open. Our competitor intelligence page shows how we approach that comparison.

Our perspective

We built Apptenium because the same pattern kept repeating: a team would do careful keyword work in one tool, check ranks in a second, look at downloads in Apple’s dashboard, and pull revenue from a fourth place. By the time the numbers met in a spreadsheet, the next release was already due.

Our perspective — overview diagram

We think indexation is best understood as a feedback loop, not a one-time task. The 160 characters are small enough that every release is a chance to improve them, and the only way to improve with confidence is to see listing changes, rank movement, installs and revenue in the same place. That is why our scanner gives copy-ready fixes from each scan rather than a long report, and why we connect Firebase, Google Analytics and ad network data to listing work.

One caution we repeat to every team: no tool can show you Apple’s private organic query data, ours included. What a good tool can do is shorten the distance between a hypothesis and the evidence. Use Apple Ads to discover, rank tracking to verify, and analytics to decide whether it was worth it.

— Mike

Put it into practice with Apptenium

If you want to check your own listing, start with the free tier, which includes a limited number of scans per month. It lets you scan your metadata, spot repeated words and see where your keyword budget is leaking. When you are ready to track keywords and rivals without limits, Pro is $9.99 per month and adds unlimited scans and premium features. You can also explore our full set of ASO tools for the App Store and Google Play.

FAQ

How many characters does iOS index for keywords?

Apple indexes a 160-character budget per localization: 30 characters for the app name, 30 for the subtitle and 100 bytes for the hidden keyword field, per Apple’s App Store Connect reference. Commas in the keyword field count toward the limit. Avoid spaces after them.

Does the App Store index the description?

The fields Apple’s guidance points to for keywords are the name, subtitle and keyword field. Write your description for people and for conversion rather than for keyword density. Don’t count on it to extend your indexed vocabulary on iOS.

Can I see which search terms bring me organic installs on iOS?

No. App Store Connect does not report organic search terms. The only official search-term data comes from Apple Ads, so many teams run discovery campaigns and then add the winning terms to their metadata. Tools that claim exact organic queries are estimating.

How often should I update my keywords?

Every app version is a chance to revise, but changing too much at once hides the cause of any rank shift. Update one cluster per release, wait long enough to see rank and conversion settle, then decide on the next change.

Sources

← Back to Guides · Home