Verify that the term belongs.
Start with the task implied by the query. Can the current app satisfy it in the intended market? A phrase selected because it looks popular may be a poor product match. Missing visibility for an irrelevant term is not a reason to expand the claim.
Use the relevance framework before changing copy. Document the feature or workflow that supports each priority term and exclude candidates whose promise the product cannot keep.
Inspect actual implementation.
Compare the research recommendation with the live metadata in the intended locale. Check whether the agreed version was published and whether later edits changed it. Different store fields have different roles; a keyword in a brief is not an implementation.
Use the iOS keyword-field guide or Google Play description guidance for the relevant workflow. Do not apply one store’s assumptions to the other.
Check what the rank evidence means.
Confirm the exact query, market, store, date and tracking range. An unobserved result may mean outside the tool’s range or missing data. It does not establish an exact position or explain the cause.
Follow rank-tracking practice. Keep observations comparable instead of switching tools or markets until a favourable number appears.
Review the competitive context.
Inspect relevant alternatives and their positioning. A good product fit does not imply easy visibility, and another app’s metadata is not a recipe for your own result. Separate observations from assumptions about hidden performance.
Use competitor research to identify questions, then prioritise a small set of defensible changes. Avoid adding every phrase just because it appears in a competitor listing.
Evaluate the next change as a hypothesis.
Define the intended effect, preserve the previous version and record the release. Review relevant acquisition evidence alongside rankings. A higher position without useful users is not the entire objective.
If visibility improves but downloads remain flat, use the next diagnostic guide. If nothing changes, examine the original assumption rather than repeating the same edit more aggressively.
