Site feedback without accounts, plugins or a third party
web · 2026-11-17 · 5 min
Most websites ask for feedback in the place where feedback goes to die: a contact form that opens a mail client, a chat bubble promising an answer within a day, a survey that arrives two days after the visit. The visitor had the thought at the exact moment something broke, and the site gave them nowhere to put it.
This is the write-up of the prototype I put at /feedback on this site. A visitor picks one of three states, writes two lines, and leaves. No account, no email required, no third-party service. It is deliberately a prototype, and the decisions worth writing down are the ones about what I did not build.
Three channels already existed, and none of them fit
The guestbook is public and social. People sign it to say hello, and that is what it is for: a complaint does not belong there, and neither does a note about a price table that breaks on a phone.
The bug report dialog posts to Discord. That is a developer channel with a developer's vocabulary, and it asks for a title, a description and a screenshot before it does anything.
Email catches everything else, which in practice means the message arrives with a subject like "question" and no page attached.
What was missing was a private channel attached to the page where the thought happened. Public or private is the first decision, not a detail: a note everyone will read is a different note from one that only I will read.
The decision: anonymous by default
The form asks one thing: how did it go. Works, something is off, not sure. Then two lines of text. Name and email sit in a collapsed row marked optional, and the copy says what they are for, a reply, and who sees them.
No account, no sign-in. Every field you add is a tax on a person already doing you a favour, and the people with the most useful bug are the least likely to fill three fields to report it.
What it is made of
The page is client-only and lives at /feedback. It is not in the sitemap, not prerendered, and it sets noindex on mount: a prototype whose content is sample notes has no business competing in a search result.
Under it, one endpoint. POST /api/feedback validates what the browser sends, rate-limits by IP, rejects the honeypot field, checks the message against the same word list as the guestbook, and writes to a JSON file next to the code. The browser never talks to a database directly, so the validation cannot be skipped with a curl.
Every note carries the page it is about, the locale, and the build that produced the page:
{
"verdict": "broken",
"message": "on the phone the price table scrolls sideways",
"page": "/prezzi",
"locale": "it",
"build": "m6rg5l0k",
"created_at": "2026-11-17T21:02:11.000Z"
}
The build field is the one I would not remove. Without it, a note about "the table" is unattributable a week later, after three deploys; with it, the note and the code that produced the bug share an identifier.
The page and the endpoint each have two data sources, switched by the build mode, not by a runtime flag. In development the page reads the API and the notes are real. In production it renders seven sample notes, labels them, and the form adds the note to the tab only. Nothing pretends to have been sent.
What I left out on purpose
A production collector. The deployed page is a demo, and it says so. Wiring Firestore or a function is half a day; deciding whether the feature is worth it comes first.
Translations. The page is Italian and English. The other five languages fall back to English, the same fallback the rest of the site uses. Forty strings across six translation modules is the wrong price for a prototype.
The inline pin. The version I actually want is the one where you click the paragraph that is wrong and leave the note there. That is the next step, not this one.
How I test it
- Development, empty database: the first note appears without a reload and the file on disk grows.
- Wrong path: submit with no verdict, then with one letter, and read the two messages a person would actually get.
- Rate limit: seven submissions in a row, expect a 429.
- Honeypot: post with the hidden field filled, expect a rejection.
- Production build: the list shows samples, the badge says sample, and the note stays in the tab.
What you can copy without the code
- Put the question where the thought happens, not in an inbox three clicks away.
- Ask one thing. The three states are the whole questionnaire.
- Make it anonymous by default, and make the optional field say who reads it.
- Store the page and the build: a note without context is a rumour.
- Read the negative ones first, and answer in public when you fix something. The same asymmetry is why testimonials work, and I wrote about it in how to add testimonials people believe.
If you want a channel like this on your site, the quote is written and the prices are public: what a website costs in Parma.