How to ask for Google reviews: text and email templates

Google review request templates you can use

Replace the bracketed details before sending. Use a channel the customer has agreed to receive these messages through. These are wording examples, not complete messaging-compliance templates; your provider may require additional sender or opt-out details.

Our suggested starting limit is one request and, where appropriate, one reminder several days later. That is a practical boundary, not a proven best timing rule. Stop if the person declines, opts out, or has already reviewed. Do not turn silence into a sequence of repeated nudges.

How to get your Google review link

Use the link for your actual Business Profile—not your account-management page or a search result that might show another company.

1. Open your Business Profile while signed into the account that manages it.
2. Select Read reviews, then Get more reviews.
3. Copy the review link. Google also provides a downloadable QR code through a computer browser.
4. Open the copied link on a phone and confirm that it shows the correct business and review destination. Test the printed QR code before ordering a batch.

Those controls come from Google’s review-link instructions; interface wording can change. Customers need to sign into a Google Account to submit a review, according to Google’s review guidance. A sign-in screen does not necessarily mean your link is broken.

An NFC card or QR sign can open that same destination. It should not promise to post a review automatically. Include clear words such as “Share your experience on Google,” and a readable link as a fallback. Our NFC and QR guide explains the physical options in more detail.

When should a small business ask for a review?

Choose an observable service milestone, such as a completed visit or a finished project handoff. Do not trigger the message because a job was merely scheduled, an estimate was approved, or a payment link was opened. None of those means the customer has experienced the finished work.

For recurring work, choose a consistent milestone after the relationship has begun rather than requesting another review after every visit. Apply the same approach across customers, regardless of whether you expect praise or criticism.

A hypothetical window-cleaning workflow might put the request on the office’s checklist after completion is confirmed. The employee records the work; the office checks the contact preference and previous requests; then the message goes out. This is an example to adapt, not a claim about a client’s results.

What should you avoid when asking?

Google’s fake-engagement and rating-manipulation policies prohibit incentives and selectively soliciting positive reviews. Keep the process neutral:

• Do not offer a discount, gift, payment, or prize in exchange for a review—even an “honest” one.
• Do not ask only satisfied customers, or send a Google link only to people who first select a high score in a private survey. That filtering is often called review gating.
• Do not ask for five stars, required keywords, employee names, or a review you wrote for the customer.
• Do not pressure people to review while you watch or make a review a condition of service.
• Do not buy reviews or recruit people with a conflict of interest to pose as ordinary customers.

Offer customer support to everyone. A private contact option can sit alongside the review invitation, but it should not replace the public link for people with complaints.

Make asking a small, repeatable part of the job

Start with a short checklist before you buy another subscription:

1. Confirm the trigger. Record the completed work or agreed milestone.
2. Check permission and history. Confirm the appropriate channel, opt-out status, and whether someone already sent a request.
3. Send the approved message. Check the name, business, and link. A duplicate completion update should not send a duplicate request.
4. Record the outcome. Distinguish prepared, sent, failed, declined, and follow-up due. A link click is not proof that a review was posted.
5. Give replies an owner. Questions and complaints should reach a person who can respond.

Track only the details you need: customer, job, channel preference, request date, delivery status, and follow-up decision. Do not ask for a screenshot of the rating as proof. If you cannot reliably tell whether someone reviewed, avoid aggressive reminders rather than guessing.

A saved message and a checklist may be enough. If the process spans your scheduling tool, customer records, and texting service, a focused integration can be scoped to connect those steps. Automation should remove repetitive administration, not decide which customers are allowed to speak.

Read the feedback, not just the star count

MU Extension’s Post, Engage, Grow recommends maintaining business listings, responding courteously to questions and complaints, and setting a regular reminder to review your presence. The practical lesson is that requesting reviews needs a matching habit of reading them.

Its social listening guide (PDF) goes further: collect recurring themes and turn them into next steps. For example, repeated confusion about arrival times suggests a scheduling-message problem. That is something you can improve, not merely a rating to offset.

For a difficult review, keep the public reply short and factual, acknowledge the concern, and offer a business contact for discussing specifics. Do not publish addresses, invoices, or private customer details to defend yourself. Google’s response guidance emphasizes privacy and constructive replies.

The Missouri resources provide broader marketing context. For what you may request on Google specifically, follow Google’s current platform rules. None of these resources guarantees more reviews, better rankings, or additional jobs.

You may only need one small improvement

Pebble Creek Media grew from building the website and operating system around Pebble Creek Landscaping & Lawn. Our approach is to connect the next useful step to the work already happening—not add a tool simply because it exists.

That might mean a programmed review tag, a clear customer-facing page, or a completion-to-follow-up workflow. Our small business solutions cover these focused projects; you do not need a full operating system just to share a review link.

If requests, customer replies, and job history are all scattered, we can also evaluate a custom operating system built around the larger process. Integrations and messaging costs depend on scope. Tell us where the handoff is getting lost, and we can help decide how small the solution can be.