For a missing Google review, first record what is visible and check Google’s current guidance. Google's guidance on missing or delayed reviews (Google Support) says reviews can be delayed while they are checked, that profile merges can also delay them, that reviews removed for policy reasons are not restored, and that if reviews disappear after a reinstatement Google directs businesses to support. These possibilities do not let you identify a specific cause from absence alone.
When you spot a review that clearly breaks the rules rather than merely a missing one, use this walkthrough on how to report a Google review that violates policy to gather evidence and file it properly.
That last point shapes everything below. You cannot diagnose from absence alone, so this guide is about building evidence and choosing a proportionate next action, not about assigning blame to a customer, a reviewer, or the platform. A missing review is one where you know a customer submitted it, yet it does not appear on your profile. This guide is about review visibility only, so if the real gap is an inquiry you never received or work that was never booked, that belongs in a different workflow.
Log what you can observe
Use this as an evidence log rather than a diagnosis. Each row is a question worth checking, an observation to write down, and a possible next action. Treat every row as open: more than one explanation can fit the same evidence, so note what you see before deciding what it means.
| Question to check | Observed evidence to record | Possible next action |
|---|---|---|
| When was it submitted, and how long ago? | Date and approximate time from the customer | Note the elapsed time and re-check later (Google Support) |
| Was the profile merged recently? | Merge date and which profile now displays publicly | Record which profile customers land on (Google Support) |
| Did anything happen around a reinstatement? | Suspension and reinstatement dates, if any | Contact support with the reinstatement context (Google Support) |
| Was the review removed for a policy reason? | Reviewer wording or a notice you received | Note that removed reviews are not restored (Google Support) |
| Can anyone see it outside your own view? | What a signed-out browser shows on a second device | Log both observations side by side |
| Do other reviews show the same pattern? | Whether other recent reviews appear, vanished, or held steady | Include the pattern in whatever you do next |
Read the log as a whole, not row by row. One matching row is a prompt to gather more, not a conclusion. If several reviews vanished in the same week, that pattern is worth recording even when you cannot yet explain it.
One log entry per review
Keep a single entry per review so you can tell one delayed item from several at once. Practical fields:
- [ ] Customer name or initials, only as much as is needed to identify the review
- [ ] Date and approximate time the customer says they submitted it
- [ ] Review text, or a screenshot the customer has agreed to share
- [ ] Your profile name and the public URL customers use
- [ ] What a signed-out browser shows, and on which device
- [ ] Whether merges, suspension, or reinstatement happened near that date
- [ ] Whether other reviews appeared, vanished, or stayed the same that week
- [ ] The date you first noticed the gap, and the date of any contact with support
Ask the customer for permission before you collect or forward a screenshot, and leave out contact details or personal information that support does not need. Keeping each line checkable is the point: "submitted Tuesday, not in the public view on Friday" can be verified, while "Google is hiding us" cannot.
Optional suggested support message format
Once an entry is complete, you may use this suggested format. It is a starting point, not a required form, and adapt or drop any line that does not apply to your situation.
My business profile is [profile name] at [public URL]. A customer reports a review submitted on [date]. As of [date], it does not appear in the public view. The profile was [merged / reinstated / neither] on [date]. Other reviews that week: [what you observed]. Supporting details are available on request.
If your profile was suspended and reinstated, Google Business Profile suspension covers the reinstatement context worth including so support has the full picture.
What a log lets you decide
A written record turns a vague worry into something a third party can check. It also tells you which next action is proportionate: keep observing while timing is short, confirm which profile is live after a merge, move on when a review was removed under policy, or contact support when reviews disappeared after reinstatement. Google’s guidance directs businesses to support in that reinstatement case. A log helps you describe the observations without inventing a cause.
Profile hygiene is worth confirming while you are in here, though it is not by itself an explanation for a single missing review. Our Local SEO for Small Businesses checklist walks through the profile fields most businesses benefit from re-checking.
Keep recovery work separate from asking for new reviews. For separate, neutral requests for new reviews, use How to Ask for Google Reviews: Copyable Messages for fresh requests, which is a different task with its own timing.
Missing-review questions
How long should I wait before assuming something broke?
Give a recent submission some time. Google notes that reviews can be delayed while they are checked. This article does not promise a resolution deadline. Re-check from a signed-out browser after that, and update your log with what you see (Google Support).
Why might a review appear for the customer but not for me?
Several explanations can fit, including display differences and an actual gap. Check from a logged-out window on a second device and record both observations in your log. Do not record the review as missing on one view alone.
Is there a limit to how many reviews a profile can hold?
The cited missing-review guidance does not identify a numerical review cap as an explanation. If reviews go missing in batches, note the pattern and whether a merge or reinstatement happened nearby, then take that pattern to support rather than trying to fit it to a single review (Google Support).
Should the customer post again while I wait?
Do not present reposting as a reliable fix. Keep the original submission and current visibility observations in the same record. For neutral review-request wording, use How to Ask for Google Reviews: Copyable Messages when you are ready to make new requests.
Investigate the visibility issue before changing your customer-acquisition plan. Bring your evidence log and profile details into a preliminary strategy so you can separate the support problem from ongoing marketing work.
Free SEO, GEO and SMM strategy, explained with examples of potential customers.