Your Business Is Being Review-Bombed: What to Do Right Now

It happens fast. You check your Google reviews on a Tuesday morning and your rating has dropped from 4.6 to 3.1 overnight. There are 8 new 1-star reviews, all posted within a few hours, from accounts you've never seen.

This is a review attack. Here's what to do, in order.

Step 1: Identify Whether This Is a Coordinated Attack

Before reacting, confirm you're dealing with manufactured reviews, not a sudden wave of legitimate complaints. The two require different responses.

Signs of a coordinated attack:

• Timing cluster: Multiple 1-star reviews posted within a short window (hours or a day), especially overnight or on a weekend
• Reviewer account age: Profiles created recently, often with no other review history
• Generic or vague content: "Terrible business" or "Do not use" without specifics is common in fake attacks
• No transaction history: If your business tracks customers (by appointment, account, or order number), none of these names match anyone in your system
• Language patterns: Strikingly similar phrasing across multiple reviews, suggesting the same author or a shared script
• No photos, limited profile activity: Fake accounts typically have placeholder profile images and no community activity

If the reviews include specific details about real experiences, specific staff names, or service complaints that align with actual recent transactions, take them seriously as legitimate feedback even if the volume feels unusual.

Step 2: Document Everything Before Reporting

Before you flag or report anything, document the evidence:

• Screenshot every suspicious review including the reviewer's profile (name, photo, review history, account creation date if visible)
• Note the timestamps of all suspicious reviews
• Note any patterns in language or content
• Save screenshots to a dated folder in case you need them later for a dispute or legal matter

This documentation step is easy to skip when you're feeling urgent, but it's important. Once Google removes a review, it's gone and you lose the evidence trail.

Step 3: Flag and Report to Each Platform

Google:

1. Find the review you want to flag
2. Click the three-dot menu (desktop) or the flag icon
3. Select "Report review"
4. Choose the most applicable reason: "Off topic," "Spam or fake," or "Conflict of interest"
5. For a coordinated attack, also submit a support request through your Google Business Profile dashboard under "Support" with your documentation attached

Google's review removal process is not fast. Standard flagging can take 3 to 5 business days for a response. Escalating through support with documentation of a coordinated attack sometimes accelerates this.

Yelp: Flag each review individually. If you have documentation of coordinated activity, contact Yelp business support directly with your evidence.

Facebook: Use the "Find Support or Report" option on each review. Facebook reviews (now called Recommendations) can be turned off entirely on your page if the attack is severe enough and you need to stop the bleeding while you address the situation.

Step 4: Respond Publicly to Defuse, Not Inflame

For each suspicious review, post a brief, calm public response. The goal is not to argue with the fake reviewer. The goal is to communicate clearly to everyone reading your profile.

A template that works:

"We've reviewed our records and are unable to find any account of a visit or transaction associated with this review. We take all feedback seriously and encourage anyone with a genuine concern to contact us directly at phone/email. We are reporting this review to Google for investigation."

This signals to prospective customers that you're paying attention, you've investigated, and you're handling it through appropriate channels. It does not escalate or sound defensive.

What not to do:

• Don't argue, accuse, or get emotional in public responses
• Don't accuse specific competitors by name
• Don't threaten legal action in your response (even if you're pursuing it)

Step 5: Launch a Proactive Positive Review Campaign

While you're working on removal, dilute the damage. Reach out proactively to recent satisfied customers, any customers who mentioned they had a good experience, and long-term loyal customers.

A personal ask from you (not a generic automated message) in this context is appropriate: "We've been the target of some fake reviews that are affecting our rating, and I want to make sure genuine customers have a chance to share their real experience. If you have a moment, a Google review would mean a lot right now."

This is transparent, honest, and effective. Customers who like your business often want to help when they understand the situation.

Step 6: Know When to Involve a Lawyer

If you can identify who is behind the attack (a disgruntled ex-employee, a competitor, someone you had a personal dispute with), you may have legal recourse:

• Defamation claims are viable when false statements of fact are published and cause real damages
• Interference with business relationships is a cause of action in many states
• Platform terms of service violations can support cease-and-desist letters

An attorney specializing in defamation or internet law can help you assess whether the situation warrants legal action. This is rarely the first move, but it's a legitimate option when the attacker is identifiable and the damage is substantial.

The Long-Term Protection: A Deep Review Buffer

The most resilient businesses in a review attack scenario are the ones with 200+ reviews before the attack. Going from 4.7 to 4.3 is painful but survivable. Going from 3.9 to 3.1 is a different situation.

Consistent, ongoing review acquisition is the only real protection against the disproportionate damage that a concentrated attack can cause. The deeper your review base, the less any individual wave of fake reviews can move your aggregate rating.

Laudy monitors your review profile for unusual activity and alerts you immediately when something looks off, so you can respond before the damage compounds. Set up your account at /signup.