All posts

The URL on the print: why custom-domain QR codes convert

8 min readBrandingBasics

qr.yourbrand.com/springREAD BEFORE IT IS EVER SCANNED

Every dynamic QR code prints two things: the grid, and — visibly, beneath or beside it — the short URL the grid encodes. That line of text is read by humans before any camera opens: by the customer deciding whether to scan, by the security-conscious employee deciding whether to allow it, by anyone burned once by a sketchy sticker. The domain in that line is either yours or a stranger's, and the difference does quiet work everywhere the code goes.

sh.ort/x8Kq2somebody's link, on your boxqr.yourbrand.com/springyour name, before the scan
The same grid, two identities. A generic shortener rents the most visible inch of your print to someone else's name; a branded domain makes the trust decision easy — and makes tampering visibly foreign.

Three things the domain changes

  • The scan decision. “Should I scan this?” is answered by the URL, not the grid. A recognisable brand domain converts hesitant scanners a generic shortener loses — especially anywhere quishing warnings have made people rightly cautious.
  • The security posture. Corporate mail filters and security teams increasingly flag generic shorteners on sight. Your own domain doesn't inherit the reputation of every other tenant of a public short domain — good or bad.
  • The exit. This is the underrated one: a printed URL on your domain is portable. The domain lives at your registrar; whoever serves it — us, today — can in principle be replaced without reprinting anything. A printed URL on a vendor's domain binds the paper to the vendor forever.

How setup actually works (one DNS session)

The mechanics are deliberately boring: pick a subdomain (qr.yourbrand.com — keep it short, character count is print quality), add one CNAME pointing it at us, add two TXT records to prove control, and certificates issue automatically — most domains are live in minutes, self-serve on Business. Your DNS never moves; you can remove the records yourself any time, which is exactly the point.

The operational questions, answered plainly

What if my DNS breaks? Codes degrade to resolving through our default domain rather than dying — the printed artwork still works while you fix the records. What if I rebrand? Codes are stamped with the domain they were printed under, permanently: a re-download in two years reproduces the exact URL already in the market, and only new codes take the new domain. The paper never lies about itself. What if I leave? The domain is yours; we hand over a continuity file mapping every printed URL to its destination — the exit plan post walks the whole scenario.

Who it's for, honestly

A café with six table codes gains little from this — our short domain is deliberately optimised for print (26 characters, the largest modules a shortened URL can produce) and serves everyone well. The domain starts paying at brand scale: packaging runs, franchise estates, anything where the print is the brand's surface, and anywhere a security review reads URLs. That's why it sits on the Business plan rather than being enterprise-gated behind a sales call — and why the comparison pages track where competitors put the same feature.