A customer who has just paid is the easiest person to ask for a review, and the hardest to send on a scavenger hunt. Telling them to open Google, search your business, scroll past the map and tap “Write a review” loses the moment. A google review qr code collapses that journey into one tap: the review form opens with the star rating on screen. The code takes a minute; the link inside it, the wording and the timing decide whether the scan becomes a published review.
This guide is part of the free QR code generator guide. It covers the only link worth encoding, placement, policy and the scan test that prevents a silent failure at the counter.
Why the direct review link wins
There are three links a business owner can put behind a QR code, and only one is useful. The ordinary Google Maps listing opens photos, hours, directions and a review section the customer still has to find. The Business Profile dashboard link asks for a login and shows internal controls, which is worse. The review form link Google generates for the location opens a page with the business name and five stars, ready to rate.
That direct link matters because friction is cumulative. The customer needs a Google account, a connection and patience to finish. Every extra tap before the form is a chance to abandon. The direct link removes the searching and the doubt about which listing is correct. It does not remove the sign-in requirement or write the review. It puts the form where the customer already is.
A QR code also beats a printed URL because nobody has to type a 30-character address. The pattern carries the full link, including the place identifier, so it cannot be mistyped.
Get your review link from Business Profile
Sign in at business.google.com with the account that manages the location, choose the location if you manage several, and find the reviews card. Google labels the action “Get more reviews” or “Ask for reviews” depending on the dashboard version. The link it offers opens the review form for that specific location, which is exactly what you want to encode.
Google also publishes a direct form at https://search.google.com/local/writereview?placeid=YOUR_PLACE_ID, with the place ID from the Maps Platform Place ID Finder. This URL is useful when the dashboard link is awkward to copy, but it is long and easy to break by hand. Copy it whole and test it signed out.
- Never encode the Maps listing URL. It adds search steps and often opens the Maps app instead of the form.
- Never encode the dashboard URL. It asks for a login and exposes controls customers should not see.
- One location, one link. One per branch, each labelled.
- Re-check after a listing change. Listing merges and name changes can break the link.
Where to place the code
Placement decides more than graphic design. The code should appear when the customer is most satisfied and least rushed: after payment, after a successful appointment, or while waiting for takeaway. A code by the door competes with traffic and rain. A code on the bill folder arrives while the customer is still seated and still thinking about the service.
| Placement | Viewing distance | Minimum size | Why it works |
|---|---|---|---|
| Bill folder or receipt sleeve | 30–40 cm | 3–4 cm | Arrives at payment, when the visit is fresh |
| Counter card | 50–80 cm | 5–8 cm | Visible while waiting, easy for staff to point at |
| Table tent | 40–70 cm | 4–7 cm | Works during a long meal without staff prompting |
| Reception frame | 1–2 m | 10–20 cm | Seen while queuing or checking in |
| Takeaway bag sticker | 40–60 cm | 4–6 cm | Extends the ask beyond the shop |
The sentence next to the code does more work than the code. “Loved your visit? 10 seconds” sounds friendly but quietly filters: a customer who had a mixed experience reads it as an invitation for happy people only. Google’s policies discourage selective solicitation, and the practice distorts the feedback you need. Use neutral wording such as “Tell us about your visit — two minutes.” Staff can add a spoken prompt at payment.
Size, contrast and scan testing
Use the same rule as any print code: minimum width in centimetres is roughly viewing distance divided by 10, with a 2 cm floor for short URLs. A Business Profile review link is usually short — often a g.page/r/... address — so the pattern is sparse. That does not make 2 cm sensible on a folder picked up and photographed at an angle. Give it 3 cm at 30 cm, 5–6 cm at 50–60 cm, and 10–20 cm for a poster read from two metres.
Export 512px for prints up to about 5 cm and 2048px above that; never upscale. Keep black modules on white, leave the four-module quiet zone untouched, and choose matte lamination. A glossy card reflecting a ceiling light is the most common reason a review code fails at a counter. The full distance table is in the QR code size and print guide.
Test before the print run. Print one copy at 100%, disable “fit to page”, then scan it signed out of Google with two phones. The form should appear without a login prompt or permission error. Scan at the real distance under the real lighting, and try an older Android as well as an iPhone. If the camera struggles, the print is the problem; the not-scanning fixes walk through size, contrast, glare and file faults.
Google policy: ask everyone, never gate
Google’s prohibited content policy bans incentives: no discount, free dessert, prize draw or staff bonus tied to a review. It also bans review gating, the trick of asking only customers who answer a satisfaction question positively. A code that opens the review form for every customer is fine. A code that opens a screening survey first is not. Reviews can be removed and ratings filtered.
Ask once, ask everyone, and never write the review for them. Do not stand over the customer or hold the phone. The code should make the honest path easy, not manufacture a rating. If a customer had a bad experience, the same code gives them a way to say so before they tell the neighbourhood. That is useful information arriving while you can still act on it.
Two worked setups
Example 1 — neighbourhood café, Kochi. A 28-seat café prints 4 cm codes on matte card stock for the bill folder. The destination is the Business Profile review link, generated at 2048px because the folder sits 30–40 cm from the customer’s phone and is handled constantly. The line above the code reads “Tell us about today’s visit — two minutes.” Staff slide the folder across with the card facing up and say one sentence. It is tested at 40 cm in daylight and pendant light on an iPhone and a budget Android. If the review link changes after a listing merge, only the folder card is reprinted; the table tents use a separate file.
Example 2 — dental clinic, Jaipur. A two-chair clinic places a 6 cm framed code at reception, with a 3 cm version on the appointment card. The frame is 60 cm from a seated patient, so 6 cm gives a comfortable margin over the distance rule. The card asks after the appointment is booked, not while the patient is in the chair. The frame is matte, fixed flat to the wall and wiped weekly. The receptionist can point to it if someone hesitates, but does not hand over a phone or dictate the wording. A small line reads “Reviews help other patients choose carefully.” That sentence is true whether the review is glowing or critical.
Measure reviews, not scans
A static QR code carries no analytics. You will not know how many people scanned it, and any service promising scan counts is routing your link through its own server. For a review code that trade is wrong: the link is short, the destination is Google, and a redirect that expires would break every printed card. Measure new reviews week by week and the proportion that mention a server, a dish, a treatment or a repair. Ask staff to note when a customer says they scanned the code; a paper tally at the till is enough.
Keep the link and the code in one document: the review URL, the date it was last tested, the print files and who approved the wording. When a manager changes, the next person can regenerate the code in a minute.