A Google review is not a newspaper article and it is not a private message. It is a product of Google Business Profile, scored, ranked and attached to a map pin. Australian owners who write to “Google support” as if it were a corrections desk will wait forever. The company will remove a review that breaks a published policy. It will not remove a review because the star rating is commercially inconvenient, or because the prose is rude.
If you remember one distinction from this guide, make it this one: policy removal versus reputation management. Do the first where the review is fake, conflicted, off-platform, restricted or spam. Do not dress the second up as the first. The rest of the platform takedowns hub covers posts and videos. This piece is only the review product.
What Google will actually consider
Google’s review policies are public and more specific than owners are told by agencies. The live buckets for an Australian listing are these.
Fake reviews. A review from someone who never dealt with the business, a review the owner wrote, a competitor wrote, or a review purchased from a panel. A human report still helps when you can show the account has never been in the store, or that the same prose appears on three rival listings.
Conflicts of interest. Current or former employees, the owner’s relatives, and anyone offered a reward for a star rating. A staff member reviewing their own workplace is the textbook case. A coffee voucher for five stars is also a conflict.
Off-platform disputes. Reviews that exist to prosecute a fight that did not happen at the business: a custody argument, a neighbourhood feud, a rant about a different company that happens to share a name. The policy is about relevance to the listing.
Restricted content. Hate, sexually explicit material, a staff member’s home address, and threats. These are the fastest human removals when the text is unambiguous.
Spam, off-topic, and the wrong listing. A review posted to the wrong branch, a review that is only a URL, a review copied from a template farm. Boring, and often successful.
What Google will not do, even if you ask politely and often: take down a one-star review that is merely rude; take down a review because you refunded the customer after it was posted; or weigh in on whether the lasagne was, in fact, cold.
Why the rude-but-true review stays
Google’s product thesis is that a genuine negative review is useful to other searchers. A late tradie, a cancelled booking, a disputed invoice — if the reviewer had a real encounter, the prose can be sharp and the review will stay. Your owner-response is the designated tool. A removal request is not.
“Not a real customer” is the most common failed hook. It is only a hook if you can show it. A diner you do not remember is not a fake. A mobile number that is not in your booking system is not proof of anything; people walk in.
If the review is false in a way that is causing serious harm, that is a solicitor’s question, not a Business Profile question. It is also not the first move. Most “defamatory” reviews we are sent are opinions about service quality. Australian defamation law is not a star-rating appeals tribunal.
Prepare the file, then flag it
Most failed flags are incomplete. The Business Profile interface is designed to take a category click, not a dossier, so you have to build the dossier yourself.
- The exact review URL, or the reviewer’s profile URL plus a screenshot that shows the listing name, the date, the star rating and the full text.
- A screenshot of the live review in an incognito window in Australia, with the date visible.
- The policy hook in one sentence. “This reviewer is a current employee.” “This text is a custody dispute and does not describe a visit.” If you cannot write that sentence, you do not have a Google Reviews job.
- The exhibits. A staff roster, a screenshot of the same prose on another listing, a message offering five stars for a voucher. Do not attach a customer’s medical file or someone else’s licence.
- Proof you are authorised to manage the listing. A third-party agency will need the owner to flag it, or to grant access.
Keep the owner-response off the review until you have decided whether you are flagging it. A long, angry response does not help a later policy report, and it is public.
Start on the review itself, signed in as an owner. Flag it. Choose the most specific category. Submit. For a pattern — a burst of five-star reviews in an hour, or identical prose on rival listings — use Google’s suspicious-activity channels where they are offered and describe the pattern once.
A third product sits with Google’s legal removals, the same family used for Search. That door is for a court order, or for a narrow personal-information claim, not for a one-star lasagne. If a review publishes a staff member’s home address, you may have both a restricted-content flag and a personal-information removal.
Copyright is almost never the right door. You do not own the customer’s prose. Dressing a reputation problem up as a copyright claim is the mistake we keep seeing; it has its own piece, copyright versus reputation. After you flag, you will usually hear nothing. If the review is still there a fortnight later, it has probably been left up. Flagging it four more times will not help.
The ACCC angle, and the fights that make it worse
Fake reviews are also a consumer-law problem. The ACCC has, for years, treated the buying and selling of reviews, and the suppression of genuine ones, as a live enforcement theme. That cuts in both directions. If a competitor is paying for one-star reviews, you may have a consumer-law complaint as well as a flag. If you are offering a voucher for five stars, or asking unhappy customers to take a review down in exchange for a refund as a matter of policy, you may be creating your own ACCC problem. This desk is not your regulator. Do not write to the Commission as a substitute for the flag button. It does not operate a takedown desk for individual map pins.
If the review will stay, the owner-response is the only public tool you have. Keep it short. Acknowledge the visit if it happened. Say what you did. Do not publish the reviewer’s surname, employer or mobile number. A defensive response that doxxes a customer can be a policy breach of its own. Do not bribe the reviewer, flee to a second listing, or send staff out to seed five-star reviews. Those moves are how a one-star problem becomes an ACCC problem. If the same text is also on Facebook or a forum, that is a set of other products. The platform takedowns hub is the map.
When to stop, and when to escalate
Stop when the review is a genuine encounter described in rude language. Your labour is better spent on the next booking.
Escalate inside Google when you have a real policy hook and the first flag failed. Escalate to eSafety only if the text is adult cyber-abuse or image-based abuse, which a map review almost never is. Escalate to a solicitor when the imputation is false and the harm is serious. Escalate to the ACCC only when you are looking at a trade in fake reviews, not a single unhappy customer.
Agencies that promise to “restore your rating in 14 days” are usually selling flags you can file, plus a volume of new five-star reviews you should not want. There is no shame in paying someone to do tedious paperwork. There is shame in buying a chorus.
A working sequence we recommend
- Capture the review URL and a dated incognito screenshot.
- Write the one-sentence policy hook. If you cannot, write an owner-response instead and stop.
- Flag the review from the owner login. If there is a pattern, describe the pattern once.
- Check restricted-content and personal-information angles before you think about defamation.
- Wait a fortnight. If it is gone, file any leftover search snippet through the Search removal tools.
- If it stays and the text is a genuine encounter, reply once, briefly, and move on.
- Diary a reminder in 90 days. Review farms come back.
If you want the desk to look at a general question about the process, use contact. Do not send the customer’s booking record, a copy of their licence, or a spreadsheet of your rival’s reviews. We publish method. We do not run your case.