QR code call to action text

QR code call to action text is one line that names the destination, set beside the symbol, not on it. Name the destination in type. Keep the quiet zone kept clear of caption. Use an editable hop under a promise if the page will move. Confirm the line matches a test scan of the live hop.

What QR code call to action text has to say beside the symbol

The camera does not explain itself. Guests ignore a naked square. The line should be the next action in their words: menu, review, map, join Wi-Fi. On a restaurant tent, "Scan for this week's menu" beats "QR."

Put the line outside the four-module quiet zone. Type that kisses the pattern eats the spec-minimum empty run and presents as a scan failure.

If the promise will change (this week's menu, this month's offer), the modules should encode a hosted website hop. Static ink cannot keep a dated promise.

A Canva one-off still needs this caption. Hosting is not a licence to skip type.

How long the line can be before it crowds the quiet zone

One short sentence. Two lines if the card is wide. Do not wrap a paragraph around three sides of the symbol; that is how quiet zones die.

On receipts, the pause is paying. "Rate this visit on Google" next to a review code is the right length. A shopfront review line asks for a rating before the visit exists.

Measure the caption after trim. Die-cuts and round corners steal both type and quiet zone. Test-scan the cut piece.

Whether the CTA should promise a destination you can still edit

If the line says "see today's specials," the hop must be editable or you will reprint when the specials change. Redirect and landing-page types can change content without new ink. Wi-Fi cannot.

Do not promise scan analytics on a Wi-Fi caption. There are none.

A 302 keeps later edits live. A leftover 301 from another vendor can make the caption true and the phone false. Test a fresh handset.

When a caption is wasted next to a static Wi-Fi join

The caption is not wasted. Wi-Fi hands a password to whoever scans. The line should say it is a network join, and the card should sit where you would write the password on a whiteboard.

Do not caption Wi-Fi as "visit our site." That trains people to expect a browser.

Confirm on a phone that is not already on the SSID. Staff phones lie.

Wi-Fi caption is a password warning, not a marketing line. Write the SSID in type so a guest who cannot scan can still type it. That fallback is the difference between a queue at the desk and a join.

On a menu tent, keep the caption to one action. "Scan for the menu" and "Join Wi-Fi" on the same 8 cm card, with two codes, is how the camera picks the join while the guest wanted lunch. Separate the cards by more than one camera-width of table.

If you host the hop, you can keep a seasonal promise in the caption and change the page. If you printed static, the caption must stay true for the life of the paper or you reprint. That is the whole decision. Test-scan after you change either the line or the page, because they can drift apart in separate tools.

A review caption on the shopfront still fights the visit pause. Move the line with the code to the receipt. Test-scan a printed receipt, not the door vinyl, if the promise is a Google review. Empty squares on doors get treated as decoration; a line of type on a bill folder gets treated as a request.

Skip the hosted generator when the CTA is a one-time URL

A funeral-order-of-service URL that will not move and will not be counted. Print a high-contrast static square from Canva or iOS, caption it plainly, size it for sitting distance, test-scan, stop.

When the caption is a campaign promise you will change, host the hop, keep type out of the quiet zone, and scan the finished card. If the line and the page disagree, the CTA failed even if the modules decoded.