So are NFC review cards allowed, or not?
Straight answer: the card is a tool, and tools aren't what Google's policy targets. Behavior is. An NFC card that opens your review page is mechanically no different from a QR code or a plain link, and none of those are banned. What Google prohibits is requiring or pressuring a customer to review while they're on your premises, and requesting that the review include specific content.
That's where the popular use runs straight into the wall. The whole pitch is speed and immediacy: catch the customer in the moment, tap their phone, get the review before they walk away. That immediacy, on-site, with you standing there, is the textbook definition of the on-premises pressure the 2026 updates were written to stop. The card is fine. The over-the-shoulder ask is not.
- Google's prohibited & restricted content policy
Google's rules: no fake engagement, no incentives, and no requiring or pressuring customers to review while on the premises.
The ways these cards get used are the ways that break the rule.
Run the common NFC pitches against the on-premises test and most of them fail on the spot. If the review is meant to happen right now, while the customer is with you, it's the pattern Google is enforcing against.
- Tapping a customer's phone on the card at the counter to review before they check out.
- Handing the card over in the driveway and waiting while they tap and type.
- A card by the register reading 'tap here to leave a review before you go.'
- Any use where the expectation is a review on the spot, under your eye.
Even a compliant tap dumps the customer at a blank box.
Set the policy question aside for a second, because there's a problem the NFC pitch conveniently never mentions. The card's only trick is opening your Google review page. It does nothing about what happens next, which is the customer staring at an empty text field wondering what on earth to type. That blank box is where most reviews die, tap card or no tap card.
So even in the rare case where an NFC card gets used with zero pressure, it solves the wrong half of the problem. It gets the customer to the page faster, then abandons them at the exact moment they were always going to freeze. Speed to a blank box isn't the bottleneck. The blank box is the bottleneck. The card just gets you there quicker.
- An NFC card opens the review page. It does nothing about the blank box after it.
- Most reviews are lost at 'what do I even say,' which the card can't help with.
- Arriving at a dead end faster is still a dead end.
Ask after the visit, and solve the blank box, not the tap.
The approach that's both compliant and effective is the exact opposite of the NFC pitch. Instead of catching the customer on-site and rushing them to a blank page, send the request after the visit so they finish it on their own time, on their own device, from their own account. No on-premises pressure, nothing to trip the policy.
Then fix the part the card ignores. Give the customer a guided link that lets them tap what stood out and approve a draft in their own words, so the ask that used to die at the blank box actually gets finished. That combination, a no-pressure ask after the visit plus a format that removes the writing, is what the NFC card was pretending to be all along.
small Talk is built exactly that way. The request goes out after the job, the customer finishes it from their own account, every customer gets the same ask, and the draft comes from their own taps, not a script. No plastic, no on-premises pressure, and the blank box is gone.
Next step
Skip the tap card. Send a link that actually gets finished.
Send one guided review request after your next job instead of tapping a card on-site. You stay clear of the on-premises rule, and the review gets written because the customer isn't left staring at a blank box.