Skip to content

App Store keyword field: choose, format, and test your terms

The App Store keyword field gives you 100 characters to describe relevant searches without displaying that list to customers. Build it from the tasks your app actually solves, coordinate it with your name and subtitle, and record what you change so the next release teaches you something.

AppNorth ·

App Store keyword field rules and comma formatting

The 100 character keyword field is a compact metadata field, not a sentence or a public feature list. Separate entries with commas and remove spaces around those commas. For example, “rent,bills,roommates” uses the space more efficiently than “rent, bills, roommates”. Count punctuation as part of your budget and check the final value in App Store Connect before saving it.

Spaces inside an intentional keyword phrase are different from padding after a comma: Apple allows them. Decide whether the phrase needs to stay together rather than deleting every space mechanically. Do not assume that a comma guarantees every possible combination will rank. Formatting makes the field valid; relevance and the searches you later observe determine whether your choices were useful.

Choose tasks before choosing popular words

Start with a short product brief: who uses the app, what they do, and which capabilities are already available. Turn each task into a few searches. For an imaginary expense app, “split rent” and “trip expenses” describe different situations even though both involve money. Search those phrases in the country you want to reach and inspect whether the results serve the same audience.

Keep a candidate only if you can connect it to a real screen or workflow. A budget planner should not target invoice creation simply because both belong to finance. Compare broad category language with narrower use cases, then choose a manageable focus. A smaller set of relevant searches gives you a clearer release hypothesis than a field filled with loosely related vocabulary.

  • Write the user task beside each candidate search.
  • Check the apps ranking in the intended country.
  • Exclude unsupported features and competing app names.

Remove duplication across the name and subtitle

Read the app name, subtitle, and keyword field together before counting remaining space. Apple advises against repeating words already included in the name, subtitle, or category. If the name contains “Trip Expenses”, spending keyword space on those same words adds no new vocabulary. Use the field for relevant concepts that your visible copy could not explain naturally within its own limits.

Among app store keywords best practices, removing duplicates is often more useful than finding another synonym. Avoid adding both a singular word and its plural just to fill the field, and remove filler such as “app”. Do not shorten meaningful words into obscure fragments to squeeze in extra entries. If you cannot identify another relevant term, leaving unused space is a reasonable decision.

Research local wording instead of translating a list

Build a separate shortlist for each language you maintain. A direct translation can preserve the dictionary meaning while missing the expression people use for the task. For a Spanish expense app, compare the actual use cases behind “repartir gastos” and “dividir cuentas” rather than treating either as an automatic replacement for an English phrase. The right choice depends on the app and the audience.

Check the country as well as the language. Save the intended storefront beside each search so you do not compare results from unrelated markets. Keep a note explaining unusual wording, especially when a native reviewer changes a literal translation. Avoid adding extra localizations solely on the assumption that all their terms will expand visibility in every country; verify the searches that matter to you.

Make one release answer a focused question

Save the previous name, subtitle, keyword field, and target searches before editing. Write a specific reason for the change, such as replacing generic finance words with roommate expense tasks. Keep useful existing terms unless there is a reason to remove them. Rewriting everything simultaneously may be appropriate for a repositioning, but it makes the contribution of any single field harder to understand.

After the metadata is live, monitor the same searches in the same countries and keep the release date in your notes. Review visibility alongside the download and product page information available to you. A ranking change alone does not establish causation: competition, demand, and other listing changes can move too. Do not promise yourself a fixed ranking or a universal number of days for improvement.

Build and review the shortlist in AppNorth

AppNorth is a Mac app with App Store keyword research across all 175 App Store countries, including research before you have a published app. Popularity uses Apple’s official Apple Ads data only after you connect your own Apple Ads account; otherwise it shows “—”. Difficulty is an AppNorth signal based on the ranking apps. Use both as context for your shortlist, not as a forecast of downloads.

Set a product brief and a “Don’t target” list, then use Optimize to compare three AI drafts for name, subtitle, and keywords against the current listing. The drafts stay within Apple’s character limits and are scored by reach and difficulty. AI runs through your own supported CLI, with your provider’s terms and costs. Review the wording before approving a draft, especially a suggestion outside your main use case.

AppNorth fills an App Store Connect draft version with approved changes and never submits your app for review. Complete that release step yourself, then follow tracked iPhone positions by keyword and country, up to position 250, with daily history. Save your hypothesis separately so you can interpret the history in context. The workflow supports a considered experiment; it does not make a keyword placement a ranking guarantee.

A compact keyword field review
CheckWhat to do
SeparatorsUse commas without padding around them.
Duplicate termsCompare against the name, subtitle, and category.
RelevanceConnect every entry to an available feature.
Local wordingReview searches in the intended language and country.

Before you start

Should App Store keywords use commas or spaces?

Use commas between entries without spaces immediately before or after the separators. A space inside a keyword phrase is allowed, so phrase spacing is a separate choice. Check each separator after pasting or editing the list, especially if it came from a document. Confirm in App Store Connect that the final value fits and is accepted.

Should I repeat keywords from my app name?

Apple advises against repeating words from the app name, subtitle, or category in the keyword field. Audit all three fields together before adding more terms. If you later remove a useful word from the subtitle, reconsider whether it belongs in the keyword field. Maintain the complete metadata set so a future edit does not silently lose or duplicate important vocabulary.

Do I have to use all 100 characters?

No. Treat the limit as a ceiling rather than a quota. First remove duplicates, irrelevant terms, and unsupported feature claims; then evaluate additional relevant candidates. A shorter field you can justify is preferable to filling the last characters with noise. The goal is a defensible set of search intents that you can observe after release, not a full character counter.

Can I put competitor names in the keyword field?

Apple’s guidance excludes competing app names and unauthorized protected terms. Use competitors to understand the tasks, categories, and language in the market, then describe your own functionality with relevant generic terms. Do not copy a rival’s brand into the field just because their audience overlaps with yours. Review generated suggestions before saving them, as plausible wording can still be inappropriate.

Does Google Play have the same keyword field?

Do not copy this comma-separated field into a Google Play description. This guide concerns Apple’s specific metadata field; an Android listing needs its own writing and research decisions. You can reuse your understanding of user tasks, but rebuild the actual store copy for that audience. AppNorth supports Google Play keyword research too, while these formatting rules remain specific to the App Store.

Sources and further reading

AppNorth · macOS

Turn your research into a better listing.

€99.99 once. Lifetime license for 2 Macs, with updates included.

AI features use your own agent CLI: Claude Code, Codex, Gemini CLI, OpenCode, Cursor, Grok or Ollama. No AppNorth AI credits; your provider’s terms and costs still apply.

See AppNorth for Mac

macOS only. No free tier or trial. No voluntary refunds; legal exceptions apply. Read the refund policy.