What you are seeing
This fix traces the language choice from the code to the page and pins the correct language. You will check the encoded URL, the site language settings, and the browser behaviour, then repair whichever layer chose wrong. Test with the language your audience actually uses, not just with your own browser defaults.
Likely causes
1.
Link points at the wrong language version — Quick test: compare the encoded URL with the address of the correct language version.
2.
Site picks language from the visitor browser — Quick test: open the same URL in a browser set to the expected language.
3.
Redirect drops the language part of the address — Quick test: follow the redirect chain and watch the language segment.
4.
Language switcher not stored for QR visitors — Quick test: pick the language on the site, then follow the QR journey again.
5.
Content not translated for that page — Quick test: check whether a translated version of the page exists.
Step-by-step fix
Step 1: Decode the payload and write down the exact URL it contains.
Step 2: Open the correct language version of the page and copy its exact address.
Step 3: Compare the two addresses and note where the language segment differs or is missing.
Step 4: Follow the redirect chain and confirm it preserves the language segment all the way to the final page.
Step 5: Fix the redirect or the site language rule if it drops or overrides the language.
Step 6: Regenerate the code from the correct language address if the payload was wrong.
Step 7: Retest on two phones, including one with a different browser language, and confirm the page appears in the intended language.
Putting this into practice
In practice, keep one proof per language version when a code is printed beside translated material. A proof in the wrong language is easy to miss if you only check that the page loads. 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
- Copying a link while viewing the page in the wrong language and printing it beside text in another language.
- 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 the wrong language will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that shows the wrong language.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The encoded URL points at the intended language version
- Redirects preserve the language segment
- The page appears in the intended language 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)
