Blog

How to share a staging site with a client for review

There are four common ways to share a staging site with a client: lock it with a password, send a preview URL, send a temporary share link, or send a review link. Each one asks something different of the client, and each handles search engines and privacy in its own way. This guide compares them and ends with what to fix before the client opens anything.

Share a staging site with a client: Passwords, preview URLs, share links and review links compared.
The short versionA password box keeps staging private and out of search, but every reviewer has to type it, and tools that load the page for comments can't get past it. A noindex rule keeps staging out of Google but doesn't stop anyone with the address. For a client review, the easiest setup is staging set to noindex, opened for the round through a link that needs no password, and a review link the client can comment on without an account.

The four options at a glance

Most teams use one of these, or two together. What matters to the client is whether they have to log in or type anything. What matters to you is whether the copy can leak into search results and who else can see it.

OptionClient loginSearch indexingPrivacyWorks for import?
Password-protected stagingA shared username and password in the browser's boxKept out, since crawlers can't get inStrong, while the password stays privateNo, the import stops at the password box
Preview URL from your hostNone, unless the host protects previewsDepends on the host and your noindex settingsAnyone with the address can open itYes, if it opens without a login
Temporary or shareable linkNone; the link carries the accessRarely an issue, but add noindex to staging anywayAnyone with the link, until you revoke itOften, if it opens without a password; test it first
Review linkNone; a name and email once to commentReview links are not indexedAnyone with the linkIt is the review

Option 1: password-protected staging

This is the classic setup. The server answers every request with a challenge, and the browser shows its own username and password box before any of the page loads. That's HTTP basic authentication. Many hosts offer it with a switch: WP Engine has a password protection toggle for each environment, and Kinsta has a password protection tool under Tools in MyKinsta. Netlify offers a site-wide password on its Pro plans, and Vercel sells password protection as a paid add-on on Pro.

What it means in practice:

  • Client login: every reviewer types the shared username and password. Expect at least one "what's the password again?" email per round.
  • Search indexing: Google's own advice for private content is to password-protect it. Crawlers can't get past the box, so the pages stay out of search.
  • Privacy: good, with one catch. Basic auth sends the details encoded, not encrypted, so it's only safe over https.
  • Feedback tools: anything that loads your page from its address stops at the box too. If your staging uses a password box, you'll need a share or preview link that opens without one, or switch the password off while the round runs.

A password form inside the page, such as a coming-soon or password plugin, is different from the browser box but has the same effect on a review: the client and the feedback tool see the form, not the site. The WordPress staging feedback guide walks through each kind of lock and how to open it for a round.

Option 2: preview URLs

Hosts and site builders give every build its own address. Webflow publishes to a staging subdomain on webflow.io, and WordPress hosts create staging copies on their own staging domains. Jamstack hosts such as Vercel and Netlify create a preview for each deploy.

  • Client login: usually none. The exception is a host that protects previews by default. New Vercel projects, for example, can ask visitors to log in with a Vercel account, which clients won't have.
  • Search indexing: a public preview can be crawled like any other page if someone links to it. Turn on the builder's setting to keep staging out of search where it has one (Webflow can disable indexing of the webflow.io subdomain in its site settings on paid plans), or add a noindex rule.
  • Privacy: anyone with the address can open it. Fine for most marketing sites, not for anything confidential.

If you build with an AI code editor and deploy previews, our guide to client feedback on a site built with Cursor covers the preview step in detail.

Some hosts let you keep staging protected and hand out a link that skips the protection. Vercel's shareable links are one version: anyone with the link can open that deployment, and you can revoke it from the project when the round ends. Other hosts call it a share link, a guest link or a temporary URL.

  • Client login: none. The link itself carries the access.
  • Search indexing: these links are rarely posted anywhere public, but they can be forwarded. Keep a noindex rule on staging as a backstop.
  • Privacy: as private as the link. Revoke or expire it after sign-off.

This is often the best of both worlds: staging stays locked for everyone else, and the client gets straight in. Open the link in a private browser window before you send it. If it shows the site with no password prompt, a feedback tool can usually load it too.

Option 4: review links

A review link is a copy of your staging page inside a feedback tool, where the client can click any element and leave a comment pinned to it. With HTMLAnnotate you paste the staging address, and the site runs with its own scripts, menus and animations. Reviewers can move between pages, and each page keeps its own comments.

  • Client login: none. Reviewers give a name and email once and need no account or browser extension.
  • Search indexing: review links are private and not indexed by search engines.
  • Privacy: only people with the link can open it. Links last up to 14 days on the Free plan when you're signed in, and never expire on Pro and Team. Password-protected review links are planned but not here yet.
  • The limit: the import has to reach the page. Pages behind a browser password box can't be imported, and pages behind a sign-in form can't be imported yet. Shopify stores in Private mode are the exception: you can import them with the store password, and reviewers comment on the real store without ever seeing it. The Shopify store feedback guide covers that setup.

So review links pair well with options 2 and 3. Use a preview or share link to get past the lock, and the review link to collect the comments.

Keeping staging out of search

Whatever you choose, staging shouldn't compete with the live site in Google. The tools behave differently, and the differences trip people up:

  • Noindex meta tag. A robots meta tag with noindex in the page head tells Google to drop the page from results, even if other sites link to it.
  • X-Robots-Tag header. The same rule sent as an HTTP response header. It does the same job and also covers files like PDFs and images.
  • robots.txt. Blocks crawling, not indexing. Google can still list a blocked address it finds through links, and it never fetches the page, so it never sees your noindex rule. Don't block staging in robots.txt if you're relying on noindex.
  • A password. The strongest option, since nothing gets in. The cost is the friction above.

The catch with all of them is launch day. A noindex rule copied over from staging will hide the live site too, so check for it when you go live. It's on the website launch checklist.

Fix these before the client sees staging

A first look sets the tone for the whole review. Run through this before you send any link:

  1. Open the link in a private window, on a phone and on a laptop, to see exactly what the client will see, password prompts included.
  2. Remove dummy text and stock filler images, or mark clearly which sections still wait on client content.
  3. Click every menu item and button. Broken links in the first minute become the whole conversation.
  4. Check forms. Make sure test sends don't land in the client's real inbox or CRM, or tell them the form is switched off on staging.
  5. Confirm noindex is on for staging, and that robots.txt isn't blocking the pages you've marked noindex.
  6. Switch off anything that blocks reviewers, such as a coming-soon page, a maintenance mode or a cookie wall that hides the page.
  7. Write a short brief: which pages to review, what kind of feedback you want this round, and the deadline.

Sending it

Send one link, not a list of addresses and a password in a separate email. Say what to look at, by when, and to check the phone view too. When the client is done, resolve the comments as you fix them, publish the next version on the same link, and turn staging protection back on or revoke the share link. For the sign-off step itself, see how to get client approval on a website.

Questions

How do I share a staging site with a client without giving them a login?

Open staging for the review round through a link that needs no password, such as your host's preview or share link, then send it as a review link. The client opens it in any browser and comments without creating an account.

Will my staging site show up in Google?

It can, if it's public and nothing tells search engines to stay away. Add a noindex rule, either a robots meta tag or an X-Robots-Tag header, or put staging behind a password. Blocking staging in robots.txt alone isn't enough: Google can still list a blocked address it finds through links, and it never sees a noindex rule on a page it isn't allowed to crawl.

Is a staging password enough to keep the site private?

A password box keeps out search engines and anyone without the password. Use it over https, because browsers send basic auth details encoded, not encrypted. The trade-off is that every reviewer has to type it, and feedback tools that load the page from its address stop at the box.

Can HTMLAnnotate open a password-protected staging site?

Not when it uses the browser's password box, and pages behind a sign-in form can't be imported yet. Use a preview or share link that opens without a password, or switch the password off for the round. The exception is a Shopify store in Private mode: you can import it with the store password, and reviewers never see it.

Are review links indexed by search engines?

HTMLAnnotate review links are private. Only people with the link can open them, and they are not indexed by search engines. Treat the link like a key and send it only to the people reviewing.

Paste your staging address, send one review link and collect comments pinned to the page. Free, and your client never needs an account.

Start a free review