How to share a staging link for feedback
To share a staging link for feedback, paste the URL into an annotation tool and share that link instead of the raw one. Your client clicks any element and pins a note to it — no login. Without this step, the feedback arrives as voice notes, screenshots that don't match the next deploy, and emails describing 'the button near the top.'
Wrap the staging URL in a review layer
A raw staging link — staging.yoursite.com, a Vercel preview URL, a Netlify deploy — works fine as a site. It gives your client nothing to comment on. They fire off a voice note, annotate a screenshot that's stale by the next deploy, or describe the 'blue button near the top' in an email. Paste the staging URL into an annotation tool instead. Tools like Drafty, Pastel, or Ruttl take any URL and return a review link. Your client clicks the exact element — hero, nav, pricing row — and the note lands pinned right to it. The staging URL keeps deploying; the review layer stays.
Set up basic access control first
Before sharing the link, confirm the staging URL is accessible to your client and not indexed by search engines. On Vercel, every Preview deployment is already behind authentication by default — you may need to add your client's email to the project or use Vercel's deploy protection settings to generate a bypass link. On Netlify, site passwords are set under Site settings > Access control. On a WordPress staging host (WP Engine, Kinsta, Flywheel), the host usually provides a staging domain with its own password field. If you skip this step and the client gets a 401, the first message you get back is 'I can't open it' — not feedback.
Send the review link with a short brief
Don't just drop the link. One sentence of context cuts a round of revision: 'Here's the staging link — click anything you'd like changed and leave a note directly on it. No account needed.' Clients who receive a bare URL default to their most comfortable feedback channel, which is usually the one that produces the least useful output. Tell them how to use the review layer before they find another way. If there are specific pages or sections you want them to focus on, name them explicitly — 'the homepage and the Services page are the ones I need eyes on this round.'
Do a complete pass before the client does
Open the review link yourself first. Check on desktop and on mobile — most layout breaks only show up at a specific breakpoint. Confirm all placeholder text is gone, every link goes somewhere real, and forms submit correctly. Clients remember the first impression of a staging link; a broken layout or 'Lorem ipsum' on the hero shifts the conversation from feedback to damage control. A 20-minute self-review before sharing saves two rounds of explaining.
Collect all feedback before acting on any of it
The most expensive staging mistake: starting revisions before the client has finished commenting. Fix the homepage hero while they're still on the contact page, and you'll create conflicts that need a full third pass to reconcile. Set a deadline for the feedback round — 'I'll check notes Friday' — and hold it. Read through the whole thread before touching code. Conflicting notes from two stakeholders show up immediately on a shared board; in separate email chains, you only find the contradiction on revision two.
Sending a client a staging link? Paste it into Drafty and share that link instead of the raw one. They click the element they mean — the nav, the headline, the mobile footer — and leave a note pinned right to it. No account, no screenshot, no voice note. Every comment lands in one thread anchored to the spot. If you push a new deploy to the staging URL, the review link still works — and Drafty's versioning keeps a record of every feedback round.
Open a live demoQuestions
- How do I share a Vercel or Netlify staging link for feedback?
- Deploy normally — Vercel and Netlify both generate a preview URL per deploy. Copy that URL and paste it into an annotation tool (Drafty, Pastel, Ruttl) to get a review link with element-pinned commenting. For Vercel, check deploy protection settings first — by default, preview URLs require authentication, so you may need a bypass link or to add your client as a project member.
- Does my client need an account to comment on a staging link?
- Not if you share a review link rather than the raw staging URL. Annotation tools that support guest commenting let your client click any element and leave a note with no signup. The distinction matters: the staging host (Vercel, Netlify, WordPress) may require a password to access the site; the annotation layer on top of it does not.
- How do I prevent the staging site from being indexed by search engines?
- Add a noindex meta tag or configure your host's robots settings. On Vercel, all Preview deployments are noindexed by default. On Netlify, set the X-Robots-Tag header to noindex in netlify.toml. On WordPress, enable the 'Discourage search engines' setting in Settings > Reading. If you use a password-protected staging domain, crawlers are blocked at the network level regardless.
- What is the best way to collect feedback on a staging site from multiple stakeholders?
- Use a shared review link everyone opens simultaneously. A common pitfall: two stakeholders submit contradictory feedback via separate email chains, and the designer only sees the conflict on the third revision. On a shared board, stakeholders see each other's notes before they're sent, which resolves most disagreements before they reach you.
- Why does email feedback on staging links cause extra revision rounds?
- Because descriptions of visual elements are almost always ambiguous without a reference point. 'The button near the top' might mean the nav, the hero CTA, or a sticky bar — and you won't know until you guess wrong. A comment pinned to the exact element removes the ambiguity before the revision starts. Designers who switch from email-based feedback consistently report shorter review cycles for this reason.
- How do I share a WordPress staging site for client review?
- Most managed WordPress hosts (WP Engine, Kinsta, Flywheel) generate a staging subdomain automatically and offer a one-click password toggle. Share the staging URL plus the password. To add element-pinned commenting, paste the staging URL into an annotation tool — it works the same way as any other URL. Note: some annotation tools can't reach a password-protected URL without credentials, so check whether the tool supports authenticated staging sites.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.