What you are seeing
The code scans, but the review page will not load: a blank page, an error, or a page that never finishes. The scan worked, so the fault sits in the review destination: the link, the review platform, or the page itself. A review code that fails loses the feedback at the moment the visitor is most willing to give it, which is why it deserves a fast fix. The fix is to test the review destination on its own, then the QR journey.
Likely causes
1.
Review link expired or changed — A review link that changed, expired, or was replaced can fail for every visitor. Test: open the review link directly.
2.
Review platform blocking the visit — A review platform can block visitors who are signed out, in the wrong region, or on an unsupported browser. Test: open the link in a second browser and while signed in.
3.
Redirect dropping the review target — A redirect can strip the review identifier from the link, landing visitors on a generic page that does not load. Test: follow the redirect chain and watch the review identifier.
4.
Page script or pop-up blocking the form — A script error or a blocking pop-up can stop the review form from appearing. Test: check whether the page loads without the form.
5.
Link mistyped in the payload — A mistyped review link can land visitors on a page that does not exist. Test: decode the payload and compare the link with the intended review link.
Step-by-step fix
1. Decode the payload and write down the exact review link it carries.
2. Open the review link directly, outside the QR journey.
3. Follow the redirect chain and check that it preserves the review target.
4. Fix the link, the redirect, or the page, whichever blocks the review form.
5. Regenerate the code if the payload carries the wrong link.
6. Retest by scanning the code and reaching a working review form on two phones.
Putting this into practice
In practice, test the review destination on its own before you blame the code. A review link that fails when opened directly is a destination problem, and no QR fix can repair it. A link that works directly but fails from the code points at the payload or the redirect. Keep a short note of what you tested, what failed, and what you changed, so the next person starts from evidence rather than guesswork. A fix that is written down survives staff changes and reprints; a fix that lives only in memory gets repeated.
Common mistakes to avoid
- Assuming a review QR code still works months after launch without ever retesting the destination.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that scans but the review page will not load will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that scans but the review page will not load.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The review link loads directly in a phone browser
- Redirects preserve the review target
- Scanning reaches a working review form on two phones
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [survey QR code generator](/survey-qr-code-generator)
- [feedback QR code generator](/feedback-qr-code-generator)
- [QR payload inspector](/qr-payload-inspector)
- [QR redirect chain viewer](/qr-redirect-chain-viewer)
- [QR expiry checker](/qr-expiry-checker)
- [UTM builder](/utm-builder)
