Case studiesContact

Google Business Profile

Google Business Profile reviews missing or not showing

A diagnostic checklist for delayed, filtered, merged, or disappeared Google reviews, including profile history, review-level evidence, reinstatement effects, and support-ready incident logging.

Do not want to work through every Google Business Profile check yourself? Send the current URL, screenshots, and timeline. We can run the buyer-controlled diagnosis and return a fixed-scope missing-review incident pack.

Define what is actually missing

A single new review that has not appeared is different from dozens disappearing after a merge, move, or reinstatement. Establish the count, period, and triggering profile event before asking for recovery.

  • Record the visible count on Search and Maps.
  • Separate never-published reviews from previously visible reviews.
  • Use customer evidence only with permission and redaction.

Check profile-level events

Merged profiles, reinstatement, category restrictions, duplicate listings, and ownership changes can affect how reviews appear. The incident log ties the review loss to the profile history without assuming causation.

  • Map old and current profile URLs.
  • Record merge or reinstatement dates.
  • Check whether reviews are limited for the business category.

Prepare a privacy-safe support case

Support needs a reproducible pattern, not a public list of customer identities. Use dates, counts, redacted screenshots, and a small sample of review references to describe the loss.

  • Do not incentivize replacement reviews.
  • Do not promise restoration of policy-removed content.
  • Keep the request focused on authentic reviews and profile history.
Technical troubleshooting checklist

Work through the evidence in a controlled order.

Each check defines what a healthy result looks like, what to do when it fails, and what evidence to preserve before the next change.

01

Incident classification

Determine whether the case is delay, individual filtering, or a profile-level event.

  1. Compare the review count and visible list in signed-out Google Search and Maps views.
    Healthy result
    Counts and visible reviews agree or the difference is explained by surface refresh timing.
    If it fails
    Record both surfaces, locale, device, and time before concluding reviews are gone.
    Save as evidence
    Dated Search and Maps screenshots with profile URL.
  2. Separate reviews that never appeared from reviews that were previously visible.
    Healthy result
    Each sample has an approximate post date and known prior visibility state.
    If it fails
    Ask for a small, permissioned sample instead of contacting every customer.
    Save as evidence
    Anonymized review reference, date, rating, and prior-state note.
  3. Check for recent merge, move, reinstatement, ownership, name, or category events.
    Healthy result
    The profile event timeline is complete for the period around the loss.
    If it fails
    Recover old profile IDs, support emails, and merge dates before filing a vague report.
    Save as evidence
    Event timeline and old/current Maps URLs.
  4. Check whether the category or location is subject to user-generated-content restrictions.
    Healthy result
    The category is eligible for reviews and no restriction notice explains the change.
    If it fails
    Use the category-specific policy path; do not ask customers to evade restrictions.
    Save as evidence
    Primary category, restriction notice, and official policy reference.
02

Recovery packet

Build a compact, respectful case that demonstrates the pattern without publishing customer identities.

  1. Create a sample table of missing reviews using redacted customer evidence.
    Healthy result
    The sample shows dates and prior visibility without unnecessary names, emails, or order details.
    If it fails
    Redact further and obtain permission before including customer-provided material.
    Save as evidence
    Five-to-ten-row review evidence table.
  2. Rule out duplicate-profile review distribution.
    Healthy result
    Reviews are not sitting on a former or duplicate profile.
    If it fails
    Document the duplicate and use the merge or ownership route before requesting review restoration.
    Save as evidence
    Duplicate URLs, counts, and relationship to current location.
  3. Write the request around the profile event and authentic-review pattern.
    Healthy result
    The request states what disappeared, when, the relevant profile event, and what evidence is attached.
    If it fails
    Remove speculation about competitors or algorithms unless supported by evidence.
    Save as evidence
    Support request draft and attachment index.
  4. Track the support response and visible counts after each material update.
    Healthy result
    The case log preserves the decision and before/after result.
    If it fails
    Reply with the smallest missing fact requested; avoid opening parallel cases.
    Save as evidence
    Case ID, email thread, count snapshots, and resolution note.
Frequently asked questions

Questions that change the next step.

Why can a real review be delayed?

Google says reviews are checked for policy compliance and may take several days. A delay is not proof that the review was deleted.

Can policy-removed reviews be restored?

Google states that reviews removed for policy violations are not restored. A recovery case is strongest when it documents authentic reviews affected by a profile event or mistaken automated removal.

Should customers post the same review again?

Do not coordinate duplicate reposting. First determine whether the original is delayed, filtered, attached to another profile, or affected by a profile-level event.

What could happen next

A first pass can remain a compact artifact, or expand into a new clearly priced scope with long-term support when the work needs upkeep, rollout help, or follow-up checks.

  • Profile merge and history mapping
  • Privacy-safe support submission
  • Decision-led evidence follow-up
CSV evidence tracker

Sample missing-review incident log

A realistic privacy-safe tracker for review samples, profile events, visible counts, support receipts, and current status.

  • Review-level evidence without customer PII
  • Profile event chronology
  • Support and count tracking
CSV fileMissing-review incident tracker

A spreadsheet-ready sample with realistic status and evidence fields.

These examples are anonymized. Names, domains, emails, private screenshots, exact products, and private commercial details are removed or generalized.

Contact

Still stuck with Google Business Profile?

For a small fixed fee, we can take over the evidence review, controllable corrections, validation, and one clearly bounded support handoff. Platform approval is never guaranteed.

Get Google Business Profile help