
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 that a visitor can find the next action without guessing.
Specify the change, reason, owner, and acceptance check. Developers and editors need actionable instructions rather than broad labels. Explain which task matters next and why it takes priority.
- A written brief
- Named responsibilities
- Agreed review points




