How to make a website url QR code

How to make a website url QR code: pick the url type, paste the live https address, and print a hosted redirect at least 2 cm across. You can change the page later. A Canva one-off static file is the right tool when that address will never move and you will not count scans.

How to make a website url QR code you can retarget

The url type is a redirect. The modules encode a SmartQRCode URL on smart-qrcode.com. Each scan hops through the tracker, then opens whatever you stored in the destination field paste. That is how a shelf talker printed in March can point at a June sale without a new plate.

This is the wrong type for Wi-Fi, for a Google review form, and for a PDF you want to replace as a file. Those are other classes. It is also the wrong spend when a single conference flyer will die on Sunday. A free static generator such as Canva should encode that flyer URL directly.

Short URL density is the print reason to host. A long marketing URL with query strings makes a static symbol denser at the same millimetre size. The hosted pattern stays the short URL. Campaign parameters belong on the destination, not in the ink.

There is no unpaid tier. $1.99, $29, $97, and $197 are the paid options.

Encode the destination as a hosted redirect

1. Open the website QR generator and paste the full destination, including https if the site needs it.
2. Add UTM on hosted destination now, or leave them off until the campaign exists; either way the printed modules do not change.
3. Set error correction H if you add a logo; M on a clean 2 cm sticker with no logo.
4. Keep four empty modules as a quiet zone. Do not bleed the pattern to the die-cut.
5. Download SVG for vinyl or cutter work, or 300 dpi PNG/PDF at the final size for toner. Never send a screenshot.
6. Print a 2 cm proof, scan from about 30 cm with iOS Camera or Android Camera / Google Lens.
7. Reject any file that still encodes /qr-preview. That is the unpaid on-screen mock, not the live payload.

For scan counts by placement, pair this with the tracking generator as a separate code per channel, not two stylings of one static URL.

Should UTMs go on the printed pattern or the hosted URL?

On the hosted URL. UTM on hosted destination feeds the same analytics property as your other campaigns without rewriting the symbol. If you bake UTMs into a Canva static QR, you cannot change the campaign after print, and the extra characters raise the QR version.

302 versus 301 cache is the other web detail. Scan redirects here are 302. A 301 would let browsers and some apps remember the old page, so a later dashboard edit would never reach those phones.

Analytics on this type: totals over time, device type, country from headers. Not the scanner's name. Not a GPS trace of the aisle.

Retail shelf-edge is arm length, so 2 cm can be enough if lighting is not a gloss flare. See retail marketing placements.

Can you retarget a website QR after the carton is printed?

Yes, if you printed a hosted url code. Change the destination. The next scan follows. Archived codes keep scanning; pause is the state that stops them.

No, if you printed a static Canva file. The URL lives in the modules. Changing the site means a new symbol. That is also true of any generator that wrote the destination into the pattern.

Provider dependence is the hosted cost. If the short URL stops resolving, the carton still looks perfect and the scan fails. A static code has no such dependency and no such retarget.

Sibling detail on the edit itself: edit a URL QR code after print. If the job was reviews, not a site, use how to make a google review QR code.

Failures that look like a dead website

The site can be up while the code is wrong. A screenshot of /qr-preview, a quiet zone eaten by a round-cornered label, or a logo past what error correction H can restore will fail on the shop floor after a desk scan worked.

Gloss card under overhead retail lighting reflects. Matte laminate on the symbol patch is the usual fix. Dark modules on a dark shelf strip without a true invert will not read.

If an old campaign page still opens, you either used a 301 somewhere outside this product, or the print was static. Confirm by changing the destination on a hosted code and scanning from a phone that has not opened it before.

Two shelf talkers in one camera frame: the reader typically returns one. Space them.

Packaging and cartons outlive campaign URLs. If the destination is a seasonal landing page, the url type is the class that lets the box stay on shelf. If the destination is a legal URL you will carve in stone, static is cheaper and has no provider in the path.

Low light and motion blur fail more often than "wrong app." A handheld scan of a poster from a moving pavement is a size-and-distance problem first. Enlarge before you blame the destination field.

Transparent stickers on glass need a white back. The scene behind the glass becomes the light modules. A busy street is not a quiet zone.

Offset jobs should treat dark modules as 100 percent of one ink, not a four-colour build that can fringing-register. Ask for vector. Vinyl cutters need vector paths; a PNG sent to a cutter is traced, and tracing QR modules produces broken corners.

What a 301 elsewhere does to a 302 scan

If you wrap the SmartQRCode hop in your own shortener and set that shortener to 301, you freeze the destination the first time a browser caches it. The dashboard will show the new URL. Old phones will not. Leave the scan path as the product 302, or use a 302 at every hop you add.

Screenshots of the builder still encode /qr-preview. A printer who "just grabbed the tab" will plate a mock. Send SVG or a 300 dpi file named as the millimetre size.

Apparel and vehicle wraps need larger modules because distance grows. Window first-surface versus second-surface is a tint problem. Stickers that curl into the quiet zone fail after a week on a kettle, not at proof.

A paused url code stops. Confirm pause versus archive before you reprint a carton line.

Use a Canva static file for a throwaway flyer

A Canva one-off or other free static generator is enough when the URL is immortal and you do not need counts. A school concert poster that dies on Monday should not live on $97. ISO/IEC 18004 still applies.

Do not host a redirect for a URL you will never touch. Do not static-encode a weekly promo URL you will change every Friday. The url type exists for the second case. If you are unsure, encode a hosted code: you can still point it at an immortal URL, and you keep the option to move.