Why URL codes are still the most common type
A website QR code is the workhorse of the format - roughly half of all QR codes generated point at a URL - for the simple reason that most marketing ultimately leads back to a web page. A card, a poster, a package, or a flyer exists to get someone to a site, and a code is the shortest path from the printed thing in their hand to the page in their browser, with no typing.
That typing is exactly the friction it removes. Even a short URL has a real abandonment rate when a person has to copy it from print into a phone, and a long one with a path and parameters is effectively un-typeable. For a Canadian small business the URL code is the entry point to digital marketing: it connects the physical presence - the storefront, the van, the trade-show booth - to the website where the actual conversion happens. It is the default choice whenever the destination is a web page; the other QR types exist for the specific cases a web page is the wrong target, such as offline content (a plain-text code) or a saved contact (a vCard code).
Where to put website QR codes
Business cards
The most common single placement: a small code (2–3 cm) on the back with the URL printed as text beside it. One scan and your site or portfolio is open in the other person's browser before the conversation ends.
Packaging and product materials
A code on the box or insert linking to the product page, care instructions, reviews, or related products turns the package into a channel. The same idea on a manual or warranty card - "scan for the online manual" or "scan to register your warranty" - removes a support call.
Flyers, brochures, and direct mail
Marketing print can carry more than one code - the homepage, a specific campaign landing page, and a contact page - each pointing where that reader wants to go. A postcard with a code to a trackable landing page is the backbone of measurable direct mail.
Storefronts, vehicles, and outdoor signage
A large window code (10 cm+) caught by passing foot traffic; a door-panel code (8–12 cm) on a service van scanned from the car behind at a light; a code on a real-estate, election, or fundraising yard sign read from the road. Each converts attention that would otherwise evaporate into a site visit.
Trade-show banners and email signatures
A large code (10–15 cm) on a conference backdrop linking to session info or a landing page; a small code embedded in an email signature that a recipient on a phone can scan from a desktop inbox. Both reach contexts a typed URL never survives.
URL best practices for codes
The URL behind the code decides whether it scans reliably and whether you can measure it. A few rules cover almost everything:
- Keep it short. A shorter URL encodes less data, so the pattern is less dense and scans better at small sizes. Use the domain root where possible, or a trusted shortener for long links.
- Use HTTPS. Modern phones may warn on plain HTTP, so any printed code should point at an https:// address.
- Make the landing page mobile-fast. Test it on a phone over cellular, not desktop Wi-Fi; compress images and check it with a page-speed tool, since the code is only as good as what it opens.
- Add UTM parameters to measure it. Something like ?utm_source=qr&utm_campaign=conf-2026 lets your analytics show exactly which printed campaign drove visits.
- Keep the URL honest. The address is sometimes shown by the scanner before opening - a clean, recognisable domain reassures, an obscure redirect frightens people off.
Design considerations
Always print the URL as readable text beside the code so someone who cannot or will not scan can still reach the site. On a business card a short URL sits cleanly next to the code; when the real link is long with tracking parameters, print only a short, tidy version (a shortener or the bare domain) as the visible text while the code carries the full tracked URL. Keep dark modules on a light background with a clear quiet zone - a code over a photo or a dark panel is the usual reason it fails outdoors. A centred logo and brand colour are available on the full generator; keep contrast high if you use them.
Common problems and fixes
"The URL changed - what about old codes?"
A static code carries the old URL, so it breaks if you moved the page. Either reprint, set a 301 redirect from the old address to the new so existing codes still resolve, or use a dynamic QR whose destination you can change without reprinting. The 301 is the cheapest fix for a code already in the wild.
"Customers get a scam warning"
Phones flag suspicious or freshly registered domains and some free shorteners. Use a recognisable domain or a reputable shortener, and avoid the throwaway free services that routinely get blacklisted - the warning costs you the visit.
"We see odd or inflated scan numbers"
Genuine counter-scanning is rare. Add UTM parameters and trust your own analytics over guesswork; a well-placed code in a high-traffic spot legitimately produces more visits than instinct expects.
"Can the code show our logo?"
Yes - the full generator embeds a centred logo and brand colour. Always test-scan a logo code at the printed size before producing it, since a logo eats into the error-correction margin.
A worked example: a tradesperson's van
The whole chain is clearest end to end. An electrician puts a door-panel code (about 10 cm) on the van, with "Free quotes - scan to book" and the bare domain printed beside it. The code points at a single mobile landing page - example.ca/quote?utm_source=qr&utm_campaign=van- not the homepage.
A driver stopped behind the van at a red light has eight seconds and a question: "could these people do my panel upgrade?" They scan, a fast-loading page opens with one job - a short "request a quote" form above the fold - and they submit it before the light changes, or bookmark it because the domain was legible enough to find again. The UTM tag means the electrician can see in analytics exactly how many quote requests the van produced versus the yard signs or the flyer, and decide where the next marketing dollar goes on evidence rather than guesswork. Every part of that depended on a decision made before printing: a specific landing page rather than the homepage, one action rather than a menu, a fast mobile page rather than a heavy desktop site, a readable fallback domain, and a tracking parameter. The code itself was the easy part - a few seconds in a generator. The campaign worked because the destination and the measurement were designed, which is the part most printed codes skip and the reason most of them quietly underperform.
Why most printed QR campaigns underperform
A website code almost never fails because of the code - it fails because of decisions around it. The recurring causes are predictable and every one is preventable before the print run:
- It points at the homepage. Someone who scanned a specific sign wants the specific thing it promised, not a generic front page they now have to navigate on a phone. Send them to the matching page.
- The landing page is slow on cellular. Scans happen on mobile data, often on a weak signal; a heavy desktop-first page loses the visitor in the seconds the code just saved them.
- There is no text fallback. A meaningful share of people will not or cannot scan - without a readable URL beside the code, they are simply lost, and so is the accessibility baseline.
- It was never tested at print size. A code that scans on a screen can fail at 2 cm on a glossy card under shop lighting; only a printed test in realistic conditions proves it.
- Nothing is measured. With no UTM parameters there is no way to know if it worked, so it cannot be improved and usually is not repeated.
None of these are technical QR problems and none cost money to fix; they are planning, and the campaigns that work are simply the ones where someone made these five decisions deliberately instead of by default. A useful habit is to walk the chain backwards from the action you want - what should the visitor do, what page makes that easiest, how will you know it happened - and only generate the code once that path is real.
Static or dynamic: which does a website code need?
A static URL code - what this free generator produces - encodes the address directly. It works forever with no account and no dependence on our servers; if the URL never changes, or you can set a 301 when it does, static is all you need and it is the simpler, more durable choice.
A dynamic QR (a paid plan feature) lets you swap the destination any time without reprinting and reports per-scan analytics - worth it for URLs that change often, A/B-tested landing pages, expiring promotions, or campaigns you must measure at the scan level. If the destination is stable, stay static.