How to Collect Client Feedback on a Website (Step by Step)

Knowing how to collect client feedback on a website is half of delivering the project. The design can be finished on time and still slip by two weeks because comments arrive as a 40-line email, a voice note and a PDF with arrows that point at nothing. Most of that delay goes away with one feedback channel, a fixed review window and a short briefing email, and there's one at the end of this page you can send today.

What is client feedback on a website?

Client website feedback is any comment, correction or request the client makes about a site you're building for them, usually during a review round on a staging or live URL. It covers bugs ("the form doesn't send"), content changes ("update the phone number"), design requests ("make the logo bigger") and new ideas ("can we add a blog?"), and each type needs a different response.

The problem is rarely the feedback itself. It's the format. A developer needs to know which page, which element, on what device and what should happen instead. Most clients don't think in those terms, so the method you choose has to collect that information for them.

What are the ways to collect client feedback on a website?

There are five common methods: email, shared documents or spreadsheets, PDF comments on screenshots, video calls and visual feedback tools. They differ in whether the screenshot, the exact URL and the browser details arrive automatically, and in how much effort they ask from the client. Most agencies combine a call for the first look with a visual tool for everything after.

• Email: everyone knows how to use it, which is its only real advantage. Comments arrive in long threads, mixed with unrelated questions, with descriptions like "the second image on the services page" and cropped phone screenshots with no URL.
• Shared documents and spreadsheets: a document or a sheet with columns for page, comment and status gives you one place for everything, but the client still describes locations in words, copies URLs by hand and pastes screenshots. Most give up halfway.
• PDF comments on screenshots: works for static designs, but the PDF is out of date as soon as you change anything, can't show hover states, forms or mobile menus, and says nothing about the client's browser.
• Video calls: walking through the site together is great for the first review of a new design, because you hear the reasoning. Someone has to take notes, though, and a call for every small fix doesn't scale.
• Visual feedback tools: a button on the website lets the client mark up a screenshot of the page and write a comment; the URL and technical data are attached automatically and everything lands in one list.

How do you run a website review round?

Freeze the version on a staging URL, set up one feedback channel and test it yourself, send a briefing email with a deadline, give a fixed window of three to five working days, triage every item into bugs, content changes, design requests and new scope, fix and mark items resolved, and close the round with a written summary.

1. Freeze the version: deploy to a staging URL (or the live site, if it's an update) and stop changing things during the review window. Feedback on a moving target creates duplicates.
2. Set up the feedback channel: install your feedback tool on the staging site and send a test report yourself before the client sees it.
3. Send the briefing email: what to review, how to leave feedback and the deadline. A template is below.
4. Give a fixed window: three to five working days is usually enough. An end date gets more focused feedback than an open "let us know".
5. Triage daily or at the end: one person on your side reads every item, merges duplicates, labels each one (bug, content change, design request, new scope) and asks about anything unclear.
6. Separate in-scope from out-of-scope: new features and changes to approved decisions go to a separate list to quote or schedule. Don't fix them silently.
7. Fix and mark as resolved: so the client sees progress without asking.
8. Close the round in writing: what was fixed, what moved to a later phase and what you need next, often approval (see our guide to client website approval).

What does good client feedback look like?

It answers five questions: where it happens (page and element), what happens now, what should happen instead, the context (device, browser, screen size) and the evidence (a screenshot with the problem marked). Vague feedback answers one of them at best. If your method doesn't capture the rest automatically, ask the client for them explicitly.

Website feedback examples, vague and good:

• Vague: "The contact form is broken." Good: "Contact page: when I click Send after filling in all fields, nothing happens and no thank-you message appears. iPhone 14, Safari. Screenshot attached with the button circled."
• Vague: "Make it pop more." Good: "Home page hero: the headline gets lost on the photo. Could it be white on a darker overlay, like the services page?"
• Vague: "The images are wrong." Good: "About page: the team photo is from 2023. Please use the new one in the shared folder, file team-2026.jpg."

Each good version can be acted on today; each vague one needs a call. For bugs specifically, our bug report template goes into more detail.

How do you brief a client for a website review?

Send one short email with a single link, a single way to leave feedback, what to focus on in this round, an example of a useful comment, the deadline and how many rounds the project includes. Clients give better feedback when they know exactly what you want, and naming the number of rounds sets expectations without sounding defensive. Adapt this one:

Subject: Website review: please send your feedback by Friday 16 October

Hi Laura,

The new website is ready for your review at: https://staging.example.com

What to review this round: all pages in the main menu. Please focus on
content (texts, images, contact details) and anything that doesn't work
as you'd expect.

How to leave feedback: on your computer, click the "Give Feedback"
button at the bottom of any page. Your browser will ask for permission
to capture the tab; click "Share". Draw on the screenshot to show what
you mean, then add a short title and description. One comment per
issue, please. No account needed.

A good comment says what you see now and what you'd like instead.
For example: "The phone number in the footer is old. It should be
600 123 456."

Deadline: Friday 16 October. We'll make the changes the following week
and send you a summary.

This is review round 1 of 2 included in the project. New pages or
features can be added later, and we'll quote them separately.

Thanks,
Alex

How does GiveFeedback.io collect client feedback?

GiveFeedback.io adds a "Give Feedback" button to the site with one JavaScript snippet. The client clicks it, the browser captures the visible part of the page, the client marks it up and writes a title and description, and the report arrives with the page URL, screen resolution, operating system, browser and version, language and time zone attached. Clients don't need an account.

You paste the snippet into the site's <head>; the help section has install guides for plain HTML, WordPress, Shopify, Wix, Squarespace, PrestaShop and Google Tag Manager. When your client clicks the button:

• Capture: on a computer the browser asks permission to capture the tab (phones skip this step), and the visible part of the page is captured.
• Mark-up: the client draws with arrows, rectangles, text, a pen or a highlighter.
• Describe: they add a title, a description and a type (Proposal, Bug, Recommendation or Feature by default).
• Context: URL, screen, system, browser, language and time zone are attached automatically.

Your team sees every item in a dashboard with its screenshot and marks it open, resolved or archived. You can invite clients by email to a read-only view of the project's feedback, and each item can be created automatically as an issue in Jira, a card in Trello, a task in Asana, ClickUp or Wrike, an item in monday.com, a page in Notion, a message in Slack or Discord, or an email to your team (all integrations).

The Free plan covers 5 projects and 50 feedback reports with no credit card, and Pro costs €19.95 a month, or €199.50 a year, for up to 100 projects; see pricing.

How do you make feedback rounds shorter?

Use one channel and repeat it everywhere, ask the client to name one reviewer who resolves contradictions, have them check the site on their own phone, and reply to every item with "fixed" or "moved to phase 2". These habits cut the number of rounds more than any tool, because the same comment stops coming back.

• One channel, repeated: say it in the kickoff, the briefing email and whenever feedback arrives elsewhere.
• One reviewer on the client side: if five people review, ask the client to name one person who resolves contradictions before you start work.
• Real devices: ask the client to look at the site on their own phone, because many issues only appear there.
• A reply on every item: a short "fixed" or "moved to phase 2" on each comment stops it from returning next round.

To compare tools for this, read how to choose a website feedback tool. Pick a method that collects the where, the what and the context for you, brief the client clearly and close each round in writing: the next review will be shorter.