An Ex-Employee Left a Negative Review? The Clause That Protects You
Published October 1, 2026 · 5 min read
"Worst management I've ever worked for, don't deal with them." One star, and the name is familiar: an employee who resigned last month after a dispute.
This is one of the few cases where you have a clear policy basis for a report — provided you handle it in a specific way, and not the way the moment pushes you toward.
Key takeaways:
- Conflict of interest is an explicit violation, and former employment is named in the text.
- Never reveal publicly that they were an employee — that is employment data.
- A report needs what is visible in the review or the account, not what you know.
- A short neutral reply is still necessary, because readers see it now and reports take days.
- A current employee posting a positive review violates the same clause.
The clause that works for you
Under Rating Manipulation, Google prohibits:
"Content that is based on a conflict of interest. A conflict of interest may include current or former employment, a contractual or consultory relationship, or other professional or personal affiliations that demonstrate a conflict of interest."
(Prohibited & restricted content)
"Current or former employment" is there verbatim. This isn't interpretation — a former employee's review violates the policy as written.
But knowing isn't proving
This is where most reports fail. You know they're a former employee; Google doesn't, and cannot verify your HR records.
What works in a report is what everyone can see:
- The text itself reveals the relationship: "I used to work here", "management treats its staff…", "salaries are late". This is the strongest thing you can point to.
- The account name matches a publicly known employee — if their name appears on your pages, for example.
- Other reviews from the same account expose the connection.
What doesn't work: "this is our former employee and they have a grudge." It cannot be verified, and the report is rejected.
⚠️ If the review discusses an employment experience rather than a customer experience, you have a second ground: off-topic content. Google doesn't allow content not based on an experience at the place as a customer.
What you never write in the public reply
The most dangerous part of this case is that the natural reply is the wrong one:
- ❌ "You're a former employee, not a customer."
- ❌ "You left after performance issues."
- ❌ "Review the reasons your contract ended."
Each of these discloses an employment relationship publicly, and its details. The asymmetry is that you are an organisation and they are an individual — readers hold you to that standard, not them.
And even setting any legal question aside, the impression is disastrous: a business discussing its personnel files in public.
What to write instead
Short, neutral, denying from records rather than from knowledge:
We couldn't find a customer visit in our records matching these details. If you've had an experience with us, we'd like to hear it directly at [email].
And if the review talks explicitly about the workplace:
Team feedback comes through our internal channels and we take it seriously. This space is for customer experiences, and we're happy to reach you at [email].
That second line is the clever one: it separates the venue without confirming the relationship, and reads as mature management rather than defence.
The practical order
- Document — screenshot with date and account name, before it's removed.
- Reply with the neutral wording within 24 hours. Readers see it now; a report takes days.
- Report, pointing at what's visible in the text: reporting a policy-violating review.
- Don't resubmit an identical report if it's rejected: Google rejected your report?
The other side: your current employees
The same clause applies to you. A positive review from a current employee is a violation — a plain conflict of interest.
And it has widened: Google's current policy also prohibits asking staff to collect a certain number of reviews, or reviews that name a specific staff member. Detail in what changed in Google's review policy.
FAQ
Can I ask them to delete it?
You can reach out calmly and ask once, without insistence and without tying it to any payment owed. Tying removal to money is an outright violation.
The review is actually accurate — do I still report?
The violation here is in who wrote it, not whether it's true. But if it describes a real problem, the report doesn't relieve you of fixing it internally.
What if they used a pseudonym?
Proof becomes hard. Focus on any signals of an employment relationship in the text, and use the neutral reply.
Do these usually get removed?
When the text states the relationship outright, the odds are decent. When it reveals nothing, it most likely stays.
The bottom line
This case hands you a clear policy weapon — and a trap alongside it. The clause serves you, but using it in the public reply instead of the report turns you from the injured party into the one disclosing staff data.
The rule: the report tells the whole truth; the public reply says nothing about employment.
Meanwhile the real reviews keep arriving daily. Raddly gathers them in one place and drafts a reply for each in your business's voice, so the exceptional case doesn't crowd out the routine that actually builds your reputation.