What to know
Apple limits the keyword field to 100 bytes. That is a byte limit, not always a character limit. Use commas to separate terms and keep the field focused on words that describe the app’s useful function.
Do not repeat words already in the app name or company name. Do not add another app name, a competitor brand, or a claim the app cannot support. Relevance matters more than filling every last byte.
Build the field from phrases that describe a real feature or task. Remove filler words, punctuation that does not separate terms, and duplicate word roots where Apple’s current guidance says they add no value. Keep the list readable enough for another person to audit.
Keep paid-search research and organic metadata connected but separate. A keyword that matches an ad can still be wrong for the organic listing. Record whether a term came from Apple Search Ads, App Store suggestions, a review, a support question, or a competitor page.
Group duplicates, remove vague words, and validate the final string before publishing. Search demand and competition can change by storefront and language, so review the field after meaningful product changes.
Save the market, language, date, source, final byte count, and reviewer with the release record. If the app has multiple locales, create a separate field for each locale instead of copying one English list into every storefront.
For a simple example, imagine a meal-planning app with terms for weekly menus, grocery lists, and recipes. Put the words that describe those tasks into separate candidates, remove terms already covered by visible metadata, then choose the remaining phrases that match the app’s real workflow. Do not add “best,” a competitor name, or a broad category word just to fill space.
Validate in a fixed order: normalize punctuation, remove duplicates and prohibited terms, calculate UTF-8 bytes, compare the string with the current Apple guidance, then ask a reviewer to read the final field beside the product brief. Save the rejected candidates too. They explain why a short field is intentional.
Score candidates with a small decision table: user task, product proof, source, storefront, field fit, and reason to keep or reject. This is not a ranking formula. It is a way to make the final 100-byte choice explainable when several relevant phrases compete for the same space.
Keep rejected candidates with a reason such as duplicate, unsupported task, unclear market language, prohibited use, or too broad for the current product. Reopen the log when the app adds a workflow or enters a new storefront instead of silently recycling an old list.
Read the final field beside the visible name, subtitle, description, and first screenshot. The terms should extend the page’s meaning, not create a separate promise. If a phrase needs the app to support a feature the build does not have, remove it even when it fits the byte limit.
Save a byte-count audit row with locale, encoding method, punctuation normalization, final string, measured bytes, rejected candidates, Apple reference date, reviewer, and build. This makes a field-length failure diagnosable instead of a last-minute guess.
Run a controlled recheck when the locale, visible metadata, product workflow, Apple field rule, or supported region changes. Compare the new field with the old decision table and keep the rejected terms so a shorter list remains explainable.
Keep a no-fill decision available. A field that is under the limit is not automatically better. Leave space unused when the remaining candidates are duplicates, unsupported, or likely to mislead the person who reads the full listing.
Use a small comparison when the field feels crowded. A meal-planning app might keep “meal planner” in the visible promise while testing “recipes,” “grocery list,” and “weekly meals” as separate candidates. Choose only the terms supported by the product and the evidence. Do not force all three into a field just because bytes remain.
ASOgenic can help draft and validate this small field, but it should not decide whether a term is true for the app. Keep the private key in the client environment and keep a human approval step before publishing.