Website QR Codes: What Actually Works for Small Businesses

The counter at a lunch spot has three things competing for attention: a tip jar, a stack of business cards, and a laminated sheet with the WiFi password. Buried in the corner is a QR code with no label. Nobody scans it.

Three blocks away, a bakery window displays a simple sign: “Today’s menu—scan here.” The code gets used constantly. Same technology, different outcome.

Website QR codes are the most common type businesses create, and the most commonly wasted. The technology is dead simple. The execution is where things go wrong.

This guide covers what separates QR codes that work from ones that don’t—with specifics on destination pages, placement, technical setup, and the long-term thinking that keeps codes useful for years.

The Only Thing a Website QR Code Does

A QR code stores data in a visual pattern. For website QR codes, that data is a URL. When someone scans it, their phone opens that URL in a browser.

That’s the entire mechanism. Phone camera reads pattern. Browser opens address.

No apps required. No accounts. No magic. The complexity lives in everything around that simple exchange: what page you send people to, where you put the code, and whether the experience on the other end actually helps.

Destination Selection: The Decision That Matters Most

The most common mistake isn’t technical. It’s pointing the QR code at the wrong page.

Homepage vs. Specific Page

Default thinking: “We’ll link to our homepage.”

Better thinking: “What does someone who scans this actually want?”

A QR code on a restaurant table should open the menu, not a homepage that makes visitors hunt for a menu link. A code on a product package should open care instructions or warranty registration, not your company story.

Questions to ask before creating any code:

• What action should follow the scan?
• Can someone complete that action on the landing page?
• How many taps separate the scan from the goal?

Each additional tap loses people. Mobile attention spans are measured in seconds.

The Landing Page Test

Before generating a QR code, open your destination URL on a phone. Actually do this—don’t skip it.

Check for:

Load time. If the page takes more than 3 seconds on a decent connection, you’ll lose scanners. Heavy images, tracking scripts, and chat widgets add up.

Mobile layout. Can you read the text without zooming? Are buttons large enough to tap accurately? Does the page require horizontal scrolling?

Immediate clarity. Within 5 seconds, does a visitor know what they can do here? Ambiguous pages create bounce.

Obstacles. Does a cookie banner cover half the screen? Does a newsletter popup appear before content loads? Each interruption is a reason to leave.

If your page fails any of these, fix the page before printing QR codes. A fast path to a bad destination is still a bad experience.

Placement That Actually Gets Scans

Location determines whether anyone uses your code. Good placement meets three conditions: visibility, relevance, and scannability.

Where People Already Pause

QR codes work best in moments of natural pause:

• Waiting in line
• Sitting at a table
• Standing at a counter
• Browsing a display
• Reading a sign or poster

They work poorly in moments of movement:

• Walking past a store
• Driving by a billboard
• Hurrying through a hallway

A code on a storefront window gets fewer scans than the same code on a checkout counter, even though the window has more foot traffic. The counter catches people who’ve stopped.

Height and Angle Matter

Phones need a clear line of sight to scan. Codes placed too low require awkward bending. Codes behind reflective glass or plastic create glare. Codes at sharp angles relative to typical viewer position fail to scan consistently.

Practical guidelines:

• Eye level to chest height works for standing viewers
• Table height works for seated viewers
• Test from the actual distance and angle customers will use
• Check different lighting conditions (morning sun, evening overhead lights)

Size for Distance

A code that looks fine up close may be unscannable from where customers actually stand.

Rough sizing rules:

• Close range (within arm’s reach): 1 inch minimum
• Counter distance (2-3 feet): 1.5 inches minimum
• Sign distance (5-10 feet): 3 inches minimum
• Across a room: Test specifically; varies by phone camera

When in doubt, larger is better. A code that’s “too big” still scans. A code that’s too small doesn’t.

Label Everything

An unlabeled QR code asks people to gamble their attention. They don’t know what they’ll get.

Weak: [QR code with no text]

Better: “Scan for menu”

Best: “View full menu with prices—scan here”

The label sets expectations and creates motivation. Tell people what they get.

The Static vs. Dynamic Decision

For anything printed with an intended lifespan over a few months—menu cards, window signs, business cards, packaging—static codes are the safer choice. They work as long as your URL exists, with no subscription fees or service dependencies.

Dynamic codes let you change destinations without reprinting, but they introduce risk: if the service shuts down or your account lapses, every printed code breaks. For website URLs you control, static is almost always the right answer.

For a detailed comparison, see Static vs Dynamic QR Codes.

Dynamic codes make sense for:

• Short-term promotions with planned destination changes
• Marketing campaigns requiring precise scan attribution
• Testing different landing pages

But understand the tradeoff: flexibility comes with dependency.

Technical Setup

URL Structure

The URL you encode should be:

Complete. Include https:// at the start. Some phones handle bare domains, but including the protocol ensures universal compatibility.

Stable. Choose a URL that won’t change. /menu is more stable than /menu-spring-2026. Page content can change; the URL shouldn’t need to.

Clean. Avoid unnecessary tracking parameters when possible. yoursite.com/contact is cleaner than yoursite.com/contact?utm_source=qrcode&utm_medium=print&utm_campaign=spring. The latter works but looks messier if anyone notices.

Canonical. Use your primary domain. If your site is www.example.com, use that consistently. Mixing www and non-www versions creates inconsistency.

Testing Protocol

Before any QR code goes to print:

1. Scan with multiple devices. Test on iPhone and Android at minimum. Camera apps handle QR codes slightly differently.

2. Test the actual printed size. A code that scans on screen may fail when printed at final dimensions.

3. Test in real conditions. If the code will be outdoors, test in bright sunlight. If it’s behind glass, test through the glass.

4. Complete the user journey. Don’t just confirm the code scans—follow through to the destination and verify the page works as expected.

5. Check periodically. Set a quarterly reminder to scan your active codes and verify destinations still work.

Print Specifications

For high-quality results:

Resolution. Use vector formats (SVG) when possible. They scale without quality loss. If using raster images (PNG), generate at 300+ DPI for print.

Contrast. Dark modules on a light background. Black on white works universally. Colored codes can work but require testing—some color combinations reduce scan reliability.

Quiet zone. Leave empty space around the code. The margin helps scanners recognize boundaries. Don’t crop the code tightly into its container.

Surface. Matte finishes scan better than glossy. If using glossy materials, test for glare issues at different angles.

Industry Applications

Restaurants and Cafés

Effective uses:

• Table codes linking to current menu (not homepage)
• Counter codes linking to online ordering
• Receipt codes linking to feedback forms

Common mistakes:

• Linking to a menu PDF that’s hard to read on phones
• Multiple codes per table creating confusion
• Codes that open a homepage requiring navigation to find the menu

Tip: If your menu changes frequently, keep the URL stable and update page content. The code doesn’t need to change when you add a seasonal special.

Retail

Effective uses:

• Product tags linking to detailed specifications
• Shelf signs linking to size guides
• Checkout area codes linking to loyalty signup or reviews

Common mistakes:

• Codes on products that link to general category pages instead of the specific item
• Too many codes competing for attention on a single display

Tip: Test codes on actual merchandise. The curves and textures of product packaging affect scannability.

Professional Services

Effective uses:

• Business cards linking to contact pages or booking
• Presentation handouts linking to slides or resources
• Office signage linking to patient/client portals

Common mistakes:

• Codes that require login before showing useful content
• Landing pages that aren’t optimized for mobile

Tip: For professional contexts, a clean code design matters. Avoid decorative elements that might look gimmicky in a formal setting.

Events and Venues

Effective uses:

• Signage linking to schedules or maps
• Table cards linking to speaker bios
• Check-in areas linking to registration or wifi info

Common mistakes:

• Codes placed where lighting is poor (stages, dim hallways)
• Codes that lead to pages requiring accounts to access

Tip: Event wifi is often unreliable. Keep destination pages lightweight so they load even on congested networks.

What Not to Do

Link to Login-Protected Content

If someone scans and hits a login wall, they’ll leave. Most people won’t create an account on the spot. If authentication is necessary, ensure the pre-login landing page explains why and makes the value clear.

Depend on Services You Don’t Control

A redirect service that goes out of business breaks every QR code pointing to it. For permanent signage, static codes eliminate this risk.

Neglect Mobile Experience

A desktop-oriented website is worse than no QR code at all. It suggests the business doesn’t think things through. Every QR scan comes from a phone—plan accordingly.

Overuse Codes

One well-placed code beats five competing ones. Multiple codes create decision paralysis. If you need to present several options, link to a simple landing page that lists choices.

Skip Testing

Untested codes that fail embarrass everyone. The few minutes testing takes prevents hours of reprinting and reputation damage.

Long-Term Maintenance

A QR code printed today might still be in use in five years. Plan for longevity.

Keep URLs Alive

Even if page content changes, maintain the URL. Redirects can help—if you move from /menu to /food-menu, set up a permanent redirect so old codes keep working.

Document Active Codes

Know where your codes appear. A simple spreadsheet noting each code’s location and destination prevents confusion later.

Regular Verification

Add “scan QR codes” to quarterly maintenance checklists. Verify each code still works and the destination remains relevant.

Plan for Changes

When you know a URL will change (website redesign, domain migration), update or replace affected codes before the change goes live. Add redirect rules as backup.

Measuring Results Without Overcomplicating

Staff notice first. Fewer “where’s your menu?” questions. Fewer requests to repeat the WiFi password. Fewer customers squinting at faded signage trying to find your website.

Your existing page analytics tell the rest. Traffic to /menu spikes after you add table cards. Mobile visits to /hours increase after the window sign goes up. If you want cleaner attribution, use a dedicated path like /menu-table that only appears on QR codes.

The strongest signal is behavioral: customers complete the action the code enables. They order online, they leave reviews, they book appointments. When the friction disappears, the results show up in your normal business metrics—not in a QR dashboard you have to maintain.

Creating Your Code

StackQR generates static website QR codes directly in your browser. See the tutorial for step-by-step instructions.

Process: Just paste your URL and click Generate. Download in your preferred format, test thoroughly, and deploy.

No account, no tracking, no subscription. The code works as long as your website does. See the tutorial for detailed steps.

The Simple Standard

A QR code should disappear into the experience. Scan, page opens, task accomplished. When people notice the code itself—because it’s confusing, broken, or leads somewhere unhelpful—something went wrong.

The technology is trivial. The thoughtfulness around it isn’t.

Choose the right destination. Put the code where people can actually use it. Label it clearly. Test it properly. Maintain it over time.

That’s what separates QR codes that work from ones that waste everyone’s time.