FREE ASO TOOL · NO SIGNUP · NO JAVASCRIPT NEEDED

ASO metadata checker.

Start with a public App Store or Google Play link, or check your own draft. Count fields, review keyword repetition and check UTF-8 bytes before your next listing update.

Start with your store link

Import the public app name into the draft. The result shows a description excerpt and clearly marks fields that still need your input.

No account needed. RateMyApp fetches public store data. Private keywords and subtitles are not guessed. The import never lists an app or changes a store page.

Custom App Store and Google Play pages use the manual checker. Enter that page’s exact text; its custom link stays with your testing handoff.

Check the complete draft

Writing the Android field? Try six editable Google Play short description examples.

Your metadata review

Submit the fields to see counts and editing checks. Input is processed by RateMyApp to return this page; the checker does not save a draft or place it in the URL.

Does the app deliver what the listing promises?

A field can fit its limit while leaving a new user confused. Ask testers to try the feature your listing leads with and report where the experience differs. RateMyApp supports private feedback; public store ratings remain voluntary and independent.

List your app for feedback Build a testing brief

What a public store-link check can tell you

A link can provide a public name and a description excerpt. The checker copies the name into the editable draft and counts its length. For an App Store link, it requests the linked storefront; an unavailable storefront stays unavailable rather than silently switching to another market. For Google Play, the requested language is shown in the result.

Other fields still need the exact text from your store console. A public excerpt can be shorter than the full description, so it is shown as context and never used to claim that the full field passes its limit. TestFlight invitation links have no public listing to import. Blocked or unavailable stores leave the manual checker available.

Imported data and submitted drafts are not saved as listings or placed in the page URL. A short-lived request counter limits repeated imports; it uses a daily hash rather than storing a raw IP address. Results remain private to the returned page and are not indexed. Search demand, ownership and ranking improvements require separate evidence.

App Store keyword characters versus bytes

Apple's search guidance describes 100 characters; its platform version reference specifies up to 100 bytes. This checker shows Unicode code points and UTF-8 bytes separately and flags keywords exceeding 100 bytes. ASCII characters use one byte each; accented letters and many other scripts can use more. Spaces and commas count. Validate the exact final draft in App Store Connect.

Try the editable keyword character and byte examples to compare ASCII, accented text, Chinese text and emoji. These synthetic inputs demonstrate counting, not recommended keywords.

Google Play field limits

The planning checks use 30 characters for the name, 80 for the short description and 4,000 for the full description. There is no App Store-style keyword field in this tool's Android workflow. Character counts use Unicode code points. A store can handle emoji or combining sequences differently; its current validation is authoritative.

What gets checked?

For iOS, the checker flags excessive keyword bytes, blank comma entries, words repeated across the field and words also found in the entered name or subtitle. It creates a separator-cleaned draft while preserving the entered wording and repeated terms for your review. Matching normalizes case and compatible Unicode forms; it does not understand all plurals, synonyms or language meaning.

What still needs a person?

Review relevance, claims, paid limits, trademark rights and the audience's language separately. A draft can fit its limits and still promise the wrong feature. These checks do not verify an app, fetch console data, publish metadata or forecast ranking. Inputs are handled to generate the response and are not saved by this tool; use public listing text and keep credentials or personal records out of the fields.

A worked example

For Binder Notes with subtitle Keep your collection organized, the input cards, binder, cards,,échanges contains a repeated cards word, a blank entry and binder overlapping the name. The accented term uses more UTF-8 bytes than visible characters. Review whether every term belongs in that locale before applying any formatting change.

Source checks: October 5, 2026. Apple field reference · Apple search guidance · Google Play field reference.