QR code CTAs and landing pages that convert: the post-scan moment

A scan is a beginning, not a result. Someone has lifted their phone to a poster, a flyer or a product label, and for one or two seconds they are paying full attention to your client's campaign. What happens in the next few seconds decides whether that scan becomes a booking, a sign-up or a sale, or whether it evaporates and shows up in your report as traffic that went nowhere.

Most QR advice stops at the moment of the scan. It tells you how to make a code scannable and then goes quiet, as if the work were done. For an agency it is the opposite: the scan is where the work starts being judged. Clients do not pay for scans, they pay for outcomes, and the two things that turn one into the other are the call to action printed around the code and the page the scan lands on.

This guide covers that post-scan moment end to end: the wording and layout of the call to action, the landing page that has to load and convert on a phone, and a way to diagnose a campaign that gets scanned but does not convert. Where a number is genuinely sourced, it is cited and labelled. Where something is a sensible rule of thumb rather than a hard fact, it says so.

The post-scan funnel: where scans leak

It helps to picture a scan as a short funnel with a handful of distinct stages, because the campaign can leak at any one of them and the fix is different each time.

1. The printed call to action. The frame, the copy and the QR code on the physical surface. If this is weak, fewer people scan in the first place.
2. The scan itself. The phone camera reads the code and opens the destination. Code size, contrast and quiet zone decide whether this even works.
3. The page load. The destination has to render on a mobile connection before the visitor gives up.
4. The landing page. What the visitor sees when it loads: one clear action, or a wall of choices.
5. The conversion. The booking, form, call or purchase the whole campaign was paid to produce.

The value of thinking this way is that "the QR campaign is not working" is never a single problem. A code that scans perfectly but lands on a slow homepage is a stage-three and stage-four failure, not a stage-two one, and reprinting the poster would fix nothing. Naming the stage is most of the cure.

The call to action does half the work before anyone scans

A bare QR code is an instruction with no reason attached. The call to action is what supplies the reason, and it does its job in the moment before the phone comes up, so it has to be readable in a glance and specific enough to be worth the effort.

Say what happens, and why it is worth it

"Scan me" answers neither of the two questions a passer-by is actually asking: what happens when I scan, and why should I bother. A good call to action answers both with a verb and a payoff. "Scan to see three-bed homes available now" beats "Scan me" because it promises a specific outcome. "Scan for the menu, no app needed" works because it removes a perceived barrier. "Point your camera here to claim 10% off" pairs the action with a reward.

You will see vendor blogs claim a call to action lifts scans by a precise figure, often something like 40 or 80 per cent. Treat those numbers with suspicion: they circulate between marketing blogs with no primary study behind them, and the same percentages turn up attached to unrelated claims. The case for a benefit-led call to action does not need a fabricated statistic. It rests on something simpler and true: a person decides whether to scan based on what you have told them they will get, and "Scan me" tells them nothing.

Respect the quiet zone

The call-to-action frame around a code is a design opportunity and a design trap. A QR code needs a clear margin on all four sides to be read reliably. The specification (ISO/IEC 18004, from QR inventor Denso Wave) calls for a quiet zone four modules wide, a module being one of the small squares that make up the code. A frame, a "Scan me" banner or a logo that intrudes into that margin can stop the code scanning altogether.

There is a little more room than people expect, because QR codes carry error correction. The standard defines four levels, recovering roughly 7, 15, 25 and 30 per cent of the code (levels L, M, Q and H). That budget is what lets a logo sit over part of a code, but it is a budget, not a free pass: spend it on a decorative overlay and you have less tolerance left for a scuffed flyer or bad lighting. Keep the frame outside the quiet zone, and if you must overlay branding, raise the error-correction level to compensate.

Size the call to action for the distance

A code on a table tent and a code on a billboard are not the same design problem. A widely used rule of thumb is the ten-to-one ratio: a code should be about one tenth as wide as the distance it will be scanned from, so a code read from ten metres away wants to be roughly a metre across. This is industry guidance rather than a clause in the standard, so treat it as a starting point and test the real artwork at the real distance. Our guide on how big a QR code should be goes into the sizing maths and the print-resolution side in detail.

The landing page is where conversions are won or lost

If the call to action gets the scan, the landing page has to keep it. This is the stage agencies most often neglect, because it lives in a different part of the production process from the artwork, and it is where the most reliable numbers in the whole funnel apply.

Speed first, because the audience is on a phone on the move

A QR scan is almost always a mobile visit, often on a cellular connection, frequently from someone standing in a shop or at a bus stop with little patience. Speed is not a nicety here, it is the gate everything else sits behind.

The hard numbers are unambiguous. Google's own data found that 53 per cent of mobile site visits are abandoned if a page takes longer than three seconds to load. Separate Google research with SOASTA put real figures on the slope: as mobile load time goes from one to three seconds, the probability of a bounce rises 32 per cent, and from one to five seconds it rises 90 per cent. The same research found the average mobile landing page took 22 seconds to fully load, which is to say most pages were already far past the point where half their visitors had left.

For a concrete target to hand a developer, use Largest Contentful Paint, the Core Web Vitals metric for when a page's main content has loaded. Google's web.dev defines "good" as 2.5 seconds or less at the 75th percentile, and "poor" as over four seconds. Treat the 53-per-cent-in-three-seconds figure as the reason it matters and the 2.5-second LCP as the spec you actually build to.

One page, one action

The commonest self-inflicted wound in QR campaigns is the homepage redirect. A poster promotes a specific offer, the visitor scans, and they land on the client's generic homepage and have to find the offer again by themselves on a small screen. Every tap you make them do on the way to the goal is a place to lose them. A scan that promised "10% off" should land on the page about the 10% off, nothing else.

The same discipline applies to the page itself: it should drive one action. The evidence from checkout research is consistent. The Baymard Institute, which has logged hundreds of thousands of hours of usability testing, found the average e-commerce checkout in 2024 used 11.3 form fields when most need around eight, and that the number of fields hurts usability more than the number of steps. They also found 17 per cent of shoppers have abandoned an order because the process was too long or complicated. Fewer fields, fewer competing buttons, one obvious next step.

Layout matters too, and here a popular statistic is wrong, so it is worth correcting. A single-column form does beat a multi-column one, but the real finding from CXL's eye-tracking study was that people completed a single-column form on average 15.4 seconds faster, not "15.4 per cent better" as it is often misquoted. Use one column, top to bottom, and let the thumb move in a straight line.

Make it tappable

The post-scan page is operated by a thumb, often one-handed, sometimes outdoors. Buttons and links have to be big enough to hit. Apple's Human Interface Guidelines call for a minimum tappable area of 44 by 44 points; Google's Material Design specifies 48 by 48 density-independent pixels. WCAG 2.2 sets an accessibility floor of 24 by 24 CSS pixels for pointer targets, which is the minimum, not the comfortable size. Design to the platform numbers, treat the WCAG figure as the line you must not cross, and keep the primary action well clear of the bottom-bar and back-gesture zones.

Diagnose a campaign that scans but does not convert

When a client says the QR campaign is not working, resist the urge to redesign everything. Walk the funnel and isolate the stage that is leaking. This is where a dynamic, trackable code earns its place, because each stage leaves a different fingerprint in the data.

Start with the scan count. If scans are low, the leak is upstream of the page: the call to action, the placement or the code size. Revisit the copy and the position, and confirm the code is large enough for its viewing distance.

If scans are healthy but conversions are not, the leak is the page. Open the destination on a real phone on a cellular connection and time it. If it is slow, you have your answer, and Core Web Vitals will tell you which part. If it is fast, look at what loads: is it the offer, or the homepage the visitor now has to dig through? Is there one action, or six?

Then check for the quiet, fatal case: a dead destination. A static code bakes its URL in permanently, so when a campaign-specific page is taken down after the campaign, the printed code 404s forever and there is nothing to be done short of reprinting. This is the strongest argument for dynamic codes in the first place. With a dynamic code the destination is a redirect you control, so you can change the destination without reprinting, repointing a slow or broken page to a fixed one while the posters stay on the wall. (If you are still weighing the two, our dynamic versus static comparison lays out the trade-offs.)

To see which stage is leaking in the first place you need the numbers. Decide up front which scan metrics matter and read them properly, as our QR code analytics guide sets out, and tag the destination so the post-scan behaviour shows up in your client's existing reporting. Our walkthrough on tracking QR scans in Google Analytics 4 with UTM covers the tagging without the common traps. All of this sits inside the wider print-campaign measurement workflow an agency runs anyway.

Frequently asked questions

What should a QR code call to action say?

It should answer two questions in a glance: what happens when I scan, and why it is worth it. Use a verb and a specific payoff, such as "Scan to book a free survey" or "Scan for tonight's specials". Avoid the bare "Scan me", which gives the passer-by no reason to act. Keep it short enough to read in a second or two from the distance the code will be scanned.

Should a QR code link to a landing page or the homepage?

A dedicated landing page that matches the promise on the print, not the homepage. If the poster offers a discount and the scan lands on the homepage, the visitor has to find the discount again on a small screen, and many will not. A focused page with a single action almost always converts better than a general one. With a dynamic code you can point to a campaign page and repoint it later if you need to.

How fast should a QR code landing page load?

Aim for a Largest Contentful Paint of 2.5 seconds or less, the "good" threshold Google's web.dev sets for Core Web Vitals. The reason the target is so tight: Google found 53 per cent of mobile visits are abandoned when a page takes more than three seconds to load, and almost every QR scan is a mobile visit.

Why do people scan my QR code but not convert?

Because one stage of the post-scan funnel is leaking, usually the page rather than the code. The most common causes are a slow-loading page, a scan that dumps the visitor on a generic homepage instead of the offer, a page cluttered with competing actions, or a destination that has gone dead since the code was printed. Open the destination on a real phone, time it, and check it shows one clear action.

How big should the "Scan me" call to action and code be?

Size the code to the scanning distance. A common rule of thumb is roughly one tenth of the viewing distance, so a code read from two metres wants to be about 20 centimetres wide. This is industry guidance, not a formal spec, so test the real artwork at the real distance, and keep the four-module quiet zone around the code clear of any frame or text.

Can I fix a low-converting QR campaign after the codes are printed?

Only if the codes are dynamic. A dynamic code stores a redirect you control, so you can change the destination, swap a slow page for a fast one, or rescue a dead link without touching the print. A static code has its URL baked in, so the only fix is to reprint.

The short version

The scan is the start of the job, not the end of it. A campaign leaks at one of a few clear stages: the call to action that earns the scan, the speed of the page, the focus of the page, and the link between them staying alive. Lead the call to action with a benefit and keep its frame out of the code's quiet zone. Build the landing page to a 2.5-second LCP and a single action, sized for a thumb. When something underperforms, walk the funnel, name the leaking stage, and fix that one thing, repointing a dynamic code rather than reprinting where you can.

Next time you brief a QR campaign, write the call to action and design the landing page in the same breath as the code itself, and put a dynamic destination behind it so you can fix the post-scan moment without going back to the printer.