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 your pricing page. Feedback tells you they left because your plan names meant nothing to them.
How do you give feedback on a website?
To give useful feedback on a website, point at the exact element, say what you were trying to do, and describe what you expected and what happened instead.
- Name the page and the element. "The second button in the pricing table" beats "the pricing page".
- Say what you were trying to do. The goal tells the site owner whether the page failed or you were on the wrong page.
- Describe expected vs actual. "I expected a PDF and got a blank tab."
- Add your browser and device. Many problems only appear on one browser or screen size.
- Leave the fix to them. Describe the problem, and offer a suggestion only as a suggestion.
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 on the site doesn't work, 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
Take two comments a visitor might leave on your own site.
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.
What tools collect website feedback?
Website feedback tools fall into four groups, and most teams use more than one.
- Visual feedback widgets let visitors and reviewers pin a comment or annotated screenshot to the page, usually with browser details attached. Best for design reviews and bug reports.
- On-page surveys ask one or two questions on a specific page, for example after a visitor has spent a while on pricing.
- Session recordings and heatmaps show behaviour nobody writes down, such as where people scroll and click.
- Review sites and support channels collect what people say after they've left the page.
Website feedback for enterprise product teams
An enterprise website is rarely one site. It's a marketing site, a logged-in product, help pages and regional versions, each owned by a different team. Feedback arrives on all of them, and the person who reads it is often not the person who can fix it.
Two things keep it usable at that scale. Each item needs the page, the browser and the visitor's context attached, so it can be routed to the right team without a follow-up email. And comments need to be counted per page and per topic, so a redesign decision rests on how many people raised something, not on the most persuasive reviewer.
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 and screen size, so a report arrives with the context a developer needs instead of a description.
- Screen recordings show a sequence of steps that a single screenshot can't.
- Micro-surveys can run on a single page to ask one question at the point where you are unsure.
- Targeting by URL limits the widget to the pages you choose, for example only the checkout or only a staging site during a review round.
- Grouping: everything lands in one place. Sentiment Sensor, included on Professional plans and above (an add-on on Starter and Growth), tags each new item with a topic and a sentiment as it arrives.
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.
What is the best website feedback tool?
It depends on who gives the feedback. Clients and internal reviewers need a visual tool that pins comments to the page and records the browser. Visitors answer short on-page surveys more readily, and analytics shows the behaviour neither group will describe.
Related terms
See how teams collect website feedback with the page, browser and screen size attached.
.svg)
