Your Google Business Profile review count dropped. A few five-star reviews vanished, the average changed, or the numbers in your report no longer match the live listing. The wrong response is to rush out and replace the missing reviews before you know what happened.
Your first job is to separate an isolated disappearance from a repeatable moderation pattern. Once you can see which ratings, review ages, locations, and acquisition methods are involved, you can protect your local SEO reporting and correct the part of your review process that may be creating risk.
Key takeaways
- Five-star reviews are not protected from removal. Positive reviews can receive especially close scrutiny in some industries and markets.
- Do not assume only new reviews are at risk. Google can remove reviews months after publication, including older feedback that once appeared stable.
- Track displayed review count, average rating, individual disappearances, and review age by location. A stable rounded average does not prove that nothing was deleted.
- Pause incentives and audit how reviews are requested before launching a replacement campaign. More requests will not fix a collection process that keeps producing moderation risk.
A deleted review is not the same as a local ranking penalty
A review can disappear at the same time that local visibility changes, but that timing does not prove Google applied a manual penalty to the business. The immediate effects are narrower and easier to verify: the public review count changes, the displayed average may move, recent feedback may become thinner, and your historical reports stop matching the live profile.
Those changes still matter. Customers see a different reputation profile, while your SEO team may compare current performance with a review set that no longer exists. An analysis of 60,000 Google Business Profiles between January and July 2025 found that removals were becoming more common, with momentum increasing near the end of the first quarter. The pattern included five-star feedback, not just critical reviews.
Start with the arithmetic. If the count falls and the average falls, the removed set probably had a positive net effect on the rating. If the count falls and the average rises, lower-rated feedback was probably removed. If the count falls while the average appears unchanged, the missing reviews may be mixed, too small to change the rounded display, or offset by new reviews. These are diagnostic clues, not proof about any individual review.
Keep local visibility in a separate column from review movement. Annotate the date of a confirmed count change, but do not attribute every ranking fluctuation to it. Profile edits, competitor activity, demand, and other search changes can occur during the same period. Your review log should help you investigate correlation without turning it into an unsupported causal claim.
Use industry and location patterns to focus the audit
Your business category changes where you should look first. It does not determine why a particular review disappeared, but it can keep you from auditing the wrong slice of data. The observed deletion patterns differ by rating, age, sector, and country.
| Business context | Observed deletion pattern | What to inspect first |
|---|---|---|
| Restaurants | Highest deletion activity among the sectors examined, with removals across star ratings | All ratings and both recent and older review cohorts |
| Home services | Greater scrutiny of five-star feedback, with many removals occurring within six months | Recent five-star reviews and the request method that generated them |
| Medical businesses | Fewer deletions than the highest-incidence sectors, but a noticeable bias toward five-star removals | Positive reviews from the previous six months and any coordinated solicitation campaign |
| Retail | Relatively high deletion activity, including older reviews | Historical cohorts as well as current acquisition |
| Construction | Among the sectors experiencing more deletion activity | The full review history until a location-specific pattern emerges |
Do not combine every location into one company-wide total. A restaurant group, home-services network, or retailer can gain reviews overall while individual profiles lose them. Keep one record per Business Profile, then compare locations using the same fields and checking schedule.
Country-level differences also deserve their own view. Five-star reviews have faced more scrutiny in many English-speaking markets, while low-rated reviews in Germany have been removed more often soon after publication. The German pattern aligns with stronger legal pressure around defamation, whereas automated moderation appears more prominent in English-speaking markets. If a German review is connected to a legal complaint or threat, preserve the relevant records and obtain advice from qualified local counsel before treating the situation as a routine SEO issue.
Build a review log that exposes removals instead of hiding them
A displayed review count is a balance, not an acquisition total. If five new reviews appear while five older ones disappear, the count looks flat even though both customer activity and moderation occurred. You need a simple cohort log to see that movement.
- Create a baseline for every profile. Record the check date, displayed review count, displayed average rating, and the newest visible reviews. Keep each location separate.
- Check on the same day each week. Weekly monitoring is granular enough to catch the deletion activity that has been appearing across many profiles without confusing a long period of gains and losses.
- Record newly visible and newly missing reviews. For each one, note the star rating and whether it was posted within the previous six months or belongs to an older cohort. Those two age groups are useful because recent removals are more prominent in medical and home services, while older removals appear more often in restaurants and retail.
- Attach acquisition context. Note the date, channel, location, campaign, and whether any benefit was connected to the request. Include requests handled by staff, software, agencies, receipts, email, or in-location prompts.
- Estimate removal volume. Subtract the net change in displayed review count from the number of newly observed reviews. Treat the result as an estimate when your checks may have missed reviews that appeared and disappeared between observations.
- Annotate SEO performance separately. Record local visibility or conversion changes beside the deletion event, but preserve the distinction between events that occurred together and events you can show were causally connected.
The useful unit is the review cohort: feedback acquired through the same location, channel, and time period. If one cohort loses a disproportionate share of its five-star reviews while organically acquired feedback remains visible, you have a much sharper lead than a company-wide count decline.
You can also track a survival measure for each cohort: the number of originally observed reviews that remain visible after six months divided by the number originally observed. Keep acquisition and survival as separate metrics. One tells you whether customers are responding; the other tells you whether those reviews persist.
A single missing review rarely reveals the cause. It may reflect moderation or another change outside the business’s control. A cluster tied to one campaign, request channel, rating, or location is more actionable because it gives you a process to inspect.
Fix the acquisition process before replacing lost reviews
Google has increased enforcement against incentivized feedback, and automated systems are being used to identify suspicious activity. If a customer received a discount, free item, entry into a drawing, or another benefit for leaving a review, stop that workflow while you assess it. Do not assume that calling the benefit a thank-you removes the moderation risk.
Map each missing cohort back to the way the request was made. Review the audience, timing, wording, channel, and responsible vendor or team. If removals cluster around one method, pause that method instead of sending a larger campaign to compensate for the loss. A replacement burst can add more questionable activity before you have removed the original cause.
A lower-risk process is straightforward: connect the request to a real customer interaction, use neutral language, offer no benefit for posting, and let the customer write in their own words. Build review requests into an ordinary operating workflow so you are not dependent on occasional pushes designed to hit a target number.
If an agency or software provider manages acquisition, require a clear description of its methods. Your internal record should show which customers were contacted, when the request was sent, which channel was used, and whether the provider attached any incentive. A promise to deliver a certain number of positive reviews is not a substitute for that process evidence.
Do not focus only on the total count. Recent, detailed reviews remain important authority signals, while older feedback can still be re-evaluated and removed later. Your working dashboard should therefore show reviews received, reviews still visible, removals by star rating, removals by age, and removals by acquisition channel.
At your next weekly check, establish the baseline before asking for anything new. Then trace every active request path and remove any attached benefit. You cannot control every moderation decision, but you can make review losses measurable, keep your reporting honest, and build an acquisition process that does not depend on reviews Google may later remove.
References
Leave a Reply