Website feedback
Run the launch review before the domain switches over
A launch review is a process with an order to it. You check the obvious things yourself, then you put the build in front of the people who have to sign off, then you close every comment they leave before the site goes live. Writhink covers the middle and the end: one link reviewers open without an account, comments pinned to the exact element they mean, and four statuses that tell you at a glance how much is still outstanding.
No credit card. Your client doesn’t need an account.
01
The order to run a launch review in
Most launch reviews fail on sequence, not on effort. Ten people looking at everything at once produces forty duplicate notes about the homepage and nothing at all about the checkout.
- Step 1
Do your own pass first, against a written list
Before anyone else sees the build, walk it yourself: submit every form for real and check the email arrives, open the 404 page, load the site at 390px wide, read the metadata and the share cards, follow the redirects from the old URLs. Every typo you catch here is a review round spent on judgment instead of proofreading. We keep a free list for this at /tools/website-review-checklist.
- Step 2
Put the build behind one review link
Create a project, paste the URL of the live site or the staging build, and share the link Writhink hands back. The page loads through the Writhink proxy, which is what lets a comment attach to a real element instead of floating on top of a picture of the page.
- Step 3
Tell each reviewer what they own, and by when
Reviewers who are given the whole site check the homepage on their own laptop and stop. Split the surface up, name a date, and put both in the same message as the link. The next block is a working split you can copy.
- Step 4
Collect in one window rather than in a trickle
A reviewer opens the link, types a display name, and starts pinning. No account, no install, no invite to accept, which matters on the afternoon the client's boss joins the review. They click the element they mean, write the note, attach a file if they have one (up to five files, 10 MB each), and reply to each other in a public thread on the pin. You will get duplicates and half-formed requests; the next step is built for exactly that.
- Step 5
Turn the pile into a work list
Generate the AI prompt. Writhink rewrites the vague comments for clarity without inventing requests, merges duplicates, groups items by page and by element, suggests priorities, and keeps the pin data and the screenshot attached to each item. Anything still ambiguous is flagged as unclear and left for the client to answer. Paste the result into Claude Code, Cursor, ChatGPT or whatever you build with, or read what a usable prompt has to carry on /feedback-to-prompt first.
- Step 6
Move the statuses as the work moves
Open, in progress, in review, resolved. One glance at the status column is the whole progress report, which is what you want when someone asks how the launch is going for the third time that day.
- Step 7
Close each item with the reviewer, not with yourself
Reply on the pin. Replies are public to the person who left the comment, so they can check the change at the same spot, on the same page, at the same width, and then confirm. An empty open column with every item confirmed is the sign-off. Resolving comments you never answered is the most reliable way to receive the same request again in round two.
02
Split the surface before you send the link
Six assignments cover most sites. Say who has which one in the message that carries the link, so nobody assumes someone else is doing it.
- The client or the content owner: names, prices, job titles, opening hours, the legal pages, anything only they can confirm is true.
- One reviewer on a phone and nothing but a phone. Their pins record the viewport size and the device class, so a comment that only applies at 390px stays tied to 390px.
- One reviewer on everything that leaves the site: outbound links, redirects from the old URLs, the share card that appears when someone posts the link, the favicon.
- One reviewer on the pages nobody remembers: 404, thank-you and confirmation pages, password reset, search results with no results, the print view if it matters.
- Whoever owns the forms: submit each one for real, from the reviewer's own address, and confirm the notification lands in the right inbox rather than a spam folder.
- You, on everything else, before any of the above start. See step one.
03
The four statuses, and who moves them
Every comment in Writhink sits in exactly one of four states. This is the page that leans on them, because a launch review is finished when the open column is empty and not before.
| Status | What it means | Who moves it |
|---|---|---|
| Open | Nobody has picked it up. Every new comment lands here. | Set automatically when the comment is created |
| In progress | Someone on your side is working on it right now. | Your team |
| In review | The fix is live on the reviewed URL and needs a second look. | Your team, then the reviewer looks |
| Resolved | The change is done and the reviewer has confirmed it. | Your team, after the reviewer replies on the pin |
Why four states rather than a checkbox: in review is the one that carries the launch. It separates work you have finished from work the client has accepted, and those two numbers are never the same on the last day.
04
The checklist is the other half of this
The comments you get back are only as good as the brief you gave. A reviewer with no list checks the homepage, likes it, and replies looks great. A reviewer with a list finds the contact form that posts to an inbox nobody reads.
We keep a free pre-launch checklist at /tools/website-review-checklist. It covers the things that break quietly: forms and where their notifications actually go, the 404 and the other pages with no links pointing at them, mobile widths, page titles and descriptions, share cards, broken and outbound links, redirects from the old site so the search results you already have keep working, analytics firing on the pages that matter, and the legal pages someone has to sign off on.
Use it twice. Once yourself, before the link goes out, so the review is not spent on things you already knew about. Then paste the sections that are relevant into the message with the review link, one section per reviewer, so the assignments in the block above arrive as specific instructions rather than a request to have a look.
05
Builds a review link cannot open
Plenty of pre-launch builds cannot be loaded through a proxy: a members area behind a login, staging with basic auth, a branch running on your laptop. For those, install the Writhink Chrome extension and pin comments directly on the page in your own browser session. Same project, same pins, same statuses. It is Chrome only, and whoever comments has to install it, so use it for your own passes and for developers rather than for a client.
There is a third way in, useful the day after launch rather than the day before: an embeddable script you drop on the page, so anyone can leave a pin at any time instead of only during a scheduled round. It carries a Powered by Writhink badge.
06
What Writhink will not do for your launch
It does not scan anything. Writhink never crawls the site, never runs a performance audit, never finds your broken links or your missing alt text on its own, and produces no score and no report. Every item in a Writhink review was left there by a person who looked at the page. If what you want is an automated site auditor, this is the wrong category of tool, and the two are complements rather than substitutes.
There is no automatic ticket creation either. Writhink has no native integrations with Jira, Linear, Asana, Trello or anything else — none exist. You can export the feedback, or connect an AI client to the Writhink MCP server so it reads the items with their full context and writes the tickets itself, but nothing syncs on its own.
There is no session replay and no video capture, so you cannot watch a reviewer use the site. The extension is Chrome only, with no Firefox, Safari or Edge build. And if procurement asks for SSO or a SOC 2 report before launch day, Writhink has neither.
Before you count on it
The embeddable widget carries a “Powered by Writhink” badge. The white-label add-on that removes it is announced but not purchasable during the beta, so today the badge stays.
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
- Can I run the review on a staging site that is behind a login?
- Yes, with the Chrome extension. The proxy behind the share link cannot get past a login screen, but the extension pins comments on the page in your own browser session, including localhost and password-protected staging. Those comments land in the same project as the ones left through the link.
- Does Writhink find the problems for me?
- No. It collects and organizes what people found. There is no crawler, no automated audit, no score. Pair it with a checklist for the mechanical checks and use the review for the judgment calls, which is the part software cannot make for you.
- How long should a review round stay open?
- Long enough for one complete pass and no longer, and say the date in the message with the link. Rounds without an end date collect comments in a trickle for a fortnight, which means you are fixing round-one items while round-two items are still arriving.
- What happens to a comment after I fix it?
- You move it to in review and reply on the pin so the reviewer knows where to look. The pin keeps its page URL, its element anchor, the viewport it was left at and its screenshot, so you are both looking at the same spot even after the page has changed. When the reviewer confirms, you set it to resolved.
- Can I get the review into our task tracker?
- Only by hand or through an agent. There are no native integrations. You can export the feedback, or point a tool like Claude Code or Cursor at the Writhink MCP server so it reads the items with their pin context and creates the tickets for you.
- What about feedback after the site is live?
- Add the embeddable widget to the page and the same project keeps receiving pins, so the first week of real-world reports arrives in the same list and the same four statuses as the launch review, rather than in six separate emails.
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.