Product Updates

How to Share a Staging Site With Clients Without a Public Widget

Give your client a private link that shows the feedback widget, keep the button hidden from everyone else, and revoke old links in one click.

A green key card parting a curtain so one cursor can see a hidden browser page.
A practical field guide
In this article 8 sections

The staging site is ready on Friday afternoon. You want the client to go through it over the weekend and leave feedback, but the same URL is open to the developer still fixing the footer, to the freelancer writing copy, and after launch it will be open to everyone. You want the feedback button in front of the client, not in front of every visitor.

This post shows how to share a staging site with a client so that only the people you choose see the feedback widget, and how the same setting carries over to the live site after launch.

Why sharing staging is awkward

Agencies usually protect a staging site in one of three ways: a password (HTTP basic auth or a CMS “coming soon” mode), an IP allowlist, or nothing but a noindex tag and some hope. Each of these decides who can open the site. None of them answers a second question: who should see the feedback tool on it?

In practice that gap causes three kinds of trouble:

  • Noise. The widget is on for everyone, so a developer testing the checkout, or a stranger who found the URL, can send reports, and your list fills with things nobody asked for.
  • Leaks to production. The site goes live with the snippet still in place, and real customers start sending “feedback” to your agency.
  • Manual switching. To avoid both, someone adds the script before each review round and removes it afterwards. That works until the one time it does not.

What you want instead is a switch in the widget itself: installed once, visible only to the people you invite.

The three visibility modes

In Zorko every project has one setting for who sees the widget. You pick it when you create the project and can change it any time in Project settings > General.

ModeWho sees the buttonWhen to use it
Everyone on the siteEvery visitorA staging site only your team and the client can open anyway
Only people with the linkOnly browsers that opened the site through your private linkStaging reachable from the internet, or a live site after launch
OffNobody, and no reports are acceptedBetween review rounds, or when a project is paused

“Only people with the link” is the default for new projects, because it is the safe choice when you do not yet know who else will open the URL. The project card in the dashboard shows the current mode as a chip: Public, Link only or Off.

Step by step: share staging with a client

1. Install the snippet once. Add the script tag to the staging site’s <head> or footer:

<script type="module" src="https://zorko.app/widget/loader.js" data-widget-key="YOUR_WIDGET_KEY"></script>

It works on WordPress, Webflow, Shopify or custom code, without a plugin. The key only works on the domains you set for the project and their subdomains, plus localhost for local development, so copying it onto another site does nothing.

2. Leave the mode on “Only people with the link”. The snippet dialog in the dashboard shows this project’s link. It is a normal address with a short key at the end, for example https://staging.example.com/?zorko=K7M2QX9PTA.

3. Send the link to the client and anyone else who should review. When they open it, the widget checks the key with our server and the feedback button appears. Their browser remembers the key, so they can move between pages, close the tab and come back tomorrow without the link. Once the key is verified it is also removed from the address bar, so a URL they copy and forward to a colleague does not carry it along.

4. Everyone else sees the site without the button. A developer who opens the plain staging URL, a search bot or a visitor who guessed the address gets the page and nothing else.

5. Revoke when you need to. If the link ended up somewhere it should not be, or a review round is over and you want a clean start, click “Revoke and create a new link”. Old links stop working at once, including in browsers that had remembered them. Send the new link to the people who should keep reviewing.

What your client experiences

For the client, the link is the whole onboarding. No account, no extension, no password to a feedback tool. They open the link from your email, see the button and click it, and the widget captures what is on screen. They mark the spot with a pin, add a comment and send. If a screenshot cannot show the problem, they can record their screen in a desktop browser for up to three minutes, with their voice if they want.

One tip that saves a round of questions: put the link in the same email as the review instructions, and say which pages to check and by when. The link handles the technical part. You still set the scope.

It is a lock, not just a hidden button

A fair question: if the button is only hidden, could someone send reports anyway by calling our API directly? No. The server refuses reports and file uploads that do not carry the current key, so the hidden button is a courtesy for visitors, and the actual check happens on our side. Revoking the link revokes that key everywhere at once. More on how we handle access and data.

What link mode does not do is protect the site itself. It decides who sees the feedback widget, not who can read the pages. If the staging content is confidential, keep your password or IP restriction as well. The widget runs inside the page, so it works behind basic auth, as long as the domain is listed in the project settings.

After launch: the same setting on the live site

The snippet can stay on the site after launch. With “Only people with the link”, real visitors never see the button, while the client and your team can still report issues on production by opening the link once. When the project wraps up, switch to Off: the widget stops, the snippet can stay in place, and nothing is accepted until you switch it back on.

This also takes care of the “we forgot to remove the script” problem from earlier. There is nothing to remember, because the widget was never public. If you want the bigger picture of how the widget works end to end, it is laid out step by step there.

Count it for your own projects

Before you change anything, look back at your last three projects:

  • How many reports came from people who were never meant to review, such as team members testing, strangers or duplicate reviewers?
  • How many times did someone add or remove the widget script by hand?
  • Did a feedback button ever go live on production by accident?

Say each project had one manual add-and-remove cycle, and each took 20 minutes including a deploy and a quick check. That is an hour across three projects. Not much, but it is the kind of hour that tends to land on the day before launch, when nobody has one to spare.

If you are still deciding which tool to use in the first place, start with our guide to choosing a website feedback tool.

New projects start in link mode, so you can try this on your own staging site in a few minutes. Create a free Zorko project.

FAQ

Does the client need a Zorko account?

No. The link and the widget are all they need. Accounts are only for your team, in the dashboard.

What if the client opens the site on another device?

The browser remembers the key, not the person. On a new phone or laptop they open the link once more, and that browser remembers it from then on.

There is one link per project. If you need to cut off one person, revoke the link and send the new one to everyone who should keep access.

Yes. You can add the same ?zorko= part to a deeper address, for example to send the client straight to the pricing page. After the first visit the browser remembers the key on every page of that site.

Zorko news in your inbox

Product updates and practical tips for agencies, about once a month. Nothing else.

Put it into practice

Give clients the right way to show what they mean.

Zorko keeps screenshot and desktop video feedback together with the page details your team needs to act.

Start free See how it works

Free includes 1 project and 10 feedbacks a month. No credit card required.