
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. Bring sales questions into the brief so the work answers real concerns.
Specify the change, reason, owner, and acceptance check. Developers and editors need actionable instructions rather than broad labels. Review both successful actions and errors before launch.
- A written brief
- Named responsibilities
- Agreed review points




