A QR code is only as reliable as the URL behind it. This checklist explains how to choose a durable QR code redirect, track scans without creating messy campaign data, change the destination later, and test the complete journey before anything is printed.
Overview
QR codes are commonly placed on packaging, posters, event materials, signage, business cards and printed instructions. Unlike a normal web link, a printed QR code cannot usually be edited after distribution. The practical solution is to encode a stable URL that you control, then use a URL redirect to route visitors to the current destination.
This approach separates the printed address from the landing page. If the campaign changes, the destination can be updated at the redirect level without reprinting the code. It also gives you a consistent place to manage campaign parameters, check status codes and review whether the link still works.
For most QR campaigns, use an HTTPS branded short URL that is easy to recognise and maintain. The redirect should lead directly to the intended mobile page, use a suitable status code for the campaign, and avoid unnecessary hops. A QR code should not send visitors through several tracking and forwarding services before reaching the content.
There are two broad choices:
- Direct destination: the QR code contains the final page URL. This is simple, but changing the page later may require a new code unless the original URL remains under your control.
- Managed QR code redirect: the code contains a stable short URL that forwards to the current destination. This is more flexible for campaigns, events and printed assets with a long shelf life.
When selecting a redirect platform or implementing the rule on your own infrastructure, confirm that you can edit destinations, inspect redirect responses and preserve HTTPS. For technical implementation, the guidance in Apache vs Nginx Redirects and the Redirect Checker Guide can help with server rules and validation.
Checklist by scenario
For a one-off event or short campaign
- Create a dedicated, branded short URL rather than reusing a general homepage link.
- Send visitors to a mobile landing page with the event details, registration route or offer described beside the code.
- Add campaign parameters if your analytics setup supports them. Use a consistent naming convention, such as a source identifying the printed material, a medium identifying offline activity, and a campaign name identifying the event.
- Choose a temporary redirect only when the destination is genuinely expected to change or the campaign is time-limited. Document the planned end date and the fallback destination.
- Decide what visitors should see after the event. A useful fallback might be a current events page, an evergreen product page or a clear explanation that registration has closed.
For packaging, labels or printed products
- Use a destination that will remain useful for the expected life of the product.
- Keep the encoded URL short and stable. Do not include a fragile session identifier or a URL that depends on a temporary folder.
- Prefer HTTPS and confirm that the certificate and redirect will continue to be maintained.
- Plan for product updates by routing the code to a controlled information page rather than a single campaign page that may disappear.
- Record who owns the redirect and where the destination, expiry date and tracking conventions are documented.
For a permanent information link
- Use a stable page URL where possible, with clear ownership and a maintenance process.
- Use a permanent redirect when moving the QR destination for the long term. See the guide to 301 vs 302 redirects before choosing the status code.
- Update internal links and the canonical URL when the underlying page changes. A redirect and a canonical tag solve different problems; neither should be used as a substitute for the other.
- Keep an older destination available or provide a relevant replacement rather than sending visitors to a generic error page.
For several locations or printed variants
- Give each location, poster, leaflet or packaging version its own redirect if you need separate scan reporting.
- Maintain a bulk redirect map containing the short URL, printed asset, current destination, campaign parameters, owner and review date.
- Keep naming consistent so reports can distinguish a shop window from an event stand or a product insert.
- Use the same landing-page experience where appropriate, but avoid combining distinct sources into one unidentifiable tracking value.
What to double-check
Destination and device experience: Open the final page on a current mobile browser and check that it loads without requiring desktop-only features, an unnecessary login or a blocked pop-up. Test both the redirected URL and the final URL directly.
Redirect path: A QR code should normally resolve through one clear redirect to the final page. Check for HTTP-to-HTTPS changes, www-to-non-www rules, tracking redirects and other platform layers. Use a redirect checker to identify a redirect chain, an unexpected status code or a redirect loop. The guide to fixing redirect chains covers how to replace multiple hops with a direct destination.
Tracking parameters: Decide whether parameters are added to the short URL or to the final destination. Avoid adding the same parameter twice when a redirect platform and analytics tool both append values. Use lowercase, predictable names and document the convention. The article on UTM tracking without losing SEO provides a useful framework for separating campaign measurement from organic URL management.
Privacy and measurement: Collect only the campaign information you need. A scan report may show useful aggregate activity, but measurement settings, consent requirements and analytics configurations differ between organisations. Make sure the landing page and analytics workflow match your own privacy review rather than assuming that every scan can be identified or attributed.
Fallback behaviour: Temporarily disable or change the destination in a controlled test environment if available. Confirm what happens when the campaign ends, the page is unpublished or the destination returns an error. A QR code printed on a long-lived asset should never depend on an unowned redirect account.
Code and print quality: Scan the actual printed proof, not only the digital artwork. Check contrast, quiet space around the code, physical size, curvature of the surface and any nearby design element that could interfere with scanning. Test from the distance and angle a real visitor is likely to use.
Common mistakes
- Encoding a temporary page: A campaign landing page may be removed after the launch. Use a managed redirect and define a useful fallback before publication.
- Using a raw tracking URL: Long query strings can make the printed destination harder to manage and may expose internal naming conventions. Put the stable short URL in the QR code and manage campaign routing deliberately.
- Creating a redirect chain: Stacking a QR service, a link shortener, a domain redirect and a tracking redirect adds delay and more points of failure. Consolidate rules where practical.
- Choosing a 302 by habit: A temporary redirect can be appropriate for a time-limited destination, but a long-term move should be reviewed as a permanent redirect. Do not choose based only on what a dashboard labels as the default.
- Forgetting alternate hostnames: Test HTTP, HTTPS, www and non-www versions if your domain supports them. Redirect rules that conflict can cause loops; see the redirect loop troubleshooting guide for a structured check.
- Failing to assign ownership: A code can remain in circulation long after the original campaign team has changed. Store access details, destination ownership and review dates with the campaign record.
When to revisit
Review each QR code before a seasonal planning cycle, print run, event, packaging update or campaign relaunch. Recheck it immediately when the landing page structure, domain, analytics platform, consent experience, hosting setup or redirect provider changes.
Use this short pre-publication routine:
- Scan the printed proof with more than one mobile device or browser.
- Run the short URL through a redirect checker and record every status code and destination.
- Confirm that the final page is mobile-friendly, secure and relevant to the surrounding printed message.
- Verify UTM values or other campaign fields in the analytics test view without duplicating parameters.
- Check the expiry or fallback plan and confirm who can change the destination.
- Record the test date, result and next review date in the redirect map.
After launch, review scan activity alongside the quality of the resulting visits rather than treating scan volume as the only measure. If the campaign is extended, moved or reused, update the destination deliberately and test again. That simple habit keeps a printed QR code useful long after its first publication.