Static QR Codes vs a Short Link You Own: A Setup Guide for Small Businesses

If you search online for “dynamic QR code generator”, you will find dozens of platforms offering “free editable codes”. What their landing pages bury in small print is that the code is only free for a 14-day trial. Once that trial expires, your printed code stops working—redirecting your customers to a splash page that says: “This campaign has been paused by the account owner”.

To keep the code active, these vendors demand £15, £30, or even £60 every single month. If you cancel your subscription five years from now, every product box, table talker, van graphic, and business card you ever printed becomes instant landfill.

There is a vastly superior, professional way to get editable QR codes: create a permanent static QR code pointing to a short vanity link on your own web domain. It costs £0 in subscription fees, keeps you in total control, and ensures your codes remain active for as long as you own your website.

Static code + own domain vs vendor dynamic codes

Compare the two approaches side by side:

How self-owned redirects work

The mechanics are straightforward:

1. You choose a short, clean slug on your website, such as https://yourcompany.co.uk/go/spring or https://yourpub.co.uk/m.
2. You generate a free static QR code encoding that exact URL and send it to your printer.
3. On your web server or website builder, you configure a redirect rule that automatically forwards anyone visiting that short slug to your active campaign page or seasonal menu.
4. When you want to change where the code points next season, you simply update the redirect destination in your website control panel. The physical printed code is never touched.

Critical technical rule: use 302, not 301

HTTP status codes communicate caching behaviour to web browsers:

• 301 Moved Permanently: Tells the smartphone browser that the address has changed forever. Browsers aggressively cache 301 redirects locally on the phone's memory. If you later change the destination of a 301 redirect, existing visitors' phones may refuse to update for weeks!
• 302 Found (or 307 Temporary Redirect): Tells the smartphone browser that this forwarding rule is temporary. The browser will re-check your server on every single scan, ensuring customers always see your latest active destination immediately.

Always configure your QR redirects as 302 (or 307).

Practical setup guides for common hosts

Implementing a 302 redirect takes less than two minutes regardless of where your website is hosted:

1. Cloudflare Pages / Netlify (_redirects file)

If your website is hosted on Cloudflare Pages, Netlify, or similar Jamstack platforms, add a plain text file named _redirects to your project root:

/menu   https://yourcompany.co.uk/menus/autumn-2026   302
/spring https://yourcompany.co.uk/offers/spring-deal  302

2. WordPress (Redirection Plugin)

If you run WordPress, install the free, trusted Redirection plugin by John Godley:

1. Go to Tools > Redirection.
2. Source URL: /menu
3. Target URL: https://yourcompany.co.uk/menus/autumn-2026
4. HTTP Code: 302 Found
5. Click Add Redirect.

3. Apache (.htaccess)

On standard cPanel or Apache shared hosting, add this single directive to your .htaccess file:

Redirect 302 /menu https://yourcompany.co.uk/menus/autumn-2026

4. Nginx Server Block

For custom VPS servers running Nginx, insert this block inside your site configuration:

location = /menu {
    return 302 https://yourcompany.co.uk/menus/autumn-2026$is_args$args;
}

Preserving UTM tracking parameters

If you plan to append tracking parameters (e.g. /menu?utm_source=table_4), your redirect server must be configured to pass query strings through to the final destination.

Cloudflare Pages, Netlify, and Apache Redirect directives forward query strings automatically by default. On Nginx, appending $is_args$args ensures all incoming UTM tags are seamlessly preserved.

Implementation checklist

• Chosen short vanity slug uses clean, memorable lowercase characters.
• Redirect is explicitly configured with HTTP status 302 (or 307).
• Query string passthrough tested with sample UTM parameters.
• Permanent static QR code generated and exported as scalable vector SVG.
• Artwork verified on a physical print proof before mass production.

Questions before you print

Related: Create direct codes with our static QR code generator, read our comparison of static vs dynamic QR codes, learn how to track redirect campaigns in GA4, and check our print size recommendations.