
Test the diagnosis
Use crawls, search reports, release history, and page comparisons to check the explanation. Avoid treating one tool score as a complete diagnosis. Review both successful actions and errors before launch.
Specify the change, reason, owner, and acceptance check. Developers and editors need actionable instructions rather than broad labels. Agree whether the evidence supports keeping, changing, or stopping the approach.
- A written brief
- Named responsibilities
- Agreed review points




