A front-desk habit that feels completely reasonable: send the post-stay review request only to guests who smiled at checkout, and quietly skip the ones who mentioned a complaint. No one calls it a policy. It's just efficient—why invite a bad review when you can simply not ask? Versions of this exact routine run at hotels and spas across Thailand every day, usually without anyone framing it as a deliberate strategy at all.
In the United States, the Federal Trade Commission fined the retailer Fashion Nova $4.2 million for "concealing reviews with ratings below four out of five stars"—the FTC's first legal action over a company hiding negative customer reviews. Hospitality Net, "Review-Gating Will Get Your Hotel Banned From Google" It sounds like a retail-industry problem, a US regulatory story with no real bearing on a Thai hotel's checkout routine. Actually, the practice the FTC penalized and the practice Google's own policy separately prohibits are the same behavior, described in almost the same words, and the habit sitting behind most Thai front desks—"only ask the guests who seemed happy"—is closer to that line than most owners realize. This piece explains what review-gating actually is, why the FTC and Google both now treat it as a serious violation rather than a gray area, and what a business should do instead.
Review-gating doesn't feel like hiding anything—it feels like being efficient with who you ask. Regulators and platforms have both stopped agreeing with that framing, and the gap between the two is where the real risk sits.
The Selective Ask
Review-gating is any process that filters which customers get invited to leave a public review based on how satisfied they seemed first—asking happy guests directly and quietly routing everyone else to a private feedback form, or simply not sending the review link at all when a stay went badly. It rarely feels manipulative from the inside. It feels like common sense: why generate a bad review you could have avoided just by not asking?
That instinct is exactly what both regulators and platforms have targeted. Google's own Prohibited and Restricted Content policy explicitly bars merchants who "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." Google Business Profile Help: Prohibited and Restricted Content That's not a policy against fake reviews—it's a policy against filtering real ones based on expected sentiment, which is precisely what a "happy guests only" review-request routine does, even when every review it generates is completely genuine.
What the FTC Actually Did to Fashion Nova
The FTC's action against Fashion Nova wasn't about fabricated reviews. Every review the company suppressed was real—the violation was systematically hiding reviews rated below four stars so customers only saw the flattering ones, described by the FTC as "concealing reviews with ratings below four out of five stars." The $4.2 million penalty, and the fact that this was the FTC's first legal action specifically over a company hiding negative reviews, signals that "we didn't fake anything, we just didn't show everything" is not a defense regulators accept.
That precedent matters beyond US retail because the underlying behavior—selectively controlling which real feedback the public sees—is exactly what a "happy guests only" review-request habit does in a hotel or spa context, just applied at the point of solicitation instead of after publication.
Google Draws the Same Line, From the Other Direction
Where the FTC penalizes suppressing negative reviews after they exist, Google's policy targets the earlier moment: selectively soliciting positive ones in the first place. Both rules converge on the same underlying practice. A hotel that never technically hides a published negative review, but only ever sends the request link to guests who seemed satisfied, is still violating Google's policy—the selectivity happens at the invitation stage, but it produces the identical distorted public picture the FTC penalized Fashion Nova for creating after the fact.
The stakes of that distorted picture are higher than they might seem: 81% of consumers always read reviews before booking a hotel, according to Drive Research, cited in the same Hospitality Net coverage of review-gating enforcement. Hospitality Net, "Review-Gating Will Get Your Hotel Banned From Google" A guest base that reads reviews that consistently isn't reading a filtered sample—it's reading whatever a property's solicitation habits actually produced.
Picture a Hypothetical Café Chain Doing the Same Thing
Picture a hypothetical café chain called Rim Khlong Cafe, a fictional four-branch operation used only as an illustration here. Rim Khlong's checkout staff handed a paper comment card to every visibly unhappy customer—"we'd love your private feedback"—while pointing satisfied customers toward a QR code for a public Google review. No one on staff thought of it as suppressing anything; they thought of it as routing feedback to the right channel. It's the same review-gating pattern the FTC and Google both target, just running through a coffee counter instead of a hotel front desk—proof the practice isn't a hospitality-specific habit, it's a general instinct that shows up anywhere staff control who gets asked to review publicly.
The Ungated Solicitation Playbook
- One Invitation, Every Guest—send the same review request to every guest who completes a genuine stay or treatment, with no filtering based on how the visit appeared to go.
- No Sentiment Sorting at the Front Desk—remove any staff judgment call about who "deserves" to be asked; the decision to invite a review should never depend on a staff member's read of the guest's mood.
- Separate Recovery From Solicitation—handle an unhappy guest's complaint directly and immediately, but don't let that recovery conversation replace or block their invitation to leave a public review if they want to.
- Audit the Habit, Not Just the Policy—review your own checkout routine against the five specific practices Google's policy prohibits, since review-gating is rarely the only one running quietly in the background.
Selective: what it all comes down to
If there's one word for what turns an ordinary front-desk habit into real regulatory and platform risk, it's Selective—not whether a business asks for reviews, but whether it decides in advance who's worth asking.
So here's a question worth sitting with: if you traced your own review-request process back to the front desk today, would you find a rule, written or unwritten, about which guests get the link—and if you would, is that rule one you'd be comfortable explaining to Google or a regulator directly?
FAQ
Is it review-gating if we just don't have time to ask every guest?
Not necessarily—review-gating specifically means filtering who gets asked based on expected sentiment. Inconsistent asking due to staffing gaps is a process problem, not the same violation, though it's worth fixing either way.
Does routing unhappy guests to a private feedback form count as review-gating?
It can, if that routing replaces their invitation to leave a public review rather than running alongside it. The problem isn't offering a private channel—it's using it to prevent a negative review from reaching a public platform.
Has Thailand seen enforcement action over review-gating specifically?
Not that this piece can confirm directly—the $4.2 million FTC penalty is a US case. The relevant risk for a Thai business is Google's own platform-level policy enforcement, which applies globally regardless of where a regulator is based.
What's the difference between review-gating and simply not overwhelming guests with requests?
Frequency management—like not sending three review requests to the same guest—is an operational choice. Review-gating specifically means choosing who gets asked based on how happy they seemed, not how many times you've already asked.
If our reviews are all genuine, does it matter how we chose who to ask?
Yes. Both the FTC's action and Google's policy treat genuine-but-selectively-solicited reviews as a violation in their own right—authenticity of individual reviews doesn't excuse a filtered sample overall.
Is review-gating treated as seriously as outright fake reviews?
They're different violations, but both distort what the public actually sees. TripAdvisor's and Google's own enforcement data shows the scale platforms dedicate to catching manipulated review patterns generally, which is the same enforcement appetite review-gating now falls under.
What this looks like with NAWA Trust
NAWA Trust's review inbox brings in every Google Business Profile review that actually gets posted—not a filtered subset chosen by whoever's on shift—so your trust dashboard reflects the real pattern of what guests are saying, not just the reviews a "happy guests only" habit would have generated. Response-time and rating tracking work the same way for every review, regardless of whether it's a five-star mention or a detailed complaint.
If you want to know what your actual review pattern looks like once solicitation stops filtering it, talk to us about your current review-request process.
Sources: Hospitality Net, "Review-Gating Will Get Your Hotel Banned From Google"; Google Business Profile Help, "Prohibited and Restricted Content"