Google Reviews
A Former Employee Left a Google Review: How to Handle It
A review about what it was like to work for you lands in the same place as your customer feedback, where nobody browsing can tell the difference. Google's policies do cover this — here's how to report it, what to write while it's still up, and the responses that make it worse.
Updated 20 August 2026 · 7 min read
Why this one lands differently
A customer review is about a transaction. A review from someone who worked for you is about a relationship, usually one that ended badly, written by a person who knows things about the business no customer ever would. It's more detailed, more personal, and often more damaging for it.
The structural problem is that it sits on the same page as everything else. A prospective customer scrolling your reviews has no way to tell that the long, specific one-star review is about a roster dispute rather than a service they might receive. That's exactly why Google's own policies treat it as content that doesn't belong there — which is the useful part of this situation.
Google's policies do cover this
Google's review content policies include a conflict-of-interest rule: reviews are meant to reflect a genuine customer experience, and content posted by current or former employees about their employment experience falls outside that. So a review about working conditions, a manager, pay or a dismissal is reportable on a policy ground, not merely because you dislike it.
Two caveats worth setting expectations around. Google makes the decision, not you — reporting is a request and rejections are common, particularly where the review is written vaguely enough to read as though it might be from a customer. And it isn't fast. Assume the review will be visible while the report is considered, and plan your response on that basis rather than waiting for a removal that may not come.
Report it properly, once
The mechanics are the same as for any policy-breaching review: flag it from your Business Profile or from the listing in Maps and choose the closest policy category — conflict of interest is the one that fits here.
- Keep any explanation factual and short. "This review is from a former employee about their employment, not a customer experience" is stronger than a paragraph about the circumstances of their departure.
- Screenshot the review with its date before you report, so you have your own record whatever happens next.
- Report once, from your own account. Asking staff, friends or family to pile on with reports doesn't increase the chance of removal and looks like exactly the kind of coordinated activity Google's systems are built to notice.
- Don't stop there and wait. Write the reply as though the review is staying, because it might be.
What to write while it's still up
The reply isn't for the reviewer — it's for the customers who'll read this page over the next two years. That reframing settles most of the hard decisions, because almost everything you'd want to say to a former employee is something a customer shouldn't be reading.
Keep it short, calm and neutral, and don't confirm the employment relationship. Something along the lines of: "Thanks for taking the time to write. We're not able to match this to a customer experience with our business. If you've dealt with us as a customer and something went wrong, please contact us at [email] — we'd genuinely like to hear about it." That does the whole job. It signals to a browser that this isn't customer feedback, without dragging the actual dispute into public view.
What you must not do is disclose that the person worked for you, why they left, or anything about their performance or conduct. That's their personal information, and airing an employment matter on a public review page is a serious step with consequences well beyond the review itself.
The responses that make it worse
- Retaliating against a current employee over a review. Before any disciplinary step connected to something an employee has said publicly, get proper workplace-relations advice — this is an area where the wrong move creates a much larger problem than the review.
- Asking your team, friends or family to post positive reviews to bury it. Reviews from people without a genuine customer experience breach Google's policies, and manufacturing a rating that misrepresents real customer experiences can amount to misleading conduct under Australian Consumer Law.
- Naming the person, or dropping enough detail that regulars can work out who it is.
- Threatening legal action in the reply. Defamation in Australia is complex and there are steps required before proceedings can start — that's a conversation with a lawyer, not a line in a public reply, where it almost always reads as intimidation to everyone else watching.
- Offering them something to take it down. Paying for a review's removal puts you in the same territory as paying for reviews in the first place.
Read it as a signal, not just a problem
One angry review from a departing employee is a bad week. Three over eighteen months, all describing something similar, is information — and it's usually information the customer reviews are quietly echoing too, in complaints about rushed service, high staff turnover or nobody knowing what's going on.
It's also a fair, non-retaliatory move to tell your team where workplace feedback should go: an exit conversation, an employer-review site, an anonymous internal channel. People often use a Google review because they don't believe any other route exists, and giving them a real one costs nothing.
The durable fix is volume
Whether or not the review comes down, the thing that decides how much damage it does is how much genuine customer feedback surrounds it. A detailed one-star review is loud on a profile with fifteen reviews and easy to read past on one with two hundred, where the pattern around it is obviously different.
So the answer to a review you can't control is the same as the answer to most reputation problems: ask every customer, consistently, on the same terms — never steering only the happy ones toward Google — and reply to what comes in. That's slower than a removal request, and it's the part that actually holds.