When a security plugin blocks your client’s feedback
Your client opens the review link, clicks an element, types a comment, and gets “Something went wrong.” Nothing you change on the review helps. They may tell you their ad-blocker is off, because that is the usual advice and it is not the problem.
What is almost certainly happening is that an anti-spam or security plugin on the site is intercepting Reviso’s requests and answering them itself.
Why it happens
Anti-spam plugins watch for anything that looks like a public contact form. A review comment carries a name, an email and a message, which is exactly that shape, so it gets checked like a form submission. If the plugin does not like the reviewer’s email, it refuses the request and replies in its own format. Reviso cannot read that reply, so all it can tell the client is that something failed.
The most common culprit is CleanTalk Anti-Spam, which runs an “email exists” lookup and rejects addresses it cannot verify. It rejects ordinary Gmail addresses this way.
Reviso 1.6.2 and later detect CleanTalk and offer you a one-click fix in the admin. If you are on an earlier version, or using a different plugin, the rest of this page is the manual route.
Confirming it in one step
Ask the reviewer to try again without filling in the email field (it is optional). If the comment goes through without an email and fails with one, a form scanner is your answer. Nothing else produces that pattern.
Fixing it: CleanTalk
Settings → CleanTalk → Advanced settings → Exclusions → Form signs, and add:
reviso_That matches Reviso’s request names and nothing else. Every other form on the site stays checked exactly as it was.
If Reviso showed you a notice offering to do this, the button does the same thing and appends to any exclusions you already have.
Fixing it: other plugins
The principle is the same whatever the plugin: exclude Reviso’s AJAX requests, which all begin reviso_ and all arrive at /wp-admin/admin-ajax.php.
| Plugin | Where to look |
|---|---|
| Wordfence | Firewall → Allowlisted URLs, allow /wp-admin/admin-ajax.php for the reviewer’s IP, or set the firewall to Learning Mode while a review is open |
| Akismet | Only checks WordPress comments, so it does not affect Reviso |
| Cloudflare / WAF | Look for a rule matching POSTs to admin-ajax.php and add a skip for action values starting reviso_ |
| Anything else | Search its settings for “exclusions”, “allowlist” or “skip”, and exclude admin-ajax.php or the reviso_ action prefix |
Is it safe to exclude Reviso?
Yes, and more so than it sounds.
A review link is private: 48 random characters, sent to one named client. Posting a comment needs that token, plus a WordPress security nonce, and is rate limited per review on top. Someone would have to be given the link before they could post anything at all.
So there is no open form here for an anti-spam plugin to protect. It cannot tell that on its own, because all it sees is a POST with an email in it, which is why it needs telling.
If it still fails
Reviso 1.6.2 and later name the blocking plugin in the error instead of saying “Something went wrong”, so the reviewer can send you a screenshot that identifies the culprit. If you are stuck, send that message to ben@getreviso.io and we will tell you what to exclude.