What you are seeing
The code scans, but the page belongs to someone else: another business, a stranger's profile, or content you have never seen. This is the most alarming QR failure, because visitors may assume you sent them to that content. The usual causes are mundane rather than sinister: a reused code file, a mistyped domain, a redirect that was changed, or a sticker placed over your code. Treat it as urgent regardless of the cause, because every scan until it is fixed goes to the wrong owner.
Likely causes
1.
Sticker placed over the original code — A printed code pasted over yours sends visitors to the other person's destination. Test: inspect the physical code for a raised edge, a second layer, or a mismatch with the printed URL beside it.
2.
Reused code file from another job — A code file copied from another project carries its original destination. Test: check the artwork history and the destination it encodes.
3.
Typo in the domain — A small typo can turn your domain into a domain owned by someone else. Test: compare the decoded domain with your real domain letter by letter.
4.
Redirect changed or hijacked — A redirect rule or a shortener entry that was edited, or an account that was compromised, can send visitors elsewhere. Test: follow the redirect chain and check the change history.
5.
Short code or shortener collision — A short link can be mistyped or can collide with someone else's short link. Test: open the encoded URL on its own and confirm whose content it serves.
Step-by-step fix
1. Stop using the code immediately and take the physical copy down if it is in a public place.
2. Decode the payload and write down the exact URL it contains.
3. Compare the decoded domain with your real domain, letter by letter.
4. Inspect the physical code for an overlay sticker or a second layer.
5. Check the redirect settings and change history for the code.
6. Replace the code with a fresh one from your own domain and verify the destination on two phones.
Putting this into practice
In practice, printing the destination URL beside the code is the cheapest protection against this failure. Visitors can compare the scanned address with the printed one, and a sticker overlay becomes obvious the moment the two disagree. Pair that with regular physical inspections of public codes. 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
- Leaving a tampered code in place while investigating, so more visitors reach the wrong content.
- 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 shows someone else's content will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that shows someone else's content.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The decoded domain is your own domain
- The physical code shows no overlay or second layer
- The replacement destination is verified 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 safety checker](/qr-safety-checker)
- [QR typosquat checker](/qr-typosquat-checker)
- [QR phishing pattern trainer](/qr-phishing-pattern-trainer)
- [QR allowlist builder](/qr-allowlist-builder)
- [QR tamper evidence planner](/qr-tamper-evidence-planner)
- [QR scan log](/qr-scan-log)
