Why my visibility score moved when I changed nothing
Applyra recomputes your scores every day from live store results, so a score moves when your positions move, when a rival slips, or when a store recalibrates.
Applyra scores measure live store results, not your settings, and they are recomputed every day. So a score that moves while you did nothing is the normal case, not a glitch: something moved in the store.
Positions are refreshed every day, and the scores follow once the day's readings are in.
The three things that move a visibility score
- Your positions changed. Someone overtook you, or you overtook someone. Open rank history on the keywords that matter most to you and the move is usually visible in one chart.
- The store recalibrated. Both stores reshuffle their results without announcing it. A day where everything moved at once shows up in the algorithm change detector, and it is the first thing to check on an unexplained drop before you go looking at your own listing.
- A competitor slipped. Your score can climb without you doing anything at all. Competitor analysis shows whose positions changed around yours.
One thing that never moves it: what you add or remove in your tracker. The score reads a fixed set of keywords from your app's niche, so your own tracking choices cannot push it either way. How the visibility score works sets out the rest.
If what puzzles you is not the move but the number itself, compared with what you see in the store on your own phone, that is a different question: why Applyra shows a different number from the store.
Reading the move rather than the number
The same app across two weeks is exactly comparable, and that is the whole point of a fixed keyword set: nothing about the measurement changed between the two readings, so the difference is your standing in the niche and nothing else. So the useful question is never "is 64 good", it is "why is it 64 today and 71 last Tuesday".
A one-day dip that recovers the next day is store noise. A slide across a week is a trend, and it has a cause you can find. There is a full walkthrough of that hunt in why your App Store keyword rankings dropped.
ASO Health is the steadier one
ASO Health grades the listing itself: what you wrote, how it is built, how it holds up against apps at your stage. It does not depend on where you rank today, so it moves far less often, and mostly when the listing changes. If ASO Health is flat while visibility falls, the problem is not your metadata.
Before you change anything
Wait for the data, not for the store. A listing change reaches the rankings the day it goes live, as measured on real listing changes, but individual keywords move on their own every day too, so it takes about two weeks of daily readings before a real effect separates from that noise. Reacting to one day of movement is how people end up rewriting a title that was working.
If you want to test a change before shipping it, score the draft in the Metadata Simulator instead of shipping it to find out.
Frequently asked questions
Why did my Applyra visibility score change when I changed nothing?
Because it measures live store positions, not your settings. It is recomputed every day, so it moves when the results move: a competitor overtakes you, the store reshuffles, or you break into the results on a keyword you track.
Why did my visibility score drop right after I added keywords?
Adding or removing keywords in your tracker cannot move the visibility score either way. Applyra computes it from a stable set of keywords drawn from your app's niche, so the score follows where your app actually ranks in that niche, not what you chose to track.
How do I tell a real drop from a store-wide event?
Check the algorithm change detector. It measures how much search results moved across the whole store that day, so a market-wide reshuffle shows up there and your own listing is not the explanation.
Does the ASO Health score move on its own?
Much less. It grades the listing itself, so it mostly moves when a listing changes, either yours or the ones you are compared with.
Last updated on