Document a review extortion demand without paying the sender

Identify the demand, not just the rating surge

A sudden group of low ratings is an observation; an explicit demand for payment or favors to remove them is a distinct event. Save the actual communication rather than assuming every unfamiliar negative review belongs to an extortion attempt.

Record when you noticed the reviews and when the demand arrived. Include the channel and sender information available in the message. Do not publicly expose the sender's details or retaliate through reviews of another business. Preserve the original material for the appropriate official reporting process.

Keep a concise evidence bundle

Google's extortion guidance asks for relevant communications, suspicious review links, sender details, and context. Organize those items so a reviewer can follow the sequence. Use filenames or a private index that show the timing without publishing customer information.

Separate unrelated customer complaints and routine billing disputes from the suspected incident. If there is no demand, review the normal policy-reporting route for a specific violation instead. A large folder of every negative review does not establish that each contribution is part of the same extortion attempt.

Preserve and report through the dedicated route

• Save original demand messages and screenshots showing relevant timing and sender information.
• Collect direct links to the reviews you reasonably believe relate to the demand.
• Write a short chronological description of the observed events.
• Use the merchant-extortion form linked in Google's current official article and provide its requested evidence.
• Retain the case reference and track the actual response without negotiating a payment for review removal.

Avoid escalating the incident yourself

Google advises against engaging with or paying malicious individuals in these cases. Payment does not guarantee removal and can encourage further demands. Do not offer a service or discount as an alternative bargain or ask staff to create positive reviews to drown out the suspected attack.

Keep customers' legitimate service concerns separate and respond appropriately when a review is genuinely about their experience. If an incident includes an immediate safety threat or other matters beyond platform moderation, seek the appropriate real-world assistance; this guide does not determine legal liability or replace professional advice.

Record the outcome and protect ongoing operations

After submitting, monitor the official case and the specific linked reviews. Record whether the incident is under review and what outcome is actually communicated. Do not announce that all suspicious reviews are removed before that happens or promise that every report will have the same result.

Check authorized profile access and business contact paths as routine operational protection, without assuming the incident also proves account compromise. The useful outcome is a well-documented report and a legitimate response process. Rating recovery and review removal remain decisions outside your direct control.

Worked example

For example, a shop notices several unfamiliar one-star reviews and later receives a message demanding an illustrative $200 to remove them. The owner preserves the original demand, dates, sender information, and direct review links. They use Google's dedicated extortion route and do not negotiate or pay. A separate ordinary complaint about service timing is not automatically added to the incident. The example shows evidence organization, not a conclusion about a real sender or a guarantee of removal.

Questions about this task