In your stack
Your client reviews the webflow.io build, Collection item pages included
Publish to yoursite.webflow.io, paste that URL into Writhink, and send one link. Your client clicks the thing that is wrong and types. Every pin records the exact page it was left on — which, on a Collection template rendering two hundred items, is the difference between a content fix and a template fix.
No credit card. Your client doesn’t need an account.
01
One template, two hundred pages
A Webflow build is mostly not pages. It is a handful of Collection page templates rendering whatever the client has put in the CMS. You designed one case study layout; your client is looking at forty case studies, and they do not think of them as one thing.
So the feedback arrives detached from its subject. "The image is stretched on the case study page." Which one. "The heading wraps badly." At what length. You open the template, everything looks correct, because the item they were on is the one with the seventy-character title and no cover photo.
A Writhink pin is left on the rendered item page and carries that page's URL with it: /work/northfield-dairy, not "the case study page". You open the item they were actually on and see what they saw.
02
Template bug or content bug, read off the grouping
Once every comment carries its item URL, a single round tells you which layer to fix. Five comments spread across five different items that all land on the same element are not five bugs. They are one template that breaks whenever a field runs long, and you fix it once, in one place.
The inverse is just as useful. Four comments piled on one item with nothing on its siblings is a data problem: the wrong photo uploaded, an empty field, a paste out of Word that brought its own formatting along.
Writhink groups comments by page and by element for you, but it has no view into the CMS — it sees rendered pages and their URLs, and nothing about the Collection behind them. The grouping you read is a URL grouping, and on a Webflow build that turns out to be exactly the grouping you wanted.
03
Which items to put in the round
Do not paste two hundred URLs into the project. Add the handful that stress the template, plus the Collection list page, and the round covers the build.
- The longest title in the Collection, and the shortest one.
- An item with no cover image, if that field is allowed to be empty.
- The item with the most tags, categories or reference fields, because that is the row that wraps at the wrong width.
- One item with a genuinely long rich-text body, so somebody reviews the reading experience and not only the header.
- The Collection list page itself, where the cards live — half of all layout complaints turn out to be about cards rather than items.
- One item that was imported rather than typed, since imported content is where the stray markup hides.
04
The round, start to finish
- Step 1
Publish to the staging subdomain
Publish to yoursite.webflow.io and leave the custom domain out of it. Webflow serves that subdomain with a noindex, so a review copy sitting there is not going to surface in search while the client picks at it.
- Step 2
Add the pages you chose
Paste each URL into a Writhink project. The pages are served through Writhink's proxy so a pin can attach to an element rather than to coordinates on a picture of the page.
- Step 3
Send one link
The review link authorises itself. Your client is asked what to call them and nothing else. No Webflow seat is involved, and nothing gets installed on their machine.
- Step 4
Let them pin
Each comment carries the item URL, the element they clicked, its position, the viewport width, the device class — desktop, tablet or mobile — and a screenshot of that spot captured as the comment is written.
- Step 5
Close the round and read the list
Duplicates merge, items group by page and element, priorities get set, and the loose comments are rewritten clearly without acquiring requests nobody made. Anything still genuinely ambiguous is marked unclear rather than guessed at.
05
Two Webflow cases a review link cannot cover
| The case | What to do | Why |
|---|---|---|
| The Designer canvas, or a Designer preview link | Pin it yourself with the Chrome extension | That view only exists inside your logged-in Webflow session, so there is no public URL to hand anybody. The extension comments on whatever page your browser already has open, and it needs a Writhink account — which makes this a path for you and your team, not for the client. |
| The webflow.io copy once the custom domain is live | Start a fresh project against the real domain | Webflow keeps both hosts publishable and they drift the moment you publish to one and not the other. A client still reviewing the staging copy will report things you shipped a week ago. |
There is no Writhink panel inside the Designer and no marketplace listing — all of this happens on the published page, from outside Webflow.
06
The handover window
Between the last staging review and the day DNS points at Webflow, the site exists twice. This is where client review quietly goes wrong, and it is a Webflow-shaped problem rather than a general one, because the staging host does not disappear when the real domain arrives.
Pins are recorded against the URL they were left on. A round run on yoursite.webflow.io stays attached to yoursite.webflow.io and stays readable there, screenshots and all. What it will not do is follow the site onto the production domain, and a client who keeps the old link keeps reviewing the old host.
So bring the round to a close before the switch, and treat post-launch review as a new project against the live domain. It costs you one extra project and saves the argument about whether a comment was already handled.
After launch, when reports arrive as one-offs months apart instead of rounds, the embeddable widget is the better shape: a script tag pasted into Site settings, Custom code, before the closing body tag. Anyone on the live site can then report something in place, and the widget shows a small Powered by Writhink badge while it is there.
07
Handing the round to whoever does the work
Nothing is going to move a div in the Designer for you. On a pure Webflow build, what the generated prompt gives you is a brief you can work down: every request in plain language, deduped, grouped, prioritised, with the item URL and a screenshot on each line. That is one pass through the list instead of three passes through a comment thread.
If part of the build is not Webflow — an embed, a custom script, a Next.js front end consuming the Webflow CMS through the API — the same output pastes into Cursor, Claude Code or ChatGPT unchanged. With an MCP-capable client you can skip the paste entirely: run claude mcp add --transport http writhink https://mcp.writhink.com/mcp and the assistant reads the feedback itself, authenticated as you and seeing only what your account can see.
The prompt closes by asking for draft replies to the items marked unclear, so the follow-up question to the client is written before you remember you owe them one.
Before you count on it
Writhink is in open beta: everything described here is available and free, no credit card. Paid plans are announced but not purchasable yet. The one limit that applies today is five AI prompt generations a month per organization.
FAQ
Questions people actually ask
- Do I need to give my client a Webflow seat?
- No. Webflow's own commenting lives in the Designer and needs somebody on your workspace. The Writhink review link needs neither a Webflow account nor a Writhink one — your client opens a URL, picks a display name, and starts pinning. Their comments stay theirs to edit or delete, proven by a token stored in their browser.
- The staging subdomain has password protection turned on. Now what?
- A review link cannot type the password for your client, so they land on Webflow's password screen and stop. Either switch protection off in Site settings for the length of the review, or leave it on and pin the pages yourself with the Chrome extension, which works on anything your own browser is already through. There is no third option.
- Can my client review a Collection item that is not on the live site yet?
- A draft item has no URL anywhere, so set it live and publish to the webflow.io subdomain only — Webflow lets you choose domains at publish time. The item becomes reviewable on staging without appearing on production, and the noindex Webflow puts on that subdomain keeps it out of search.
- I republish ten times a day. Do the pins survive?
- Mostly. Writhink stores the element anchor, the position on the page and a screenshot taken at the moment of the comment. Editing copy or swapping an image leaves a pin where it was. Rebuilding the structure of a section can move one, and then the screenshot is what tells you what your client was looking at.
- Does Writhink know which Collection a page belongs to?
- No. It sees the rendered page and its URL, the same as any visitor. In practice the URL does the job, because item pages share a path prefix — pins on /work/anything read as one group without anything ever being told what the Collection is.
Start
Send one link. Get feedback you can build from.
Your clients comment right on the page — no account, no screenshots, no voice notes. Writhink sorts the comments and writes the prompt for your AI.