Skip to content
Link Me.

Practical guide About 4 min read

Choose a short link you can keep using

Name a link clearly, choose its redirect behavior, and avoid changes that break links already in circulation.

Start with the reader's next step

A useful short link tells someone what they are about to open. Before choosing its name, write down the destination, the audience, and where the link will appear. A link printed on a product insert has a different life from one shared in a temporary event message. Decide whether the destination will need updates after the first share.

For a restaurant's current menu, a name such as menu makes the purpose clear and can survive a seasonal change. For a workshop that ends on a specific date, a name tied to that event can reduce confusion later. Keep an internal note explaining the link's purpose so the next person maintaining it understands why it exists.

Choose a readable, public name

A slug is the final part of the short URL. This service accepts letters from a to z, digits, hyphens, and underscores, then normalizes letters to lowercase. Spaces and other punctuation are not supported. Slugs must be unique, and some names are reserved for site pages. An automatically generated slug is available when a meaningful name is unnecessary.

Read your proposed name aloud and type it once from memory. Avoid a string whose meaning depends on capital letters, an easily confused spelling, or several unrelated abbreviations. A shorter name is helpful only if the reader can still recognize it. The slug is public: leave customer names, account numbers, private project details, and access tokens out of it.

  • Prefer one clear purpose, such as booking or installation-guide.
  • Use the title and description to explain context; do not force every detail into the URL.
  • Check the complete URL, including the domain, before sharing it.

Check the destination before choosing the redirect

Open the full destination in a private browser window. Confirm that it reaches the intended page without requiring your own signed-in session. Check spelling, HTTPS, language, and any campaign parameters. Shortening a URL does not hide its destination from the browser or make a private document public. Avoid storing credentials in the destination URL.

For an ordinary browsing link that may change, a temporary redirect is a practical starting point. A permanent redirect tells clients that the move is lasting; browsers and other clients may cache it. Updating the saved destination therefore may not immediately change what every returning client opens. Choose a permanent redirect when that caching behavior matches your intention. Method-preserving redirects also preserve the request method, so review their behavior carefully before using them for anything beyond normal page visits.

Add a gate only when it helps the reader

An interstitial can explain a destination or present a challenge before continuing. It also adds another step. Use it when the explanation or abuse control serves a clear purpose, and test the experience on a phone. A CAPTCHA is an extra check; it does not establish a visitor's identity or guarantee that all automated traffic is removed.

Make instructions understandable before someone taps Continue. If the link has a waiting period or an expiry date, make that condition clear in the surrounding message. Test the public link as a signed-out visitor so that your own account does not hide a problem your audience will encounter.

Maintain the address after publication

Once a link appears in email, print, or a saved message, treat its address as a commitment. Editing the destination can keep that same short URL useful. Changing the slug changes the address itself; previously shared copies do not automatically learn the new name. If you need a replacement, update the places you control and test the original address before assuming it still works.

Review lasting links when the destination website changes. Keep a note of where each important link is published, who maintains the destination, and when it was last checked. Set an expiry only when stopping access is intentional. A small maintenance habit is more useful than a memorable slug that eventually points to the wrong page.