Share short links in email and messages without confusing readers

A short link saves space, but its unfamiliar address tells the reader less about where it leads. Add that context in your message and test the route a recipient will actually take. Don’t assume a link that works in your own browser will behave the same in every email or messaging app.

This guide follows a made-up club sharing the details of its next meeting. Links creates the short link; it doesn’t send messages, manage mailing lists or decide whether your email reaches the inbox. The goal is a clear invitation that works, not a way around anyone’s security checks.

Choose the address that fits the message

In an HTML email, you can put the link on meaningful text that points straight to the destination, without showing a long address. Use a short link when it really helps: you need an address you can change later, the message is plain text, or you want to count clicks for each placement. Adding a redirect to every link isn’t automatically better.

For a meeting invitation, give the club name, the date and what’s on before the link. Readers should know whether it opens meeting details, a document or a sign-in page. Send from your usual, recognizable name and address; a short link says nothing about who sent it.

Prepare a destination that recipients can open

Test the final page while signed out. If access is limited, test with the account of someone who should have access, and explain in the message what’s needed. Don’t make a private document public just to skip its login screen. If an address you plan to share contains a temporary sign-in code, get a proper sharing address from the host instead.

Create the link in the Links app, under your own links or the right identity. Give it a clear title for your own use, then copy the full short link. Keep a note of where the message goes and where the link leads. The title helps you manage the link; apps won’t necessarily show it in their previews.

Write both a labelled and a plain-text version

A labelled version could say: “Read the club’s meeting details for 14 November.” Link that text to the tested short link. In a plain-text version, put the explanation next to the full address, ideally on a line of its own so punctuation isn’t mistaken for part of it.

W3C’s advice on writing links recommends labels that say what the link is for. Don’t make a short link look like a link to a different website. If you send text messages, check the real length and cost with your provider; a shorter address alone doesn’t decide how a message is split or billed.

Test the delivered message, not only the draft

Send a test the way you normally send messages, to people who agreed to help, or use your provider’s preview or test feature. Check the result in a typical email app and a phone messaging app:

1. Check that the address is clickable and hasn’t swallowed a full stop or bracket next to it.
2. Open it from the message and check the final page and the next step.
3. Check the plain-text version and any line breaks.
4. Look at the preview title and image, if a preview appears.
5. Test a relevant routing rule and the normal fallback.

If a preview looks out of date, open the current destination directly. Previews are made and refreshed by the receiving app, not by Links, so they may not update straight away.

Understand security rewrites and click counts

Some organizations scan or rewrite links in email. Microsoft’s Safe Links documentation describes protection that can rewrite links and check them when someone clicks. So if the visible address has changed, look into it before assuming the message was damaged.

If a legitimate link is blocked, contact the recipient organization’s support. Don’t hide the destination behind more shorteners to get past the check. Links doesn’t count the bots, link previews and browser prefetches it recognizes, but its numbers aren’t a delivery report or an email-open count, and they don’t prove how many different people read your message. Someone who opens the link twice counts twice, and a click with no referring site doesn’t tell you which messaging app was used.

Maintain the invitation after sending

People may reread sent messages long after the meeting. Keep the same short link and, when it makes sense, point it to a page saying the event has ended; recipients won’t get a notification about the change. Update any text you can still edit separately, and keep information people still need.

Use the event lifecycle guide for what to show when an event closes, and the UTM guide to measure placements. Put campaign tags in the saved destinations, not at the end of the short link. Counted clicks use credits, and links pause when the balance runs out, so agree who pays and when you’ll check. Links keeps the address working; a clear message and a real test make it trustworthy.