Collect client feedback on a website
Good client feedback is specific: which page, which spot, what request and what status.
The problem
Screenshots, voice messages and email lists lose context quickly. Developers have to guess what the client means. Clients feel unsafe when asked to touch files or code.
Simple solution
- Send a static export or ZIP.
- Let clients add comments or suggestions at the exact spot.
- Separate notes, questions, issues and approvals.
- Export an HTML feedback report.
- Work through open items systematically.
Common mistakes
- Collecting all requests in one long email.
- Writing feedback without page names.
- Mixing approval and change requests.
- Asking clients to use developer tools.
Checklist
- Project opened locally
- Comments per page
- Suggestions separate from code
- Open/done status maintained
- Feedback report exported
- Approval documented
FAQ
Why not just screenshots?
Screenshots help, but without page context and status they become hard to manage.
Can the client break the site?
Comments and suggestions do not directly change website code.
When is the code editor useful?
Only for advanced users who intentionally want local file changes.