Works with · Webflow
Client feedback on Webflow sites
Send your client the webflow.io staging link through HTMLAnnotate and they pin notes on the exact section, button or image they mean. No Webflow seat, no Designer, no account.
Free for 3 projects. Reviewers never need an account.
Why Webflow teams use HTMLAnnotate
Webflow makes building fast, but the review round is where projects stall. You publish to staging, send the webflow.io link, and the replies come back as a long email: "the second section feels off", "can the button be bigger", a screenshot of a phone with a red circle. You spend the next hour working out which section, which button, and whether the note was about the desktop layout or the mobile one. Freelancers and small agencies hit this on every project, usually more than once.
Webflow's own comments are good, and comment-only links now let people leave notes without an account. They open the site in Webflow's preview on the canvas, though, which suits teammates more than a client who just wants to look at their website. Screenshots lose the hover states and interactions you spent days on. Loom videos are slow to scrub through, and emails turn a simple fix into a thread of guesses about what "the top bit" means.
With HTMLAnnotate, the client opens the real published site in their browser, with your interactions running. They switch to Comment mode, click the heading or image they mean, and type. Each note is pinned to that element, tagged with the page, the view (Desktop, Tablet or Mobile) and their browser and screen size. You get one list to reply to, resolve, and hand over, instead of a pile of messages to decode.
How it works with Webflow
Three steps, about a minute.
Publish to staging
In the Designer, click Publish and tick your webflow.io subdomain. If the site is already live on a custom domain, you can use that address instead.
Paste the link
Paste the webflow.io address into HTMLAnnotate. You get a review link back in a few seconds, with every page of the site reachable from it.
Send it to your client
They open it in any browser, give their name and email once, click what they mean and type. Interactions and animations keep running.
A full review round, start to finish
What a typical round looks like on Webflow.
Get staging ready
Publish the latest version to your webflow.io subdomain only, so the custom domain stays untouched. If you set a site password under Site settings, General, Website password, turn it off for the round: Webflow's password page is a form, and HTMLAnnotate can't get past it yet.
Create the review link
Paste the webflow.io address into HTMLAnnotate. Sign in first if the round will take more than a day, since links made without an account last one day, and up to 14 days on Free. Pro and Team links never expire.
Brief the client
Send the link with two sentences: use Browse mode to click around as normal, switch to Comment mode to leave a note on anything. Ask them to check Tablet and Mobile too, because notes stay in the view they were left in.
Collect and sort
As notes arrive, add labels such as Copy, Design or Bug and set a priority. Reply to anything unclear in the thread. If the client typed new wording as a suggested text change, open it to see the new words live on the page.
Make the fixes in Webflow
Press Copy for AI to get every open comment as one brief with the element, CSS selector, view and page path. Work through it in the Designer, or paste it into your AI tool to plan the changes, then republish to staging.
Check and sign off
The review loads the latest staging version each time it opens, so the client sees your fixes in place. Resolve each comment as you confirm it. When they are happy, they press Approve, and you can switch comments off and publish to the custom domain.
Webflow's own tools and HTMLAnnotate
Use both. Here is what each is good at.
| What you need | Webflow comments | HTMLAnnotate |
|---|---|---|
| Comment without an account | Yes, with a comment-only link | Yes, name and email once |
| Where reviewers comment | Webflow preview mode on the canvas | The published site in their own browser |
| Best suited to | Teammates and collaborators working in the Designer | Clients and stakeholders who just want to look |
| Notes on elements made with custom code | Not supported | Yes, any element the page renders |
| Notes on elements shown only by animation | Not supported | Yes, the site runs live |
What works
- Interactions, sliders and dropdown menus run as they do on the real site
- Separate Desktop, Tablet and Mobile notes, which fits how Webflow breakpoints work
- Every page of the site can be reviewed from one link
- Notes can sit on custom code embeds and SVGs, not just Webflow elements
- Copy for AI turns open comments into one brief for whoever builds the changes
- Nothing is added to your Webflow project or published code
Good to know
- Webflow's site and page passwords use a form, so protected pages can't be imported. Turn the password off on staging for the round, or review before you add it.
- Forms on the reviewed copy can't be sent, so test submissions never reach your client's inbox.
- Edits still happen in the Designer. HTMLAnnotate never changes your project, so someone still has to make each fix and republish.
Tips for better Webflow reviews
Map the breakpoints
HTMLAnnotate's Tablet view is 820px wide, which lands on Webflow's Tablet breakpoint (991px and below). Mobile is 390px, which lands on Mobile portrait (478px and below). Check Mobile landscape yourself in the Designer.
Publish staging only
In the Publish menu, tick only the webflow.io subdomain while the round runs. The client reviews the new version while the live custom domain stays as it was until they approve.
Remove the password for the round
Webflow's site password applies to the whole project, including webflow.io. If you rely on it, take it off for the few days of review, then put it back before you publish anywhere else.
Name your pages clearly
Each comment records the page path, so tidy slugs like /pricing or /about make the Copy for AI brief easy to follow when you work through it in the Designer.
Questions about Webflow
Does my client need a Webflow account?
No. They open the review link in any browser and give their name and email the first time they comment. They never see the Designer and can't change anything in your project.
Can I review the webflow.io staging site?
Yes. Any address that opens in a browser without a sign-in form works, including webflow.io staging links. If the staging site has a Webflow password turned on, switch it off for the review round.
How is this different from Webflow's comment-only links?
Webflow's comment-only links open the site in Webflow's preview on the canvas, which works well for collaborators. HTMLAnnotate shows the published site in the reviewer's browser and adds suggested text changes, Approve, labels, priority, CSV export and a Copy for AI brief.
Will comments break when I republish?
No. Each comment is pinned to the element it is about, and the review fetches the latest published version every time it is opened, so your client sees the fixes in place.
Can my client comment on the mobile layout?
Yes. They switch to Mobile in the review bar, and their notes stay in that view. Tablet works the same way, so you always know which breakpoint a note is about.
Can I review a password-protected Webflow page?
Not yet. Webflow's password page is a sign-in form, which HTMLAnnotate can't import. Turn the password off under Site settings, General, Website password while the review runs, then turn it back on.
Other website builders
HTMLAnnotate works with any page anyone can open in a browser.