Website design feedback tool
Collect website design feedback on the real page instead of in an email thread. Clients click the element they mean and comment, and every note arrives with a screenshot, the page and the screen size it was made at.
01
Feedback on the element, not a description of it.
A client pins a comment to the heading, button or image they mean. You get the exact element, not “the thing near the top”, and a screenshot of what they saw.
02
Mark up the screenshot.
Circle, box or arrow the part of the design that needs to change, so a note about spacing or alignment points at the pixels it is about.
03
Check spacing and type without guessing.
Inspect mode shows an element’s size, padding, margins, font and colours on the live page, so “make it bigger” turns into a value a developer can set.
04
Review every breakpoint.
Switch between desktop, tablet and mobile widths in the review, and each pin records the screen size it was left at.
Keep reading
Frequently asked questions
Short answers before you start.
What is a website design feedback tool?
A tool that lets clients and teammates comment on a website design where it lives, in the browser, instead of describing it in an email. Each comment is tied to the element it is about, with a screenshot, so the designer or developer knows exactly what to change.
Do clients need an account to leave design feedback?
No. They open the review link, type a name and start pinning comments. There is nothing to install and no password to manage.
How is this different from commenting in Figma?
Figma comments sit on the design file. Website design feedback here happens on the built page in the browser, with real content, real fonts and real breakpoints, which is where most last-round design issues show up.
Can I collect design feedback on a staging site?
A public URL, staging included, works from the review link alone with nothing added to the site. For pages behind a password or login, add the one-line Layerdock snippet before </body>, and the review link loads your real site. The docs page “Review a web app behind a login” has the steps.