When to file a BRF instead of an in-product flag
The in-product flag from the three-dot menu is the right first move on every suspect review. It is fast, it does not require login to anything outside Maps, and it gives Google's automated system a chance to remove obvious policy violations within hours. In our 2025 to 2026 log, in-product flags removed 14% of the reviews they were filed against, with a median resolution time of 4.6 days.
File a BRF when the in-product flag has been denied and you still believe the review violates a specific policy, when the violation requires an attached screenshot to be visible (off-topic content, conflict of interest, identifiable confidential information), or when the same business has been hit by a coordinated cluster of reviews that the in-product flag is unlikely to recognize as a pattern. BRF resolution time in our log was a median 11 days, with removal at 31%.
31% removal across 18,402 BRF submissions in 2025 to 2026, vs 14% on in-product flags filed without a BRF follow-up. The BRF is the second step, not the first.
The five Google policies the BRF queue actually enforces
Google's review content policy is long. The BRF queue removes against five clauses with high consistency. Citing the right one in the first sentence of the dispute roughly doubled removal rates in our matched-pair sample of 2,108 BRF submissions in Q4 2025.
- Off-topic: the review describes a service, location, or product the business does not offer
- Conflict of interest: the reviewer is a current or former employee, a competitor, or a person with a financial relationship to a competitor
- Spam: the same review text or near-identical text appears on multiple unrelated business profiles
- Confidential or personal information: the review names an employee in a way that violates privacy policy or includes contact details
- Restricted content: the review contains hate speech, harassment, sexually explicit content, or threats
The evidence package that doubles BRF success
Every successful BRF in our log included at least one of three evidence types. A screenshot of the review with timestamp 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 result 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.
Across the 18,402 BRF submissions in our log, removal rates split cleanly by evidence count. No attachment removed at 9%. 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.
The BRF wording template we use
Keep the dispute under 120 words. Open with the policy clause being violated. Name the review by its URL. Describe the signal in one sentence. Reference the attached screenshot. Stop. Long emotional submissions consistently underperformed short clinical ones in our matched-pair sample.
Template: 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\]. Please remove.
What happens after you submit
Google sends an acknowledgement within minutes that contains a case ID. The first substantive response usually arrives within 7 to 14 days. In 23% of our 2025 cases the response was a removal confirmation. In 47% it was a denial with no further explanation. In the remaining 30%, Google requested additional information; supplying that information within 72 hours converted 38% of those cases to removal.
When a BRF is denied with no further explanation, the right move is rarely to refile the same submission. Refile rate in our log was 11%; the rate of removal on refiles with the identical text was 4%. Refiles that added a new piece of evidence (a fresh screenshot of the reviewer's profile changes, a newly discovered competitor relationship) removed at 22%.
31% removal on 18,402 BRF submissions vs 14% on in-product flags. The BRF is the second step, not the first. Two pieces of evidence remove at 51%; no attachment removes at 9%.
Common mistakes that get a BRF auto-denied
Three patterns we see weekly that produce auto-denial inside a day. Naming the suspected reviewer by their real legal name in the dispute text rather than by their Google profile name; Google treats this as a privacy violation and rejects on principle. 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 BRF on a review that is critical but does not violate any policy. The right counter to a harsh-but-honest review is a public response that addresses the substance, not a dispute that the queue will deny and that signals to the queue that this profile generates low-quality reports.
When to escalate beyond the BRF
If the BRF is denied and the review contains a specific defamatory factual claim (a service the business never provided, an event that did not occur, a named individual accused of a crime), the next step is a Legal Removal Request through Google's separate legal channel. In our log, legal escalations on factual-defamation cases removed at 24%, with a median resolution time of 41 days. They require a notarized statement and, in most jurisdictions, identification of the specific false statement of fact rather than a general impression of unfairness.
For coordinated attacks (10 or more 1-star reviews from new accounts within 72 hours), the right path is a single BRF that frames the cluster as a coordinated event with a list of review URLs, a timeline screenshot, and the common signal (same template language, same vertical of competitor reviews, same account creation window). Cluster-framed BRFs in our log removed at a 51% aggregate rate vs 31% for single-review BRFs.
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. Sort by the policy clause being violated. For any review where the in-product flag has already been denied, queue a BRF this week with the screenshot attached. For any review filed in the last 30 days where no flag has been filed, file the in-product flag first and only escalate to BRF if denied. The wrong move is filing 10 BRFs at once on borderline cases; the queue throttles profiles that submit clusters of low-evidence disputes, and quality of submission predicts removal rate more strongly than any other variable in our log.
