Skip to content
Owais KhanSoftware Reviews
Free browser tool

App Store Keyword Field Deduplicator

Paste your metadata, get back a keyword field with nothing Apple already indexes.

Apple gives you 100 characters for keywords and indexes your app name, subtitle and categories separately. Any word that appears in those fields is already working for you, so repeating it in the keyword field buys no extra weight — it just spends characters you cannot get back. The same goes for plurals of words you already have, for filler words likethe, for generic terms like app, and for the space most people type after every comma. Finding all of that by eye, across four fields, is exactly the kind of cross-referencing people do badly.

This tool does it in one pass and tells you which field caused each removal, so you can disagree with any of them. It is an app store keyword field counter and anASO keyword deduplicator in one: an iOS keyword field optimizerthat works as an App Store 100 character keyword field cleaner and anApple keyword field strategy tool — without downloading anything.

Your data never leaves your browser. All processing happens locally. Nothing you paste is uploaded, logged or stored, and the tool issues no network request of any kind — disconnect the network and it still works.

Clean your App Store keyword field

Comma-separated. Cleaned as you type.

Options

Cleaned keyword field

runner,gps,jogging,marathon,training,cardio,exercise,steps,pace

63 / 100 characters93 characters saved

Removed (11)

TermWhy
runAlready in App Name
runningAlready in Subtitle
trackerAlready in App Name
trackersPlural of an indexed word
fitnessAlready in Primary Category
workoutAlready in Subtitle
healthAlready in Primary Category
sportsAlready in Secondary Category
appGeneric term
theFiller word
cardioRepeated in this field

How it works

Every rule below comes from Apple's own search guidance, and each one is applied conservatively: when a rule does not clearly apply, the keyword is kept. Deleting a term Apple was not already indexing costs you a ranking word silently, which is far worse than leaving a few characters on the table.

  1. Your indexed words are collected from the app name, subtitle, primary category and secondary category.
  2. Keywords matching those words are removed, and the tool tells you which field caused each removal.
  3. A multi-word phrase is only removed when every word in it is already indexed.Partial overlap is kept, because the phrase still buys a term the other fields do not cover.
  4. Plural duplicates are folded — but only when the fold is safe. Words likefitness, news and class merely end in “s” and are left alone.
  5. Filler and generic terms are dropped, and the field is rejoined with commas and no spaces.

The Apple keyword field rules this tool applies

RuleWhy it matters
Separate terms with commas and no spacesA space after a comma costs one of your 100 characters and adds nothing.
Do not repeat words from the app name, subtitle or categoryAll are indexed already. Repeating a word does not increase its weight.
Do not include plurals of words you already haveApple gives "climbs" and "climb" as an example of a duplicate pair.
Skip generic termsWords like "app" and "game" are too broad to rank for.
Skip filler wordsWords like "the" and "to" add no value.
Spaces are allowed inside a keyword phraseApple’s own example is Property,House,Real Estate.

Why an app store keyword field counter alone is not enough

Most web tools for this field count characters and stop. Counting tells you that you are over 100; it does not tell you which terms to cut. The useful question is which of your keywords are already covered by your title, subtitle and categories — and that needs all four fields cross-referenced at once, which is what this ASO keyword deduplicator does. The alternative currently ranking for these searches is a native iOS app you have to download, which is an odd requirement for work you are doing at a desk in App Store Connect.

Where these rules come from

The character limit, the comma formatting, the indexed fields and the plural guidance are all taken fromApple's App Store search documentation. The caveat about plural matching being imperfect comes from published ASO testing rather than from Apple, and is flagged as such in the FAQ. If Apple changes the rules, this tool is wrong until its tables are updated — check the source if something here contradicts what App Store Connect tells you.

More utilities: all free developer tools.

Frequently asked questions

Does Apple automatically index words from my App Name and Subtitle?
Yes. Apple states that search results are based on “text relevance (matches for your app’s title, subtitle, keywords, and primary category)”, and its guidance tells you not to repeat any words already included in your app name, subtitle or category. A word sitting in your title is already working for you, so spending characters on it again in the 100-character keyword field buys nothing — it does not add weight or rank you higher. Note the part most tools miss: your primary category and your optional secondary category are indexed too. If your app is in Health & Fitness, the words “health” and “fitness” are already covered, and this tool removes them for you along with the name and subtitle overlaps.
Do spaces after commas count toward the 100-character App Store keyword limit?
Yes, and they are the cheapest characters you will ever get back. Apple’s own instruction is that keywords are “limited to 100 characters total, with terms separated by commas and no spaces”. Every space you type after a comma consumes one of your 100 characters and does nothing. On a field with twenty terms that is nineteen wasted characters, which is roughly two extra keywords. This tool always rejoins your terms with commas and no spaces. One important exception: spaces inside a keyword phrase are legitimate and are preserved. Apple’s documented example is “Property,House,Real Estate” — collapsing that phrase to “realestate” would stop it matching altogether.
Should I put plural forms of words in the iOS keyword field?
Generally no. Apple explicitly lists “plurals of words you’ve already included, such as ‘climbs’ and ‘climb’” as duplicates to avoid, so including both usually wastes characters. That is why plural folding is on by default here. It is worth knowing the limits, though. AppTweak’s testing found that while apps generally rank similarly on singular and plural forms, the overlap is not perfect — in one comparison two of the top ten results for a singular term did not appear in the top ten for its plural. Apple’s handling is also weaker outside English. So this is a toggle, not a rule: if you have characters to spare and a plural is a genuinely high-volume term in your market, switch plural removal off and keep both.
How does keyword deduplication work across multi-language localizations on iOS?
Each localization has its own separate 100-character keyword field, so deduplication is per-localization: the words in your English app name do not stop you using them in your German keywords. Where it gets useful is that some storefronts index more than one localization at once. An App Store account viewing the US storefront in English is generally matched against the English (U.S.) metadata, while several storefronts also draw on English (U.K.) or a second regional Spanish or Portuguese localization. Developers exploit that by filling the extra localization with entirely different keywords rather than a translation, effectively doubling the field. This tool works on one localization at a time — run it once per field, and paste each field’s own name, subtitle and categories so the overlap it removes is the right one for that locale.
Is my keyword data uploaded or processed on a server?
No. Everything runs in your browser using JavaScript served with the page, and the tool issues no network request of any kind — this site has no backend to send anything to. You can verify it in your browser devtools: open the Network tab and clean a keyword field, and you will see no request carrying your input. For completeness, the one request you may see is a Cloudflare analytics beacon to /cdn-cgi/rum on this same domain, which the host adds to report anonymous page-load timings; it fires on page load, never reads the form, and never sees your keywords. Disconnect the network entirely and the tool still works, which is the simplest way to prove the point to yourself.