Do Google Review Replies Survive a Business Profile Merge?

A duplicate Google listing is its own headache: the same business shows up twice on Maps, reviews split across two profiles, and customers land on whichever one Google feels like surfacing that day. So when Google finally agrees to merge them, it feels like the fix. Then you check the surviving profile and notice half your carefully written replies are gone, even though the reviews themselves made it across fine. That's not a glitch. Google says so itself.

The short answer

Yes, this happens, and Google confirms it directly. Buried in its own help documentation on resolving duplicate profiles is one plain sentence that most owners never see until it's too late.

“When 2 profiles are merged, their reviews are combined, but replies to reviews may be lost.”

Reviews and their star ratings almost always survive a merge intact. Replies are the part that don't, and once one is gone, there is no support ticket or appeal that brings it back.

Why replies vanish but reviews don't

Google hasn't published the internal mechanics, so treat any confident explanation, including this one, as informed reasoning rather than confirmed fact. The pattern reported consistently by owners and agencies who've been through a merge: a review is anchored to the reviewer's own Google account, which is why it travels cleanly to whichever profile survives. A reply, by contrast, is tied to the specific listing that received it. When that listing gets folded into another, the review keeps its home, but the reply pairing doesn't always come with it.

The practical result is the same either way: you did the work once, and a routine cleanup step that Google itself recommends for duplicate listings can quietly undo it.

This tends to hit the profiles most likely to have duplicates in the first place: a business that moved and never cleaned up the old address, one that rebranded under a new name, or a multi-location operator where a duplicate quietly appears at one storefront while the rest stay clean. Running several locations doesn't make any single merge riskier, but it does mean the checklist below is worth keeping on hand rather than reinventing at whichever location hits this next. See multi-location review management for the broader setup.

Before you request a merge

The right fix for a duplicate listing isn't always the same, and knowing which one you need changes how much risk you're taking on.

• Confirm you actually need a merge, not a deletion. If the duplicate is empty, no reviews, no photos, nothing worth keeping, deleting it outright is simpler and the reply-loss risk doesn't apply. Merging is for when both listings carry real reviews you want to keep.
• Save a copy of every reply first. Screenshot or copy the replies on both profiles into a document before you request anything. Google gives no way to recover a lost reply after the fact, so this is the only safety net you get.
• Write down which reviews have replies. A two-minute checklist beats trying to remember later, and you'll need it to audit the result.
• Don't merge mid-campaign. Merge requests go through Google's review queue with no published timeline, so avoid submitting one right before a review push you're tracking closely.

After the merge: audit before you assume it's fine

A completed-merge notification, if you get one at all, just confirms the profiles were combined. It won't tell you what didn't survive. Assume nothing until you've checked.

• Go through every review on the surviving profile and compare it to your pre-merge checklist.
• Flag anything that now shows as unanswered but has a reply on your saved copy.
• Check reply text closely even where a reply does show; wording is occasionally intact but a detail or link inside it has changed.
• Do this within a week or two of the merge completing, while your checklist is still fresh, rather than finding it during a routine sweep months later.

Rewriting what's missing, without it looking stale

Here's the one wrinkle worth knowing before you start retyping: from the customer's side, a reply that disappeared doesn't show up as edited or deleted, it just looks like you never answered. You aren't picking a conversation back up, you're starting one that reads as brand new to anyone who sees it.

• Don't reference the original reply or apologize for a delay the reader has no way of knowing about; write it as a normal, first-time reply.
• Check the review's original date before writing anything time-sensitive, like thanking someone for stopping by last week, that no longer matches.
• Batch the reviews with real detail first; plain star-only ratings can wait, same as any other backlog.

For wording by star rating and scenario, the full set is in 30+ Google review response templates, and for the harder ones specifically, how to respond to negative reviews.

If a merge wiped out more than a handful of replies, redoing them one at a time is exactly the kind of backlog that never gets finished. The same approach that works for catching up on an old backlog works here too: clear it in one batch instead of trickling it out. Automating the routine replies going forward, or drafting the missing ones with the free reply generator, turns a dreaded backlog into a five-minute pass.

Keep this from happening again

The real fix isn't avoiding merges. Google explicitly recommends merging over deleting when a duplicate carries real reviews. It's catching duplicates before they build up months of reply history worth losing.

Duplicate listings cause other visibility problems too, including reviews that never post at all. The full list of causes is in Google reviews not showing up, and the full routine for staying on top of reviews generally is in how to manage Google reviews.