Template
Google review policy escalation record template
Keep one dated record for each review report. Copy the exact Google reason and status, preserve links to the evidence, and tie the next action to the status shown in Google's tool. This is your business-owned continuity record. Use Google's own tools for the report and appeal; the record does not promise that a review will be removed.
By Sergey Sulimko, Founder · · 5 Google help pages, read Oct 14 - Oct 28, 2026
| Situation | Jump to the template |
|---|---|
| You are reporting a review that appears to violate a Google policy | Ordinary policy report |
| Google has returned a status or you are using the one-time appeal | Status and appeal update |
| A person demands money, goods or services to remove reviews | Extortion escalation |
When you report a review that appears to violate a Google policy
Google review policy escalation record
Record owner: [business name or responsible team]
Record last updated: [YYYY-MM-DD HH:MM timezone]
Review URL: [direct Google Maps review URL]
Review identifier: [review ID or another identifier, if available]
Observed policy category: [exact Google reason selected or displayed]
Factual basis: [neutral description of the content or conduct that appears to match that category]
Owner-reply decision: [no public reply / reply planned / submitted, awaiting Google review / approved and posted / Google asked for an edit / not applicable]
Reply submitted: [YYYY-MM-DD HH:MM timezone, or not submitted]
Reply status checked: [YYYY-MM-DD HH:MM timezone, or not checked]
Public reply boundary: [Keep the reviewer's private information and personal attacks out of the public reply. If the issue is complex, invite contact through the business's normal private channel.]
Private follow-up record: [service owner; private channel or controlled-record pointer; next action; next date. Keep sensitive customer details in the business-controlled record, not in the public reply or a broadly shared copy of this template.]
Evidence pointer: [screenshot, saved file or controlled record location]
Report route: Business Profile → Read reviews → Report → [exact reason] → Send report
Report submitted: [YYYY-MM-DD HH:MM timezone]
Google status: [exact displayed status, or not checked]
Status checked on: [YYYY-MM-DD HH:MM timezone]
Appeal eligible or used: [not checked / eligible / not eligible / used]
Appeal submitted: [YYYY-MM-DD HH:MM timezone, or not submitted]
Next action: [specific action, owner and date]
Google's documented report route is Business Profile → Read reviews → Report → choose the reason → Send report. Google gives Spam and Profanity as examples, so keep the exact reason selected instead of replacing it with “bad review.”1
Read the full section
Keep the owner-reply fields separate from the policy report fields. Google requires a verified Business Profile before a business can reply and documents the path as Business Profile → Read reviews → Reply → enter the reply → Reply.2 Google reviews replies before posting them, so submitted, awaiting Google review is a different record state from approved and posted.2 Google says replies are public, warns against sharing a reviewer's private information, and recommends private contact when a situation is complex.3 Keep the service owner, private channel or controlled-record pointer, next action and date in the business-controlled record, not in the public reply or a broadly shared copy of this template.
When Google returns a status or you submit the one-time appeal
Google review report follow-up
Review URL: [direct Google Maps review URL]
Original report submitted: [YYYY-MM-DD HH:MM timezone]
Owner-reply decision: [no public reply / reply planned / submitted, awaiting Google review / approved and posted / Google asked for an edit / not applicable]
Reply submitted: [YYYY-MM-DD HH:MM timezone, or not submitted]
Reply status checked: [YYYY-MM-DD HH:MM timezone, or not checked]
Public reply boundary: [Keep the reviewer's private information and personal attacks out of the public reply. If the issue is complex, invite contact through the business's normal private channel.]
Private follow-up record: [service owner; private channel or controlled-record pointer; next action; next date. Keep sensitive customer details in the business-controlled record, not in the public reply or a broadly shared copy of this template.]
Status checked on: [YYYY-MM-DD HH:MM timezone]
Google status, copied exactly: [Decision pending / Report reviewed - no policy violation / Escalated - check your email for updates]
Appeal eligibility shown: [eligible / not eligible / not shown]
Appeal submitted: [YYYY-MM-DD HH:MM timezone, or not submitted]
One-time appeal used: [yes / no]
Evidence or appeal record pointer: [screenshot, saved file or controlled record location]
Next action: [check the Reviews Management Tool / monitor the email named by Google / record the final result, with owner and date]
Record last updated: [YYYY-MM-DD HH:MM timezone]
Google lists Decision pending, Report reviewed - no policy violation, and Escalated - check your email for updates as the possible report states. Review evaluation typically takes several days. If a flagged review does not qualify for removal, Google describes a one-time appeal, with up to 10 reviews selectable in one appeal. A review that complies with Google's policies remains live.1
When a direct extortion demand accompanies the reviews
Google review extortion escalation record
Record owner: [business name or responsible team]
Record last updated: [YYYY-MM-DD HH:MM timezone]
Business Profile URL: [Google Business Profile URL]
Extortion condition observed: [direct demand for money, goods or services in exchange for removing reviews]
Demand first noticed: [YYYY-MM-DD HH:MM timezone]
Communication channel: [email / messaging service / social profile / other]
Sender contact pointer: [controlled pointer to the sender's details]
Evidence pointers: [screenshots or files showing the demand, dates, times and sender details where possible]
Suspicious review URLs: [direct link to each review]
Review surge first noticed: [YYYY-MM-DD HH:MM timezone, if applicable]
Extortion report submitted: [YYYY-MM-DD HH:MM timezone]
Google response or notification status: [awaiting result / result received / exact status from the notification]
Notification pointer: [controlled location of the email or result]
Next action: [specific action, owner and date]
Google's extortion guidance says not to engage with or pay the people making the demand. It asks businesses to gather evidence, include direct links to the suspicious reviews, report relevant communications, and provide the dates and times of the demand and review surge where applicable.4 Use this branch only for a direct demand tied to review removal. For the wider incident sequence, see how to handle a Google review attack or extortion attempt.
What does a filled record look like next to the bare template?
Use only details the business can verify. The example shows the ordinary report template with a factual policy basis, an exact status, and a next action that does not promise removal.
| Bare record | Filled example |
|---|---|
| Review URL: [direct Google Maps review URL] Observed policy category: [exact Google reason selected or displayed] Factual basis: [neutral description of the content or conduct] Report submitted: [YYYY-MM-DD HH:MM timezone] Google status: [exact displayed status, or not checked] Next action: [specific action, owner and date] |
Review URL: https://maps.google.com/[business-review-link] Observed policy category: Rating manipulation Factual basis: The review appears to be part of a coordinated request for specific ratings; screenshots are stored in the incident folder. Report submitted: 2026-10-14 09:20 PT Google status: Decision pending Next action: Taylor will check the Reviews Management Tool after the typical several-day evaluation window and record the displayed status. |
The filled example records an observed basis without treating the category as proven. Google's policy defines rating manipulation as an attempt to influence a place's star rating through fake or misleading content, including soliciting fake reviews, pressuring people for specific ratings, or coordinating campaigns to inflate or deflate a rating.5
How should you use this record without sounding like a template?
- Replace every bracketed field before saving the record. Use the review's direct URL, the exact reason or status Google displayed, and the business's own date and time.
- Keep the factual basis separate from the policy category. Describe what the business observed, then name the Google category that fits those facts.
- Store evidence as pointers to controlled files. Keep the record readable and avoid copying unnecessary private contact details into a shared document.
- Add a next action with an owner and date. For Decision pending, the next action is a later status check. For Escalated - check your email for updates, the next action is to monitor the email Google names and record the final result.
- Update the same record after an appeal or notification. Do not start a second appeal when the one-time appeal has already been used.
For the policy boundary and ordinary reporting route, read how to report a fake or abusive Google review and how to report and remove a Google review. If the issue is how the business solicited reviews rather than the content of one review, read review gating.
What should you not put in an escalation record?
| Do not | Do instead |
|---|---|
| Call a review “bad” and leave the policy basis blank. | Record the exact Google reason, or mark the basis unconfirmed until the facts fit a policy category. |
| Treat a one-star rating, an unfavorable opinion or an ordinary customer dispute as a policy violation. | Separate negative sentiment from conduct or content that matches a Google policy. Google says disagreement alone is not a removal reason.1 |
| Treat a report or appeal as a removal promise. | Record the status Google displays and the next action that status supports. |
| Re-submit a one-time appeal as if it were an unlimited review loop. | Mark whether the one-time appeal was used and keep the final notification with the record.1 |
| Pay or negotiate with someone demanding money, goods or services to remove reviews. | Preserve the demand and evidence, then use Google's extortion route for the direct-demand case.4 |
Maps Agent service
Where your profile stands now
Visibility Score 0-100 · 20 scored factors · free · no signup
- Profile Completeness
- 11 checks · 40% of score
- Performance
- 4 checks · 35% of score
- Competitive Position
- 5 metrics · 25% of score