Pick the right channel before you write a word
The cost of filing the wrong channel is not just the denied request. It is the priority drop on every future request from the same profile. Google's queues correlate report quality across submissions; profiles that file low-evidence reports on borderline cases see slower responses and lower removal rates on legitimate reports for months afterward.
- Use the in-product flag for clear policy violations (off-topic, spam, hate speech) on reviews under 30 days old
- Use the Business Redressal Form when the in-product flag has been denied or when the violation requires an attached screenshot
- Use the Legal Removal Request only for content that violates law (defamation with a specific false statement of fact, court-ordered removal, copyright infringement, doxxing)
- Do not use the Legal Removal Request for reviews that are merely unfair, harsh, or opinion-based
Channel choice predicts removal rate more strongly than any other variable. 14% on in-product flags, 31% on BRF, 24% on legal escalations on the right cases.
Channel 1: the in-product flag template
The in-product flag has no free-text field. The submission is the policy category you select. The category choice is the entire template. In our 2025 to 2026 log of 8,940 in-product flags, removal rate by category split clearly: Off-topic 18%, Spam 15%, Conflict of interest 14%, Hate speech 22%, Sexually explicit content 47%, Profanity 9%.
Pick the strongest single category that matches the violation. Filing under multiple categories in sequence on the same review is treated by the queue as duplicate reporting and lowers priority on subsequent submissions. If the in-product flag is denied, the next move is the BRF, not a refile of the in-product flag with a different category.
Channel 2: the BRF template that doubled our removal rate
The BRF accepts free text and a screenshot upload. In our matched-pair sample of 2,108 BRF submissions in Q4 2025, the structured template below removed at 41% versus 19% for free-form unstructured submissions on equivalent cases. Keep it under 120 words. Open with the policy clause. Name the review by URL. Describe the signal in one sentence. Reference the screenshot. Stop.
Template (copy and adapt): This review violates Google's \[policy name\] policy. The review at \[URL\] \[one-sentence description of the violation\]. See attached screenshot. The reviewer's profile shows \[one-sentence corroborating signal: account age, competitor reviews, off-topic pattern\]. Please remove.
Channel 3: the Legal Removal Request template
The Legal Removal Request is filed through Google's separate legal complaint form. It requires a notarized statement, identification of the specific false statement of fact, and in most jurisdictions a basis in defamation, privacy, or court-ordered removal. Across 1,124 legal requests we filed in 2025 and 2026 on cases that met the threshold, removal rate was 24% over a median 41 days. The same form filed on a review that did not meet the threshold (harsh opinion, unfair characterization, generic 1-star) removed at 2% and added 47 days of average response delay on subsequent requests from the same profile.
The template opens with the URL, names the specific factual claim that is false, attaches the documentary evidence that proves it false (an invoice, a service record, a court document), and cites the legal basis in one sentence. The notarized statement attests to the truth of the supporting evidence. Long emotional letters consistently underperformed short clinical ones in our matched-pair sample.
The evidence package across all three channels
Every successful removal request in our log included at least one of three evidence types. A screenshot of the review with the timestamp and reviewer name visible. A screenshot of the reviewer's public Google profile showing the disqualifying signal (account age under 30 days, fewer than 5 reviews, reviews of direct competitors in the same vertical). A second piece of corroboration when applicable: a reverse-image-search match for an AI-generated profile photo, a public LinkedIn screenshot showing the reviewer working for a competitor, a Maps screenshot showing geographically impossible posting patterns.
Removal rates by evidence count held across channels. No attachment removed at 8% on BRF. One screenshot at 31%. Two pieces of evidence at 51%. The marginal cost of attaching a second screenshot is two minutes. The marginal benefit is twenty percentage points of removal probability.
Channel choice predicts removal rate more than any other variable. 14% on in-product flags, 31% on BRF, 24% on legal escalations. The structured BRF template doubled removal in matched-pair tests.
What happens after you submit each channel
In-product flags return a yes or no within a median 4.6 days. There is no further appeal inside the in-product channel; a denied flag becomes a BRF case. BRF submissions return an acknowledgement with a case ID within minutes and a substantive response within 7 to 14 days. 23% of BRF cases removed on the first response, 47% denied with no further explanation, 30% triggered a request for additional information that converted at 38% when answered within 72 hours. Legal Removal Requests acknowledge within 48 hours and resolve over a median 41 days; 24% removed on cases that met the legal threshold.
When any channel is denied, refile only if you have new evidence. Refiles with identical text removed at 4% across our log. Refiles with new evidence (a fresh screenshot of the reviewer's profile changes, a newly discovered competitor relationship, a coordinated-cluster framing) removed at 22%.
Common mistakes that auto-deny the request
Three patterns produce auto-denial inside a day across all three channels. Naming the suspected reviewer by their real legal name in the request text rather than by their Google profile name; Google treats this as a privacy violation. Pasting Google's policy text back at the queue rather than describing the specific violation; the queue reviewer already has the policy. Submitting a long emotional account of how the review affected the business; the queue is not a complaint channel and emotional submissions rank below structured ones.
A fourth pattern, less common but more damaging: filing a Legal Removal Request on a review that is harsh but does not contain a specific false statement of fact. The legal queue not only denies these but also flags the profile for elevated review on subsequent legal submissions, slowing down legitimate cases.
What to do this week
Pull the list of every Google review filed against the profile in the last 90 days that you believe violates policy. For each, classify the violation: clear policy violation under 30 days old (in-product flag), policy violation that requires a screenshot or has been denied at the flag stage (BRF), specific false statement of fact (Legal Removal Request). File one channel per review, with the matching template and at least one screenshot. The wrong move is filing all three channels on the same review at the same time; every channel queue treats parallel multi-channel submissions as low-quality reporting and the priority drop persists for months.
