Website approval for freelancers
Freelancers need an approval workflow that feels professional and remains easy for clients.
The problem
Without a fixed process, feedback loops multiply. Clients report the same issue several times, approvals remain vague and final changes are not documented.
Simple solution
- Deliver a finished static export instead of a source folder.
- Explain that files are reviewed locally and not uploaded.
- Ask clients to add comments and suggestions directly on the page.
- Export and archive the feedback report.
- Separate approval, open requests and future work.
Common mistakes
- Sending a ZIP without instructions.
- Treating unfinished legal pages as final.
- Applying changes without status.
- Skipping live canonical and sitemap checks after launch.
Checklist
- Export clearly named
- Start page clear
- Feedback deadline set
- Status per request maintained
- Legal notice final
- Privacy final
- Launch check completed
FAQ
How do I avoid misunderstandings?
Use page-based comments and reports instead of scattered messages.
Does the client install anything?
No. A browser is enough for static exports.
Should the client edit code?
Usually no. The code editor is for experts only.