Where Should a QR Code Link To? Landing Page Rules

A scan is expensive. Somebody noticed your printed piece, read it, decided it was worth their time, got their phone out and pointed it at a square. That is more deliberate effort than almost any digital click.

And then most of them land on a homepage.

The destination is the part of a QR campaign that gets the least attention and decides most of the outcome. These are the rules that matter.

Never send a scan to your homepage

A homepage is a menu. It is built for someone who might want any of twenty things and has to be helped to choose. A person who just scanned a poster about a specific offer wants that one thing, and making them hunt for it on a small screen while standing up is how you lose them.

Send them to the specific page: the menu itself, the property listing, the booking form, the offer. If the destination does not exist yet, that is a reason to build one page — not a reason to fall back on the homepage.

Keep the promise the print made

If the flyer said *“Claim 15% off”*, the first thing on the page should be the 15% off. Not a hero image, not a brand statement, not a cookie wall — the thing you promised, visible without scrolling.

This is the same idea as message match in paid advertising, and it is stronger here because the printed piece is often still in the reader's hand. They can see both at once. Any gap between what the poster said and what the page shows reads as a bait and switch, even when it is just untidy.

Reuse the actual wording. If the copy beside the code said “tonight's specials”, the page heading should say “tonight's specials” — not “Seasonal Offerings”. What to write next to a QR code covers the print half of this.

Assume a phone, held one-handed, outdoors

Essentially every QR scan is on a phone. Not most — practically all of them. So the mobile view is not the fallback layout, it is the layout.

• Tap targets big enough for a thumb, with space around them.
• Text readable without pinching. If you zoom to check something on your own page, it is too small.
• One clear action per screen. Scrolling is fine; deciding between five things is not.
• No horizontal scrolling. Tables and wide images need to reflow or scroll inside their own container.
• Forms as short as you can bear. Every field loses people, and typing on a phone while standing costs more than you think.

Test it on a real phone rather than a browser's device emulator. Emulators do not reproduce thumb reach, glare, or a slow connection.

Speed matters more here than anywhere else

Scan traffic arrives in the worst possible network conditions. Mobile data rather than wifi, often indoors, sometimes in a basement restaurant or a concrete-walled venue. The person is standing up, waiting, with nothing to look at but a white screen.

Patience in that situation is very short. A page that takes eight seconds on office wifi may take twenty on a weak signal, and most people will have given up well before that.

• Compress images properly and size them for mobile rather than shipping desktop assets.
• Cut third-party scripts. Chat widgets, heat-mapping, multiple analytics tags and ad pixels are usually the bulk of the weight.
• Make the promised content the first thing that loads, not the last.
• Test on a throttled connection, not your office wifi.

Remove everything standing between them and the thing

Friction that is merely annoying on desktop is fatal on a phone in a queue.

• Interstitials and popups. A newsletter modal appearing over the offer someone just scanned for is the fastest way to lose them.
• App install prompts. A banner asking someone to download an app, when they scanned a code to avoid exactly that, is a straight rejection.
• Logins and account creation before they can see what you promised.
• Cookie walls that block content. You may be legally required to ask; you are not required to hide the page behind it.
• Age gates and region selectors that could be inferred or deferred.
• Autoplaying video with sound, in a restaurant, at dinner.

Every one of these is a place where someone who had already decided to engage changes their mind.

Design for where the person physically is

This is the advantage print has over almost every digital channel: you know a great deal about the context. Use it.

• Scanned in your restaurant? They are seated, hungry, and probably deciding within five minutes. Lead with food, not your founding story.
• Scanned outside a closed shop? Lead with ordering for tomorrow or opening hours, not the full catalogue.
• Scanned from packaging at home? They already bought it. Lead with setup, warranty registration or refills.
• Scanned at an estate agent's board? They are on the pavement looking at the house. Lead with photos, floor plan and a way to book a viewing.
• Scanned at an event? Signal is probably terrible and they are standing. Keep it very light.

A dynamic code makes this easy to act on, because you can change the destination as the context changes — opening hours during the day, an ordering page after close, a different page during an event.

Deep link into apps where it helps

Sometimes the best destination is not a webpage. A WhatsApp link opens a chat with a message already written; a maps link opens directions; a calendar file adds an event.

These convert well because they skip the page entirely and land the person inside something they already use. Two cautions: always have a web fallback for people without the app, and never make an app the only route to information someone needs right now.

Measure past the scan

Scan counts tell you the printed piece worked. They say nothing about whether the page did. To know that, scan traffic has to be identifiable in your analytics — which it is not by default, because camera scans arrive with no referrer and get filed as direct traffic.

Tag the destination with UTM parameters applied at the redirect, then look at bounce rate, time on page and conversions for that traffic specifically. How to track QR code scans covers the setup.

The useful comparison is scans against completions. High scans and low completions is a landing page problem, and it is a much cheaper problem to fix than a print problem — you can change the page this afternoon without reprinting anything.

A checklist before you print

1. The destination is a specific page, not the homepage.
2. The promise from the printed piece is visible without scrolling.
3. It loads in a couple of seconds on mobile data.
4. No popup, cookie wall, login or app prompt blocks the content.
5. The next action is obvious and thumb-sized.
6. It has been opened on a real phone, on mobile data, by someone who did not build it.
7. UTM parameters are in place so the traffic is identifiable.
8. It is a dynamic code, so the destination can change when the campaign does.