One link, and every part of the review happens inside it
Comments pinned to the page. Versions behind a link that never changes. Your domain on the outside. And a way to hand the whole list to your assistant when you would rather not do it by hand.
Free plan 5 projects No card
What your client can do without an account
They open the link, add their name once, and start pointing at things. Nothing to install, no seat on your billing, no password to remember.
Click the spot, type the note
The comment sticks to that element on that page, so nobody has to describe where they mean.
Browse or comment
One switch. In Browse they use the site normally, in Comment a click drops a pin.
Coming back is one click
A returning reviewer gets a sign-in link to a portal listing every preview they are reviewing, on any device. Still no password.
Context arrives attached
Browser, system, viewport, screen, pixel ratio, language and time zone, captured with the comment.
A screenshot, automatically
Taken at the moment they clicked, so "it looked broken" comes with proof of how it looked.
Threads, replies and reactions
You reply in place. They reply from the email. Reactions save a round of "yes, agreed".
Desktop and mobile views
They can switch device view in the room, and the comment records which one they were on.
Assign it to someone
Hand a comment to a teammate. They get an email and it lands in their own list.
Some notes are not for the client
Mark a thread private and it is yours alone: the client never sees it, on the page or in their emails. Useful for the honest version of why something cannot be done.
Filter to what needs you
Open or resolved, just what is new since you last looked, or only the ones left on mobile.
Open and done, kept apart
Resolve moves it out of the active list, so nothing gets asked for twice.
The review goes out as yours, all the way through
Point a subdomain at SiteViewer and every link you send is on your address. Your logo and colours on the gate the client meets first. SSL issued and renewed without you touching it.
- 01
review.yourstudio.com - 02
Your logo, or one of eight gate backgrounds.
- 03
Ten domains on Studio, so every retainer client gets their own.
Included from Pro, $6.40 a month billed yearly
If your client can open it, they can comment on it
| What you drop in | How it works | Pinning |
|---|---|---|
| A hosted page | Drop in an HTML file or a zip. Pages built by hand, or generated with Claude, v0, Lovable or Bolt. | Pins anchor to the element |
| A live website | Paste the URL. Squarespace, Webflow, Framer, WordPress, Wix, anything that serves a page. | Pins anchor to the element |
| A PDF | Decks, brand guidelines, proposals, in our own viewer. | Fixed page geometry |
| A single image | One visual, comment only. | Fixed geometry |
| An image set | Sign-off collections: a thumbnail gallery with Approve or Request changes on each image. | Per-image decision |
One link for the whole project, from kickoff to sign-off
Push a new version and the share link stays the same. The client always lands on the current one, and you can roll back to any earlier version in a click.
- 01
Comments can come with you.
Publish v4 and SiteViewer offers to bring the earlier comments forward. They land in the same spot, keep the number they had, and carry a “previously #3 · v1” badge.
- 02
You can see when they opened it.
Total views and the last time the link was opened, per project.
- 03
Set a date it stops working.
Give a link an expiry, so last year's pricing is never still live.
- 04
Quiet links tidy themselves up.
On Free and Pro the clock runs on inactivity, not age, so a preview under active review never dies. You get a warning a week before, and again the day before. On Studio they stay put.
Feedback closes when you said it would
Give a review a window and it looks after itself. Comments stop when the window shuts, so a project cannot quietly gather notes for another six weeks.
- 01
Set the window, not a reminder.
Commenting genuinely stops on the date, so there is nothing for you to police.
- 02
They get a nudge first.
An email about two days before, so nobody loses their last round of notes.
- 03
Your timezone, not ours.
The deadline lands at nine in the morning where you are, and the date on screen is the one your client sees.
- 04
Reopen it if plans change.
One click, and the next sweep will not quietly close it again behind you.
Nobody has to remember to chase anybody
The link does its own following up. Your client hears when there is something new to look at, you hear when they have said something, and both emails look like they came from you.
Preview ready
Goes out when you publish, so you are not writing the same email every time.
New version published
Tells them there is something new behind the same link.
Somebody replied
Reaches you on the schedule you pick, from every fifteen minutes to once a week.
A digest, not a drip
Comments are gathered up and sent as one summary rather than one email per pin.
You pick how often
Every fifteen minutes, hourly, daily, weekly, or off. Set per person, so the designer and the account manager can differ.
Or instantly, in Slack
Connect a channel and the message lands the moment a client comments, with a link straight to it.
Closing soon
Goes to the client about two days before a review closes, so they can get their last comments in.
Replies come to you
Sent in your studio’s name, and when the client hits reply it reaches you, not us.
The client-facing ones are editable, so the wording is yours
Hand the whole list to your assistant
Every comment already carries the page, the element and the screenshot. Turn one into a prompt, export the lot as Markdown, or let your assistant read and resolve them itself.
- 01
It reads more than the comments.
Every pinned note, and the page's own accessibility and SEO findings, each as a plain instruction it can act on.
- 02
It publishes the fix in place.
The new version goes out on the same review link, and pins are kept per version, so your client just sees the update.
- 03
Then it closes its own loop.
We tell it which comments the change looks to have addressed, so it marks them resolved. The review moves toward done without you.
- 04
Or keep it manual.
Turn one comment into a prompt, or copy every open comment out as plain Markdown for any tool.
Feedback arrives where you already work
Two connections, both proper ones. Slack posts the comment the moment it lands, and your AI tool can read the whole list and push the fix back.
- 01
Add to Slack, the normal way.
You approve it in Slack and pick the channel in Slack's own dialog. One channel per workspace, disconnect whenever.
- 02
The message is useful on its own.
Who said it, what they said, which page, and a link that opens the comment rather than the homepage.
- 03
Your assistant, connected directly.
It reads the feedback and publishes the fix back. Fenced so it can never rename, delete or unlock a link you have already shared.
Assistant tools on Pro and Studio, with client feedback to read on Studio. Slack on Studio
Private by default, without making anyone sign up
A password on the link
Stored scrambled, never in plain text, and you can change it without changing the link.
No passwords on your account
You sign in with a link sent to your email, so there is nothing to leak or reuse.
See where you are signed in
Active sessions in one list, and one button to sign out everywhere else.
Client work stays apart
Previews are served from a different address to your dashboard, so an uploaded page can never reach your account.
What SiteViewer does not do
There is no sprint board, no assignee workload view and no two-way Jira sync. If you need those, BugHerd is the better tool. If you are gathering feedback from thousands of end users rather than a handful of named clients, look at Usersnap.
SiteViewer is built for the studio or freelancer running a handful of client projects at a time, who wants the whole review to look like it came from them.
If that isn't you, we've just saved you a signup.
Send your next review link from your own domain
Five projects free, no card. Add your domain when you are ready for the client to see your name on it.