I was w I was writing fresh code for reviews and wanted to put it on more than one site, so I wrote ReviewSnippet. Then I built the approval queue, because that's what every reviews widget has: reviews land in your dashboard and wait for you to wave them through. I looked at it for a day and deleted it. Now reviews publish the second they're written. The site owner can reply to any of them and delete none of them -- there's no route in the code, and the reviews don't sit on their server, they sit on mine. Taking one down needs a reason from a fixed list, and the widget tells your visitors it happened. The person who wrote a review is the only one who can erase it. It goes against the grain. I'm taking the delete button away from the people who pay me, and that's a harder sell than the alternative. I'd rather say that myself than have it said to me. But you don't have to trust anyone for it to work -- that's the whole point. A 4.6 nobody could edit beats a 5.0 anyone could. It's live at reviews.whitneys.co, showing zero reviews. Day one, and that seemed more honest than writing my own.riting fresh code for reviews and wanted to put it on more than 1 site, so I wrote ReviewSnippet. It goes against the grain, so only real, ethical people will use it.

ReviewSnippet for any website - one line

Immutable reviews that actually build trust

Immutable reviews that actually build trust