The symptom is specific: organic traffic falls and every article gets rewritten. Start with the affected item and identify the decision or input that could produce this behavior.
Find the likely cause
A sitewide symptom is assumed to be a content problem.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Segment the decline by page group, query, device, and time.
Search reports become useful when a change in numbers leads to a specific, testable explanation.
Check that the repair worked
Identify the affected pattern before choosing an intervention.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: average position changes are misread as a single ranking. Inspect relevant query-page combinations and their volume.
Monitor the useful outcome
Use impressions, clicks, query mix, and business outcomes together instead of relying on one aggregate number.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.