Getting started

How clients comment on your site

Nothing to install for most sites; the review tag for the rest.

Share a version with its staging link and your client can comment on the real page. When Settings › Client review says *Ready — nothing to install*, Studio opens the site for your client through its own review link, with comments switched on, and nothing goes on your site.

A site behind a company sign-in, or one only your network can reach, needs the review tag: one script tag from Settings › Client review. Studio uses the tag automatically wherever it finds it. A staging site protected by Vercel, Netlify or Cloudflare Access can instead be given its bypass header in the same place.

The tag does nothing for normal visitors. It only switches on for someone who opened a review link, and it never changes your page’s layout.

Signing in with Google, GitHub or another outside service, or paying through one, sends your client to that service, and it can only send them back to your real site, not to the review link. Studio tells them before they go and takes them back to the review in one press. When a site does this, the review shows you a note and Settings › Client review marks the site: add the review tag to that site and check it, and its reviews open on the real site, where signing in works. A test login with an email and password works too.

A site that signs people in with a link sent by email works on the review link: your client presses Comments, then Paste a sign-in link, and pastes the link from the email. Studio opens it inside the review, including links from sign-in services such as Supabase, Clerk or Auth0.

If it is not found

Almost always one of four things: a Content-Security-Policy that blocks the script, the tag on production but not staging, the wrong site key, or a site behind a login Studio cannot see. You can share anyway; your client will still be able to comment once the tag loads for them.