Branded vs Generic Keywords on the App Store

Your brand and a generic word are not the same kind of keyword, and they do not belong in the same slot. The brand is a query you want to own: someone hears “Inkwell,” searches it, and should find you, not a dictionary result and not a competitor who stuffed your name. A generic is a query you share with everyone who built a similar job: “focus timer,” “pomodoro,” “deep work.” You will not own those. You can still be eligible for them.

The 160-character indexed budget is how you keep them apart. Name, 30. Subtitle, 30. Keyword field, 100. Apple’s rules, including the ban on competing app names and celebrity names, are on Creating your product page . This article is the split. The comma-level rules for the hidden field are in the keyword field guide, and the recall-versus-search naming decision is in how to name an app.

Your brand belongs in the name

If the brand is not in the name, you are asking the keyword field to do a job the search result will not show. The field is invisible. A person who was told the name and types it should see that name in the result, spelled the way they heard it. Put the brand at the front. Do not bury it in keyword position eight behind a string of generics, and do not assume the subtitle is a good enough home. The subtitle can help. The name is what they are matching with their eyes.

Protect that query by not letting it get diluted. Do not add a second brand, a pun on a famous app, or a celebrity who writes. “Inkwell” is yours to type into the name. Someone else’s product name is not a brand strategy. It is their brand, and Apple treats unauthorized use of competitor names as an improper keyword and a common rejection reason.

Competitor brands are not generic keywords

A generic describes a job: timer, draft, deadline. A competitor brand names a company. Developers blur them because the competitor brand has demand and the generic feels hard. The blur is the rejection. Apple’s product-page guidance says not to use competing app names, unauthorized trademarks, or celebrity names in keywords. “Like Forest, but for novelists” can be a sentence in a private note. It cannot be a subtitle, a keyword, or a screenshot caption that exists to piggyback.

You also cannot see whether a competitor ranked because of their brand demand or because of a hidden keyword. Copying the brand into your field does not copy their history. If you want to know which generic queries are even worth contesting, research them from autocomplete and from your own Analytics later. The method is App Store keyword research. Paid ads are a separate system and do not write those generics into the organic field, which is the point of Apple Search Ads vs organic ASO.

Generics are how non-brand search finds you

Most people who need a focus timer do not know your brand. They type the job, a method, or a situation: pomodoro, deep work, a chapter, a deadline. Those words are contested because every focus app wants them, and Apple does not publish a weight that says metadata beats downloads. Eligibility is still binary in one sense: if the word is not in your 160 characters, you are not in that conversation. If it is, you still may sit under apps with years of history.

That is why a new app should spend generics on terms it can convert, not on the single most famous word in the category if the screenshot cannot win the tap. “Pomodoro” is fair if the timer uses that pattern and screenshot one shows a work interval and a break. “Productivity” is a category costume. It matches everyone and convinces no one. Specific generics are still generic. They are just specific enough that your frame can prove them.

A 30 + 30 + 100 split for a writer’s focus timer

The sample app is a focus timer for people drafting long work: intervals, a break, and a session aimed at a chapter rather than an inbox. The brand is Inkwell. This split keeps the brand alone in the name so the brand query is unambiguous, puts the job in the subtitle where it is still indexed and still visible, and spends the hidden field on generics. The name is only 7 characters, so you could move the job up into the name instead. That tradeoff is the naming article. Here is the brand / job / generics version, counted.

The brand owns the name, the job owns the subtitle, and the keyword field spends 99 characters on generics that do not repeat focus, timer, or writers.

Words already spent: inkwell, focus, timer, for, writers. None of those return in the keyword field. “deep work” and “word count” keep their internal spaces. There is no space after commas. One character is unused. Leave it unused rather than adding “app” or a plural of “draft.” If a better noun shows up in reviews, that character plus a cut elsewhere can hold it on the next version.

When a generic is too contested for the name

“Timer” and “focus” are in the subtitle here, so they are indexed, and they are visible under the brand. Putting them in the name as well would repeat the words and, if you only have 30 characters, would push the brand out. For a launch with zero brand searches, repeating is still wrong, but hiding the job can also be wrong. If you choose “Inkwell: Focus Timer” as the name, the subtitle must change, because focus and timer would already be spent. Do not keep both versions at once.

A generic earns the name only when it is the one job you want every search result to display, and the brand still fits. A generic stays in the field when it is a neighbor: draft, deadline, pomodoro. A generic you cannot screenshot does not earn any slot. New apps feel this more, because they have no history to compensate for a vague page. That constraint is ASO with zero downloads. Count every candidate in the ASO Character Counter after you delete duplicates.

What the screenshot owes each kind of query

A brand search already decided to look for you. Screenshot one can assume they want Inkwell and show the timer they were told about. A generic search has not decided. Screenshot one has to answer “focus timer” without relying on the brand mark to do the explaining: an interval on screen, a break coming next, a chapter named in the session. If the first frame is a manifesto about writing, the generic tap leaves.

• Brand query: the name on the result matches what they heard. The icon matches the word.
• Job query from the subtitle: the first screenshot shows a timer, not a quote.
• Neighbor from the field, such as pomodoro or deadline: a later screenshot can prove it if you have room. If you cannot show it, do not keyword it.
• Competitor brand: nowhere. Not in the name, not in the field, not in a caption that says “alternative to.”