Website Feedback Form Questions: 45 Examples by Goal (Free Template)

Website feedback form questions decide whether a form brings back answers you can act on or a pile of "it's fine" and empty text boxes. The difference is rarely the form tool. It's asking one thing at a time, at the moment the person has the answer, and not wasting their patience on what the browser already knows. Below are 45 questions grouped by goal, three ready-made forms, the mistakes that ruin answers, and an Excel question bank that tells you when to ask each question and what it tells you.

What is a website feedback form?

A website feedback form is a short set of questions, shown on a website or sent after a visit, that asks visitors, customers or reviewers what they came to do, whether it worked and what should change. It can be a button that opens a form on any page, a few questions at the end of an article, a popup when someone is about to leave, a survey on the order confirmation page or an email sent the day after.

It is not a contact form. A contact form starts a conversation with one person; a feedback form collects the same answers from many people so you can improve the site. Agencies also use feedback forms in a narrower way: to collect a client's comments on a new site during a review round, before launch.

Which questions should a website feedback form ask?

It depends on the goal, and each form should have only one. A good form asks three to five questions, most of them closed (a rating, yes or no, a short list), with one optional open question that asks why. It appears at the moment the person has the answer, and it never asks what the browser can record by itself.

Start by choosing the goal, then pick the moment, then the questions:

Timing matters as much as wording. A popup that opens two seconds after the page loads asks about a visit that hasn't happened yet. A question at the end of an article, after a purchase or on a button the visitor clicks when they notice something gets answers from people who have something to say.

Website feedback form questions by goal

These are the 45 questions in the template, with the same numbers, so you can find them in the spreadsheet with their answer type, options and the reason to ask them.

Purpose of the visit

Ask these early, and keep the answer options short. They split the rest of the answers by type of visitor.

1. What brought you to the site today? (Buy something, compare options, find contact details, get help, just browsing, other)
2. How did you hear about us?
3. Is this your first visit to the site?

Finding things

The first question here is the most useful single question for a content or service site. Show the second only to people who answer "partly" or "no".

4. Did you find what you were looking for? (Yes, partly, no)
5. What were you looking for that you couldn't find?
6. How easy was it to do what you came to do? (1 = very difficult, 5 = very easy)
7. What almost stopped you from finishing?

Usability and navigation

8. How easy is it to find your way around the site?
9. Was anything on this page confusing?
10. Did a link, button or form not work the way you expected?
11. Which device are you using? (Skip it if your tool records the device.)
12. Was the text easy to read on your screen?

Content and trust

Question 15 catches the errors that cost the most: an old price, last year's opening hours, a phone number nobody answers.

13. Did this page answer your question?
14. What would you add to this page?
15. Is any information on this page wrong or out of date?
16. How much do you trust the information on this site?
17. What would you still like to know before you contact us or buy?

Design and first impression

Compare the answers to question 19 with the words in the design brief. If the brief said "friendly" and visitors pick "dated", you have a concrete problem to discuss.

18. What was your first impression of the site?
19. Which words describe the site best? (Pick up to three: modern, professional, trustworthy, friendly, cluttered, dated, confusing)
20. How visually appealing is the site?
21. Is anything on this page hard to see or read?

Problems on the page

These follow the structure of a bug report: what happened, what should have happened, the steps and where. Our bug report template explains why each part matters.

22. What went wrong?
23. What did you expect to happen?
24. What were you trying to do when it happened?
25. Can you show us where? (A marked-up screenshot)
26. How much does this problem affect you? (I can't continue, it slows me down, it's minor)

Buying and leaving

27. What is stopping you from buying or signing up today? (Price, not sure it fits my needs, need more information, just looking, other)
28. Is the pricing clear?
29. What other options are you considering?
30. What nearly made you leave without buying?
31. How easy was the checkout?

Satisfaction and recommendation

A score on its own tells you something changed, not what. Always follow it with question 34.

32. Overall, how satisfied are you with the site? (1 = very dissatisfied, 5 = very satisfied)
33. How likely are you to recommend us to a friend or colleague? (0 to 10)
34. What is the main reason for your score?
35. What one thing would you change about the site?
36. What do you like most about the site?

Client review of a new website

For agencies and freelancers. These go to the client during a review round and ask about what only the client knows: facts, missing content and tone. Our guide to collecting client feedback on a website covers the round itself.

37. Does the home page make it clear what you do, within a few seconds?
38. Are all prices, opening hours, addresses and phone numbers correct?
39. Is anything missing that your customers will look for?
40. Does the site sound like your business?
41. Which pages can we mark as approved?
42. What must change before launch, and what can wait?
43. Have you checked the site on your own phone?

Follow-up

44. May we contact you about your answer?
45. Your email address (optional; show it only after a yes to question 44)

Website feedback form examples

Three forms built from the bank, each with one goal. Copy them as they are or swap in other questions from the same group.

At the end of a help article or blog post (three questions, the second only after "partly" or "no"):

Did this page answer your question?   ( ) Yes  ( ) Partly  ( ) No

What would you add to this page? (optional)
[                                                  ]

May we contact you about your answer?   ( ) Yes  ( ) No

On exit from a pricing or product page (two questions, shown once per visitor):

Before you go: what is stopping you from signing up today?
( ) Price
( ) Not sure it fits my needs
( ) I need more information
( ) Just looking
( ) Other: [                    ]

What would you still like to know? (optional)
[                                                  ]

For a client reviewing a new site (five questions, sent with the staging link at the start of the round):

1. Does the home page make it clear what you do, within a few seconds?
   ( ) Yes  ( ) No. What is missing? [              ]
2. Are all prices, opening hours, addresses and phone numbers correct?
   ( ) Yes  ( ) No. Which ones? [              ]
3. Is anything missing that your customers will look for?
4. What must change before launch, and what can wait?
5. Have you checked the site on your own phone?  ( ) Yes  ( ) No

For anything on a specific page, use the Give Feedback button
on that page instead, so we see exactly what you see.

How do you write questions that get useful answers?

Ask about one thing, in the visitor's words, about something that already happened. Most bad questions break one of those three rules: they lead to an answer, pack two questions into one, use the team's jargon or ask people to predict what they would do.

A few habits make every form better:

• Keep scales the same across the site: if 1 means bad and 5 means good in one form, don't flip it in another, and label both ends.
• Make open questions optional. A required text box gets "ok" or an abandoned form.
• Say how long it takes ("Two questions, 20 seconds") and thank people when they finish.
• Give every field a visible label, not only placeholder text, so screen reader and keyboard users can answer too. The W3C's forms tutorial covers labels, instructions and error messages.
• Read the answers on a fixed day each week and note what you changed, so the next batch tells you whether the change worked.

Survey form or visual feedback button?

Use a survey form for scores and opinions from many people, and a visual feedback button for comments about a specific page. A survey asks the same questions at a moment you choose; a button waits until the person notices something and lets them show it. The two work well side by side.

Questions 22 to 26 are where a written form struggles most. "What went wrong?" in a text box gets "the button doesn't work"; the same question next to a screenshot of the page gets an arrow pointing at the exact button, on the exact page, with the browser that failed.

That is what GiveFeedback.io does. You add one script to the site and a "Give Feedback" button appears on every page. Whoever clicks it, with no account needed, gets a screenshot of the page (on a computer, after the browser asks permission to capture the tab) to mark up with arrows, rectangles, text, numbered markers, a pen or a highlighter, and can blur anything private or point at the element they mean. The form itself is short: a title, a description and a category. The defaults are Proposal, Bug, Recommendation and Feature, and you can rename them in your profile to match your goals, for example Bug, Content, Design and Idea.

Every report arrives with the page URL, the browser and version, the operating system, the screen resolution, the browser language and time zone, plus a log of the page's console messages, errors and failed requests. It works on computers, phones and tablets. The website annotation tool page shows the marking-up in detail, and each report can go straight to Jira, Trello, Asana, ClickUp, monday.com, Wrike, Notion, Slack, Discord or email.

Pick one goal, take three to five questions from the bank and put them where people have the answer. After a month of reading the answers every week, you'll know which questions earn their place on the form and which ones to swap for the next one in the bank.