For a business with several locations, a branch-specific review link should match the branch name to the destination a visitor will open. It is not enough for a link or code to work; it must open the correct Business Profile. Do not assume that one card or a general link automatically routes visitors to the nearest location. Unless the selected tool proves that behavior, treat destination selection as a manual step that needs verification.
Google lets businesses share a review link or QR code for a Business Profile through its official guidance. Pair that capability with an internal branch-to-link register, and do not describe the register as automatic routing.
Build a three-part branch register
Keep one approved source of branch information. A simple register can include:
| Field | What to record | Check before release |
|---|---|---|
| Internal branch label | A clear team code and customer-facing name | Does it match the location visitors recognize? |
| Location description | Enough detail for staff to distinguish nearby sites | Does it identify the branch without unnecessary data? |
| Business Profile link | A review link collected from the intended profile | Does it open this branch rather than a nearby location? |
| Touchpoint | Where the card or link will be shared | Is the item assigned to the branch in the same row? |
| Review date and owner | Who checked it and when | Who will recheck after a closure or move? |
Do not put login details or customer information in the register. Its purpose is to match public branch details to the correct public destination. Limit editing according to your own internal procedures and keep a clear record of the latest approved version.
Test each branch-specific review link separately
Before sharing a link or printing a new item:
- Open the intended branch’s Business Profile using Google’s official tool.
- Create a shareable review link for that profile and enter it in the matching row.
- Open the link in a new window or on another device and verify the business name and location.
- Compare the destination with the card or other touchpoint assigned to that branch.
- Ask a second person to review the row when two branches have similar names.
- Recheck after a link changes, a location closes or a touchpoint moves.
If a business serves visitors in more than one language, make sure the invitation does not confuse them about the branch they visited. A prompt could say, “Choose the location you visited, then share feedback if you wish.” Do not use a button or intermediary page that suggests automatic routing unless you have verified that the actual tool does this.
Connect each printed item to its branch
Keep the branch name or an internal code in the material register; it does not necessarily need to appear in the public-facing design. Before printing or distributing a new item, reopen the link and scan the actual printed code. A QR pattern can look fine while pointing to the wrong location because artwork from another branch was reused. If a selected product has separate codes, check that product’s specifications; do not infer the number of links from its category or size label.
ADMAL’s Google review link check before printing provides a destination-check framework. If a visitor receives the wrong link, acknowledge the error and correct the item; do not ask them to review a branch they did not visit.
Fair practices across locations
Invite honest feedback consistently. Do not send satisfied visitors to the public review link while withholding it from other visitors. Do not offer incentives or ask for a positive review. Google’s prohibited and restricted content policy explains the rules that apply to reviews and incentives.
A branch owner can recheck the register at the start of a work cycle or after a change. That is a suggested internal process, not a monitoring service provided by ADMAL. Keep a short log with the branch, tested link, reviewer and date. Do not add customer names or review text to the check sheet.
A handoff checklist for marketing and branch teams
- Confirm the correct Business Profile for each branch.
- Match each link to the touchpoint assigned to that location.
- Verify the name and address after opening every link.
- Test the printed code from the physical sample.
- Mark old materials for replacement when a destination changes.
- Tell staff that a review is optional and no incentive is offered.
- Record who checked the destination and when, without personal data.
For related review touchpoints, see ADMAL’s review card and stand comparison and Smart Reviews archive. These resources help with the type of access point; the accuracy of each branch destination still requires testing that branch’s own link.
Control the handoff when a branch link changes
A location name, Business Profile or review link can change. Decide who may edit the link register, who checks the change and how obsolete printed pieces or message templates are withdrawn. Do not leave an old branch link in a shared template after a location closes or moves. Keep a review date and source for each link; do not store account passwords or staff login details in the register.
In a small team, one person may prepare the entry and another can open the destination before printing. In a larger team, include the branch name and approval date in the design request itself. This simple handoff reduces mix-ups without implying automatic location routing or an unverified integration.
