A website feedback tool that’s actually quick to add
Collect feedback on any website — yes/no, polls, NPS, or a contact form — from one small snippet, with a dashboard that’s actually worth checking.
What a website feedback tool actually does
A website feedback tool answers one deceptively simple question: is this page working? Your analytics can tell you a page gets traffic, that visitors scroll halfway, that some bounce. What it can't tell you is why — whether the pricing confused them, whether the docs answered the question, whether the demo convinced anyone. The only way to know is to ask, in context, while the page is still in front of them and the impression is fresh.
The reason most teams never do this isn't lack of interest — it's friction. Traditional setups want a backend, a plugin to maintain, a build step, or a tracking script that drags consent banners along with it. widgetful removes all of that: you create a widget, paste one <script> tag before </body>, and responses stream into a dashboard. No server, no plugin, no build. The embed is a tiny piece of vanilla JavaScript, so it works on plain HTML, Rails, Next.js, WordPress, Shopify, and static sites alike.
Page-level feedback vs. customer-level feedback
It's worth being precise about the job, because two related tools get lumped together. Page-level feedback is anchored to a URL: it asks whether this specific page did its job, and the answer is only useful next to the page it came from. That's what this tool is for — diagnosing a docs article, a pricing page, or a blog post one at a time. Customer-level feedback is anchored to a person or account: how a customer feels about your product overall, watched over their lifecycle, regardless of which page they happen to be on. If that's your job — relationship health, churn signals, an account-wide score — start from the broader customer feedback tool overview instead.
The same widgets serve both jobs; the difference is what you attach the answer to. widgetful records which page every response came from, which is exactly what makes page-level diagnosis possible: a dip in “was this helpful?” points straight at the article that needs a rewrite, not at a vague, site-wide average.
Which pages should have feedback on them?
You don't put the same question everywhere. The most useful placements map to a page's actual job, and the page is failing in a different way each time:
- Docs and help articles. The classic home for a feedback widget: a yes/no “Did this answer your question?” at the foot of each article. Friction is low enough that response rates hold across hundreds of pages, so you can spot the few articles quietly letting people down without reading every one.
- Pricing. The highest-stakes page on most sites, and the one analytics describes worst — a bounce here could mean “too expensive” or “couldn't tell which plan I needed.” A short open prompt (“anything stopping you from choosing a plan?”) or a framed poll surfaces the real blocker.
- Blog and content marketing. A poll or a “what brought you here?” ask turns passive readers into a signal about what to write next, and helps you tell genuine interest from drive-by traffic.
- Product and onboarding screens. Inline feedback after a real action (“was this step clear?”) catches confusion at the exact moment it happens, while the user can still tell you what tripped them up.
- 404s and error states. A contact prompt where frustration peaks turns a dead end into a reported bug or a recovered visitor.
How page-level feedback differs from analytics and heatmaps
This tool doesn't replace your analytics or your heatmap — it answers the question those tools structurally can't. The split is between inferred behaviour and stated intent:
| Tool | Tells you | Can't tell you |
|---|---|---|
| Analytics | How many came, where they went, where they dropped | Why they dropped, or whether they got what they came for |
| Heatmaps / session recording | What people clicked, scrolled, and hovered | What they were thinking, or what they wished the page did |
| Page feedback (widgetful) | What visitors say, in their words, on the exact page | What people who said nothing did — pair it with the above |
Behavioural tools observe; a feedback widget asks. A heatmap can show you that everyone rage-clicks a non-link; only a feedback prompt tells you they expected it to open a demo. They're complementary, which is why teams run both — see how widgetful compares as a Hotjar alternative if you're weighing the behavioural side specifically.
How it works: installing the widget
Here's the entire setup — short enough for a non-developer. Create a widget in the dashboard, copy your snippet, and paste it just before the closing </body> tag:
<script src="https://cdn.widgetful.com/w.js" data-key="pub_yourkey" defer></script>
That's it. The embed loads with defer from the edge (cdn.widgetful.com), so it never blocks rendering, and ingestion runs on Cloudflare Workers — fast and cheap at any traffic level. The snippet's public key is write-only and safe to ship in plain HTML; its security comes from an origin allowlist plus rate limiting, not secrecy. The full walkthrough lives in the docs.
One more option: a coding agent (Claude Code, Codex, and the like) can do the whole setup via API before you even sign up — account, widget, and verified install — from the machine-readable docs at /install.md and /llms.txt. Paste a prompt, get a working widget.
Pick the widget that fits the page's job
The right widget depends on what the page needs to learn — and widgetful ships the whole catalog on every plan, including the free one, so the choice is about fit, not about which feature you've paid to unlock:
- Feedback — the yes/no “Was this page helpful?” with an optional comment. Lowest friction, best for monitoring many pages at once.
- Poll — a multiple-choice question (2–10 options) with a live breakdown, when you can name the options yourself. Details on the poll widget page.
- NPS — the 0–10 recommend score, tracked over time, for an account-wide benchmark rather than one page. See the NPS survey tool.
- Contact form — a hosted, open channel when you can't predict what people will say; every submission stored, emailed, and exportable. See the contact form widget.
The dashboard: from raw responses to a decision
Collecting answers is only half the job; reading them at a glance is where a website feedback tool earns its keep. Every widget rolls up into totals and breakdowns, plots trends over time, and records which page each response came from. Polls show a live breakdown; NPS gets score-over-time, a histogram, and comments on one screen. Live tallies update through a Durable Object while aggregates roll up via Analytics Engine, and anything you see exports to CSV. Two habits make it useful: read responses per page rather than as one pile, and watch the trend, not the day — one bad comment is noise, a two-week slide is a signal.
Where to place a widget so it actually gets answered
The biggest lever on response quality isn't the question — it's placement and timing. A widget nobody sees collects nothing; one that interrupts collects junk:
- Put it after the content, not before. Ask at the end of an article, where the reader has formed an opinion. At the top you measure intent, not experience.
- Match the moment to the question. A helpfulness ask belongs inline on content pages; NPS belongs inside the product after real usage; a contact form belongs where frustration peaks, like error states.
- One ask per page, and stay visible without being modal. Keep the open comment optional — an unobtrusive inline placement gets more (and more honest) responses than a pop-up that blocks the page.
- Use the “which page” data to audit placement. A high-traffic page with almost no responses usually has a placement problem, not an interest problem — move the widget up and watch the rate.
Privacy that doesn't need a banner
This is the part teams underestimate until legal asks. The widgetful embed is cookieless and does no cross-site tracking — it isn't building a profile or following visitors around the web, just recording an answer to a question they chose to answer. In practice a feedback widget generally won't add a new line item to your cookie-consent banner, a real win for both compliance and conversion. You can read exactly what is and isn't collected on our privacy page.
Pricing, honestly
You pay widgetful for scale, history, and polish — never for features, since every tier includes the full catalog. Free is $0 forever: 1,000 responses a month, 90 days of history, up to two widgets, a small “powered by widgetful” badge, no card required. Pro ($29/mo, less on longer cycles) lifts you to 50,000 responses a month, unlimited history and widgets, removes the badge, adds a custom domain, and turns on webhooks and integrations. Business ($99/mo) adds 500,000 responses a month, team members and roles, and SSO. The full breakdown is on the pricing page.
Frequently asked questions
Do I need a developer to install a website feedback tool?
No. If you can paste a line of HTML before </body> — which most CMSes, site builders, and theme editors allow — you can install widgetful. There's no backend and no build step, and a developer or coding agent can do it in one prompt via the API and /install.md.
Can I show a different question on different pages?
Yes — that's the point of page-level feedback. Each widget is its own question, so you can run a “was this helpful?” on docs, a “what stopped you?” prompt on pricing, and an interest poll on the blog, each reporting separately and tagged with the page it came from. The Free plan caps you at two widgets total; paid plans are unlimited.
Will it slow down my site?
It shouldn't. The embed is tiny vanilla JavaScript loaded with defer from the edge, so it doesn't block rendering, and ingestion runs on Cloudflare Workers, not your server.
How is this different from a heatmap or session-recording tool?
They're built for different jobs and pair well together: heatmap and session-recording tools observe behaviour, whereas a website feedback tool like widgetful collects stated answers to a question you ask directly. If you want expressed opinions rather than inferences drawn from clicks, that's the gap widgetful fills. For the NPS side specifically, see how we read as a Delighted alternative, and for forms a Typeform alternative.
What happens to my data — can I export it?
Everything is exportable to CSV at any time, and contact-form submissions are also emailed to your workspace as they arrive. On paid plans you can push responses onward with webhooks and integrations. Forms also include a honeypot field to soak up spam bots.
How do I get enough responses to trust the result?
Place the ask after the content, keep the comment optional, and run one question per page. Then watch the trend rather than any single day — a handful of answers on a low-traffic page is anecdote, but a consistent direction across a week or two is a real signal you can act on. For more ideas by scenario, browse the use cases.
What if I have a question that isn't here?
Reach out any time — contact support, or read about the team behind widgetful. When you're ready, start free and have your first widget live in a few minutes.
Try it on your site
Create a widget, paste one snippet, and watch responses roll in. The free plan is genuinely free — 1,000 responses a month, no card, live in about a minute.