# Triage keyword rank alerts before editing metadata

URL: https://storelift.net/guide/keyword-rank-alert-triage/
Language: en
Updated: 2026-10-02

An alert is a prompt to inspect an observation. It is not proof that a metadata change is needed. A consistent triage process checks data quality, scope and persistence before assigning an action, so isolated movement does not repeatedly trigger conflicting edits.

## Investigation steps

1. Read the app, term, storefront and two observations behind the notification. Verify that both are successful and that an outside-range state is represented honestly.
2. Check whether related terms or countries moved at the same time. Compare the competing result set and any recent release or listing changes.
3. Classify the case as a collection issue, an isolated movement or a broader pattern requiring investigation. Record the next check and who owns it rather than immediately changing several fields.

## Worked interpretation

Illustrative case: one term briefly moves while the fixed group is stable and the next successful observation returns near its earlier position. Keep the event in history; it does not by itself justify replacing the subtitle.

## Decision and next check

Tune product notification thresholds to the decisions the team actually makes and review repeated false urgency. Keep the notification history with the investigation outcome so the team can distinguish a useful signal from a repeated transient movement.

## Related Storelift feature

Read Keyword rank alerts for the available product data and its scope. Keep the app, storefront, period and measurement status with the observations used in your report.