Feedback on a website

Feedback on a website

Website feedback is what visitors tell you about a site: what confused them, what broke, and what they could not find. It arrives through in-page comments, surveys and bug reports, and it explains the behaviour analytics can only show you.

Go back to Glossary

What is website feedback?

Website feedback is what visitors tell you about a site, either because you asked or because something went wrong and they wanted you to know. It covers design opinions, usability problems, broken features and missing content.

It answers the question analytics cannot. Analytics shows you that 60% of people leave the pricing page. Feedback tells you they left because the plan names meant nothing to them.

Types of website feedback

  • Design feedback. Reactions to layout, hierarchy and visual clarity, usually gathered during a review round before launch.
  • Usability feedback. People telling you they could not find or complete something.
  • Bug reports. Something is broken, on a specific browser or device.
  • Content feedback. The words did not answer the question the visitor arrived with.

These need different collection methods. Design feedback works best as comments pinned to the page itself. Bug reports need technical context attached. Content feedback usually needs a question, because people rarely volunteer that they did not understand something.

How to run a website design feedback round

Pin comments to the page, not to a document. Feedback in a spreadsheet loses the thing it refers to. “The header is confusing” is unusable a week later. A comment attached to the header is not.

Ask for the problem, not the fix. “Make the button blue” is a solution. “I did not realise that was clickable” is the finding, and it may have nothing to do with colour.

Give reviewers a scope. An open request produces opinions about the logo. A request to complete a specific task produces information about whether the page works.

Capture the technical context automatically. Browser, screen size, console errors. Asking a reviewer for their browser version is how you lose the report.

Website feedback questions to ask

  • What were you trying to do on this page?
  • Was there anything you expected to find and could not?
  • What made you hesitate?
  • If you could change one thing here, what would it be and why?
  • Did anything on this page not work as you expected?

Keep it to one or two questions in context rather than a long form afterwards. Response rates and quality both fall the further you get from the moment.

Useful feedback and useless feedback

Useless: “The site looks outdated.” No task, no page, nothing to act on.

Useful: “I was looking for pricing for a team of 20 and the page only shows per-user cost, so I could not work out what we would pay.” A specific goal, a specific page, a specific gap.

The difference is almost always whether the person was doing something at the time.

How Usersnap collects website feedback

Visitors point at the thing they mean. Usersnap captures an annotated screenshot of the page as they saw it, along with browser, operating system, screen size and console errors, so a report arrives with the context a developer needs instead of a description. Screen recordings cover problems that a screenshot cannot show. Micro-surveys can run on a single page to ask one question at the point where you are unsure. Everything lands in one place and gets grouped by topic automatically.

Website feedback FAQ

How do you collect feedback on a website?

Through an on-page widget for comments and bug reports, micro-surveys on specific pages, and annotated screenshots that capture what the visitor saw. The method matters less than the timing: feedback collected during the task is more specific than feedback collected afterwards.

What questions should you ask for website feedback?

Ask what the person was trying to do, what they expected to find, and what made them hesitate. Avoid asking whether they liked the design, because the answer is rarely actionable.

What is website design feedback?

Reactions to layout, hierarchy and visual clarity, usually collected during a review round before launch. It works best as comments pinned directly to the page rather than notes in a separate document.

Collect website feedback with the page context attached. Start free with Usersnap, first 20 feedback items included, no card needed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.