Your Google review reply is not showing. The order worth checking

A reply you wrote is not under the review. That is one symptom with at least six causes, and the Business Profile interface distinguishes between none of them. The grouping below is ours, because no page we read lists the reasons a reply can be missing. The field that would answer it does exist, documented, in an API rather than in the dashboard. So the method is elimination, cheapest check first.

Look at the public profile, and at your own view

These are two different instruments. Google’s route to your replies is to “Go to your Business Profile” and “Select Read reviews”, and its editing steps add a usable test: “Under the reply you want to edit, select Edit”. If an edit control sits under the review, a reply is on the record.

The public side is stated conditionally: “If your reply is approved, it will be publicly posted under the customer’s review.” No page we read says whether your own Read reviews view shows a reply that has not been approved, so a reply visible to you and absent in public is consistent with moderation not having finished.

Do not read the customer’s alert as proof of publication. Google documents that “The person who wrote the review is notified when you reply” and says nothing about when that notification fires, at submission or after approval. We have not tested it and we are not going to assert either answer.

Was it ever submitted

Three published conditions stop a reply before moderation.

Verification. Google’s help page is blunt about the order of operations: “Before you can reply to reviews, you must verify your business.” That is not a reply that failed moderation. It is a reply that was never eligible.

Availability. The same page says “Reviews are available only in certain countries or regions and for certain business categories.”

Length, if you replied through software. The API caps the reply body: “The maximum length is 4096 bytes.” A long reply sent through a tool can fail at the request rather than at moderation, which looks identical from the profile.

No page we read describes an outbox, a sent log or a submission history for replies. If you kept no record of what you sent and when, that record does not exist.

Is it still in moderation

Google publishes one timing statement, on the help page for owners:

Google reviews your replies: This makes sure that they follow Google’s content policies. If your reply isn’t approved to be posted, you’ll be asked to edit it. Replies usually take up to 10 minutes to review, but sometimes a review can take up to 30 days.

Read that sentence closely, because it changes subject halfway through: “Replies usually take up to 10 minutes to review”, then “sometimes a review can take up to 30 days”. Google does not say whether the 30-day tail belongs to the reply’s moderation or to the review, and we are not going to resolve an ambiguity in someone else’s sentence by guessing. What is unambiguous is the outer bound of 30 days, so a reply missing after a week is inside documented behaviour and rewriting it on day two is guessing. That is also the whole of Google’s published timing: no average, no median, no distribution.

The machinery behind it is a field described as “Output only. The state of the review reply.”, on an enum Google introduces as “Represents the moderation state of a review reply.” Output only means you cannot set it, so nothing you send skips moderation or asks where you are in the line. The four values, in Google’s words:

Value	Google’s description, verbatim
`REVIEW_REPLY_STATE_UNSPECIFIED`	“Indicates that the state is unspecified.”
`PENDING`	“Indicates that the reply is pending moderation.”
`REJECTED`	“Indicates that the reply was rejected.”
`APPROVED`	“Indicates that the reply was approved.”

PENDING is the only place a pending reply is visible as pending, and the unspecified value is the enum’s default rather than a moderation outcome. The rest of the object is thin: updateTime is “Output only. The timestamp for when the reply was last modified.”, which is the only timestamp available and is about the reply rather than about moderation. Nothing records when moderation started or when it should end.

The state is read-only and recent. Google’s changelog entry for 2026-04-01 reads “ReviewReplyState can now be retrieved as part of reviews.”, and the three methods it names are all reads. The method that writes a reply is updateReply, “Updates the reply to the specified review.” and “A reply is created if one does not exist.”, whose response “contains an instance of ReviewReply”. Whether the value returned at write time is already PENDING is not stated, so checking the state means reading the review back.

Well past 30 days, treat it as overdue rather than as rejected. Nothing published turns elapsed time into REJECTED: the state is whatever the API reports, and no documented transition runs on a clock.

Was it rejected

A rejection has a published reason, in that same place and nowhere else. The field beside the state reads “Optional. Output only. The policy violation that resulted in rejection. Only populated if reviewReplyState is REJECTED.” So no reason code exists before rejection, and none appears in the dashboard after it. The reasons themselves are on the list of published rejection reasons.

Is the problem the account, not the reply

This is the cause worth ruling out early: the symptom is a missing reply and the subject is the listing. Three values from that same rejection enum, in Google’s words:

Value	Google’s description, verbatim
`LOCATION_VERIFICATION_REQUIRED`	“This Business Profile is not verified.”
`LOCATION_SUSPENDED`	“This Business Profile has been suspended.”
`OWNERSHIP_REVOKED`	“Another Google Account has claimed this Business Profile. You can no longer manage this profile.”

None of those is about your wording. Google also flags the list as open: it “Represents standardized policy violations. New values may be added in the future. Clients should be prepared to handle unknown values.” Check the standing of the profile before editing a single sentence of the reply.

Access rules out one explanation. Owners and managers both hold the capability listed as “Respond to reviews”, and when a user is removed Google states that “their replies to reviews, posts, comments, and other actions stay on the Business Profile”. So “the manager who wrote it has left” is not a documented cause of a disappearing reply.

Is the review gone, and the reply with it

A reply is not an independent object. In the API it is a field on the review, described as “The owner/manager of this location’s reply to this review.”, and the method that removes one is described as “Deletes the response to the specified review.” Nothing in the published model holds a reply with no review. What Google does not state anywhere we have read is what happens to an approved reply when its review is removed, so that is the data model, not asserted behaviour.

Reviews do go missing for reasons Google does publish, including moderation delay, a recent profile merge, a category whose user-created content is temporarily disabled, and the permanent case: “Reviews removed for policy violations won’t be restored.” Those cases, and the reviewer’s own control over deleting a review, are set out in why a Google review is not appearing.

Note what that page covers. Google publishes an article about missing reviews and none about missing replies, which is why your symptom has no official answer. If the review went because it was fake, reporting a fake review and what can actually be removed are the adjacent questions.

The part that is genuinely indistinguishable

Look at what an owner can observe. A reply in moderation, a reply rejected, a reply whose review was removed, and a category whose user-created content is temporarily disabled all present as the same thing: no reply on the profile. The interface offers no status, no notification after the submission prompt and no reason code. The distinctions exist in an API field and an enum, gated behind API access rather than shown to the owner whose reply it was.

That gate costs a new business time. Google’s prerequisites require you to “Manage a Google Business Profile that is verified and active for 60+ days”, and its FAQ says “Requests are reviewed within 14 days.” The qualifying profile need not be the one whose replies you want to read: “This GBP can be the applicant’s own office or headquarters or it could belong to one of the clients they manage”, and “GBP API access is granted on a Google Cloud project level”. So an approved agency reading a client’s brand new profile is not waiting again. The wait falls on an applicant with no other qualifying profile to apply with, and for them up to 74 days can pass before the field is readable on their own profile, which is our arithmetic from those two pages rather than a figure Google states.

So the honest answer to “why is my reply not showing?” is that from outside the API you cannot tell, and looking harder at the dashboard will not resolve it. Reading the state directly is what review management software is for.

What to do, in order

Open the listing as a customer, then as the owner through Read reviews.
Confirm the profile is verified and not suspended before touching the text.
Inside Google’s stated 30 day bound, wait rather than rewrite.
Check the review is still there. If it is gone, the reply question is moot.
If you rewrite, rewrite for the policy that plausibly caught it, not for a better tone. An account-level rejection is not improved by better words.
Keep your own log of replies and dates. No page we read describes one Google keeps for you, and without one you cannot tell a reply that vanished from a reply that never sent.