Content revised 20 October 2026.
A useful content review produces specific decisions: what to keep, what to correct and what the reader still needs. Start with the audience, examine the explanation, then test the finished page.
1. Define the reader and the task
Write one sentence describing who opens the page and what they need to do. A service buyer may need scope and enquiry details; an existing customer may need a process answer. Use actual customer questions where available. Demographic labels alone rarely explain the information someone is missing.
2. Review each part against that task
Mark the facts, examples, instructions and claims. Verify information that may have changed and identify unsupported assertions. Keep useful original detail. Replace repeated introductions or vague promises with an explanation that helps the reader decide or act.
Use a short decision log
- Keep: accurate information that serves the page.
- Correct: outdated facts, unclear claims or broken references.
- Add: a necessary answer or meaningful limitation.
- Investigate: overlap, ownership or a change requiring approval.
3. Check the published experience
Read the revised page on desktop and mobile. Test navigation, media and the next step in a safe environment. Confirm that titles and descriptions still fit the answer and that related links reach the intended pages. A tidy draft can become confusing inside the actual layout.
Leave a maintainable record
Keep the original source and note significant changes, approvals and review dates. Assign someone to resolve uncertain business details. Do not update a displayed revision date simply because a page was opened in the editor; use it for a genuine review or meaningful change.
Official guidance: Google’s helpful-content review questions.