
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. Check the reasons suitable customers hesitate or leave.
Specify the change, reason, owner, and acceptance check. Developers and editors need actionable instructions rather than broad labels. Review the whole path instead of judging one screen in isolation.
- A written brief
- Named responsibilities
- Agreed review points




