How to get client feedback on a Webflow site
To get client feedback on a Webflow site, share the staging subdomain URL (yoursite.webflow.io) before publishing to the custom domain — then use a review tool that lets clients pin notes to the exact element on the live page. Webflow's own commenting is team-only; your client can't use it without a Webflow account. A third-party review link fixes that: they click any element, leave a note, and you see it without chasing email.
Share the Webflow staging URL — not the final domain
Every Webflow project gets a free staging subdomain: yourproject.webflow.io. This URL is live and browsable before you've connected the client's custom domain, which makes it the right link to send for review. One common mistake: sending the client the Webflow Designer link. That lands them inside the Webflow editor — they'd need a team seat and a Webflow account to do anything. The staging URL opens in any browser, on any device, with no account. Share that link. If the site is behind a password (Webflow lets you set a site password in Project Settings), include the password in the same message or the client will hit a wall before they see anything. Staging is also safe to share before you go live: changes you push update the staging URL in seconds, so you can iterate and re-share the same link without touching the production domain.
Paste the staging URL into a review tool so clients can pin feedback to the exact spot
The core problem with "here's the staging link, let me know what you think" is that feedback comes back as a wall of text: "the header looks heavy," "something feels off near the services section," "can we change the CTA?" With no anchor to the element, you're guessing. A review tool solves this: paste the Webflow staging URL, get a shareable review link, and send that to the client. They open it in a browser — no account, no Webflow plan — hover the element they're talking about, and leave a note pinned right there. "Make the CTA stand out" arrives anchored to the actual button. Two things to check before picking a tool: does it work on your staging URL without injecting a script into the Webflow project (script-injection tools require you to edit the project just to collect feedback), and does it render properly on mobile (clients often review on their phone, which is also how their customers will see the site). Tools like Drafty and Markup.io support this without code changes.
Walk through it on a screen share before async review opens
Async comments work well for round two. Round one often goes better on a live call. Share your screen, open the staging URL in a browser, and walk section by section while the client reacts out loud. The discipline that makes it useful: stay quiet when they first see a section. Let them talk before you explain what you intended. Ask "what's the first thing you'd click here?" not "does the CTA work?" — the first question gets you their real mental model; the second gets you a yes/no. Take notes in a doc during the call and follow up with a numbered list of items you'll address. A 30-minute call before async review usually halves the number of async comments you get, because clients arrive with context and the vague impressions have already been resolved. After the call, open the review tool link for round two so they can flag anything specific they remember.
Close the loop: mark resolved, publish, share the same link
One underrated trick with Webflow's staging URL: it's a persistent link. After you address feedback, push changes in the Designer — the same staging URL updates without a new link. Send the client a message saying "I've addressed your notes, the staging link is updated" rather than sharing a new URL each round. They open the same bookmark they already have. In your review tool, resolve each comment when it's fixed so the client can see at a glance what's done and what's still open. Avoid a common trap: if you push to the custom domain before you've finished closing comments, you now have two places to track feedback — the staging URL (which some notes reference) and the live site. Finish the review cycle on staging, then publish to the custom domain as a final step.
If client feedback keeps coming in as "the thing near the top of the page" — paste your Webflow staging URL into Drafty and share the review link instead. They open it on their phone or laptop, click the exact element they mean, and leave a note anchored right there. No Webflow account, no install. Every comment lands in one threaded place; you resolve each one when it's fixed. The staging URL stays the same link as you iterate, so they open the same bookmark each round.
Open a live demoQuestions
- Can my client leave feedback on a Webflow site without a Webflow account?
- Yes — if you share the staging URL (yoursite.webflow.io) or the live site URL through a third-party review tool. Webflow's built-in commenting requires team members to have a Webflow account and a seat on your plan. External clients don't have that, so a review tool that supports guest commenting is the practical answer.
- How do I share a Webflow site for client review before it goes live?
- Use the Webflow staging subdomain — yourproject.webflow.io. It's available as soon as you create the project, before you connect a custom domain. In Project Settings you can also set a site password so only your client can access it during review. Share the staging URL (and password if set) directly in your message.
- Why is Webflow's built-in commenting not working for my client?
- Webflow's comment feature is designed for collaborators inside your Webflow team, not for external clients. Your client needs to be added as a team member with a paid seat to use it. For client review, a third-party tool that takes the staging URL and gives your client a guest-commentable link is the standard workaround.
- Do website feedback tools work on Webflow staging URLs?
- Most do, but check two things: whether the tool works on password-protected staging URLs (some proxy-based tools can't handle them), and whether it renders your Webflow animations and custom code correctly. Link-based tools that annotate the live page in a browser — rather than proxying or screenshotting it — handle Webflow's JavaScript and scroll animations better.
- How do I get clients to give specific feedback on a Webflow site instead of vague impressions?
- Give them a way to point at what they mean. A review tool that lets them click an element and leave a note anchored to it produces "make the headline stronger" pinned to the actual H1, not a paragraph email describing its location. Pair it with one or two specific questions per section — "does the pricing table make the tier difference clear?" — rather than open-ended "thoughts?"
- Can clients review a Webflow site on their phone?
- Yes — Webflow staging URLs open in any mobile browser. If you're using a review tool, make sure it supports mobile commenting. Extension-based tools don't work on mobile browsers at all; link-based tools that open in Safari or Chrome on iOS work fine.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.