Google Review QR Codes: The Rules on How You Ask

A QR code on the receipt that opens your Google review page is fine. Google publishes documentation on making one.

What gets businesses in trouble is not the code. It is the funnel some tools put behind it, and the penalty is worse than most people printing these realise.

The code itself is allowed

Google Business Profile provides a short review link and a QR code for it directly. Using that link as the destination is the supported path, and putting the resulting code on a card, a receipt, a window or a vehicle is an ordinary thing to do.

So the format is not the question. The question is what you do with the people who scan it.

Review gating, and why it is worth understanding

Review gating is asking customers how they feel first, then sending the happy ones to your public profile and the unhappy ones to a private feedback form.

It is popular because it looks like customer service and works like a filter. It is also prohibited.

The part worth sitting with is the scope of the penalty. Enforcement is not limited to the reviews collected through the funnel. It can extend to every review on the profile, including the genuine ones you collected properly over years beforehand.

That turns a tactic that nudges your average up by a few tenths into one that can remove your entire review history. Even read purely selfishly, it is a bad trade.

The four rules, plainly

Ask neutrally. "We would appreciate a review" is a request. "Leave us a five-star review" instructs people what to say, which is not allowed.

Ask everyone. The same request, to every customer, regardless of how the interaction went. The moment who gets asked depends on predicted sentiment, you are gating.

Offer nothing in exchange. No discount, no free item, no entry into a draw, no loyalty points. Incentivised reviews are treated as fake engagement, and this applies to incentives for changing or removing a review as well as leaving one.

Do not write it for them. No suggested wording, no phrases to include, no list of things to mention.

Where a private feedback code fits

You can still want to hear about the broken thing before it becomes a public review. That is a legitimate thing to want, and there is a compliant way to do it.

Run the feedback code as its own thing, visible to everyone, rather than as a fork in the review path. A card on the table that says "tell us how we did" alongside, and independent of, a review request breaks no rule, because nobody is being sorted. Everyone can see both. Everyone can use either.

The difference is not cosmetic. Gating is the conditional: if you think they are unhappy, then they see a different destination. Remove the conditional and you have two ordinary requests.

Why the code should be dynamic

Almost every review code should be a dynamic code rather than one encoding the review URL directly.

Review destinations change more than people expect:

• You open a second location with its own profile.
• You rebrand, and the old profile is no longer the one you want reviewed.
• The directory that mattered last year is not the one that matters now.
• A platform changes its link format, which has happened before.

With a dynamic code the printed pattern encodes a short link belonging to you, and the destination is a setting. Every card, receipt and decal you have already printed follows the change. With a static one, the review URL is physically part of the pattern, and a changed link means a reprint of everything. That is the argument in full: see editing a QR code after printing.

Placement decides whether it is scanned

Review codes fail from placement far more often than from design. Scans cluster tightly around the moment someone is already pleased and already holding their phone.

• On the receipt or invoice, where the phone is out.
• On the card handed over at the end, not the one at the entrance.
• By the door on the way out, at eye level.
• In the follow-up email, as an image, which is the same code doing double duty.

A code by the entrance is scanned by people who have not experienced anything yet, which is the wrong moment and produces nothing.

Check what sits between the scan and the review

One last thing worth testing before printing. Some free QR generators fund themselves by serving a full-screen advertisement between the scan and the destination, usually with a countdown.

On a review request that advertisement is standing between a willing customer and the thing you asked them to do, which is close to the worst possible place for it. It takes ten seconds to check and here is the test.

Worth checking whether the codes expire too, for the same reason: a review code printed onto a thousand receipts is not something you want to reprint because a plan lapsed.

The short version

Print the code. Point it at your Google review link, or wherever your customers actually read reviews. Ask everyone, ask neutrally, offer nothing, and do not tell them what to write.

Then make it dynamic, so the one decision you are locking into print is the artwork rather than the destination.

More on the practical side in review QR codes.