QR Redirect Error Handling: Prevent, Diagnose and Recover

A QR redirect error happens when a scan reaches your short link but the browser cannot finish the trip to the destination: it lands on a 404, an “unavailable” page, a loop or a blank screen. You handle it in three layers: build the redirect so it fails rarely, watch it so you hear about a failure before customers do, and keep the code editable so you can fix the destination without reprinting. That third layer is the reason we build QR codes the way we do: codes created during an active QRlytics subscription keep working, and their destination can be changed at any time.
This guide is for marketers, agencies, retail and hospitality teams, event organisers and publishers who have codes on printed material. It explains what a redirect error looks like, what causes it, how to diagnose it in minutes, and what a customer should see when something does go wrong.
TL;DR
- A dynamic QR code points to a short link, and that link redirects to your destination. Errors come from the destination, the redirect rule, the code’s status or the scan environment, not from the printed pattern itself.
- The usual culprits are a deleted or deactivated code, a destination that now returns a 404, a redirect loop, an expired certificate and a change that has not yet reached every device.
- Test the full path on real phones before printing, and monitor the destination for non-200 responses, certificate expiry and slow responses afterwards.
- Plan a fallback: a working page that is never switched off, so a failed offer or campaign still shows something useful.
- Choose a platform that lets you edit the destination after printing and keeps codes working, so recovery takes a minute, not a reprint.
Table of Contents
- What a QR redirect error looks like
- What causes a QR redirect to fail
- A five-minute diagnosis
- Static or dynamic: why it changes your options
- Test before you print
- Monitor after launch
- What the customer should see when it fails
- Recovering quickly when a code breaks
- How we think about redirect reliability
- Put it into practice
- FAQ
- Sources
What a QR redirect error looks like
A dynamic QR code does not contain your final web address. It contains a short link on a redirect service. When someone scans, the phone opens that short link, the service looks up where the code should go, and it sends the browser on to the destination. We explain the mechanics in more depth in our guide to QR redirected links.
Because there are several steps, there are several ways for a scan to fail. From the customer’s side, they look like this:
- A 404 or “page not found” screen. The redirect worked, but the destination no longer exists.
- An “unavailable link” or “this code is inactive” page. The short link itself is deactivated, deleted or has no routing configured.
- “Too many redirects” or “this page isn’t working”. The browser was bounced between addresses until it gave up.
- A certificate or security warning. The destination’s HTTPS certificate has expired or does not match the domain.
- A very slow load or a blank page. The destination is overloaded or the redirect chain is too long.
- A scan that does nothing at all. This is usually the printed code, not the redirect: too small, low contrast or damaged.
That last point matters for diagnosis. A code that will not scan is a print problem. A code that scans and then shows an error is a redirect problem. Separate the two first, because the fixes are completely different.
What causes a QR redirect to fail
The destination changed or disappeared
This is the most common cause by far. A landing page is deleted after a campaign, a website is rebuilt with new URLs, or a product page is retired. The QR code still redirects correctly, but it now sends people to a 404. This slow decay is known as link rot, and we cover how to stop it in our guide to preventing QR link rot.
The code is deactivated or missing its routing
Redirect platforms document several reasons a scan can end on an unavailable-link page. ShopHero’s troubleshooting guide lists a nonexistent or deactivated code, missing routing configuration, a malformed product code, an expired offer, or a change that has not propagated yet. The same guide notes that a redirect can succeed and still end on a 404 if a template variable is misspelled and produces a wrong URL.

The lesson applies to any platform: every dynamic code has a status and a destination rule, and an error on either one is visible to the customer immediately.
A redirect loop
A loop occurs when address A sends the browser to B and B sends it back to A, or when a rule keeps rewriting the same URL. The browser reports “too many redirects”. The most common real-world trigger is forcing HTTPS on a site before a valid certificate is in place, as Kinsta’s guide to the ERR_TOO_MANY_REDIRECTS error explains. Cached redirects and conflicting rules between a website plugin, a server and a content network are other typical causes. Loops usually appear when someone changes the destination site, not the QR code.
Certificate expiry and slow responses
A destination can be up and still unusable. If its certificate expires, phones show a security warning that most customers will not click through. If it responds slowly, people give up on a screen they scanned on the move. QRCodeFYI’s link rot monitoring guide suggests alerting on any non-200 response, on certificates 30 days before expiry, and on response times over 3 seconds. Those are sensible starting thresholds for a campaign page.
Redirect type and caching
Redirects come in permanent (301) and temporary (302) types. A permanent redirect can be cached by browsers and search engines, while a temporary one generally is not cached unless the server adds instructions to do so, as this comparison of 301 and 302 redirects describes. For a QR code, this means a change you make to the destination may reach some phones later than others if a permanent redirect was cached. It is one reason a “fixed” link sometimes still looks broken to a colleague who scanned yesterday.
Parameters that get stripped
Campaign links often carry tracking parameters. Some redirects or website rules drop them on the way, which does not break the page but does break your measurement. If your scan counts look right but your campaign reports show nothing, check whether the parameters survive the full path.
A five-minute diagnosis
When someone reports a broken code, work from the outside in. Do not start by editing anything.
- Scan it on a phone, on mobile data. Wi-Fi at the office can hide problems such as a geo-restricted page or a cached redirect. Note exactly what appears.
- Decide whether it is print or redirect. If the camera does not recognise the code, look at size, contrast and damage. If the phone opens a page, it is a redirect or destination problem.
- Open the short link in a private browser window. A private window ignores cached redirects and saved cookies, which rules out a stale local cache.
- Check the code’s status in your dashboard. Is it active? Is it inside any scheduled start and end dates? A code outside its schedule will behave as unavailable.
- Open the destination URL directly. If it returns a 404, you have found the cause. If it loads, compare it with what the redirect sends: a misspelled variable or a missing parameter produces a wrong address even when the page exists.
- Look for loops. If the browser reports too many redirects, test the destination without the QR path. A loop that appears there lives on the website, not in the code.
- Check the certificate. Click the padlock or look for a security warning on the destination.
- Fix the destination, then rescan on two phones (one iPhone, one Android) in a private window.
If the fault is a dead destination, you only need to point the code somewhere that works. With QRlytics you can update the link without reprinting, and the printed code stays exactly as it is.
Static or dynamic: why it changes your options
A static QR code holds the final address inside the pattern. If that address breaks, the only repair is a new code and a new print run. A dynamic code holds a short link you control, so a broken destination becomes a settings change. For printed materials such as packaging, posters, menus and brochures, that difference decides whether an error is a five-minute fix or a write-off.
It also decides what you can see. Scans of a dynamic code are counted, so a sudden drop to zero on a code that should be busy is itself an early warning. Our dynamic QR code generator is built around editable destinations and scan data for this reason.

Test before you print
Most redirect errors are visible before a single copy leaves the printer. Run this checklist on the exact file that goes to print.
- Scan the proof, not the screen. Print at the final size on the final material and scan it from the distance a customer will use.
- Test on both major phone platforms and at least two camera apps.
- Test on mobile data and on Wi-Fi.
- Follow the whole path to the final page and confirm it loads fast on a mid-range phone.
- Check error correction. QR codes carry built-in error correction at four levels, restoring about 7%, 15%, 25% or 30% of damaged data, according to Scandit’s technical guide to QR codes. Higher levels survive scuffs and logos better but make the pattern denser, so test the one you choose. This protects against print damage, not against a broken destination.
- Confirm tracking parameters arrive and that the scan appears in your analytics.
- Check the schedule. If the code has a start and end date, make sure the dates cover the whole campaign, including late scans after it formally ends.
For seasonal work, where codes are printed months before they go live, our seasonal QR code strategies cover how to plan destinations around the calendar.
Monitor after launch
A code that tested fine on day one can still fail on day 90. A website migration, an expired certificate or a deleted page will break it without anyone telling you.
Keep monitoring simple:
- Watch scan volumes. A code that normally gets daily scans and suddenly gets none deserves a check. Real-time analytics make this visible quickly, and the analytics view shows where and when scans happen.
- Check destinations on a schedule. A weekly check of every live campaign URL for a 200 response catches most dead pages.
- Calendar the certificate renewals of every domain your codes point to, a month ahead.
- Tell the web team. Most destination breaks happen because a page was moved by someone who did not know a printed code pointed to it. Keep a list of the URLs that codes depend on.
- Keep landing pages working as offers change. When campaigns end, offers expire and URLs are reorganised, a destination needs maintaining, not deleting. These landing page optimisation strategies are a good companion for that upkeep.
What the customer should see when it fails
You cannot make failure impossible, so decide what a failure looks like. A customer who scanned a code on a poster in a shop has shown real intent. A raw error page throws that away.
A good fallback has four properties:
- It is always live. A stable page on your own domain, such as a campaign hub or product category page, that never gets switched off.
- It acknowledges the context. If the code was for a spring offer that has ended, say so and show what is current.
- It offers one clear next action. A search box, a contact route, a store locator or the current offer.
- It loads fast on mobile. Keep it light.
For expired campaigns, do not let the code fall into an error page. Repoint it to the fallback. For codes with a planned end date, set the lifecycle schedule so the destination changes by itself at the end of the campaign instead of relying on someone remembering. For ideas on what these pages can contain, see examples of branded code landing pages and QR landing pages that convert.
A single shared fallback is fine for old codes, but each live campaign benefits from its own page, which also keeps your reporting clean. Our guide to building a unique QR landing page per campaign shows how.
Recovering quickly when a code breaks
Speed matters because every minute of failure is a minute of lost scans on printed material you cannot recall. Use a fixed routine:
- Confirm the failure using the diagnosis above, so you fix the right thing.
- Repoint the code to a working page, even a temporary one. Do this first, before finding the root cause.
- Fix the root cause on the website: restore the page, correct the rule, renew the certificate.
- Repoint to the intended destination once it is verified on two phones.
- Check the analytics to confirm scans are arriving again.
- Record what happened and add the dependency to your list of URLs that codes rely on.
This routine depends on one thing: that you can still edit the code. A platform that deactivates codes when a subscription lapses or a payment fails turns a minor destination problem into a dead print run. Our guide to redirection stability and piece on QR code consistency go further into why that reliability matters.
How we think about redirect reliability
Most QR redirect errors are not technical mysteries. They are the result of a code being treated as disposable while the paper it is printed on is not.
That is why we built QRlytics around permanence. Every code created during an active subscription keeps working, even after cancellation, because a printed code should never be held hostage by a billing status. Your destination stays editable, so a dead page becomes a quick change instead of a reprint.
We pair that with real-time scan analytics and global heat maps, so you can see when a code stops performing, and with lifecycle scheduling, so campaigns can end on your terms. Tracking is designed to be GDPR-compliant, and you can start without a credit card.
Our view: redirect error handling starts with choosing infrastructure you do not have to worry about, and continues with a simple routine of testing, watching and fixing.
*The
Put it into practice
If you have printed codes in the field, start by listing each one with its destination and its owner. Then give every campaign code a working destination and a fallback. You can create editable, trackable codes on the QRlytics free plan, which needs no credit card, and look at the Pro plan when you need unlimited codes, advanced analytics and API access.

If you want to start with a single code, the free QR code generator takes a minute. For more guidance, browse the QRlytics blog.
FAQ
Why does my QR code scan but show an error page?
The code itself is readable, so the problem sits in the redirect or the destination. Common causes are a deactivated code, a deleted destination page, a redirect loop or an expired certificate. Open the short link in a private browser window, then open the destination directly to see which step fails.
Can I change a QR code link after it is printed?
Yes, if the code is dynamic. A dynamic code points to a short link whose destination you can edit at any time, so the printed pattern never changes. A static code stores the final address inside the pattern and cannot be changed.
How much error correction do QR codes have?
There are four levels, which can restore about 7%, 15%, 25% or 30% of the data if the code is dirty or damaged. This helps a code survive scuffs, folds and logos. It does not help if the destination behind the link is broken.
Why does a fixed QR link still look broken to some people?
A browser or phone may have cached an earlier redirect, especially a permanent one. Open the link in a private window or clear the browser cache to see the current behaviour. Changes usually reach everyone within a short time, but test on a fresh device.
What should a failed QR scan lead to?
A live fallback page on your own domain, such as a campaign hub or a current offers page, with one clear next step. It should load quickly on mobile and explain, where relevant, that an offer has ended. Never leave an expired campaign code pointing to a deleted page.
Sources
- ShopHero LinkCore troubleshooting guide
- QR Code Link Rot: Prevention and Monitoring, QRCodeFYI
- How to Fix The ERR_TOO_MANY_REDIRECTS Error, Kinsta
- 301 vs 302 Redirects, How HTTP Works
- QR Codes: Complete Technical Guide, Scandit
- Optimizing Landing Pages: Proven Strategies for 2025