QR code landing pages: what works on a phone
A scan is not a visit — it is a decision to spend five seconds on whatever you printed. The page you send people to decides whether that time is wasted, and it is judged on a phone, often standing up.
Updated October 6, 2026 · 4 min read
Design for the moment of scanning
Someone scanning a menu code is standing in a restaurant. Someone scanning a poster is outdoors, in whatever the weather is doing. The page has to satisfy that moment immediately, not after a cookie banner and a carousel.
The reader gave you five seconds and no context. If the first screen does not answer the question the print raised, they close the tab and the scan is spent.
- First screen answers why they scanned
- No interstitial or full-screen popup
- Loads fast on mobile data
- Nothing requires an app download to be useful
Keep the promise the print made
If the poster says 'see the menu', the code should open the menu — not the homepage. Mismatches are the most common reason a scan does not convert, and they are entirely avoidable.
The test is simple: read the printed asset as a stranger, then scan it. If the first thing you see is not the thing the print promised, the page is wrong — however good it looks.
- A menu code opens the menu, not the restaurant's homepage
- An offer code opens the offer, not a list of offers
- A packaging code opens the product, not a company history
The first screen decides
Treat the first screen as the entire page, because that is all most scanners will read. Put the answer at the top: the menu, the offer, the download, the form. Prices, opening hours and a single primary action belong there too.
Keep the layout thumb-sized. Buttons and links need to be comfortable to hit one-handed, text large enough to read outdoors, and the primary action should be the only thing competing for attention.
- Answer above the fold, detail below it
- One primary action per page
- Tap targets large enough for a thumb, not a cursor
- No autoplaying video or heavy animation on arrival
Speed is part of the design
The person scanning is on mobile data, sometimes on one bar of signal, and they are holding a phone in a position they will not keep for long. Every second of loading loses a share of them.
In practice that means a light page: compressed images sized for a phone rather than desktop artwork, no unnecessary scripts, and no font loading chain that leaves the text invisible while it resolves. Test on a throttled connection, not on office wifi.
- Aim for the page to be useful within about three seconds on mobile data
- Serve images sized for the screen, not the print file
- Avoid blocking scripts and third-party widgets on the critical path
- Test on a throttled connection before the print run
Measure the step after the scan
You can see the scans on the code side and the drop-off on the page side, but only if you know which is which. Comparing the two tells you whether the print failed to attract scans or the page failed to hold them.
Tag the destination so the page's analytics can separate scan traffic from other visitors. Without that, a landing page that works and one that leaks every visitor look identical in the numbers.
- Compare scan counts with page visits to find the leak
- Tag the destination so scan traffic is identifiable
- Watch the first-screen exit rate, not just the overall bounce
- Change the page via the dynamic code rather than reprinting, then re-measure
Frequently asked questions
Should a QR code link to my homepage?
Do QR codes need a special landing page?
How can I change the page later?
How fast does a scan landing page need to load?
Can I show a cookie banner on a scan page?
What should the page do once the offer ends?
Keep reading
Ready to create one?
Dynamic codes are editable forever from €3/month.
Create your first dynamic QR code
Free to start. One code, editable forever, with scan tracking from the first scan.