Google Review Replies Not Showing? It's a Bug — Here's What To Do (July 2026)

TL;DR: A widespread Google bug is hiding business owners’ review replies when they’re logged in. The replies aren’t deleted — they typically still appear in incognito mode. Google Product Experts have confirmed it’s a bug and Google is aware. Do not mass re-reply. Verify in a logged-out window, document what you’re seeing, warn your clients, and wait it out.

The short version

On July 22, 2026, business owners across a wide range of Google Business Profiles opened their dashboards and found something alarming: every reply they had ever written to a customer review appeared to be gone.

Not one or two. Not the recent ones. All of them. Years of carefully written responses — the polite thank-yous, the diplomatic damage control on one-star reviews, the ones legal reviewed before posting — showing as if they had never existed.

The good news, and it is genuinely good news: they haven’t been deleted. This is a display bug. The replies are still stored on Google’s side, and in most reported cases they remain visible to anyone viewing the profile while logged out — which describes essentially every actual customer.

But “it’s just a display bug” undersells the operational chaos this causes. Business owners panic. Clients call their agencies. Someone with good intentions and admin access starts re-typing four hundred replies. That’s the real damage, and it’s avoidable.

What business owners are actually seeing

The reported symptoms are consistent:

• Zero replies visible in the dashboard. Reviews display normally with their star ratings and text, but the owner-response section is empty across the board.
• It affects historical replies, not just new ones. This isn’t a case of new replies failing to post — replies written months or years ago are equally invisible.
• New replies appear to submit, then don’t show. Test replies left during the outage have been observed sitting in a pending-type state rather than rendering as published.
• It’s not account-specific. Multiple unrelated businesses, in different verticals and countries, reporting identical behaviour within the same window.

That last point is what elevates this from “something’s wrong with my account” to “something’s wrong with Google.” When a problem is isolated, you troubleshoot. When it’s simultaneous and global, you wait.

Barry Schwartz of Search Engine Roundtable — who has covered Google’s local products for two decades — tested it on his own profile and confirmed he saw zero replies while logged in, despite knowing he had left replies over the years. He also left a fresh test reply and observed it not displaying.

How the bug surfaced

The pattern followed the usual route for Google local bugs: forums first, confirmation second. Threads began piling up in the Google Business Profiles support forums from owners reporting that they had replied to all their reviews as of the previous day, and that those replies were suddenly no longer visible — with no explanation and no notification.

Two well-known Google Product Experts responded quickly: Sherry Bonelli confirmed it was a bug and that Google was aware of it, and Tim Capper independently identified the behaviour as a bug rather than an intentional change.

Product Experts aren’t Google employees, but they’re the closest thing the local-SEO community has to an early-warning system. When two of them independently call something a bug within hours, that’s usually the end of the diagnostic phase. Discussion also spread to the Local Search Forum and X, where a user posted the single most useful piece of information in the entire episode: the replies were still visible in incognito mode.

The signed-in vs. signed-out clue

This is the detail worth internalising, because it turns a five-alarm fire into a shrug. If your replies are invisible while you’re logged into your Google account, but visible when you view the same profile in a private/incognito window, then:

1. The data is intact. Google still has your replies. They’re in the database. Nothing was deleted.
2. Customers are still seeing them. The overwhelming majority of people reading your reviews are not logged into your business account — they’re seeing the normal, correct version of your profile.
3. The failure is in a specific serving path. Something in the authenticated view — the one that renders your profile differently because it knows you’re the owner — is failing to attach replies to reviews.

In other words, the version of your profile that matters commercially is fine. The version that’s broken is the one only you look at. That’s the difference between “our reputation is on fire” and “our dashboard is annoying today.”

This is the third review bug in a short window

This is not an isolated glitch. It’s the third significant review-related failure on Google Business Profile in recent memory:

• Bug 1 — Reviews not displaying at all. Businesses were shown a “you have no reviews yet” state despite years of accumulated reviews. Google later said it had fixed this.
• Bug 2 — Reviews vanishing. Separately, businesses reported reviews disappearing from their profiles entirely — a problem we broke down in why your Google reviews aren’t showing up.
• Bug 3 — Replies not displaying. Today’s issue.

Three failures, all in the same subsystem, all within a compressed timeframe. Individually, each is a bug. Together, they’re a pattern — and the pattern suggests Google is doing something structural to how local review data is stored, indexed or served, and the migration is not going smoothly.

For business owners, the practical implication isn’t that Google is falling apart. It’s that the review layer of Google Business Profile is currently unreliable enough that you should not treat it as your only copy of that data.

What’s likely going wrong technically

Google hasn’t published a root cause, so this is informed inference rather than fact — but the symptom profile narrows the possibilities. Google serves your profile differently depending on who’s asking: the logged-out public view is cached and heavily optimised for millions of searchers, while the logged-in owner view is dynamically assembled with management controls and owner-specific state.

When replies vanish in one path but persist in the other, the underlying review records are almost certainly fine. What’s broken is the join — the step where the system fetches a review and attaches its associated owner response before rendering. Plausible culprits:

• A caching or index layer rebuilt incorrectly. If owner responses live in a separate index merged at render time, a bad rebuild produces exactly this: reviews present, replies absent, no data lost.
• A schema or field migration mid-flight. If replies were being moved between storage structures, the authenticated read path might be pointing at the new location before the data finished arriving.
• A permissions or scoping regression. A change to how owner-specific content is filtered could accidentally filter out the owner’s own replies from the owner’s own view.

The reported behaviour of new test replies sitting in a pending-looking state supports the caching/indexing theory: the write succeeds, but the read path can’t yet see it. Practically, this class of bug tends to resolve within hours to a few days once identified, because the fix is usually a re-index or a rollback rather than a data-recovery operation.

Step-by-step: how to check whether you’re affected

Do this before you do anything else. It takes ninety seconds.

1. Open an incognito or private window. Chrome: Ctrl+Shift+N (Windows) / Cmd+Shift+N (Mac). Firefox & Safari: Ctrl/Cmd+Shift+P.
2. Search for your business by name and city. Don’t navigate from a bookmark or a logged-in tab — search fresh.
3. Open the reviews section on your Business Profile and view the full review list.
4. Look for owner responses on reviews you know you replied to. Pick three or four you’re certain about.
5. Interpret the result using the table below.

If replies are missing in both views, check whether the reviews themselves are also missing — that points to one of the earlier review-display bugs rather than this one, and the advice is broadly the same: don’t take destructive action, document, and wait. Either way, take screenshots — timestamped evidence of what you saw and when is worth more than your memory in three weeks.

What to do — and what not to do

❌ Do NOT mass re-reply

This is the single most important instruction in this article. If you look at an empty reply field and conclude your responses were deleted, the instinct is to rewrite them. Resist it completely. When the display bug resolves — and it will — your original replies will return. If you’ve written new ones in the meantime, you risk duplicate responses, overwritten originals, or a review history that reads as if you replied twice months apart. There is no scenario in which mass re-replying during a known display outage beats waiting.

❌ Do NOT delete and recreate anything

Don’t remove reviews, don’t “refresh” the profile by unpublishing and republishing, don’t remove and re-add profile managers. Destructive troubleshooting during a Google-side outage turns a recoverable situation into an unrecoverable one.

❌ Do NOT file a ticket claiming reviews were deleted

Framing matters. If you report “my replies were deleted,” you may get routed into a slow content-restoration workflow. If you report “replies are not displaying in the authenticated dashboard but are visible when logged out,” you’re describing the actual bug and giving support something useful.

✅ DO verify in incognito, and keep replying to new reviews

The incognito check is the whole diagnosis. And keep responding to new reviews as normal — response time is a real factor in customer perception, and submissions are being accepted; they just may not render for you immediately. Keep a copy of what you wrote in a separate document so you can confirm it posted later.

✅ DO document everything and monitor the forums

Screenshots of the empty state, timestamps, the incognito comparison. If you manage profiles for someone else, this is your evidence that the responses existed and the failure was on Google’s end. The Google Business Profiles support forums, Local Search Forum and the local-SEO community on X will know the bug is fixed before any official announcement — watch there, and re-verify in 24–48 hours before taking any action.

For agencies and multi-location brands

If you manage profiles on behalf of clients, this bug has a second-order problem: your client may discover it before you tell them, and conclude you never did the work. Review response is one of the most visible deliverables in a local-SEO retainer, and one of the easiest to spot-check. A client who logs in, sees zero replies across two years of reviews, and hasn’t heard from you is going to draw an ugly conclusion.

Get ahead of it today

Send a short, plain-language note before they find it themselves — something like:

Subject: Heads up — Google display bug affecting review replies

Hi [Name],

Quick proactive note: Google is currently experiencing a widespread bug where owner replies to reviews aren’t displaying in the Business Profile dashboard. If you log in today, your replies may appear to be missing.

They aren’t. The data is intact — you can confirm this by viewing your profile in an incognito window, where the replies still appear normally. Customers browsing your listing are seeing your responses as usual.

Google Product Experts have confirmed it’s a bug and Google is aware. We’re monitoring and will confirm once it resolves. In the meantime we’re not re-posting anything, since the originals will return and duplicating them would make things worse.

Nothing you need to do — just wanted you to hear it from us first.

Multi-location specifics

• Spot-check across locations, not just one — confirm the scope on your own portfolio before communicating.
• Pause any automated reply tooling. If a reputation platform posts replies via API, pause scheduled sends until the display path is stable so automation doesn’t retry against a confusing state.
• Check your reporting. If client dashboards pull “response rate” from the GBP API, that metric may read as zero — annotate it now so nobody panics at month-end.
• Don’t let a junior team member “fix” it. Make sure everyone with dashboard access knows not to re-reply. This is the classic scenario where a helpful person creates the real problem.

Does this hurt local rankings?

Almost certainly not. Review responses function as a trust, engagement and freshness signal — but this bug doesn’t remove the responses from Google’s systems; it fails to render them in one specific authenticated view. The underlying data still exists, as shown by logged-out users seeing the replies normally. For a ranking impact, the data would have to be genuinely absent from the systems that feed local ranking, not merely absent from the owner’s dashboard. Nothing in the observed behaviour suggests that.

The more realistic risks are behavioural, not algorithmic: a conversion risk if any subset of searchers sees an unanswered one-star review you actually answered (spot-check your public view from a different device and network); a temporary response-rate metric distortion in your reporting; and — the biggest actual risk — self-inflicted damage from panic-posting duplicate replies. Don’t restructure your local-SEO strategy around a rendering bug.

The real lesson: stop treating GBP as your system of record

Three review bugs in short succession should change how you think about this data. Your Google reviews and your responses to them are a genuine business asset — they influence purchase decisions, they took years to accumulate, and in many local industries they’re worth more than the website. And right now they live in exactly one place: a platform you don’t control, that changes without notice, that has no meaningful support channel for small businesses, and that has demonstrated three times recently that this data can become inaccessible without warning.

You would never run your customer list that way. You’d never run your accounting that way. The fix isn’t to abandon Google Business Profile — that’s not an option, and it’s not the point. The fix is to keep a copy. (If you’re also shoring up the profile itself, our complete Google Business Profile guide covers the fundamentals.)

How to back up your reviews and replies

In rough order of effort:

1. Manual export (free, tedious, works). Periodically copy your reviews and responses into a spreadsheet — date, reviewer, rating, review text, your response, response date. For under a hundred reviews it’s a one-hour annual task.
2. Google Business Profile API (technical, thorough). Pull reviews and their replies programmatically and store them monthly. The right answer for multi-location operations.
3. Reputation-management platforms (paid, automatic). Most established tools keep their own copy of your review data — check whether yours retains historical replies and lets you export them.
4. Screenshot your highest-value reviews (free, five minutes). At minimum, capture the detailed five-star reviews and the negative ones where your response saves the sale, with the response visible. Store them somewhere that isn’t Google.
5. Keep a running draft file of responses as you write them. Write your reply in a document, then paste it into Google. Ten seconds per reply, and you can reconstruct anything.

The recurring theme in every one of these bugs is that businesses had no independent copy of data they consider valuable. That’s the fixable part — and it’s exactly why Harry AI keeps your reviews and replies flowing and logged, so a Google hiccup is never your only copy.

Frequently asked questions

Are my review replies deleted?

No. In the reported cases the replies persist and remain visible in logged-out views. This is a rendering issue in the authenticated dashboard, not data loss.

Why can I see them in incognito but not when logged in?

Google serves a different, dynamically assembled version of your profile when it recognises you as the owner. The failure is in that authenticated path; the public, cached view is unaffected.

Should I re-reply to all my reviews?

No. This is the most damaging thing you can do right now. Your originals will return and you’ll be left with duplicates or overwritten responses.

Can customers see my replies?

In most reported cases, yes — customers browse logged out, which is the unaffected view. Spot-check from a different device to confirm for your own profile.

Should I contact Google support?

Only if you’ve verified the replies are missing in both logged-in and logged-out views. If it’s the standard display bug, support can’t do anything a re-index won’t fix on its own, and reporting it as deletion may route you incorrectly.

How long will this take to fix?

Google hasn’t given a timeline. Bugs of this type — where the fix is a re-index or rollback rather than data recovery — have historically resolved within hours to a few days once acknowledged.

Will this affect my Google Maps ranking?

There’s no indication that it will. The underlying data appears intact, so the signals that feed local ranking should be unaffected.

New replies I post aren’t showing — are they saving?

Reports suggest submissions are being accepted but not rendering to the owner. Keep a copy of what you wrote so you can verify once display is restored.

Sources

• Search Engine Roundtable — Another Google Local Bug: Review Replies Not Displaying (Barry Schwartz, July 22, 2026)
• Google Business Profiles Help — reply visibility thread · missing replies thread
• Local Search Forum — Review responses not showing in GBP dashboard
• Prior coverage: reviews not displaying · reviews vanishing