Review a live website, not just a file
You do not only review uploaded files. Paste any live URL and your client can pin comments straight on the real, working site.
How it works
Paste a site address and SiteViewer puts that live site behind your private review link. It works with Squarespace, Webflow, Wix, WordPress and any public web address. Your client opens the link, sees the real site, and pins comments exactly where they want them.
Paste the address however you have it. If the site has a secure version, SiteViewer uses that address for you, even when the one you pasted is an older, insecure one. SiteViewer only ever sends a site's password over a secure connection, so if it can't reach a secure version of a site that needs a password, it says so. Check the address, or ask whoever runs the site to turn on a secure connection.
Where it helps
- Sites still in build. Review a Squarespace site while it is in trial mode, before it is published. Add the trial password once and the client never sees the gate.
- Preview links with the password in them. Some site builders, such as Doormingo, share a preview as a link ending in
?access=and a code. Paste the whole link: SiteViewer moves the code into Site password, checks it opens the site while you add it, and keeps it out of everything your client sees. - The real thing. The client reviews the actual working site, so navigation, hover states and forms behave normally, not a flat screenshot.
- Same review tools. Pinned comments, threads, screenshots and the full downloadable comment record work exactly as they do on uploaded files (Studio).
Two passwords, and who types each
A live website can have two passwords. SiteViewer names each one by who types it, everywhere it appears.
- Client password. Your client types this to open the preview. You set it in the project's Settings.
- Site password. SiteViewer uses it to open the site for your client. They never see it. You only need one if your site asks visitors for a password. When only one page of the site has its own password, SiteViewer calls it a Page password, and the Versions tab shows which versions open with which.
When your site starts asking for a password
While a site is public there is nothing to fill in, so the project's Overview shows no Site password. If the site later starts asking visitors for a password, for example when a Squarespace site's password is switched on, the Overview shows a card that says so and since when. Until SiteViewer has the password, your client sees the site's own password page instead of the site. If only one page has its own password, your client sees that page's password page in the preview, and if that page is meant to stay locked you can say so on the card.
Type the password into the card and press Save site password (Save page password when the card is about one page). SiteViewer checks that it opens the site before keeping it, then the card goes and the site shows again for your client.
SiteViewer keeps one password per website. If a page has a different password from the one already saved, SiteViewer says so before anything is replaced, wherever you save one (the card, Settings, or Add version), and you can keep the saved one.
When a live website is ready to go public, you can turn the review chrome off so ordinary visitors just see the site itself.