Google Maps Branch Reputation Drift

Multi-location reputation monitoring that spots which of your Google Maps branches lost rating or are gaining reviews unusually fast since the last check — without paying to scrape review text.

Multi-location reputation monitoring on Google Maps

One evidence-backed drift row per flagged branch, plus a per-branch summary every run. The Actor snapshots each branch's rating and review count, compares every scheduled run against it, and flags only the branches that crossed your threshold — a cheap weekly triage that tells you which branch to look at.

When an MCP agent should use this

• "Which of my branches lost rating since last check?"
• "Flag branches gaining reviews unusually fast."
• "Cheap way to see which locations are slipping on Google."
• "Watch all my branches for rating drops weekly."

When to use something else

You want	Use instead
To read the actual new bad reviews / draft replies	Google Maps Negative Review AI Monitor
To know why a rating dropped (review text, themes)	Google Maps Negative Review AI Monitor
Changes to your listing's address/hours/category	Google Maps Listing Edit Alerts
Competitors' rating/review movement	Google Maps Competitor Momentum Watch
A one-off pull of rating + review count	a raw Google Maps places scraper

How it works

1. Collect — fetches each branch's listing in rich mode (rating + review count), with a trusted fallback.
2. Snapshot & diff — compares against your saved baseline for this monitorId.
3. Threshold — flags a branch only if its rating fell by ratingDropThreshold or it gained reviewSurgeThreshold reviews since the last check.
4. Emit — writes export-ready rows (JSON / CSV / XLSX) and updates the snapshot.

Inputs

Field	Required	Example
locationUrls	yes	["https://www.google.com/maps/place/..."]
monitorId	yes	"acme-all-branches"
mode	no	"check_for_changes" (default) or "reset_baseline"
ratingDropThreshold	no	0.2 (default)
reviewSurgeThreshold	no	5 (default)

Example output

{
  "recordType": "branch_drift_alert",
  "monitorId": "acme-all-branches",
  "placeId": "ChIJ...",
  "businessName": "Acme Cafe - Dallas",
  "driftFlag": "rating_drop",
  "ratingDelta": -0.3,
  "reviewsCountDelta": 12,
  "currentRating": 4.1,
  "currentReviewsCount": 486,
  "windowSinceLastCheck": "since 2026-05-26",
  "evidence": ["Rating fell from 4.4 to 4.1 (>= 0.2 threshold)"],
  "sourceUrls": ["https://www.google.com/maps/place/..."],
  "snapshotDate": "2026-06-02T08:10:00Z"
}

Modes

• check_for_changes (default) — compare against the baseline and return which branches drifted. Auto-creates the baseline on the first run, so use this almost every time.
• reset_baseline — save a fresh starting point and report nothing. Use only to re-baseline after you intentionally changed your branches.

Billing

Event	Price	When
location-checked	$0.012	One branch snapshotted or checked (both modes).

No per-flag charge — a flagged branch and a stable branch both cost one location check.

FAQ

Is this online reputation management software?

It's the monitoring and alerting layer of reputation management — it flags which branch lost rating or is gaining reviews fast. It doesn't respond to reviews or manage your profiles; it tells you where to look, cheaply.

How is it different from a reputation monitoring tool that reads reviews?

It deliberately skips review-text scraping to stay cheap. You get rating and review-count drift per branch — the "which branch" triage — then open the review monitor for the "why".

Is it built for multi-location or franchise teams?

Yes — multi-location reputation monitoring is the core use case. One monitorId covers a whole branch portfolio for franchise ops, regional managers, and multi-location SEO.

Limits & support

• Reads rating and review count only — not review text. It flags which branch drifted; open the review monitor to see why.
• "Unusually fast" is measured against your last check — schedule sets the window.
• The first run on a new monitorId is a baseline; drift flags begin on the next run.
• A failed fetch is reported clearly, never silently treated as "stable".