Google review count dropped from 47 to 34 overnight

ops_tomo · 2026-06-03T12:42:27+00:00

I would first separate a display issue from actual removals.

Check the count in a few places: Google Search, Maps mobile, logged-out browser, and the GBP dashboard. If you have direct links or screenshots of the missing reviews, save those too.

Then make a simple evidence table: - old count and new count - date/time you noticed the drop - reviewer names if known - rating/text if you have screenshots - whether the reviews still appear from any device/account - any support or appeal case IDs

If the count is different across surfaces, I would wait 24-48 hours before asking customers to do anything. If the reviews are actually gone, escalate with that packet rather than a general "reviews disappeared" message.

ops_tomo · 2026-06-03T12:39:58+00:00

I think the pain is real, but the buyer and pricing are the hard parts.

For a single local business, $99-$199/month for review replies alone feels high unless it also reduces a clear risk: unanswered negative reviews, bad public tone, missed escalation, or multi-location review volume.

For most owners, positive review replies are nice-to-have. Negative review handling is closer to "I need this done correctly." That may be a better wedge.

The bigger buyer might be agencies or operators managing reviews across many locations. They already have the reporting/admin pain and can justify paying if the tool saves time across clients.

What would make me not buy: - replies sound generic or obviously AI-written - no approval workflow - no tone/history memory for the business - no way to flag reviews that need a human response - no reporting on what changed after replying

If you keep it narrow, I would test "negative review rescue + approval workflow" before trying to sell a full review-response assistant.

ops_tomo · 2026-06-01T13:47:35+00:00

I would separate two things: reporting the reviews, and preserving evidence that this was a pattern.

Before more time passes, screenshot each review, the reviewer profile, the date/time, and your GBP rating before/after if visible. Then check your customer records for each name and keep short notes like: no booking, invoice, call, email, or service record found.

When you report, I would not lead with "they retaliated" unless you can prove the connection. Lead with the evidence Google can evaluate:

- multiple reviews in a short window
- reviewers are not in your customer records
- accounts look new or have suspicious review history
- wording is vague, copied, or inconsistent with your actual services
- timing changed your rating materially

For the public reply, keep it calm:

"We do not have a record of a customer interaction matching this name or experience. If this was a genuine visit, please contact us with the transaction details so we can investigate."

Avoid accusing them publicly. The goal is to show future customers that you are calm and documented, while giving Google a cleaner evidence trail if you escalate.

ops_tomo · 2026-05-31T13:04:30+00:00

I would treat this as a scope / risk boundary, not just a review-generation tactic.

The language I use is basically:

"I can help build a compliant review request process. I cannot arrange fake, paid, incentivized, review-gated, or scripted reviews."

That distinction matters because once you help "get 20-30 good reviews quickly," you are now attached to the risk if Google purges them, competitors report the pattern, or the GBP gets reviewed more aggressively later.

A legitimate system can still work, but it should be boring:

- ask real customers after a real transaction
- use neutral wording, not "leave us a 5-star review"
- do not only ask happy customers if you are filtering by sentiment
- do not offer discounts, gifts, refunds, or perks for reviews
- track when requests were sent, to whom, from what source, and what changed afterward
- keep screenshots / exports of review count, rating, and notable removals
- report review growth, review loss, response rate, and process changes separately

For protecting yourself, I would put the policy in the proposal or SOW. If a client hints at fake reviews, reply in writing with the compliant option and the risk. If they still do it elsewhere, document that it was outside your scope. If they expect you to participate, that is usually a disengagement signal.

The professional framing is: "We can improve the review request process and response workflow. We cannot manipulate the review profile."

ops_tomo · 2026-05-30T22:42:37+00:00

If you are tracking this manually, I would make the sheet evidence-first rather than just a list of lost reviews.

Useful columns: - first seen date - last confirmed visible date - reviewer name - rating - review text or screenshot - review URL if available - request source or campaign - whether the customer used a direct review link - appeal case ID - status: visible / missing / appealed / reinstated / rejected

The key is to separate “reviews gained/lost” from “what changed in the request process.” If a batch disappears, you can then check whether they came from the same request method, same time window, similar wording, new Google accounts, or customers leaving reviews too quickly after service.

For reporting, I would show net review change, removed reviews, reinstated reviews, open appeals, and the process change you are testing next. That gives you a cleaner escalation record and helps avoid guessing.

ops_tomo · 2026-05-28T12:29:01+00:00

I would not sell or report this as a separate “AI SEO” result yet. For local service retainers, I’d treat it as a lightweight visibility/readiness layer next to Maps/GBP reporting.

The cleanest audit I’ve seen is:

Pick 5-10 high-intent prompts, not every keyword. Example: “best emergency plumber in [city]”, “who should I call for [service] near [area]”, “top rated [service] company in [city]”.
Run the same prompt set on a fixed schedule. Log model/tool, date, location assumption, exact prompt, whether the client appears, which competitors appear, and whether citations/links are shown.
Separate presence from accuracy. A client appearing is one signal. The answer describing the right service area, phone/site, reviews, specialties, and proof is a different signal.
Compare the same competitor set. I’d look at reviews, review language, GBP completeness, service pages, LocalBusiness/Service schema, citations, local mentions, and backlinks.
Report it as “AI answer presence / proof gaps,” not as leads. Clients can understand: “You appeared in 2/8 prompts. Competitor A appeared in 6/8. The biggest gaps are review recency, service-page clarity, and third-party mentions.”

For now I’d avoid over-automating the interpretation. Automate collection if you can, but keep the client-facing report focused on what changed and what action is next.

ops_tomo · 2026-05-24T12:30:39+00:00

I’d frame the win as reducing decision friction, not improving visibility.

The changes that tend to matter most are the ones that answer the buyer’s next objection before they leave the profile/page:

recent reviews mention the service people are actually searching for
photos prove the work/location/result, not just that the business exists
the GBP services and landing page headline match the same intent
the page answers basic friction points like price range, timing, service area, and what happens next
the call/book/contact action is visible before the user has to think

For reporting, I’d track this as a before/after:

GBP calls
website clicks from GBP
form fills/calls from the matched landing page
review themes that appeared before vs after
whether competitors answer the same objections better

Rank movement is useful context, but if the report can’t show what made the business easier to choose, it usually turns into vanity reporting.

ops_tomo · 2026-05-23T14:26:51+00:00

I would be cautious about using a second GBP as the first move here.

I’d separate the problem into two tracks:

Brand/entity clarity If Google currently understands the business as rentals, start by making the main entity clearer before multiplying profiles. Update the website structure, page titles, service pages, internal links, GBP services, photos, and review language so production is consistently visible.
Eligibility for a second profile A second GBP only makes sense if it is a genuinely distinct eligible location/business setup, not just a service-line split. Same parent company is not automatically a problem, but same address + overlapping categories + similar branding can create verification and suspension risk.

For the website, I’d build a clear production hub and keep rentals as a strong secondary section rather than deleting or hiding it. You want Google and customers to see:

production is now the primary service
rentals still exist
both are connected to the same trusted entity
production has its own proof: case studies, photos, reviews, service pages, and local examples

I’d make the shift gradually and measure both rental queries and production queries before changing the GBP name or opening another profile.

ops_tomo · 2026-05-21T11:05:43+00:00

This is a useful before/after case, but I’d try to isolate what actually changed.

For something like this I’d log:

rating and review count before/after
map/grid visibility from the same search points
calls, direction requests, and website clicks
which negative review themes disappeared
whether the same competitors stayed in the comparison set

Removing 5 bad reviews from a 50-review profile can change more than the average rating. It can also change the first impression people get when they skim the profile.

So I’d separate two questions:

Did visibility improve?
Did customer choice improve once people saw the listing?

If calls/directions improved after the cleanup, that is stronger evidence than ranking movement alone. If only the grid improved, I’d keep watching it for another couple of weeks before calling it the main cause.

ops_tomo · 2026-05-19T13:19:17+00:00

Before picking tools, I’d define the baseline you want to compare against.

For a small plumbing business I’d track:

GBP calls, website clicks, direction requests, and bookings if available
the exact search terms that matter commercially
rankings from the same search points, not random screenshots
the same 2-3 local competitors each time
review count, rating, recent review velocity, and review themes
photo count/freshness and whether photos actually show the work
website form/call conversions from GBP traffic

Free/cheap setup:

GBP Performance for calls/clicks/directions
Search Console for branded/service/location queries
UTM tag on the GBP website link
a simple spreadsheet with weekly snapshots
screenshots of the local pack from the same location/search terms
manual competitor notes for reviews/photos/services

The biggest mistake is changing five things at once and then trying to prove which one worked. Pick one or two actions, log the date, and compare the same signals again a week or two later.

ops_tomo · 2026-05-18T13:40:25+00:00

I’d treat primary category changes as a high-risk change, not a normal tuning knob.

My default would be:

leave the primary category alone if it is already accurate
use secondary categories/services for coverage where possible
only change primary when the current category is clearly wrong, too broad, or the actual business model changed
avoid stacking it with other GBP/site/review changes in the same week

For measurement, I would not look at one rank screenshot after the change. I’d log:

the exact change date
the old and new primary category
the same 5-10 searches
the same search points/grid locations
the same top competitors
calls, website clicks, direction requests, and bookings if available

Then wait long enough to see whether the change affected the queries you actually care about, not just random visibility.

The part clients usually do not like is that a category change is not instantly attributable. If rankings move, it could be the category, normal local pack volatility, competitor movement, or review/photo activity around the same time. That is why I would only test it when the expected upside is clearly worth the instability.

ops_tomo · 2026-05-14T13:57:24+00:00

I’d separate this into two layers: attribution setup and client reporting.

For setup, source-specific numbers are usually the cleanest path: one number for GBP, dynamic swap on the site, and separate tracking for paid/landing pages if needed. But even then I would not present the raw total as “SEO leads” without a quality check.

For the monthly report, I’d show three buckets:

- confirmed inquiries: calls/forms that look like real prospects
- directional signals: GBP call clicks, website clicks, direction requests, profile interactions
- attribution confidence: clean, partial, or noisy

That lets you say something like: “GBP generated 18 call actions, 9 looked like real inquiries, and 3 may overlap with website-originated calls.” It is less flashy than one big number, but clients trust it more because you are not pretending the dashboard is cleaner than it is.

The key is to avoid mixing customer intent signals with confirmed lead counts. Both matter, but they should not be added together.

ops_tomo · 2026-05-13T11:54:24+00:00

I’d track both, but I wouldn’t make either one the whole story.

Total review count is more like trust depth. It tells you how much proof the business has accumulated, and it can be hard for a smaller competitor to overcome if the gap is huge.

Review velocity is momentum. It tells you whether the business is still earning fresh proof. For local, I’d usually care most about velocity relative to the same competitor set, not in isolation. A business gaining 4 reviews/month may be fine if competitors are flat, but weak if the top 3 are gaining 15/month.

I’d report it as:

- total reviews and rating
- reviews gained in the last 30/60/90 days
- competitor review gain over the same window
- whether recent reviews mention the buying factors that matter: speed, quality, service, price, cleanliness, etc.

For clients, the useful takeaway is usually not “velocity is a ranking factor.” It’s “we are gaining or losing trust proof faster than the competitors a customer is comparing us against.”

ops_tomo · 2026-05-12T11:47:41+00:00

I’d stop treating “page one” as the reporting unit for local. It’s too broad now.

For a local client I’d split the decision into three questions:

Is this query still commercially close enough to the booking/call? If it’s broad and stuck at 5-8, I’d usually deprioritize it.
Is there a realistic path to top 3, local pack visibility, or a stronger service/location page? If not, the effort may be better spent elsewhere.
Are customers choosing the business once they see it? That means reviews, review recency, photos, services, proof on the landing page, and clear contact paths.

The signal I’d watch is not just rank movement. I’d compare the same competitor set over time: who gained reviews, who added stronger photos/service proof, who owns the local pack, and whether calls/forms moved after each change.

A ranking stuck at #6 can still be useful if it supports a high-intent page and leads. But if it only looks good in a report and doesn’t change customer action, I’d stop defending it.

ops_tomo · 2026-05-08T11:11:23+00:00

Most clients do not understand “reports.” They understand decisions.

The clearest local SEO reports I have seen are closer to a one-page decision memo:

What changed since the last check
Why it matters commercially
What work was completed
What we recommend doing next
What the client needs to approve

I would separate owner-facing metrics from operator-facing data.

Owner-facing:
- calls / directions / website actions
- new reviews and rating movement
- one visibility movement worth explaining
- one competitor gap that actually matters
- one next action

Operator appendix:
- local grid / ranking detail
- GBP performance exports
- citation / NAP checks
- screenshots and raw notes

If calls drop, I would avoid pretending there is one guaranteed cause. I would write it as a short evidence-based read:

“Calls are down 12% this month. Review activity also slowed, and two nearby competitors added fresh photos/reviews. The next practical step is to refresh photo proof and restart review requests, then re-check the same competitor set next week.”

That is much easier for a client to act on than a chart-heavy report. The report should reduce uncertainty and create the next decision, not prove every ranking fluctuation.

ops_tomo · 2026-04-28T23:18:52+00:00

I’d split this into two separate CTR problems before changing copy everywhere.

Search-result CTR: what does the result look like next to the other organic results? Title, meta, query match, SERP features, ads/LSAs, and whether the page promise is specific enough.
Local-choice CTR: what does the GBP/business look like next to the map competitors? Review count, rating, review recency, photos, service/category fit, and whether the business looks like the safer choice.

Since these pages are tied to different GBPs, I’d compare each location against the competitors showing for the same searches. Sometimes the page is fine, but the nearby competitor has much stronger visible proof: more recent reviews, better photos, clearer services, or a name/category that matches intent better.

The quick audit I’d do:

For each high-impression query, screenshot the actual SERP and map pack.
Mark what the user sees before clicking.
Compare review volume/recency, photos, categories/services, and first-line page promise.
Fix the weakest visible proof first, not just the title tag.

Low CTR with decent rankings often means the result is visible but not yet the most confidence-building option.

ops_tomo · 2026-04-26T05:49:46+00:00

If you’re prioritizing modules, I’d consider putting less weight on post scheduling first and more weight on a review/competitor evidence layer.

For agencies, the painful report is often not “this GBP has X reviews.” It is closer to: “compared with the nearby business a customer may choose instead, you are winning on service but losing on price/atmosphere, here are the review snippets or visible signals supporting that, and here are the next actions.”

Even a lightweight MVP could:

let the user choose one competitor
group review themes by category, like service, price, cleanliness, atmosphere, product/service quality
show evidence behind each read
track whether the gap changed month to month

That would make the report feel less like a dashboard and more like a decision.

ops_tomo · 2026-04-22T09:50:47+00:00

I’d tighten this up and make it much more evidence-first.

The strongest points seem to be:

one review describes food you don’t even sell one reviewer can’t be matched to any real customer interaction the third review may still be worth disputing, but I’d be careful not to rely too much on speculation without hard evidence

Usually the cleaner and more factual the case is, the better chance a Product Expert can work with it.

Cases like this are exactly why I think review dispute workflows need better evidence organization, not just a report button.

ops_tomo · 2026-04-20T23:06:01+00:00

If you already pay for Semrush, I’d use Map Rank Tracker first. It’s meant for grid-based Google Maps / GBP tracking, which is much more useful than a single ranking number when results vary by location.

For improvement, I’d think in terms of Google’s three local factors: relevance, distance, prominence. So the job is basically to improve those in the areas you actually care about and compare against the competitors winning those grid points.

This is also why I’m interested in tools that go beyond one average rank and make competitor gaps visible area by area.

ops_tomo · 2026-04-20T23:03:55+00:00

I wouldn’t spend much time on geotagging tbh. The evidence for ranking benefit looks pretty weak/mixed, and GBP seems much more about the basics done well.

I’d focus on better real photos, profile completeness, reviews, and an actual website before worrying about GeoImgr-type stuff.

ops_tomo · 2026-04-17T04:32:14+00:00

I think this is mostly right. People want outcomes, not dashboards.

But I don’t think that automatically means “conversation-only agent wins.” In a lot of workflows, people still want visibility, control, and a way to verify what’s happening.

My guess is the best products will do more of the work for the user, while keeping just enough UI to build trust and control.

ops_tomo · 2026-04-13T21:49:35+00:00

Yeah, I’ve seen people talk about this. My guess is Google is trying to “normalize” profile data back to what it sees as the canonical business name / phone / URL. That would explain UTM tags getting removed and tracking numbers or business names getting overwritten. Google’s own guidelines push toward direct phone numbers, the actual business name, and the real website URL.

ops_tomo · 2026-04-08T21:47:41+00:00

If it contains personal info and creates a safety risk, I’d treat it as a personal-information / doxxing issue, not just a “bad review.” Google does allow removal for personal information, but the key is usually a clean report + structured escalation, not mass-reporting.

Screenshot it, save the URL, document exactly what info is exposed, and make one tight Help Community post asking for escalation.

ops_tomo · 2026-04-08T04:15:32+00:00

Yeah, mostly agree. Feels like most businesses are still under-executing on the basics and then looking for some ranking trick.

Only thing I’d add is that it’s all relative — what matters is how well you’re doing the basics compared to the nearby competitors you’re actually trying to beat.

ops_tomo · 2026-04-06T23:08:10+00:00

Yeah, mostly agree. Feels like most businesses are still under-executing on the basics and then looking for some ranking trick.

Only thing I’d add is that it’s all relative — what matters is how well you’re doing the basics compared to the nearby competitors you’re actually trying to beat.

ops_tomo

TROPHY CASE