The Client Feedback Tool for Webflow Projects
Send your Webflow staging or live URL, get precise comments pinned to the page. Clients review without a Webflow seat, a login or any setup.
Webflow review should not live in your inbox
You ship the staging URL on Friday and by Monday your inbox has fifteen emails, a Slack thread and three Loom links. dotts pulls all of it into one clear place. Clients open a review link, click anywhere on the live or staging Webflow site and leave precise comments pinned to the exact element, with browser and viewport already attached. No Webflow seat needed.
Webflow client review, before and after dotts
Emails about staging URLs clients can barely navigate
"The button on the pricing page" which one of the four
Figma feedback that does not match the live site
Designer, PM and client in separate threads
Multiple revision rounds, slow handoff
One review link, no Webflow seat needed
Comments pinned to the exact element on the live page
Browser, device and screen size on every comment
@-mentions, file attachments, threaded discussions
Mark items as done, see what's still open
Made for the Webflow handoff
Works with .webflow.io subdomains, custom staging domains and live production sites.
Skip the Workspace invite. Clients open a review link in any browser and start commenting.
Comments are pinned to the exact element with browser, OS and viewport metadata attached.
How freelancers use dotts on Webflow projects
Staging URL handoff
Share your .webflow.io staging URL with the client through dotts. No Webflow seat, no Designer access, just a review link.
Pre-launch QA
Final live review before pointing the custom domain. Catch typos, mobile glitches and copy tweaks in one pass.
Multi-team design review
Designer, PM and developer leave feedback in the same thread, with @-mentions and clear pinned context.
Three steps to feedback on your Webflow site
Copy your Webflow staging or live URL and paste it into dotts. No embed, no custom code, no integration.
dotts creates a review link. Send it to your client. They open it in any browser, with no Webflow seat needed.
Clients click anywhere to leave pinned comments. You reply, mark items as done and keep every request in one place.
Published site, staging URL or password-protected?
| Situation | Works with dotts? | Note |
|---|---|---|
| Published Webflow site on a custom domain | Yes | Paste the URL and you are done. No plugin, no snippet, no change to the site. |
| Published site on *.webflow.io | Yes | Works by the same rule as a custom domain: what counts is that the URL is publicly reachable. |
| Webflow password protection | Not confirmed | Platform password pages are not confirmed to work. Remove the password or share the published site for the review. A Webflow site on a custom domain is one of the two reference sites that run through the proxy completely. |
| Editor preview or a link that asks for a sign-in | No | dotts fetches the page without a session. If the link leads to a login, dotts says so instead of showing a blank frame. Use a publicly reachable URL. |
| Site behind HTTP Basic Auth | No | Tested on 16 September 2026: the proxy passes the 401 and the authentication challenge through, but the browser offers no sign-in inside the review frame, so the page stays empty. dotts has no field for those credentials. Take Basic Auth off for the review and put a password on the dotts link instead. |
| Cookie banner on the site | Yes | Tested on 16 September 2026: the choice your client makes in the banner is stored on the review link and survives a page change, so the banner does not come back on every click. |
| Site behind a WAF or bot filtering | Not tested | Some protection systems block any proxy. That cannot be solved server-side with any guarantee. Try the link before you send it to your client. |
Checked against the dotts app and proxy code on 15 September 2026 and re-tested through a live review link on 16 September 2026 (docs/platform-facts-2026-09.md). "Not confirmed" means we have not seen it work and do not claim it does. If you try it, tell us and we will put the answer here.
Webflow feedback, answered
Yes. dotts works on any publicly accessible Webflow site, including .webflow.io staging URLs and custom domains. Paste the URL and share the generated review link.
No. Clients do not need a Webflow seat, a Workspace invite or any login. They open the review link and comment directly.
Yes. dotts works with .webflow.io staging URLs as well as live custom domains.
No. dotts needs no embed, no custom code and no integration. It works through a shared review link.
Yes. Besides Webflow, dotts also collects client feedback on Squarespace, Wix and Framer sites — the workflow is identical. New to this? See how to get feedback on a website.
What a review with dotts looks like
One link to share
Paste the URL of a live site, or upload a PDF or an image. dotts gives you a link to share, with a password if you want one.
Clients comment without an account
They type a name, the email is optional, and the Just browsing option skips even that. No signup, no install.
Every comment carries its context
Browser, device, screen size and page URL are stored on the comment, together with a screenshot that already has the dot on it.
Set the status, or have it set
Open, in progress, resolved. On Pro, Claude Code or Cursor read the comments over MCP, change the status and reply as doby AI.
Collect Webflow feedback the easy way
Share one link, get precise comments pinned to your live or staging Webflow site. No client seat, no login, no back and forth.
Not tested. There is nothing in the dotts code about Webflow's password protection, so we make no claim either way. A Webflow site on a custom domain is one of the two reference sites that run through the proxy completely.