Custom URL Shortener for QR Codes: Set Up Your Own go.yourbrand.com

Why Use a Custom Shortener?

A QR code linking to `go.acmecorp.com/menu` communicates brand ownership and trustworthiness in a way that `bit.ly/3xYz9q` does not. When a customer scans and sees your domain in the redirect, they know where the link is going. Custom shorteners also eliminate the third-party dependency risk.

Option 1: Shlink (Self-Hosted)

Shlink is a modern, open-source URL shortener built for self-hosting. Features:

- Custom domain support (`go.yourbrand.com`) - REST API for programmatic link creation - QR code generation built in - Click analytics with geolocation - Docker deployment available

Setup overview: 1. Deploy Shlink on a VPS (DigitalOcean, Hetzner, Railway) or as a Docker container 2. Point your `go.yourbrand.com` subdomain to the server IP 3. Configure SSL certificate (Let's Encrypt, free) 4. Access via Shlink Web Client (free, open-source) for link management

Cost: ~£3–10/month server cost, zero software licensing.

Option 2: YOURLS (Self-Hosted)

The original open-source self-hosted URL shortener. Simpler than Shlink, plugin ecosystem available.

Pros: Mature project, lots of plugins, minimal server requirements. Cons: Older codebase, less elegant API than Shlink, basic analytics.

Option 3: Dub.co (SaaS with Custom Domain)

A modern SaaS link management platform that supports custom domains on paid plans. Managed infrastructure — no server to maintain.

Pros: Modern UI, excellent analytics, easy setup. Cons: Monthly subscription cost; links depend on Dub.co's uptime.

Option 4: Cloudflare Workers + KV

For developers: a Cloudflare Worker script handles redirects, with KV (key-value storage) storing the short code to destination mapping.

Pros: Serverless, globally distributed, extremely fast, free for modest usage. Cons: Requires developer setup; management UI must be custom-built.

Domain Configuration

For any custom shortener:

1. Register or use a subdomain: `go.yourbrand.com`, `links.yourbrand.com`, or a short standalone domain (`yourbr.co`) 2. Add a CNAME or A record in your DNS management pointing to your shortener server/service 3. Enable HTTPS via SSL certificate 4. Test a redirect before publishing QR codes

Creating QR Codes from Your Custom Shortener

Once your shortener is running:

1. Create a short link (e.g., `go.yourbrand.com/menu`) 2. Copy the short URL 3. Generate a static QR code from this URL (no need for another dynamic layer — the shortener IS the dynamic layer) 4. The QR is now permanent; update destinations in the shortener dashboard as needed

Putting this into practice

Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.

Common mistakes to avoid

The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.

Quick checklist

- Keep the payload as short as practical so modules stay large. - Keep dark modules on a light background with strong contrast. - Leave a clear quiet zone on all four sides of the symbol. - Test the printed code at the real viewing distance and lighting. - Confirm the destination page loads fast on a phone. - Recheck the code after any change to the link, design, or placement.

Related tools and guides

- Use the [QR size calculator](/qr-size-calculator) to match the printed size to the expected scan distance before you commit to a print run. - The [error correction simulator](/error-correction-simulator) shows how damage tolerance changes the density of the symbol at each level. - Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it. - Create a fresh code with the [URL QR code generator](/url-qr-code-generator) when the destination is a web page. - Run unfamiliar destinations through the [QR safety checker](/qr-safety-checker) before you share a code widely. - The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.