Who signs a Google review reply, when Google shows only your business name

A reply is posted as the business, and Google states that your personal name is not shown on it. Any name inside a reply is therefore one you added to text that was already attributed. The IMPERSONATION rejection reason, which is where this question usually gets argued, is about assuming an identity that is not yours, aimed at people pretending to be somebody else on Maps, and it never mentions replies.

What the API publishes

IMPERSONATION is one of the 43 values in the PolicyViolation enum returned by the v4 Business Profile API. Google’s description in full:

Content that violates our policy on impersonation isn’t allowed. Impersonation includes assuming a false identity in order to mislead others or gain improper benefits.

It arrives in a field documented as “Optional. Output only. The policy violation that resulted in rejection. Only populated if reviewReplyState is REJECTED.”

The object it arrives on shows how Google models a reply. A ReviewReply has four fields: comment, updateTime, reviewReplyState and policyViolation. None is an author. The reference calls it “the location owner/manager’s reply to a review”, and that is the only attribution there is.

Compare the review. A Reviewer carries a displayName: “The name of the reviewer. Only populated with the reviewer’s real name if isAnonymous is false.” Google models the reviewer’s identity, including their right to withhold it, and models none at all for whoever replies.

The policy behind the value names no merchant

The category sits on Google’s prohibited and restricted content page, under Fake & Misleading Content & Behavior. Quoted in full, it is short:

Using Google Maps to mislead others is against the spirit of delivering useful information to assist users as they explore the world around them. Don’t use Google Maps to impersonate any person, group, or organization.

Its prohibitions, verbatim:

Content posted or shared seeking to impersonate any person, group, or organization.

Content that is pretending to be a verified authoritative source.

Then its allowance:

We do allow content that contains alternative names for a person or organization where the content is not attempting to mislead others.

Note what is missing. Sections elsewhere on the same page split their rules by who is posting: the solicitation rules prohibit “Merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member.” Google has written one rule about staff names, and it is about asking customers to name your staff. The impersonation section scopes nothing to merchants and never mentions a reply.

Google states your name is not on the reply

The sentence that changes the answer is on the help page about managing reviews, not in any policy:

Your reply is publicly posted: If your reply is approved, it will be publicly posted under the customer’s review. It will appear like your business replied, and your personal name won’t be shown.

So the identity question is decided before you type. The reply is in the business’s voice because Google publishes it that way. That makes a signature redundant at best. Consider a reply written by Raj and signed by his colleague:

Thank you for taking the time to write this. We have passed your comments to the kitchen. Priya, General Manager

Google has attributed that reply to the business. “Priya, General Manager” is the only part that asserts anything about a person, and the only part that is false.

Is that a policy problem, or just bad practice?

Test it against the words Google published. The enum description has a purpose clause: a false identity assumed “in order to mislead others or gain improper benefits”. The policy prohibits impersonating “any person, group, or organization” and pretending to be “a verified authoritative source”. A manager’s name over a colleague’s text misstates who typed a sentence, inside a reply the reader was already told came from the business. No outside identity is adopted and no benefit is gained.

Google nowhere states whether a business may sign a reply with the name of someone other than the writer. We have not tested it and we are not going to assert an answer we cannot show you. It is poor practice for reasons that have nothing to do with moderation. A reply outlives the arrangement: the owners and managers page states that when a user is removed, “their replies to reviews, posts, comments, and other actions stay on the Business Profile”. Priya’s name stays on that reply after Priya leaves.

Three of the 43 values turn on misleading somebody, and the neighbour is the sharper risk. MISREPRESENTATION covers “misleading representations or omissions for the purpose of gaining improper benefit”, and its policy section prohibits “False or misleading accounts of the description or quality of a good or service”. Inventing a person who does not work for you, or attaching a qualification nobody holds, reaches that. A misplaced signature does not.

The agency or the tool replying for you

This is the case a business with staff actually faces, and none of the pages we read takes it up. An agency, a receptionist or a piece of review management software replies for the owner, in the business’s voice, and no reader can tell.

What Google publishes covers the access, not the authorship. The capability table lists “Respond to reviews” under both owner and manager, and the roles page tells you to grant a role rather than share a login: “To access and manage Business Profiles without the need to share your password, each user needs their own Google Account.” An agency holding manager access is authorised by the organisation whose voice it writes in, so the act of replying is not itself the adoption of an outside identity.

Keep those two things apart, because permission and representation are not the same claim. Manager access settles who may write. It settles nothing about what the writing asserts: a name, a role or a qualification inside the reply is a statement about a person, and access does not make one true. The authorised agency that signs off as the owner is authorised and still inaccurate.

On disclosure, Google is silent. We found no published requirement that a reply state who wrote it, whether a third party was involved, or whether the text was machine-generated: no field for it in the API, no sentence in the policy or the help pages we read. That is a gap, not a permission, and we are not filling it with an inference either way.

What to do instead

Write the reply as the business, in the first person plural, and let Google’s attribution do the work it already does:

Thank you for taking the time to write this. Your comments reached the kitchen the same morning, and the chef has changed how the pass is checked at the start of service. We are glad you came in and we hope to see you again.

If you want a name anyway, because a single-operator business reads better with one, use a real person who holds access and writes the replies. Do not rotate a manager’s name over other people’s text, invent a person, or claim a title. The method for the reply itself is in how to respond to a negative review, and the rest of the reasons a reply can be refused are in what Google publishes when a reply is rejected.

What this policy is genuinely for is the reverse case: a review posing as your business is what “impersonate any person, group, or organization” was written about, and the route there is flagging it.

The short version

Google’s impersonation reason is about assuming a false identity to mislead or to gain a benefit, and it never mentions replies. The sentence that decides the ordinary case is on the help page instead: your reply appears to come from your business and your personal name is not shown. A signature adds a claim Google left out, so it should be true or absent. Manager access authorises an agency or a tool to write in the business’s voice, which answers who may reply and not whether the names in the reply are accurate, and no page we read requires a reply to disclose who wrote it.