What you need before programming
Programming a Google review tag means writing an HTTPS URL to an NFC chip in the standard NDEF format. You need the business's official Google review link, an NDEF-compatible tag, an NFC-capable phone or writer, and software that can write a URL record.
Do not lock the tag during the first write. Locking can make the record permanently read-only. Test the full destination and final placement before making any irreversible choice.
1. Copy the official Google review link
On a computer, open the verified Google Business Profile, select Read reviews, then Get more reviews, and copy the provided review link. Google also offers a QR code from the same interface.
Open the copied link in a private browser window before writing it. Confirm that it resolves to the correct business and reaches the intended review experience without requiring an owner account.
2. Decide between a direct link and a managed URL
A direct tag stores Google's review link on the chip. It is simple, but changing the destination later requires rewriting every unlocked tag or replacing a locked one.
A managed tag stores a stable HTTPS URL controlled by the business or service. That URL can redirect or open an editable venue page, allowing the destination and surrounding guest actions to change without rewriting the hardware.
| Decision | Direct review URL | Managed venue URL |
|---|---|---|
| Initial setup | Write Google's link | Write a stable controlled URL |
| Change later | Rewrite or replace the tag | Update redirect or page |
| Guest options | Review destination only | Reviews plus other venue links |
| Activity reporting | Not included by the tag | Possible through the managed page |
3. Write an NDEF URL record
Use an NFC writer that explicitly supports NDEF URI or URL records. Create a URL record, paste the HTTPS destination exactly, and write it to the tag while holding the phone near the chip.
NDEF is the cross-platform data format used by NFC Forum tags. For broad Android compatibility, use a standardized NFC Forum tag type and an ordinary HTTPS URL rather than a vendor-specific payload.
- Choose URL or URI as the NDEF record type.
- Paste the tested HTTPS destination.
- Write one tag and wait for a confirmed success response.
- Move the tag away from the writer before testing so the write session is fully complete.
- Repeat only after the first tag passes the full test.
4. Test before locking or deploying
Wake a recent iPhone and hold the top edge near the tag. Unlock an NFC-enabled Android phone and hold the back near the tag; NFC may need to be enabled in Settings. Confirm that both open the intended business.
Then test the tag on its final surface. Metal can interfere with an ordinary NFC antenna, so metal tables, stands, or bar tops need an on-metal tag. Test through any holder or adhesive layer that will remain in production.
5. Label and document the tag
A working chip is not ready for a venue until the placement and ownership are known. Record the venue, room, placement, programmed URL, and test result. Use a short human label that an operator will recognize later.
If the tag opens a managed page, keep the public URL stable and make future changes in the page or redirect system. Rewriting deployed tags should be the exception.
How Tap handles programming
Tap tags arrive assigned, programmed, and QA-checked for the venue. The physical tag opens a stable Tap URL, while the operator edits menus, reviews, reservations, events, and other guest links from the dashboard.
That approach is useful when a venue wants more than a one-time DIY review link or needs multiple labelled placements across a restaurant or bar.