What is a good ASO Health score?

In Applyra, 80 and above is Excellent, 65 to 79 is Solid, 45 to 64 is Needs work, and below 45 is Critical. Excellent is a genuine top tier rather than a mark every listing reaches, so Solid is already a good place to be and Excellent is the target.

What is the difference between ASO Health and the visibility score?

ASO Health is the cause and the visibility score is the result. ASO Health grades the listing itself and only moves when you change it. The visibility score grades where you actually rank today and moves every day with the store and the competition.

Why can my ASO Health score not reach 100?

Because rewriting text never moves store appeal. A low appeal axis caps what any rewrite can reach, and Applyra shows you that ceiling next to the score. Raising your rating, filling your screenshot slots or shipping an update is what lifts it.

Why does Applyra say my targeting fit is not measured?

Because the listing holds no word that people actually search on that storefront, so there is no targeting to grade. Applyra drops the axis out of the score rather than inventing a number for it, and keyword coverage is the axis reporting the real problem.

The ASO Health score and its three axes

ASO Health is Applyra's 0 to 100 score of how well your listing is built: keyword coverage, targeting fit and store appeal. The weakest axis is your lever.

ASO Health is Applyra's 0 to 100 score of how well your listing is built, as opposed to how it is currently doing. It reads three axes: keyword coverage, targeting fit and store appeal. A listing cannot buy its way out of one broken axis with two good ones, so the score always points at the work that matters.

It is the other half of the visibility score. That one answers "am I being found" and moves every day. This one answers "is my listing built to win" and moves only when you change something. A brand new app can have an excellent listing and no visibility, and an old app can coast on its installs with a listing that wastes half its indexed characters.

The three axes

Axis	The question it answers	What it reads
Keyword coverage	Do your store fields carry words people actually search?	Your title first, then the two other fields the store indexes.
Targeting fit	Are the keywords you go after winnable for an app your size?	The competitiveness of the terms in your listing, against what an app at your stage can realistically rank for.
Store appeal	Once someone lands on your page, do they install?	Your rating, how much of your screenshot space you use, and how recently you shipped.

Which fields the first axis reads depends on the store: app name, subtitle and keywords field on iOS, title, short description and long description on Google Play. See the metadata fields each store indexes.

Coverage is not about filling a field. A character earns its place when somebody searches the word it belongs to, so an invented brand nobody types contributes nothing, and a real brand people do type counts fully.

What a good ASO Health score is

Score	Band	What it means
80 to 100	Excellent	The listing is doing its job. Keep it fresh and protect what works.
65 to 79	Solid	Good foundations. A couple of targeted fixes put you in the top tier.
45 to 64	Needs work	There is real room here, and the findings are the fastest way to use it.
0 to 44	Critical	The listing is holding you back more than your competitors are.

Which axis to work on

You get one lever, not a list. Applyra names the axis with the most room and leaves the other two alone, because an axis the score already calls excellent is not a defect whatever its siblings look like. When all three are in good shape, nothing is named: there is nothing to fix, and inventing a chore would waste your afternoon.

The ceiling a rewrite can reach

Metadata never moves store appeal, so when that axis is low it caps what the best rewrite in the world can reach. Applyra shows that ceiling next to the score, which saves you the week you would otherwise spend polishing a subtitle that was never the problem. When the ceiling is what binds, the work is your rating, your screenshots or a release.

Graded against apps at your stage

Targeting fit is graded against your app's stage, not against an absolute bar. Aiming at the biggest term in your category is a strategy for an app that can carry it and a waste of your title for one that cannot, so Applyra compares you with apps at your stage rather than with the category giants.

That comparison moves with you. As the app grows, the terms it is expected to contest grow with it and the audit stops flagging ambition it now considers earned. Nothing to configure, and nothing to re-check when you ship.

When an axis is not measured

Two cases, and neither is a failure on your side.

Targeting fit is absent when your listing holds no searched term at all. There is no strategy to grade, so the axis drops out rather than being given an invented number. Keyword coverage is the axis reporting that problem.
The iOS keywords field is invisible. Apple publishes it to nobody, so Applyra scores coverage on your title and subtitle alone until you supply it. You can type it in, or import it automatically by connecting App Store Connect.

To test a change before you ship it, score the draft first in the Metadata Simulator. It runs the same audit on the text you type, including the keywords field, so you see the new score before App Review does. The breakdown it returns, the same as on your app page, is read table by table in reading the result.