QR code sign riders that actually get scanned
A QR sign rider gets scanned when it promises one specific thing the person standing there already wants, sits at eye level, and opens instantly to a mobile page with no app and no form. Riders that say 'scan for more info' and land on a homepage are ignored, because the promise is vaguer than a search.
The Showfeed team · Last updated
Do QR codes on real estate signs actually work?
They work for narrow jobs and fail at broad ones. A code that does one specific thing, such as opening the photo gallery for that exact address or logging an agent's arrival for a showing, gets used. A code that means 'visit my website' does not, because anyone curious enough to scan is equally able to type the address into their phone and get more.
That is the whole test. Before you order a rider, finish this sentence: scanning this gets me ___ , right now, without typing anything. If the blank is hard to fill, the rider will not earn its place on the post.
The second reason they fail is friction after the scan. The scan is the easy part and people will do it out of curiosity. Losing them happens on the next screen, when the page is slow, not built for a phone, or asks for a name and email before showing anything.
Who is actually standing at your sign?
Two very different people, and a rider designed for both serves neither. The first is a passer-by on foot or slowing in a car, curious and anonymous, who wants pictures and a price. The second is a buyer's agent arriving with clients for a scheduled showing, who wants to get inside and get on with it.
The passer-by is a lead capture problem. They will scan if the promise is concrete, and they will abandon instantly if the page gates the photos behind a form.
The agent is a workflow problem, and a much better fit for a code. They are already at the door with a phone in hand, and a scan that takes one action off their plate or takes ten seconds after the showing has an obvious payoff. If you only run one rider, run this one, because it produces information about the property rather than another cold lead.
How to design a sign rider that gets scanned
In order. Most riders fail at step one or step five, and no amount of design fixes a vague promise.
- Write the promise before the codeDecide the single outcome of a scan and write it in four or five words. 'See all 40 photos', 'Floor plan and price history', 'Agents: leave feedback here'. Then generate the code. The other order is how riders end up saying 'scan me'.
- Size the code for the distanceA code read from a car needs to be far larger than one read from arm's length. If the rider is meant for someone standing at the post, a smaller code with big legible words above it beats a giant code with tiny text.
- Use hard contrast and leave the quiet zoneDark code on a light background, no photo behind it, no logo dropped into the middle, and a clear margin on all four sides. Scanners cope with less than designers assume, but weathered vinyl and low light do not help.
- Land on a page built for one thumbThe destination must load fast on a cellular connection, fit a phone screen without pinching, require no app, and show the promised thing above the fold. No login, no cookie wall you cannot dismiss, no PDF.
- Test it in the field, not on your deskScan it at the actual sign, in daylight and at dusk, from the distance someone will really stand at, on both a recent phone and an older one. Then have somebody who has never seen it try, and watch where they hesitate.
Rider wording that works, and wording that does not
The code is identical in every row. Only the sentence above it changes.
| Works | Does not work | Why |
|---|---|---|
| See all 40 photos | Scan for more info | A specific quantity is a promise; 'more info' is a maybe |
| Agents: 10-second showing feedback | Feedback form | Names the audience and caps the time commitment |
| Price, taxes, floor plan | Visit our website | The destination is the offer, not the brand |
| Open house times | Follow us | Answers the question the person at the sign is actually asking |
The rider that pays for itself
Of everything a QR rider can do, the highest-value job is capturing the showing itself. The most common reason a feedback request never goes out is that nobody logged the showing in the first place.
A code the buyer's agent scans on arrival solves that without depending on anyone's memory, and it works for the showings that never touch your scheduling platform.
Showfeed offers exactly that rider, where the arriving agent scans once and the feedback request goes out afterwards with no app and no login. If you would rather build it yourself, point your own code at the showing feedback form and read how to get showing feedback for the follow-up sequence that makes it work.