Quick answer
Google reviews disappeared after merge because Google usually has to reassign review data between duplicate Business Profile records, old CIDs, and map entities before the surviving listing shows the full count again. Some reviews come back on their own within a few days, but a missing count that still has not corrected after about 3 to 7 business days often needs support escalation. The fastest cases include both profile URLs, before-and-after screenshots, and proof that the old and new listings were the same business at the same location under Google Business Profile rules.
We deal with this as casework, not blog theory. In the post-merge cases we handle, the public count often drops first, then a few reviews stay attached to the retired listing URL or old CID until Google support gets evidence strong enough to move the case beyond a generic policy reply.
BGR Review has handled review recovery and removal work since 2019 from New York, London, and Thornhill, and the pattern is consistent: weak screenshots waste a support cycle, while dated before-and-after captures, both Maps URLs, dashboard access proof, and storefront evidence usually get a proper review. We also handle removals on a pay-after-success basis at $449 per removed review link with $0 upfront, so we see where visibility loss ends and actual policy-based removal begins.
Why reviews disappear after a Google Business Profile merge
Google reviews often disappear after a Google Business Profile merge because Google has to reconcile two separate listing records before it decides which review set should attach to the surviving profile.
That reconciliation can break review visibility even when the reviews still exist in Google’s system. In the merge cases we handle at BGR Review, the usual fault line is record mismatch: the two profiles had different CIDs, slightly different map pins, or different ownership histories, so Google treats the merge as a data consolidation event rather than a simple move. The result is a dropped public count first, then a partial return later if the transfer completes cleanly.
This is why a missing-review case after a merge is often a transfer or display problem, not immediate deletion under the Google Business Profile review policy. If one profile was older, verified earlier, or used a different address format such as “Suite 4” on one listing and “Ste 4” on the other, Google may take several business days to resync the reviews to the surviving profile. Support often treats that waiting window as normal before it looks for an actual merge error.
The first diagnostic step is simple: check where the loss happened. If reviews vanished only from public view, you are usually dealing with a visibility or attachment issue. If they also disappeared from the owner dashboard, that points more strongly to a transfer problem tied to the merged record itself, and the fix path is different.
How many reviews usually go missing, and for how long
There is no fixed Google number for how many reviews disappear after a Google Business Profile merge, and the visible loss can range from a single review to almost the entire count.
In the merge cases our team reviews at BGR Review, the pattern varies with the underlying listing record. Sometimes only a few reviews drop from the public total. In messier cases, Google appears to leave reviews attached to the retired profile record or old CID, so the surviving profile shows a much lower count even though the reviews were not fully removed under the Google Business Profile review policy.
Temporary drops often correct themselves within 3 to 7 business days. That window is more common when both profiles clearly represented the same location, the name-address-phone history matched, and there was no ownership conflict inside the dashboard. If the count has not changed after more than 7 business days, we usually stop treating it as normal post-merge syncing and start checking for a merge error.
A star-rating mismatch is one of the better clues. If your profile still shows a strong average rating but the visible review total is lower than expected, Google is often still reconciling the underlying review data rather than wiping every review outright. That distinction matters, because a rating-and-count mismatch usually points to a data-linking problem, not a review-policy penalty.
Temporary sync issue or real merge failure
A temporary sync issue shows recovery signals within a few days, while a real merge failure keeps reviews attached to the wrong listing or the retired profile URL.
In the post-merge cases we handle at BGR Review, the harmless version usually looks uneven before it looks fixed: the star rating comes back first, then a few older reviews reappear, then the surviving Google Business Profile starts showing historical review snippets again. That staggered return can happen over several days because Google's systems are reconciling two profile histories, not simply moving a visible count in one step.
The pattern turns more serious when the wrong profile stayed live after the merge. We see this most often where the surviving listing kept the weaker category history, or where reviews still appear only on the closed, removed, or old Maps URL instead of the active profile. If the old profile URL still shows review content while the live profile does not, that points to a bad association rather than a normal delay.
Risk goes up if you changed core business signals at the same time. An address edit, phone change, or primary category change within 48 hours before or after the merge gives Google more reasons to treat the two profiles as different entities, which is exactly where review transfer errors start.
Write down the exact merge date and every edit made around it. Google Business Profile support often asks for a clean chronology even when the first reply is a generic policy message, and weak timelines waste a support cycle because each follow-up pushes the case out again.
What Google usually checks before it restores missing reviews
Before Google restores reviews after a merge, support usually checks whether both profiles described the same real-world business at the same address, rather than two listings that only shared a brand name.
That distinction decides a lot of cases. In the merge and reinstatement work our team sees, Google support looks for matching location signals first: storefront signage, the same street address across both profiles, and address history that explains any edits. If one profile used “Suite 200” and the other had no suite, or one still showed an old phone number from before the move, support often pauses the case until you explain the mismatch.
They also check profile control. Support usually asks for the old and new Maps or Business Profile URLs, plus proof that you own or manage the live listing inside Google Business Profile. Public evidence helps more than most guides admit: your website contact page, a location page, and photos showing the business name on the door all give support something to match against the retired listing.
A clean paper trail speeds the review. The useful set is simple: a screenshot of the review count before the merge, the date the duplicate was removed or merged, and a dated screenshot showing the lower count after the change. Weak evidence burns time because each support reply can reset the cycle, which is exactly what we try to avoid in post-merge recovery cases.
The proof pack that gives support the best chance of fixing it
A strong proof pack is one file set that shows the two listings, the review loss, your ownership, and the fact that both profiles belong to the same real-world business.
Start with the listing identifiers. Add both Google Maps profile links, both business names exactly as they appeared before the merge, and any old CID or Place ID references you still have from rank trackers, call tracking notes, old spreadsheets, or past support emails. In the Google Business Profile recovery work we handle at BGR Review, cases stall fast when support has to guess which retired listing held the missing reviews.
Add dated screenshots next. The useful set is simple: the public review count before the merge, the lower count after the merge, your dashboard ownership status, and any notice showing the duplicate was marked closed, removed, or merged. Put the date in the filename or on the capture itself. That saves a reply cycle.
Then prove both profiles point to one entity. Include current storefront photos, a utility bill or business registration if support asks for formal proof, and your website contact page showing the same address and phone number. Google Business Profile Help threads often turn on location consistency, so mismatched phone numbers or suite numbers can hold the case up for a few business days.
Send everything in one submission. Splitting links, screenshots, and documents across three or four replies often adds another few business days because each response lands with less context, and the support queue effectively resets.
What to do in the first 72 hours after the merge
The first 72 hours after a Google Business Profile merge are for observation and evidence capture, not repeated edits.
Leave the surviving profile alone unless a core fact is wrong. In the merge cases our team reviews at BGR Review, extra changes to the primary category, address or phone in that 72-hour window often muddy the transfer history and make it harder to show Google what changed because of the merge versus what changed because you kept editing.
Record the public review count once or twice a day with screenshots. Include the date, the visible count, and the live listing URL in the image if you can; Google Business Profile support often asks whether any reviews returned on their own, and a dated sequence answers that in one reply instead of three.
Check the retired profile in both Google Maps and branded search. If the old listing still resolves, copy that Maps URL straight away, because missing reviews sometimes remain attached to the retired listing URL or its old CID even after the duplicate looks merged on the surface.
Ask one or two recent reviewers to check whether they can still see their review in their profile history or by direct link. That tells you whether you are dealing with a visibility problem on the surviving listing or a deeper detachment issue where the review still exists in Google's system but no longer connects to the profile you kept.
When to escalate to Google support
Escalate to Google support once a merged profile shows no sign of review recovery after about 3 to 7 business days, or sooner if the merge clearly left the wrong listing live.
That window matters because Google Business Profile merges often need a few days to sync review data across the surviving profile, the old CID and the public Maps result. In the cases our team handles at BGR Review, opening a ticket on day 1 often gets you a generic Google Business Profile Help reply telling you to wait, which burns a support cycle before anyone checks the actual merge.
Contact support earlier if the surviving profile has no review history at all, if Google kept the duplicate live and retired the stronger listing, or if the merged Maps result now shows the wrong name, address, phone or pin. Those are merge-error signals, not normal lag, and they usually need manual review rather than more waiting.
Use one case. Do not open two or three threads from different accounts. Multiple tickets often split the handoff between support teams and produce conflicting replies, which adds days.
Your first message should state the exact fault in one line, then give both profile URLs, the merge date and the number of missing reviews. Short and exact works better than a long complaint. If you later need outside help, BGR Review handles Google review removals on a separate pay-after-success model at $449 per removed link with $0 upfront, but a post-merge restore issue should go through Google support first.
How to write the support request so it does not get a generic reply
A support request moves faster when your first four lines tell Google exactly what changed, when it changed, and which profile should keep the reviews.
Write the opening like this: “On 14 February 2026, we merged duplicate Google Business Profiles for the same location. After the merge, the surviving profile lost 18 visible reviews. Active profile to keep: [surviving profile URL]. Retired duplicate: [old profile URL].” Put both URLs in that first block. In the post-merge cases we handle at BGR Review, support often sends a policy template first when the surviving CID, old Maps URL, and missing count are buried further down.
Attach your evidence in the order support can verify it: screenshot of the pre-merge public review count, screenshot of the current lower count, screenshot proving dashboard ownership of the surviving listing, then proof both profiles represented the same location. That last part usually means the same address, storefront signage, business licence, or utility bill tied to the same name and premises. Weak attachments waste days because each reply tends to reset the support cycle.
Ask for one action: review reassociation or review restoration to the surviving profile. Do not write “please investigate.” Google Business Profile support routes clearer requests better, especially when your evidence already matches the Google Business Profile guidelines on duplicates and eligibility. If you want a second pair of eyes before you send it, BGR Review can audit the case file, but plenty of owners can do this themselves if the pack is clean.
Cases where Google will not restore the missing reviews
Google usually refuses to restore missing reviews after a merge when the two profiles did not represent the same real-world business under Google's Business Profile guidelines and review policy.
Support pushes back fastest when the merged listings point to different entities: different addresses, different map pins, different phone numbers, or a service-area business merged into a storefront profile without a clean history showing they were the same operation. In the post-merge cases we handle at BGR Review, that distinction matters more than the review count drop itself. If the records look like two separate businesses, support often treats the missing reviews as non-transferable rather than lost.
Policy-violating reviews do not become recoverable because a merge happened. If a review had already tripped Google's spam or policy filters before consolidation, support will not restore it simply to match the old total. That is where many DIY appeals fail: the owner argues from the missing number, while support checks policy status on the underlying review links.
Ownership and identity changes also break restoration. If you moved premises, rebranded, changed ownership, and merged profiles in the same 30-60 day window, support may decide the old reviews belong to the prior listing history, not the current one. We also see failed restorations where the duplicate was created mainly to collect reviews; support checks historical edits, dashboard control, and public business data, so a weak paper trail usually ends the case.
What most guides get wrong about missing reviews after a merge
Most guides get the diagnosis wrong because they treat a dropped review count and missing review visibility as the same problem. In the Google Business Profile merge cases we handle at BGR Review, the public total often falls first while some underlying review records still exist on the retired profile URL or old CID. That distinction matters, because a count drop can be a sync problem, while a visibility gap often points to reviews still attached to the old entity record.
Most posts also miss the single piece of evidence you should save on day 1: the retired listing URL. Once the duplicate stops showing in normal Maps or branded search results, that URL gets harder to recover, and support loses an easy way to verify where the reviews sat before the merge. We tell clients to save both Maps URLs, the old and current place pages, and dated screenshots before waiting the usual first few business days.
Repeated edits create another mess. If you change categories, address formatting, and business name while waiting for reviews to reattach, you give Google fewer continuity signals and make the support agent less certain that both profiles represent one business record under the Google Business Profile rules. In the support escalations our New York and London team sees, weak continuity evidence adds days because each reply cycle tends to restart from a generic policy template.
The useful question is whether Google still recognises both profiles as the same entity. If it does, reviews often come back or can be reattached after a clean support review; if it does not, asking “where did my reviews go” is too vague to move the case.
What actually happens in a real recovery case
A real post-merge recovery case usually stalls on a generic Google Business Profile support reply until you send one complete evidence pack in a single thread.
In the cases we handle at BGR Review, the pattern is repetitive. A duplicate profile gets merged or removed, the surviving listing loses part of its visible review count that same day, and the first support response reads like a policy note from Google Business Profile Help rather than a fix. The reviews have often not vanished in the simple sense; some are still tied to the retired listing URL, the old CID, or a slightly different map pin.
The case starts moving once support can match the old profile to the live one without guessing. That usually means sending both Maps URLs, dated before-and-after screenshots showing the review count drop, proof that you manage the surviving profile, and proof that the business details match across both listings. Storefront photos, dashboard access screenshots, and a clear view of the business name, address and phone number save time because they answer the next support question before it arrives.
Weak submissions drag the case out. One missing screenshot, one cropped URL, or one vague line like “our reviews disappeared after merge” often triggers another reply cycle, and that usually costs several more business days before a specialist looks at it again. We structure these packs the same way we structure review and profile evidence across our New York, London and Thornhill teams because vague tickets burn time and leave you stuck between two bad assumptions: waiting too long for a sync that is not coming, or escalating too early with proof that will not survive review.
A practical checklist to recover reviews after a merge
A workable post-merge recovery checklist starts with a 7-day triage window, then one clean Google Business Profile support case built around evidence instead of guesswork.
- Day 0 to day 3: Stop non-essential edits on the surviving profile. Do not change the name, category, address or hours while Google is still syncing. Capture dated screenshots of the public review count, the dashboard view, both Maps URLs, and any reviews still visible on the retired listing. Save the old and surviving profile links in one file.
- Day 3 to day 7: Check for partial recovery rather than assuming the merge failed. Compare what the public listing shows against what you see inside Google Business Profile, then build one proof pack with storefront photos, signage, address evidence, dashboard access evidence, and a simple merge chronology.
- After day 7: Open one support case and attach the full evidence set. Ask Google to restore the missing reviews to the surviving profile URL, and name both profile links clearly. In the cases we handle at BGR Review, weak first submissions burn days because each generic reply resets the cycle.
- If support stalls: Rebuild the file set before escalating again. A clean second submission with labelled screenshots and a dated timeline usually performs better than replying angrily inside a messy thread.
If you need help after support has stalled, BGR Review handles Google review issues and removals from our New York, London and Thornhill teams. Our removal model is separate from merge recovery: $0 upfront and $449 per removed review link, only after success.
Where to go from here
A review drop after a profile merge usually starts as a transfer delay or a visibility mismatch between the live listing, the retired URL and the old CID. Give it roughly 3 to 7 business days before you treat it as a true merge failure. After that, the fastest next step is a clean evidence pack: both Maps URLs, the old and new profile details, dashboard access proof, storefront photos, and dated before-and-after screenshots showing the review count change.
Send one support request with that full set. Google Business Profile support often answers the first message with a generic policy note, and weak evidence usually costs you another reply cycle. In the post-merge cases we handle at BGR Review, cases move faster once the ticket already shows the two listing URLs, ownership proof and the timeline in one thread.
If the missing reviews were legitimate, you need review recovery support. If the problem is a review that breaches Google’s review policy, removal is the cleaner route. BGR Review handles removals on a pay-after-success basis at $449 per removed review link with $0 upfront, and our review packages carry a 30-day free replacement guarantee. Your next action is simple: document the loss properly, file once, then escalate only with better evidence.