Review Bombs and Bad Months Need Different Playbooks
Most operators treat a review bomb the same way they treat a rough patch of bad reviews. That's the wrong call.
A bad month is a signal about your property. A review bomb is an attack on your account. Treat the second one like the first and you'll just sit there drafting polite responses nobody asked for while the damage sets in.
Here's how you tell them apart. A bad month has range. Different complaints, different units, different move-in dates, spread out over weeks. Maintenance is slow, the pool's closed, a renewal jumped too much. It reads like actual residents with actual gripes on their own schedule.
A review bomb looks manufactured, because it is. A pile of one-star reviews inside a few hours or a couple of days. Vague language that repeats itself post to post, sometimes nearly word for word. Reviewer profiles with no other history, all created the same week. No unit number, no specific incident, nothing you can trace to an actual lease.
Sometimes you can name the trigger. A termination, an eviction, a vendor dispute, a competitor who just lost a leasing deal to you. Sometimes there's no motive you can find, and you have to work off the pattern instead.
Once you're confident it's coordinated, stop replying to individual reviews like they're feedback. That's mistake number one. Writing "we're sorry you had this experience" under twelve fake reviews doesn't calm anybody down. It just adds your name to a wall of noise that Google and Yelp are happy to keep indexing forever. It also tells whoever's running the campaign that engagement works, which is an invitation for round two.
Here's what to do instead. Document everything before you touch a single review. Screenshot each one, note the posting time, the account age, any language that repeats across posts. You'll want this if you escalate, because reviews have a habit of getting edited or quietly deleted once the poster realizes you're building a file.
Then escalate through the platform's abuse channel, not the reply box. Google Business Profile has an actual process for reporting reviews that violate policy, including fake engagement and posts from accounts with no verifiable tie to the property. Yelp has its own version. Both are slow, both are inconsistent, and your results depend on how clean your documentation is. But skip straight to public replies and you burn the option to report it cleanly later.
If the volume's heavy enough to move your aggregate rating, loop in legal before you post anything public. A coordinated campaign traced to a specific person, an ex-employee, a rejected applicant, a competitor, can sometimes support a cease and desist or a platform complaint with real teeth behind it. That's not a call for marketing to make solo. Treating it like one just slows down the people who could actually get the reviews pulled.
What you shouldn't do is go quiet and wait for it to pass. Silence on a review bomb reads exactly like silence on real complaints. Prospects can't tell the difference from the outside.
Post one calm, factual response on the platform itself, not on all twelve reviews, noting that you've identified irregular activity and are working with the platform on it. Then let the documentation and the escalation do the actual work.
Responding to every bad review kindly and individually is a good instinct most months. It's the wrong tool for an attack, and reaching for it anyway is how a three-day problem turns into a three-month dent in your rating.
A bad month is a signal about your property. A review bomb is an attack on your account.
A weekly for the people who run apartment marketing.
Get it Tuesdays