Send a site with SiteViewer Assistant
Add any website you can open to SiteViewer, including sites whose host turns SiteViewer away, and keep it up to date. It's a small Chrome extension that works from New project, or from its own button.
When to use it
Most sites can be added straight from SiteViewer with Add a website. A few hosts turn SiteViewer away, so SiteViewer can't load the site from its end. WordPress.com is the common one. Your own browser can still open those sites, so the Assistant adds them from your browser instead, as a copy of their pages and files in your workspace.
It only adds what your browser can see. It never works around a site that refuses visitors.
Install it once
- Add SiteViewer Assistant to Chrome. Find it in the Chrome Web Store and press Add to Chrome. It also works in Edge.
- Allow it to add websites. A welcome page opens. Press Allow, then confirm in Chrome's own box. This is asked once, never site by site.
- Connect to SiteViewer. A small window opens and connects by itself if you're signed in to SiteViewer. If not, sign in there and it carries on.
Add a site from New project
Add the website in New project as usual. If its host turns SiteViewer away, the Assistant adds it for you, with the usual progress, and opens the new project. There's nothing else to press.
- If the Assistant isn't installed yet, New project says so with an Install button. Install it, then press Try again.
- If it hasn't been allowed to add websites, New project says so with Give permission, which opens the welcome page again.
Or send the site you have open
- Open the site in Chrome and click the Assistant's button. It shows the site's name, its address and how many pages it found.
- Choose a new project or a new version, the workspace, and the project for a new version. Projects are listed A to Z.
- Choose this page or the whole site. The whole site is read from the site's own page list, up to 200 pages. If it has more, the rest link to the live site.
- Press Send to SiteViewer. You can close the window while it sends.
Keep it up to date
A project the Assistant added works like a live website. On its Versions tab:
- Refresh from site brings in the site as it is now, the same pages as before. It replaces what your client sees in one step, so nobody sees half of each. Comments stay where they are, and nobody is emailed.
- Undo refresh puts the copy from before the last refresh back.
- Keep this copy up to date automatically is on by default. While Chrome is open and you're away from your computer, the Assistant checks the site every few hours and refreshes it when it has changed, at most once a day. If a teammate's browser is already looking after it, yours leaves it.
- To keep a milestone, upload a new version as usual. Refreshes don't make new versions.
Pages behind a login aren't included: the Assistant reads the site as a visitor would, without your own sign-in. A copy fits the storage your workspace has left. If a site is bigger, its code, styles and fonts come first and its last images and large videos stay on the live site, and the Assistant tells you exactly which.
What comes across, and what doesn't
The Assistant copies every page you choose and everything those pages load: styles, scripts and the pieces they load in turn, fonts, images and the data a page asks for. It also opens each page in the background for a moment to catch anything that only appears once the page runs, then opens the finished copy in SiteViewer to check it, and brings in anything that's missing.
- Copy taken on the project's Versions tab says when the copy was made and whether everything came across. Open it to see, in plain words, anything that didn't, such as a search box that needs the website's own server, or a widget from another company that only shows on the real site.
- Safe for feedback. In a copy, forms never send, checkout and sign-in do nothing, and analytics and tracking are removed, so your client can click around without anything reaching the real site. Links to pages you didn't copy open the real site in a new tab.
- Your client is told. The review room shows them a short note that they're looking at a copy taken on a certain date, and that forms, checkout and anything that needs the live website won't work there. They can hide it, and it comes back after a refresh.
On Squarespace?
A Squarespace site doesn't need a copy: SiteViewer shows it live, so your client always sees the latest version. Click the Assistant's button on your site, or in the Squarespace editor, and press Add as a live site. SiteViewer opens with the site's public address filled in, in the workspace you picked. Check it, then press Add website. SiteViewer for Squarespace shows your clients' comments inside the Squarespace editor.
If the site is already in SiteViewer, the Assistant says so and links to it, so you don't add it twice. Adding a website is part of the Pro and Studio plans, and the Assistant tells you when the workspace you picked has no websites left. A copy you sent before Squarespace sites went in live stays as it is; press Add it as a live site instead to show the live site from then on. On your Squarespace account page there's no site to add yet: open the site first.
In a website builder's editor?
The Assistant sends the published site, not the editor. If you click it in the WordPress, Wix, Webflow, Shopify or Framer editor, it says so, and offers to open the published site when it can. Open the site's own address, then click the Assistant's button again.
Signing out
Press Sign out in the Assistant, or go to Account in SiteViewer, open Connected browsers, and sign that browser out. You can also take back its permission to add websites in Chrome's own extension settings.