A Practical Guide to Choosing a Short Link Alias

Why the alias matters more than the domain

A random short code does its job, but a custom alias does more: it tells people what they’re about to click before they click it. "lumara.chat/links/summer-sale" reads differently than a string of random characters, and that difference shows up in click-through rate, especially in print or verbal contexts where someone has to type the link by hand.

The trade-off is that a memorable alias has to be chosen carefully once, because changing it later breaks anything already printed, shared, or bookmarked.

Keep it short and easy to type

Aim for something a person could read once and retype from memory. Hyphens are fine as separators, but avoid anything that requires explaining out loud — underscores and hyphens sound identical when spoken, so picking one convention and sticking to it across a campaign avoids confusion.

Numbers are fine for things like years or version numbers, but avoid using them as a substitute for letters (like using "0" for "O"), which is a common source of mistyped links.

Plan for the whole campaign, not just today

If you’re going to need several related links, decide on a naming pattern up front — for example, "summer-sale-email", "summer-sale-instagram", "summer-sale-print" — rather than improvising each one as you go. It keeps your links self-documenting months later when you’re trying to remember which link went where.

Avoid reserved and ambiguous words

Most shorteners, including Lumara Links, reserve a handful of words to keep them from colliding with site routes or future features. If your first choice of alias is rejected, it’s usually one of these edge cases rather than a bug — try a slightly more specific variant instead.