25 website feedback questions to ask your clients before launch
Web designers and freelancers: ask your client the right question at the right stage and you get specific changes instead of “looks good!”. Here are 25 website feedback questions for reviewing a site with your client (not a visitor survey), from first impression to sign-off, plus a feedback form template.
Sounds familiar?
- You send the link and get back “looks good!” or “make it pop”.
- The real feedback arrives after launch, when changing things costs the most.
- The question lists you find online are surveys for visitors, not questions for your client.
Here’s the fix
- 25 neutral questions for your client, grouped by project stage, from first impression to sign-off.
- Ask them on the page, so every answer lands on the element it is about.
- A form template and examples that turn vague notes into changes you can make.
By Radek Svoboda · Updated · 9 min read
Table of contents8 sections
TL;DR: ask fewer questions, on the page, at the right stage
A client who gets 25 questions at once answers five of them. Pick the group for the stage you are at, ask three to seven questions, and ask them where they apply.
Pick the stage
First impression and content early; design and navigation mid-way; mobile, conversion and sign-off before launch.
Ask on the page
Pin each question on the part of the page it is about, so the answer lands in the same place.
Close the loop
Reply to every answer, resolve what is done, and finish with the sign-off questions.
Why visitor survey questions fail with clients
Search for website feedback questions and you get survey questions for visitors: “How did you find us?”, star ratings, Net Promoter Score. They measure how a live site performs with strangers. Your client is not a stranger, and the site is not live yet.
A client review has a different job: catch what is wrong or missing before launch, in the client’s own words, while it is still cheap to change. That needs questions about their business, their customers and their brand, asked at the stage where the answer can still change the work.
It also needs neutral wording. Nielsen Norman Group calls a question leading when it builds the expected answer into its wording, and a client who is paying for the site leans toward agreeing with you. “Don’t you love the new header?” gets a yes. “What, if anything, would you change in the header?” gets an answer.
- One topic per question. “Is the site clear and attractive?” asks two things and gets half an answer.
- Open first, closed later. Ask what they notice before you ask whether they like something specific.
- Do not name the thing for them. Point at it with a pin and ask “What is this for?” instead of “Is the pricing table clear?”.
- Leave room for “nothing”. Add “if anything” so a client does not invent a problem to be helpful.
Sources: Nielsen Norman Group: avoid leading questions, Contentsquare: on-site survey questions
The 25 website feedback questions, by stage
Copy the group you need into your next review. The numbers run through the whole list so you and your client can refer to “question 13”. Replace anything in brackets with your own page or task.
First impression (questions 1 to 4)
Ask these before anything else, ideally on the first design or the first build of the homepage.
- 1. In the first five seconds, what do you think this site offers?
- 2. Who do you think this page is for?
- 3. What is the first thing your eye goes to?
- 4. What, if anything, would you expect to see here that is missing?
Content (questions 5 to 8)
Clients know their business better than you do. These questions turn that into corrections.
- 5. Which sentence or section would you change, and to what?
- 6. Where does the wording differ from how you describe the business to customers?
- 7. Which facts on this page need checking: prices, names, dates, addresses?
- 8. What would a customer still want to know after reading this page?
Design (questions 9 to 12)
Ask about fit with the brand, not about taste.
- 9. Which parts feel like your brand, and which do not?
- 10. What, if anything, feels out of place on this page?
- 11. Which images would you replace, and with what?
- 12. How does this page compare with the reference sites you sent us?
Mobile (questions 16 to 18)
Send these with the link and ask the client to open it on their own phone.
- 16. On your phone, what is harder to read or tap than on a laptop?
- 17. What, if anything, is cut off, overlapping or too small?
- 18. Which part of this page should a phone visitor reach first?
Conversion (questions 19 to 22)
Every page has one job. These questions check that it does it.
- 19. What is the one thing you want a visitor to do on this page?
- 20. Where would a visitor hesitate before contacting you or buying?
- 21. What would make a first-time visitor trust you more here?
- 22. Which form fields could we remove?
Sign-off (questions 23 to 25)
Ask these last, once the open comments are resolved.
- 23. Which open comments must be fixed before launch, and which can wait?
- 24. Who else needs to approve this page?
- 25. With the remaining comments resolved, is this page ready to go live?
Three to seven questions per round is plenty. The rest of the list waits for the next round, and the client answers the ones you send properly.
Website feedback form example
If you prefer a form to questions on the page, these seven fields cover a client review. The satisfaction scale is the five-option one the GOV.UK Service Manual uses.
| Field | Type | Why it is there |
|---|---|---|
| Your name | Short text | So you know who to reply to; no account needed |
| Page or screen | Link or dropdown | Feedback without a page is a guessing game |
| Overall, how satisfied are you with this page? | Very satisfied, Satisfied, Neither satisfied nor dissatisfied, Dissatisfied, Very dissatisfied | A quick temperature check you can compare between rounds |
| What should change? | Long text | The actual feedback, in the client’s words |
| Where on the page? | Screenshot or a pin on the page | Removes “which button?” follow-ups |
| How important is it? | Must fix before launch, Should fix, Nice to have | Lets you plan the next round |
| Anything else? | Long text, optional | Catches what your questions missed |
A form still makes the client describe where the problem is. Pinning the comment on the page itself answers “Where on the page?” for them.
Website feedback examples: vague and actionable
The questions above are built to turn the left column into the right one.
| What the client writes | What you can act on | The question that gets it |
|---|---|---|
| “Make it pop.” | “The headline is hard to read over the photo. Try white text or a darker overlay.” (pinned on the headline) | 10. What, if anything, feels out of place? |
| “I don’t like the colours.” | “The orange buttons clash with our red logo. Use the red from the style guide.” | 9. Which parts feel like your brand? |
| “The menu is confusing.” | “I looked for prices under Services. Our customers call it Pricing.” | 14. Which menu labels would customers word differently? |
| “Something is off on mobile.” | “On my phone, the contact button sits under the cookie banner.” | 17. What is cut off or overlapping? |
| “Can we change the text?” | “Second paragraph: we no longer deliver on weekends. Delete the last sentence.” | 7. Which facts need checking? |
| “Looks good!” | “Approved once comments 3 and 7 are fixed. Maria in marketing signs off the pricing page.” | 23 to 25, the sign-off questions |
How to ask these questions on the page with Comnview
A form separates the question from the thing it is about. Here is how to keep them together, for free.
Capture the page or upload the design
Paste the page address on comnview.com, or use the Chrome extension for staging, localhost or a page behind a login. Mockups and PDFs work too: drop them in.
Paste the address and capture the page. Pin your questions where they apply
Add the questions for this round as your own comments: question 13 on the menu, question 19 next to the main button. The client answers in the same thread, on the same spot.
Start each pinned question with its number from the list, so “13” means the same thing in your notes and in the client’s reply.
A question pinned on the button it is about. Send one link
Copy the link, or invite up to five people by email with a free account. The client types a name once and replies; no account, no install. Add a password if the site is confidential.
Invite by email or copy the link. Reply, resolve, then ask for sign-off
Answers arrive as replies to your pinned questions. Resolve each one when it is done, and when the Open list is empty, pin questions 23 to 25.
Replies sit under each pin; resolve when done.
Tips for website feedback clients actually give
Send a deadline with the link
Feedback without a date drifts. “Comments by Thursday noon” gets more answers than “when you have a moment”.
One reviewer, one voice
Ask the client to collect colleagues’ comments in one place, or invite each person to the same link so you see who said what.
Show the real thing
A screenshot in an email loses context. A page they can scroll, on their own phone, gets better answers to questions 16 to 18.
Ask before you build
Questions 1 to 4 on a first design save a week of building the wrong page.
Answer every comment
A reply, even “done”, shows the client their time was worth it, and they give more next round.
End with a clear yes
Do not launch on silence. Question 25 turns “looks good” into a decision.
Frequently asked questions
What questions should I ask for website feedback?
Ask about what the client sees first, what the content gets wrong, how the design fits the brand, how easy it is to find things, how it works on a phone, what visitors should do, and whether it is ready to launch. The 25 questions above cover all seven.
How many questions should a website feedback form have?
For a client review, three to seven per round. More than that and answers get shorter. Send the next group in the next round.
What is a good website feedback form example?
Name, page, a five-option satisfaction scale, what should change, where on the page, how important it is, and anything else. The table above shows each field and why it is there.
When should I ask a client for website feedback?
At three points at least: on the first design (first impression and content), mid-build (design and navigation) and before launch (mobile, conversion and sign-off).
How do I get specific feedback instead of “make it pop”?
Ask one thing per question, ask it on the part of the page it is about, and leave room for “nothing”. Specific questions get specific answers.
Should clients answer in a form or on the page?
On the page when you can. A comment pinned on the element says where the problem is without a screenshot or a description, and you can reply in the same place.
Is the template free?
Yes. Copy the questions straight from this page. They work with any tool, or with none.
All sources (3), checked 21 October 2026
- Nielsen Norman Group: avoid leading questions (checked 21 October 2026)
- Contentsquare: on-site survey questions (checked 21 October 2026)
- GOV.UK Service Manual: feedback pages (checked 21 October 2026)
The example feedback is made up to show the pattern. Screenshots are of Comnview, taken by us; the websites shown belong to their owners.
More from the blog
GuideHow to annotate an image online, free
Drop or paste a picture or a screenshot, pin comments and arrows on the exact spot and send one link: a step-by-step guide with screenshots, six ways compared, and screenshots of localhost or logged-in pages.
· 10 min readRead
GuideHow to annotate any website, free
Paste a link, pin comments on the exact element and send one link: a step-by-step guide with screenshots, plus localhost, staging and tips for feedback that gets acted on.
· 9 min readRead
ComparisonThe best website feedback tools in 2026
Ten website feedback tools compared honestly: what each costs, how clients leave feedback, staging and localhost, files, and where the feedback goes next.
· 12 min readRead