What you are seeing
This fix traces the code from scan to final page and corrects the link at the point where it goes wrong. You will decode the payload, follow every redirect, and fix the payload, the redirect, or the destination page, whichever is actually at fault. Verify the full journey on two phones before you reprint, because a fix that only corrects the first hop can still land on the wrong page.
Likely causes
1.
Typo in the encoded URL — Quick test: decode the payload and compare the URL with the intended address character by character.
2.
Old artwork reused for a new campaign — Quick test: check when the artwork file was created and which campaign it belonged to.
3.
Redirect chain points elsewhere — Quick test: follow the redirect chain hop by hop and note where it diverges.
4.
Dynamic code destination was changed — Quick test: check the redirect settings and change history for the dynamic code.
5.
Lookalike domain or typosquat — Quick test: compare the decoded domain with your real domain letter by letter.
Step-by-step fix
Step 1: Decode the payload and write down the exact URL it contains.
Step 2: Compare that URL with the intended destination character by character, including the domain ending.
Step 3: Open the encoded URL in a browser and follow every redirect to the final page, noting each hop.
Step 4: If the encoded URL is wrong, regenerate the code from the correct URL.
Step 5: If the encoded URL is right but a redirect is wrong, fix the redirect rule or the shortener setting.
Step 6: If the destination page itself is wrong, fix the page or restore the correct content.
Step 7: Test the corrected code on two phones, following it all the way to the final page, and confirm the page is the intended one.
Putting this into practice
In practice, keep the intended destination written on the job file and check the proof against it out loud if you can. A second pair of eyes on a URL catches the typo that the person who typed it keeps missing. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Fixing the printed code without checking the redirect chain, so the new code lands on the same wrong page.
- 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 opens the wrong URL will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that opens the wrong URL.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The decoded payload matches the intended destination exactly
- Every redirect hop lands on the intended page
- The final page is the intended one 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
- [QR redirect chain viewer](/qr-redirect-chain-viewer)
- [QR expiry checker](/qr-expiry-checker)
- [QR batch validator](/qr-batch-validator)
- [QR typosquat checker](/qr-typosquat-checker)
- [QR safety checker](/qr-safety-checker)
- [UTM builder](/utm-builder)
- [blog](/blog)
