How to Auto-Reply to Google Reviews (and Which Ones Never to Automate)

To reply to Google reviews automatically, you need software connected to Google’s Business Profile API: a review tool, or an automation flow in Zapier, Make or n8n with an AI step that writes each reply. Automate the 4–5★ reviews, where a specific thank-you is all the reviewer needs. Send every 1–3★ review to a person, with a reply drafted and waiting.

Two things decide whether it works. Google checks every owner reply against its content policies before it appears, so identical or promotional replies can be turned down and never show. And a flow that answers every review will sooner or later thank someone for a complaint. Below: which reviews to automate, how Google’s moderation works, what a do-it-yourself flow needs, and how ReputeMap’s switch handles it.

Which Google reviews to answer automatically

The review	Answer it automatically?	Why
5★ with a comment	Yes	A thank-you that picks up one detail from the review is all it needs
4★ or 5★ with no comment	Yes, briefly	There’s nothing to quote, so keep it to one line and vary it: the same line under every rating is repetitive content, one of the reasons Google gives for rejecting a reply
4★ with a small complaint (“great food, slow service”)	Yes, if the reply names the complaint	A thank-you that ignores the slow service tells every reader you didn’t read it
3★	No	Mixed reviews need someone who knows what happened that day
1★ or 2★	Never	An automatic apology can promise a refund you won’t give; a cheerful reply under a complaint reads worse than silence
Any rating that mentions health details, an injury, money owed or a legal dispute	No	A person should choose every word of a public reply about those
Your backlog of old, unanswered reviews	Not in bulk	Hundreds of late replies at once look automated; answer the recent and the negative ones first, by hand

The line sits at 4★ because a 4★ review is still praise, and a 3★ review usually isn’t. Wording that works for both kinds, with 15 templates, is in how to respond to Google reviews.

Google checks every owner reply before it shows

Google’s help page for business owners says replies are reviewed against Google’s content policies: usually within 10 minutes, sometimes up to 30 days. A reply that isn’t approved comes back to you to edit.

Every automation and review tool posts replies through the Business Profile API, and there Google reports the outcome on the reply itself, in a field called reviewReplyState:

reviewReplyState	Meaning, per Google’s API reference	What to do
PENDING	Waiting for moderation	Nothing yet: the reply isn’t public
APPROVED	Approved	It shows under the review
REJECTED	Rejected; a second field, policyViolation, names the policy	Rewrite the reply and post it again

policyViolation has more than 40 codes, from suspended profiles to hate speech. These are the ones an automatic thank-you can run into:

Code	The policy it names	How an automatic reply tends to trip it
REPETITIVE	Repetitive content	The same sentence under review after review
ADVERTISING_AND_SOLICITATION	Advertising or solicitation	A promo code, a “book again” link, a sales line
PERSONAL_INFO	Personal information	Repeating a customer’s order number, health details or address back to them
OFF_TOPIC	Off-topic content	A stock reply that has nothing to do with the review

One vendor’s data points the same way. In June 2026, GMBapi, a company that sells Business Profile API access, posted an analysis of 12,752 rejected owner replies from its own platform on Local Search Forum. It reported that 92.6% of the rejections were on 5★ reviews and 67% contained recognizable AI boilerplate, such as “thrilled to hear” and “look forward to welcoming you back”. One account’s “Thank you!”, sent word for word to more than 100 reviews, was rejected every time, and all 38 replies with hashtags were rejected. That is one vendor’s sample, not Google’s numbers, but it fits Google’s codes: the replies that get rejected look automated.

How to write automatic replies Google lets through

1. Reply to what the review says. Pick up one detail (the dish, the technician who showed up early, the leak that’s gone) so no two replies read alike.
2. Write a fresh reply for every review. Don’t fill one template with a name; vary the sentences, not just the greeting.
3. Leave out links, hashtags, promo codes and phone numbers. A thank-you doesn’t need them, and Google’s codes name advertising, solicitation and personal information.
4. Keep it to two or three sentences. Google’s API allows up to 4,096 bytes; a short, specific reply beats a long generic one.
5. Reply in the reviewer’s language, the original rather than Google’s translation (how to reply to Google reviews in other languages).
6. Answer within days, not months. In the vendor’s sample above, the average rejected reply was posted about 50 days after its review.
7. Check that replies appear. If you build your own flow, read reviewReplyState back a day later; otherwise, look at your public profile now and then.

ReputeMap doesn’t show Google’s moderation state in its inbox today, so that occasional look at the public profile is worth doing whichever tool posts your replies.

Google drafts replies now too

Google now helps with drafting in two places:

• The Gemini web app. Google’s Business Profile help says Gemini can draft replies to reviews for an owner or manager of only one verified Business Profile, signed in with a personal Google account. It isn’t available in the European Economic Area or the UK.
• A test inside Business Profile. On March 24, 2026, Search Engine Roundtable reported a “Reply to reviews with AI” option showing in some Business Profile dashboards, described as using Google AI to create personalized replies. Search Engine Land covered the same test. The reports describe a test seen on some profiles, not an announced feature.

If you run one verified profile outside the EEA and the UK, Google’s own drafts may be all you need: read, adjust, post. What a drafting button leaves to you is the rest of the job: deciding which reviews get an automatic answer and which wait for a person, hearing about a 1★ review the hour it lands, and handling several locations or client profiles at once.

Do-it-yourself automation vs a review tool

Every route below posts through the same Business Profile API. They differ in who holds the Google connection and how much you build:

Route	Google API approval	Catches new reviews with	Posts the reply with	What you still build
Zapier	Not yours: you sign in with Google	The New Review trigger (Updated Review is a separate trigger)	Create Reply, which can also change an existing reply	The AI step, the star filter, the language rule, any approval step, error alerts
Make	Not yours with the standard connection; Make’s custom-credentials route needs Google’s API form	Watch Reviews	Create/Update a Review Reply	The same
n8n	Yours: the Google credentials come from your own Google Cloud project	The Review Added trigger	The Reply operation	The same, plus hosting if you self-host
Your own script	Yours: a profile verified and active for 60+ days, a website and an access application; until Google approves it, the project’s quota is 0 requests per minute (300 after)	Polling the reviews list	updateReply, which creates a reply or replaces the one already there	Everything, including token refresh
ReputeMap	Not yours: you connect the profile once on Google’s sign-in screen	Reviews written after you switch on Auto-reply to new reviews (paid plans, 4–5★ by default)	The inbox’s own AI draft, in the reviewer’s language	Nothing to build; 1–3★ reviews arrive as alerts with the reply drafted

Zapier’s help lists the same profile requirements Google sets for API access: a profile verified and active for 60+ days, with a website on it. n8n’s Business Profile node isn’t on its list of managed Google sign-ins, so it runs on credentials from your own Google Cloud project.

The connection is the easy part. What breaks in a home-made flow is everything around the reply:

What happens	What goes wrong	The guard
A customer edits their review	A flow that listens for updated reviews fires again, and Google’s reply call replaces the reply that’s already there, including one a person wrote	Trigger on new reviews only, and skip any review that already has a reply
The review is in another language	The AI step may answer in the language of your prompt	Tell it to answer in the language the review was written in
Google rejects the reply	The API call succeeds while moderation is still to come, so a simple flow never hears about the rejection	Read reviewReplyState back later
A 2★ review slips through	A missing star filter thanks someone for a complaint	Filter on FOUR and FIVE and route everything else to a person
The AI step fails	A fallback template posts the same sentence under every review	Post nothing when the AI step fails
You add a location or a client	Each profile needs its own access, and a lapsed one stops replying without telling anyone	An error alert on every step that talks to Google

The details of each API route, including what Google’s public Places API can’t do, are in Google Reviews API, explained.

When a DIY flow is the right call. You run one location, see a handful of reviews a week, already use Zapier or Make, and you’re happy to maintain a flow with an approval step. That costs little and you control every word of the prompt. A tool starts to pay off when there are several locations or client profiles, when 1–3★ reviews have to reach a person within the hour, and when nobody wants to own the flow when Google changes something.

How ReputeMap’s Auto-reply switch works

In ReputeMap, automatic replies are one switch: Auto-reply to new reviews, in the review inbox, on paid plans (every plan from Solo up), answering 4–5★ reviews by default. It is off for every workspace until an owner or admin switches it on. On the free trial, the switch offers to start the paid plan first; it never switches itself on.

• Only new reviews. It answers Google reviews written after it was switched on, never older ones.
• 4–5★ by default. The owner can widen it to all ratings. By default, 1–3★ reviews keep their alert with a drafted reply that waits for a person to tap Publish.
• The inbox’s own draft. Each automatic reply is the inbox’s AI draft, with the saved tone and details, posted in the reviewer’s language by the same language rule as every draft.
• No fallback text. If the AI is unavailable nothing is posted, and a reply a person is already drafting always wins.
• Marked afterwards. The inbox marks each one “Replied automatically”.
• Easy to stop. Switching it off stops it. It also switches itself off if the subscription lapses, and switching it back on never answers the reviews that arrived in between.

The complaints take the other path. When a 1–3★ review lands, the alert email quotes a reply the AI has already drafted, and Review & publish reply → opens a personal, single-use, 7-day link to a page with no login: the review, the draft you can edit with tone chips, and one Publish to Google button. The Monday digest carries the same link. In a Telegram private chat, ✅ Publish draft posts exactly that text in one tap, and ✏️ Edit & publish lets you change it first. A Telegram group gets the alert without publish buttons, and WhatsApp carries the alert only. On the free trial, replies are drafted inside the first 2 alerts; on paid plans, inside every alert. How the alerts reach the right person is on the negative review alert software page.

Setting it up

1. Pick a plan and connect Google. Connect each Business Profile on Google’s own sign-in screen; there’s no API application to file.
2. Set the reply tone. The automatic replies use the same saved tone as the drafts you see in the inbox.
3. Switch on Auto-reply to new reviews in the inbox. It’s on paid plans only, so on the trial it offers to start your plan first. Leave it at 4–5★, the default.
4. Keep the 1–3★ alerts on. Email or a Telegram private chat, so every complaint reaches a person with its reply drafted.

The switch, its rating options and the “Replied automatically” label are explained in the review inbox documentation.

When automatic replies aren’t the right fit

• One location, a couple of reviews a month. Write them yourself: a two-line reply from the owner reads warmer than anything generated, and it takes two minutes a week.
• Healthcare, legal and other confidential work. Even a thank-you can confirm that someone was a patient or a client. Many practices keep a person on every reply.
• Nobody watches the complaints. Automating the praise while 1–3★ reviews sit unread only makes the profile look tended. Set up the alerts first.

Sources (checked October 1, 2026)

• Google Business Profile APIs, REST resource: accounts.locations.reviews: reviewReplyState (PENDING, REJECTED, APPROVED), policyViolation and its codes, the 4,096-byte reply limit, the star-rating values.
• Google Business Profile APIs, Method: accounts.locations.reviews.updateReply: creates a reply or updates the existing one; verified locations only.
• Google Business Profile APIs, Prerequisites: a profile verified and active for 60+ days, a website, the access application, 0 QPM before approval and 300 after.
• Google Business Profile Help, Manage customer reviews: replies checked against content policies, usually within 10 minutes and sometimes up to 30 days.
• Google Business Profile Help, Manage your Business Profile on Google with the Gemini web app: drafting replies, one verified profile, a personal Google account, not available in the EEA or the UK.
• Search Engine Roundtable, Google Tests Reply To Reviews With AI, March 24, 2026, and Search Engine Land, Google Business Profile tests AI-generated replies to reviews, March 2026.
• Local Search Forum, Google’s review reply rejection filter: what 12,752 rejected replies reveal, posted by GMBapi on June 9, 2026.
• Zapier Help, “How to get started with Google Business Profile on Zapier”, and Zapier’s Google Business Profile app page: prerequisites, the New Review and Updated Review triggers, the Create Reply action.
• Make Help, “Google Business Profile”: the Watch Reviews and Create/Update a Review Reply modules, the standard and custom connections.
• n8n Docs, “Google Business Profile node”, “Google Business Profile Trigger node” and “Google OAuth2 single service” credentials.

This page is written by ReputeMap, which makes one of the options compared above. ReputeMap is not affiliated with Google, Zapier, Make or n8n.

See the plans: on any paid plan you can switch on automatic replies for new 4–5★ reviews, and every complaint arrives with its reply drafted. Every plan starts with a 14-day free trial: card required, cancel anytime, plans from $19/mo for one location, and setup takes about 3 minutes.