The keyword field

Expert: with sources and numbers. Plain: the same, without them, for beginners.

The hidden 100-byte field. Apple's own rules for it, the bytes-versus-characters question, and how to spend it.

Verified 2026-09-20 · 36 days ago ios metadata keywords indexing

A comma-separated list, invisible to users, set per localization, read by search. It is the only iOS field that exists purely for ranking, which makes it the one place where you can be entirely mechanical.

The rules

Apple’s own description of the field is short and contains four separate rules worth separating out.

A The field holds 100 characters. (Creating your product page, verified 2026-09-19)

A Each keyword must be greater than two characters. Same source.

A The app name and the company name are already searchable, so they should not be duplicated in the keyword list. Same source. This is Apple confirming that the developer name is an indexed surface. See 10-06.

A Names of other apps or companies are not allowed. Same source, and reinforced by App Review Guideline 2.3.7, which prohibits packing metadata with trademarked terms or popular app names. See 30-07 for the trademark exposure this carries.

A The field is localizable and not editable without a new app version. See 10-09.

A Apple states it may modify inappropriate keywords or take other steps to prevent abuse. (Guideline 2.3.7)

A Apple publishes an explicit list of what wastes the field. To maximise the number of words that fit, avoid plurals of words already included in singular form, names of categories and the word “app”, duplicate words, and special characters such as # or @ unless they are part of your brand identity. Apple adds that special characters carry no extra weight in search. (Creating your product page, verified 2026-09-20)

The plurals line is the important one, and it is stronger than the advice usually given for it. Apple telling you not to include a plural you already have in singular is Apple saying the store matches them. That makes it documented rather than folklore, with a real caveat outside English, in CONFLICT-022.

A On separators: terms are comma-separated with no spaces, but a space may be used inside a keyword phrase. Apple’s own example is Property,House,Real Estate. Same source. So a multi-word phrase is permitted; whether it is a good use of the field is a separate question (30-04).

The bytes wording in Apple’s reference, resolved

Apple’s two pages do not agree, and the discrepancy is worth knowing about because it will come back.

For English these are identical. For anything else they would not be: in UTF-8 a CJK character costs 3 bytes, so a strict byte ceiling would mean roughly 33 Chinese characters rather than 100, a threefold difference in some of the largest storefronts in the world.

The working limit is 100 characters, confirmed from App Store Connect use including in non-Latin locales. The reference page’s “bytes” wording is an inconsistency in Apple’s documentation, not the operative limit.

Recorded rather than deleted, so nobody re-derives the byte theory from Apple’s reference page in a year’s time. Full account in CONFLICT-004.

How to work with it

No spaces after commas. A space is a character, and you have 100.

Single words, not phrases. The store combines terms across fields to match multi-word queries, so writing photo editor spends 13 characters to buy what photo,editor buys for 12 while also contributing to other combinations. See 30-04.

Never repeat a word. Repetition adds nothing and costs characters.

Leave out your app name and developer name. Apple says so directly, and it is the most common way people waste a third of the field.

Leave out category names you already rank for by category. Both categories are indexed (10-08), so spending bytes on the category label is usually a duplicate.

Leave out plurals where the singular is present. But verify this per locale rather than assuming it. B Practitioners consistently report that iOS handles simple English plural matching without a separate entry; this is not documented by Apple, and it does not transfer cleanly to other languages.

Fill it. There is no benefit to leaving characters unused. If terms are scarce, the problem is the research, not the field. See 30-01.

What goes wrong

Spending it on brand. Your name and developer name are already indexed. This is the single most common waste.

Writing phrases. Spends bytes on word order the algorithm does not need.

Competitor names. Prohibited by Apple in two separate places, removable at Apple’s discretion, and a trademark risk that sits with your company rather than with the person who added the keyword.

Changing it and expecting immediate movement. It is bound to a version, so the change ships with a release, and ranking movement follows indexing rather than submission. Measure on the cadence in runbooks/quarterly-keyword-refresh, not the next morning.

Re-deriving the byte theory from Apple’s reference page. It is an inconsistency in Apple’s documentation. The limit is 100 characters.

In short

Every fact on this page in one line, with its evidence tier, source and verification date, 7 A · 1 B. Generated from the claim register, so it cannot drift from the page above.

A Apple's App Store Connect reference states the keyword field holds up to 100 bytes of content, while Apple's product page overview states 100 characters. The working limit is 100 characters.
IOS-KW-001 · verified 2026-09-18
A Each keyword must be greater than two characters.
IOS-KW-002 · verified 2026-09-18
A Apple states the app is searchable by app name and company name, and that these should not be duplicated in the keyword field.
IOS-KW-003 · verified 2026-09-18
A Names of other apps or companies are not allowed in the keyword field.
IOS-KW-004 · verified 2026-09-18
A Apple may modify inappropriate keywords or take other steps to prevent abuse of metadata.
IOS-KW-005 · verified 2026-09-18
A Apple advises maximising the number of words that fit in the 100-character keyword field by avoiding: plurals of words already included in singular form, names of categories and the word 'app', duplicate words, and special characters such as # or @ unless part of the brand identity. Apple states special characters carry no extra weight in search.
IOS-KW-006 · verified 2026-09-20
A The keyword field is a comma-separated list set per localization, holding 100 characters.
IOS-MD-003 · verified 2026-09-18
B iOS handles simple English plural matching without requiring a separate keyword entry. This does not transfer reliably to other languages.
IOS-KWB-002 · verified 2026-09-18

Think your app deserves better?

Send the App Store link.
The audit comes back within two working days, whether you hire us or not.

Free, and we mean it. No card, no call required.