QR code to landing page: bridging print and conversion
Published on 30 July 2026 · 8 min read
A QR code is nothing more than a printed URL — but that technical banality changes the nature of the traffic it brings: the person scanning is in the physical world, on mobile, in a precise context (in front of your poster, your booth, your product), and they made a voluntary gesture to learn more. That is rare, qualified traffic. Wasting it on a generic homepage is nonetheless the most widespread mistake in print campaigns.
What research says about the act of scanning
As early as the first adoption wave, Dong-Hee Shin, Jaemin Jung and Byeng-Hee Chang studied what makes a QR code actually get used, in “The Psychology Behind QR Codes: User Experience Perspective” (Computers in Human Behavior, 2012): perceived quality and above all perceived interactivity — the sense that the scan opens a useful exchange, not a brochure — determine attitude and intention to use. The operational translation: a scan is an implicit contract. The printed medium promises something (“see the menu”, “estimate your property”, “10% off your first order”) and the page must deliver exactly that promise, immediately. A code that lands on a homepage breaks the contract — the principle of message match, applied to paper.
Rule #1: a dedicated page per medium, not the homepage
Every QR code placement has its context and intent: a flyer handed out at a trade show doesn't promise the same thing as a sticker on packaging or a poster in a shop window. The code's target must be a dedicated landing page that extends the medium — same offer, same vocabulary, same visual if possible — with a single call to action. The most common use cases each have proven mechanics: menu and booking for a restaurant (see our article on the restaurant landing page), lead capture on a booth (see the trade show landing page), local quotes for a tradesperson whose van or card carries the code (see the local trades landing page).
Designing the page for the scanning context
- 100% mobile, not merely “responsive” — a scan is always a phone; design the page for a phone screen first, hero readable without zooming, as detailed in our mobile-first guide.
- Fast on cellular networks — scans often happen on average 4G (street, trade show, restaurant); every second of loading loses scans, a cost quantified in our article on page speed.
- An action doable standing up in thirty seconds — a 2-3 field form at most, a tap-to-call button, or a simple email capture; longer requests can continue by email.
- A sticky CTA — the person is often doing something else at the same time (walking, talking); the action must stay under the thumb.
- Visual continuity with the medium — same colors, same offer, same photo: the scanner must instantly recognize they're in the right place.
Measuring: a QR code without UTMs is a black hole
Print is historically the least measurable medium; the QR code fixes exactly that flaw, provided you encode a tracked URL. The standard method: UTM parameters per medium (utm_source=flyer-tradeshow-lyon, utm_source=window-poster…), which surface in GA4 like any campaign. You will then know — often for the first time — how many visits and conversions each print run actually produces, and which medium deserves reprinting. Two precautions: encode a short URL on your own domain (a 301 redirect to the full UTM-tagged URL) to keep the code sparse and scannable, and test the printed code in real conditions before the print run.
The mistakes that kill the scan
- A code too small or too dense — below roughly 2 × 2 cm on a flyer, or stuffed with an endless URL, scanning becomes unreliable; the short URL fixes both problems.
- No reason to scan — a bare QR code, with no printed promise next to it (“scan to get X”), gets almost no scans: the benefit must be readable before the gesture.
- An unmaintained page — printed media live for months; if the page's offer expires, the code distributes disappointment. Plan the “offer ended” version with an alternative.
- A PDF instead of a page — a PDF menu or brochure on mobile is unreadable and converts nothing; a web page must sit behind the code.
- Requiring an app or an account — every extra step after the scan divides the result.
Special case: the offer traceable through to the sale
To connect print to revenue and not just visits, add an offer identifier: a promo code specific to the medium (“FLYER10”), a “how did you hear about us?” question in the form, or an offer reserved for scans. It's the same end-to-end logic as calculating a landing page's ROI: a visit is only worth what it becomes.
On the page side, no need to custom-build for every campaign: LanderKit templates (€89 each, standalone Next.js code) cover a QR code's natural targets — booking with the Restaurant template (demo), local quotes with the Local Business template (demo), email capture with the Newsletter template (demo) — and can be duplicated at will, one page per printed medium.
FAQ
Frequently asked questions
Where should a QR code point?
To a dedicated landing page that extends exactly the printed medium's promise — never to the homepage. One page per medium (flyer, poster, packaging, booth), designed for mobile, with a single action doable in thirty seconds: booking, quote request, email capture or promo code.
How do you measure QR code scans?
By encoding a URL with UTM parameters specific to each medium (utm_source=flyer-tradeshow, utm_source=window-poster…), which show up in GA4 like a regular campaign. To keep the code sparse, encode a short URL on your domain that 301-redirects to the full tracked URL. A per-medium promo code additionally tracks through to the sale.
What's the minimum size for a printed QR code?
About 2 × 2 cm for a hand-held flyer; considerably more for a poster scanned from a distance — the common rule of thumb is about one tenth of the expected scanning distance. In every case, test the printed code in real conditions (light, distance, an average device) before launching the print run.
Why does my QR code generate so few conversions?
The three most frequent causes: no printed promise next to the code (nobody scans without a reason), a generic or slow landing page that breaks the medium's promise, and an action too demanding for a standing, mobile context (long form, PDF, account creation). Fix in that order: promise, continuity, friction.
Read next
Related articles
- Banner blindness: when your own block looks too much like an adYou polished your finest block: big colored panel, rounded corners, contrasting background, perfectly written copy. And nobody sees it. Since the late 1990s, ergonomics research has had a name for this: banner blindness. The problem, on a landing page, is that it doesn't hit other people's ads — it hits your own arguments.
- Landing page for YouTube Ads: converting video traffic that never askedOn YouTube, nobody searched for your product: your ad interrupted a video the viewer wanted to watch. That traffic doesn't convert like Google Search traffic — it needs a page that continues the video instead of starting over. Here's how to build it.
- Landing pages for native advertising: what changes with Taboola and OutbrainContent recommendation widgets at the bottom of news articles sell very cheap clicks from people who weren't looking for anything. A standard promotional landing page almost always fails on that traffic, because it asks for commitment from someone who thought they were still reading an article. Here's how to structure the page, handle the sponsorship label, and measure what the channel actually returns.