Quick answer
Review the actual file or CMS diff, then test the visitor behavior the change is intended to fix. A plausible explanation from the assistant is not a substitute for examining what changed. Give special attention to credentials, tracking, forms, links, and business facts.
Apply this guidance to your website task
Before you start
Start from a clean baseline or known commit. Preserve the previous version and use a development preview. Decide which files or content were within scope before reviewing the output.
What to do
- Read the changed files or CMS revision and confirm that each edit belongs to the task. Look for unrelated formatting churn, new dependencies, and generated placeholder content.
- Check that no password, key, token, customer export, or private path was added to public code, logs, or the repository.
- Run the relevant syntax, build, or interaction checks and inspect desktop and phone layouts. For content changes, review claims, spelling, links, and image permissions.
- Approve a specific artifact or commit for the named destination. Keep a current deployment backup and a clear rollback step.
Check the result
After deployment, compare remote files or hashes with the approved artifact and test the public behavior again. Cache differences can hide an incorrect or incomplete upload.
If something does not work
If the diff is too broad to review, ask for a smaller change. If a tool claims success without changed-file evidence, request a readback rather than repeating the deployment blindly.
Related help
- Create a recoverable checkpoint before an AI website deployment
- Use Git to review website changes without treating it as a full backup
- Review a website before approving its launch
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.
