SiteViewer Help Centre

Push a new version from your AI assistant

Your assistant can publish straight to SiteViewer, so a fix goes live on the same link without you uploading anything by hand.

How it works

  1. Ask your assistant to push the updated HTML to a preview.
  2. It uploads it as a new version.
  3. The shared link now shows the latest, with nothing to do on your side.

When your assistant can't send the files itself

Some AI tools, such as Claude Design, can build a whole site but can't send its files to SiteViewer on their own. When that happens, your assistant makes the preview for you straight away and gives you a link to finish it.

  1. Your assistant makes the preview. It should ask you first whether the preview should be password-protected or public. The preview appears on your Projects page at once, with its name, its own address and an amber "Waiting for files" label. It is password-protected unless you chose public when it was first made. Asking again for a preview that is already waiting keeps it the way it was first made. Your assistant can tell you the address before the files exist.
  2. Download the site from your AI tool. Most tools give you a .zip.
  3. Drop the .zip on the preview's card. Or click the card's drop area to choose it, or open the link your assistant gave you. The files go up the usual way and the preview is ready on its link.

Until the files arrive, anyone who opens the address is asked for the password first (unless the preview is public) and then told the preview isn't ready yet, with your logo and your business name. The link your assistant gives you works for 24 hours. After that the preview stays on your Projects page as a draft: drop the files on it whenever you're ready, or delete it. It isn't removed when the link runs out.

Good to know

  • It uses the same quality checks as the dashboard.
  • Only the files a website uses go on a preview: pages, styles, scripts, images, fonts, video, audio, PDFs, 3D models and WebAssembly. Anything else, such as server code, source files, settings, or a file that holds a password or a private key, is left out, and your assistant tells you which files and why. Send the folder your build creates (often called dist, build or out), not the project folder it came from.
  • The link never changes, and neither does who can open it. A password-protected preview keeps its password.
  • Before your assistant creates a brand-new preview, it should ask you whether it should be password-protected or public. If you don't say, or an older assistant doesn't ask, the preview is password-protected. If your assistant doesn't ask and makes it public, you can add a password in the preview's Settings tab. The reply never includes the password: it ends with a link to the preview in SiteViewer, where you can see or change it, or make the preview public.
  • That is the client password, the one your client types to open your SiteViewer link. It isn't your website's own password, the one a live website asks its visitors for. Your assistant never asks for that one: you add a live website, and its password, in SiteViewer yourself.
  • A preview waiting for its files counts as one of your previews, just like any other.
  • Comments stay tied to their version.
Tip

This closes the loop. Feedback in, fix out, all from your chat.


Was this helpful?Thanks for the feedback.

Still stuck?

Our team replies to every message, usually within a few hours. No bots, no ticket queues.