Volatility Triage and Client Escalation (QA)

Volatility Triage and Client Escalation (QA)

1. 01

   Confirm the movement is real before anyone touches the client deck

   Re-pull the affected keyword set on a second engine and a second device profile. A single-source dip is often a rendering or personalization artifact, not a ranking loss.

2. 02

   Classify each drop by SERP feature displacement rather than raw position number

   A fall from 3 to 6 caused by an AI Overview or local pack insertion is a different problem than a fall from 3 to 6 with no feature change. Nozzle's pixels-from-top and above-the-fold metrics separate the two cases.

3. 03

   Separate algorithm-wide movement from client-specific movement

   If 60 percent or more of tracked keywords across unrelated client accounts moved on the same date, treat it as a platform event and hold individual account narratives until the pattern stabilizes.

4. 04

   Check whether the client's own site changed in the 72 hours before the drop

   Deployments, CMS migrations, and robots directives account for a large share of sudden losses. Confirm with the client's dev contact before attributing the shift to search engines.

5. 05

   Log the movement with a timestamp, engine, and confidence level in the shared tracking record

   Retain the raw export. When a client disputes a monthly report six weeks later, the dated snapshot is the only defensible artifact.

6. 06

   Decide within one business day whether the movement crosses the escalation threshold

   Set the threshold in the retainer agreement: for example, a top-10 keyword exiting the top 20, or a 15 percent drop in tracked visibility across the account. Below threshold, note it and move on.

7. 07

   Draft the client note with the observed change, the likely cause, and the next checkpoint date

   Avoid promising recovery timelines. State what will be re-measured and when, then deliver that measurement on schedule.