How to send a website to a client for review
A repeatable way to get a page in front of a client, collect notes that are specific enough to act on, and close the loop without a status call.
Client review has a predictable failure mode. You send work, they reply "looks great, just a few small things", and the small things arrive four days later across two emails and a phone call, contradicting each other.
Very little of this is the client’s fault. The way most work gets sent makes precise feedback difficult and vague feedback easy.
Send the page, not a picture of the page
PDFs and screenshots strip out everything that makes a web page a web page: hover states, scrolling, transitions, how it reflows on their laptop versus their phone. Clients reviewing a flat image ask flat-image questions, and then get surprised later by behaviour they never saw.
Sending the real page also removes an entire category of round trip — "does this work on mobile?" is answered by them opening it on their phone.
Remove every step between noticing and saying
Each hoop between a reaction and a recorded comment costs you comments. Account creation is the biggest one. If your review tool asks a client to sign up, a meaningful share of their notes will instead arrive as a voicemail, or not at all.
The setup that works: comments enabled on the page, guests able to comment with just a name. The client clicks the link, types their name once, and starts leaving notes attached to the thing they are looking at.
Make notes point at something
A comment pinned to an element is a task. The same words floating in an email are an interpretation exercise.
When a reviewer pins a note to a specific card, heading or button, opening that comment later scrolls straight to it. You stop guessing which "spacing" they meant.
Keep one link for the whole engagement
The single highest-leverage habit: never send a second URL. Upload each revision over the previous one so the link is stable for the life of the project.
Everyone always has the current version, the comment thread accumulates in one place, and "which version are you looking at?" stops being a question. Notes left on earlier versions stay stamped with the version they belong to, so superseded feedback does not resurface as though it were new.
A review loop that converges
- ✓Send one link with comments enabled and a deadline: "notes by Thursday, please leave them on the page."
- ✓Let notes accumulate in one thread instead of chasing replies across channels.
- ✓Upload the revision to the same link and tell them to refresh.
- ✓Check the view stats before the call — knowing whether they opened it changes how you run the meeting.
Frequently asked
Not with FileShare Pro. Enable comments and anyone with the link can comment after typing a display name. Accounts are only required to upload and manage files.
Treat the link itself as the access control: it is unguessable, and you can switch it off at any time, which takes effect within seconds. For ongoing engagements, a workspace with per-person roles keeps each client scoped to their own files.
Yes — each file has a view count and a 30-day traffic graph, so you know before the call rather than during it.
Drop the file, copy the link — live in seconds, free plan included.
Start sharing free