How to Choose a Custom Short Link Alias People Remember
A random short code like tinyur.in/x7Kp2 works fine in a clickable post. The moment someone has to read it aloud, type it, or decide whether to trust it, a well-chosen alias wins.
When a Custom Alias Is Worth It
Auto-generated codes are short and guaranteed unique, which is all you need for links that are only ever clicked. Custom aliases earn their keep anywhere a human interacts with the link text itself:
- ▹Spoken links — podcasts, webinars, videos, and conference talks where people hear the link once
- ▹Printed links — posters, packaging, business cards, and slides that have to be typed by hand
- ▹Trust-sensitive links — emails and messages where a readable word reassures people about where they're going
- ▹Links you'll reuse — a resume, portfolio, or signup page you share for months
Five Rules for a Good Alias
1. Describe the destination
The alias should tell people what they'll get: /webinar-signup, /menu, /priya-resume. If someone sees only the link, they should be able to guess the page.
2. Keep it short, but not cryptic
One to three words is the sweet spot. /q3-report is better than both /q3r (meaningless) and /quarterly-financial-report-third-quarter (defeats the point of a short link).
3. Use lowercase and hyphens
Short link aliases are usually case-sensitive, so /Menu and /menu can be different links. Sticking to lowercase removes the guesswork. Hyphens are easier to read and say than underscores, which can disappear when a link is underlined.
4. Avoid look-alike characters
In printed or spoken links, the letter l, the digit 1, and capital I are easily confused, as are O and 0. Words avoid this problem almost entirely.
5. Don't put dates in evergreen links
/pricing-2026 looks stale next year. Add a date only when the content really is tied to it, like an event or a yearly report.
Naming Patterns for Campaigns
Once you create more than a handful of links, a consistent pattern stops aliases from colliding and makes them easier to find later. Pick one pattern and use it everywhere:
/topic-channel—/launch-email,/launch-insta,/launch-poster/event-purpose—/devfest-slides,/devfest-feedback/brand-product—/acme-shoes,/acme-bags
The topic-channel pattern is especially useful because each channel gets its own link and therefore its own click count. You can compare how the email performed against the Instagram post without any extra tooling. For deeper attribution, combine it with UTM tags on the destination URL — see our UTM parameters guide.
Alias Rules on TinyUR
TinyUR aliases can be 3 to 50 characters long and may contain letters, numbers, hyphens, and underscores. Spaces, slashes, dots, and emoji aren't allowed because they either break URLs or get encoded into unreadable strings when shared.
Aliases are first come, first served. If the one you want is taken, add context rather than a random number: /menu-cafe-pune is still readable, while /menu7 looks like a typo.
Mistakes That Hurt Trust
- ▹Misleading aliases. An alias like
/free-giftthat leads to a signup wall teaches people not to click your links. - ▹Impersonating other brands. Aliases using another company's name look like phishing, and links like these are removed when reported.
- ▹Reusing an alias for something new. Old posts and printed material keep pointing at it. Create a new alias instead.
For more on how readers judge whether a short link is safe, read Short Link Safety: Spotting Malicious Redirects.
Key Takeaways
- ▹Use custom aliases wherever people will read, hear, or type the link
- ▹Describe the destination in one to three lowercase, hyphenated words
- ▹Use one link per channel so each gets its own click count
- ▹Never make an alias promise something the page doesn't deliver
