The website feedback tools worth shortlisting are Sleekplan, BugHerd, Marker.io, Ybug, Ruttl, Hotjar and Microsoft Clarity. They are not interchangeable: three of them collect annotated screenshots from people, two record what people do without asking them anything, and only one turns a report into something the person who sent it can follow. Sleekplan runs that whole loop from a single widget and has a free plan, where BugHerd’s cheapest plan is $50 per month and has no free tier at all.
- Sleekplan: best for turning a visitor’s annotated screenshot into a votable post with a roadmap and a changelog. Free plan, paid from $13 per month.
- BugHerd: best for an agency running client sign-off on a site before launch. $50 per month, or $42 per month billed annually.
- Marker.io: best for pushing annotated bug reports straight into Jira or Linear. $39 per month billed annually.
- Ybug: best for a solo developer or small team who wants annotation on a budget. Free for one project, then €13 per month.
- Ruttl: best for design and copy review on a live page. Free plan, then $18 per user per month.
- Hotjar: best for watching behaviour when nobody is filing reports. Free plan, paid from $49 per month.
- Microsoft Clarity: best for heatmaps and session replays at no cost.
What is a website feedback tool?
Website feedback tool: software that lets a visitor, client or teammate report what is wrong with a page without leaving it, usually by capturing the page and drawing on the part that is broken.
That definition covers a wider range of products than it sounds like. A tool that captures an annotated screenshot and a tool that silently records mouse movement are both sold as website feedback tools, and they answer opposite questions. The first tells you what one person thinks. The second tells you what a thousand people did. Choosing well starts with deciding which of those two you are short of.
The four kinds of website feedback tools, and when each is wrong
Visual annotation tools capture the page and let the reporter draw on it. They are the right choice when the feedback is specific and visual, and the wrong choice when you need to know how many people hit the same thing, because each report arrives alone.
Session replay and heatmaps record behaviour without asking. They are the right choice when nobody is filing reports and you need to see where attention goes, and the wrong choice when you need the reason behind a behaviour, because a replay shows the click and not the thought.
In-page ratings and surveys ask a short question on the page where the behaviour happened. They are the right choice for measuring a page over time, and the wrong choice when you need detail, because a score is not a description.
Public feedback boards collect requests where other people can see and vote on them. They are the right choice when the same request keeps arriving and you need to rank it, and the wrong choice when the feedback is confidential.
Most teams need two of the four. The pairing that covers the most ground is an annotation tool plus a board, so a single report can become ranked demand rather than a ticket nobody else sees.
1. Sleekplan: the annotated screenshot becomes a post
Sleekplan puts a screen-capture button in a widget that also carries a feedback board, a public roadmap and a changelog. The visitor captures the page as they see it, marks it up with a pen, highlighter, arrow or comment pin, blurs anything private in the frame, and sends it.
What happens next is the part that separates it from the annotation tools below. The report lands on a board where other visitors vote and comment, so ten people hitting the same broken checkout become one ranked item instead of ten tickets. Status changes notify the person who reported it, the roadmap shows what you picked up, and the changelog announces the fix to everyone who voted.
The same widget runs CSAT and NPS prompts, which means you can ask a question on the page instead of waiting for someone annoyed enough to open a form. There is a longer walkthrough of the capture flow on our website feedback tool page.
The free plan runs a board and a changelog with unlimited feedback items and subscribers, and the Sleekplan pricing page lists paid plans from $13 per month.
Best for: teams who want the person who reported a problem to find out what happened to it.
2. BugHerd: client sign-off on a site before launch
BugHerd pins feedback to the element it belongs to, and every comment becomes a trackable task on a kanban board. Each one carries a screenshot and metadata such as browser, OS and screen resolution. It is built around the agency workflow: the client clicks around a staging site, leaves pins, and the team works the board until the site is approved.
Its pricing page lists Standard at $50 per month, or $42 per month billed annually, for five members, with additional members at $8 each. There is no free plan.
Best for: agencies and freelancers who need a client to sign off on a site.
3. Marker.io: annotated reports that land in your issue tracker
Marker.io is the same idea aimed at engineering rather than client review. A report carries the annotated screenshot plus advanced technical metadata, and it is created directly in Jira, Trello, Asana, GitHub or Linear, so the developer never opens a second tool.
The Marker.io pricing page lists Starter at $39 per month billed annually, $59 billed monthly, with a 15-day free trial and no free plan.
Best for: teams whose backlog already lives in Jira or Linear and who want visual bug reports to arrive there.
4. Ybug: annotation with an actual free plan
Ybug covers the same job as BugHerd and Marker.io at a much lower entry price. Reports carry annotated screenshots, browser metadata, JavaScript console logs and optional screen recordings, and they sync to a tracker.
Its pricing page lists a free plan limited to one project and one team member, and Basic at €13 per month, billed in euros rather than dollars.
Best for: a solo developer or a small team who wants annotation without a $40 floor.
5. Ruttl: review for design and copy, not only bugs
Ruttl is aimed at reviewing the work rather than reporting faults with it. Comments are left on the live page at pixel level, and a reviewer can make live changes to the page to show what they mean instead of describing it.
Ruttl’s own pricing page lists a free Basic plan and Pro at $18 per user per month, which is per seat rather than per project.
Best for: design and content review where the feedback is “move this” rather than “this is broken”.
6. Hotjar: what people did, when nobody filed a report
Hotjar records sessions and builds heatmaps, so you see where people click, hover and scroll, and where they hit errors and frustration, without anyone having to tell you. It also runs on-page surveys, which is the part people forget when they file it under analytics.
The Hotjar pricing page lists a free plan with 200,000 monthly sessions and 10,000 replays, including basic surveys and feedback widgets at 100 surveys per month, with paid plans from $49 per month.
Best for: finding the pages that are quietly failing, before anyone complains about them.
7. Microsoft Clarity: heatmaps and replays at no cost
Microsoft Clarity describes itself as “a free user behavior analytics tool that helps you understand how users are interacting with your website through session replays and heatmaps”. There is no paid tier and no seat limit, which makes the argument for adding it alongside whatever else you run fairly short.
Best for: any site that has no behavioural data at all today.
Compare them in one table
| Tool | What it collects | Entry price | Free plan |
|---|---|---|---|
| Sleekplan | Annotated screenshots, votes, CSAT and NPS | $13 / month | Yes |
| BugHerd | Pinned annotations as kanban tasks | $50 / month | No |
| Marker.io | Annotated reports inside Jira or Linear | $39 / month annually | No |
| Ybug | Annotated reports with console output | €13 / month | Yes, one project |
| Ruttl | Comments and live edits on a page | $18 / user / month | Yes |
| Hotjar | Session replays, heatmaps, surveys | $49 / month | Yes |
| Microsoft Clarity | Session replays and heatmaps | Free | Yes |
Prices were read from each vendor’s own pricing page in September 2026 and change without notice.
The mistake that makes all of them useless
The tool is the cheap part. What decides whether website feedback is worth collecting is what happens to a report after it arrives, and most teams never decide that.
A report that gets fixed silently teaches the reporter that sending it was pointless, and they stop. That is why the shortlist above separates the tools that end at a ticket from the one that sends a status back. If your tool cannot tell the person who wrote in that the thing they reported shipped, your feedback volume will fall quarter after quarter and the tool will look like the problem.
The second mistake is running one tool and calling it coverage. Annotation catches the specific and the visual. Replays catch the silent majority. Neither catches the thing that fifty people want and nobody has bothered to write down, which is what a board is for.
Where to start this week
Pick one page that matters commercially, usually pricing or signup. Put a free behavioural tool on it and leave it for a week, then read the replays for the ten seconds before every exit. You will have a list of suspicions rather than facts.
Then add a way for the people on that page to tell you directly, and make sure the reply path exists before you turn it on. If you want that in one install, our feedback widget carries the capture tool, the board and the changelog behind a single script tag.