A QR code can scan perfectly and still send people to the wrong page, a login screen, or a link that stops working after your flyers are printed. Use this pre-print checklist to verify the destination, follow redirects, and test the printed-size code on multiple phones.
Key Takeaways
- Open the exact URL encoded in the QR code and confirm the page and its content are correct.
- Follow every redirect and check that the final page loads securely and works for someone who is signed out.
- Test the code on more than one device and camera app, including a print-sized proof.
- Decide who controls the destination after printing. A static QR code does not update itself if its encoded URL changes or stops working.
Pre-print checklist
1. Confirm the encoded destination
Scan the QR code or inspect its encoded URL with a trusted QR reader. Compare it character by character with the URL you intended to use. Check the domain, path, spelling, and any required campaign or event parameters. A single typo can send visitors somewhere unexpected.
Open the URL directly in a browser, too. This checks the destination itself rather than only whether the QR code can be recognized. If the URL contains tracking parameters, confirm that they are present and that the page still works with them.
2. Check redirects and the final page
Short links and campaign links often redirect. Follow the link in a browser and note where it ends up. Confirm that each hop is expected, the final destination belongs to the organization or service you intended, and the final page uses HTTPS. Be cautious if the link passes through an unfamiliar domain or redirects to an unrelated page.
If you have curl installed, you can inspect the response headers for a real destination URL. Replace the placeholder with the URL encoded in your QR code:
curl -sS -L -D - -o /dev/null -w '\nFinal URL: %{url_effective}\nHTTP status: %{http_code}\n' 'YOUR-QR-DESTINATION'
-L follows redirects, and -D - prints the response headers, including headers from redirect responses. Check the Location headers to review the chain, then compare the final URL and status with what you expect. This command makes a request from your computer; it does not establish that every phone, network, or browser will behave the same way. If a site behaves differently for automated requests, verify it in a normal browser as well.
3. Check mobile usability and access
On a phone, open the final page and complete the action the QR code promises, such as viewing event details, opening a menu, or registering. Check that text is readable, buttons are usable without excessive zooming, and important content is visible without a desktop-sized layout.
Test while signed out, preferably in a private or incognito browser window. If the page requires a login, decide whether that is intentional and whether the people scanning the code will have the account they need. A page that works for its owner while signed in may show visitors a login wall or an access-denied message.
If possible, also test on a mobile connection rather than only on office Wi-Fi. Check for unexpected app-install prompts, blocked content, or a page that takes too long to become useful.
4. Scan on multiple devices and camera apps
Test the actual QR code—not just the destination link—on at least two different phones if available. Use each phone’s built-in camera and, where practical, a second QR-scanning app. Confirm that the preview shows the expected destination before opening it, then check the page after it loads.
For printed materials, print a proof at the intended size and scan it under realistic lighting and from a normal distance. A code that scans on a large monitor may be difficult to scan when reduced on a small flyer. Test the actual design, including its contrast, clear space around the code, and any logo or decorative elements. These are recommended checks; no particular QR code, device, or printed proof was provided for testing here.
5. Decide whether the destination will remain reliable
A static QR code stores its URL in the code. Changing a webpage later does not change that stored URL. If the page moves, the domain expires, or the link is removed, the printed code may no longer lead where expected.
You can keep the printed code working by maintaining the encoded URL or by using a redirect you control and can update. A dynamic QR service may also let you change its destination, but then the code depends on that service, its account and terms, and the continued availability of its redirect. Check any service-specific expiry, ownership, or subscription conditions before relying on it for a long-lived print run.
Before approving artwork, assign someone to own the domain, redirect, or QR service for as long as the printed materials will be in circulation. Keep a record of the encoded URL and the intended final page.
Final pre-print sign-off
Use this short sign-off for each QR code in the artwork:
- Scanned or decoded the code and confirmed the exact encoded URL.
- Opened the URL and verified the expected redirect chain and final destination.
- Confirmed the page loads over HTTPS and displays the intended content.
- Tested the page on a phone while signed out; confirmed any login requirement is intentional.
- Scanned the design on at least two devices or camera apps where available.
- Printed and scanned a proof at the intended size and in realistic lighting.
- Confirmed who maintains the destination, redirect, domain, or QR service after printing.
Common Mistakes
- Testing only while signed in: This can hide a login requirement or permissions problem visitors will encounter.
- Checking only the short link: Confirm the final destination after redirects, not just the first URL.
- Scanning only a screen preview: Print size, contrast, and surrounding design can affect scanning.
- Assuming the destination can always be changed: A static code contains its original URL. It changes only if you control a redirect or use a service that manages the destination.
- Treating one successful scan as proof: Different phones, camera apps, networks, and browser states can produce different results.
Best Practices
Keep the encoded URL on a domain your organization controls when possible, and use a maintained redirect if the destination might change. Avoid making the QR code depend on a link you cannot renew or administer. Save the final artwork and encoded URL together, and scan a physical proof before approving the full print run.
Conclusion
Before printing, verify both parts of the experience: the QR code must scan, and its destination must be accurate, accessible, usable on a phone, and maintainable over time. A short, documented proofing process can catch problems while the artwork is still easy to change.