Short links on X, where shortening saves you nothing

On every other platform the shortener pitch starts with character count. On X it cannot, and pretending otherwise is the fastest way to lose a reader who already knows better.

X wraps every URL you post through t.co and counts it as 23 characters regardless of its real length, as of September 2026. Post a 200-character tracking URL and it costs you 23. Post gc.mw/hi and it costs you 23. The saving is exactly zero.

So here is the honest case for shortening anyway, in the order the reasons actually matter.

One: the link is read by humans before it is clicked

X displays the destination host in the post and in the link preview card. It does not display your UTM parameters, but people who copy your link into a message, a doc or a slide carry the whole thing with them.

gc.mw/thread survives that copy intact and legible. A URL with utm_source, utm_medium, utm_campaign, utm_content and a session id hanging off it turns into a wall of text in someone's Slack, and a fraction of the people who see it there decide it is an ad and do not click.

Two: you can change where it goes

A post from eighteen months ago that still gets traffic is pointing at a URL that was correct eighteen months ago. You cannot edit a post's link on X without deleting the post and losing every reply, quote and like attached to it.

A short link makes that edit possible from your side. The post stays; the destination moves. For anyone running an account where old threads keep circulating, which is most technical accounts, this is worth more than every other benefit combined.

Three: attribution that survives the wrapper

Because X routes through t.co, the referrer your analytics receives is frequently t.co and sometimes nothing at all. t.co also appears when the link was shared to Slack, Discord or WhatsApp from X, so the referrer alone cannot separate the original post from its downstream life.

UTM parameters stored on the short link solve it. They are appended during the redirect, so they arrive whatever the wrapper does, and a distinct code per post separates the launch tweet from the follow-up thread from the quote-post three weeks later.

A worked example

An account with 40,000 followers ran a product launch across a thread, a pinned post and a reply in someone else's thread.

Three codes, one destination. gc.mw/x1 in the thread, gc.mw/pin pinned, gc.mw/re3 in the reply. All three carried utm_source=x with different utm_content values stored on the link, so the posts themselves stayed clean.

The pinned post out-earned the launch thread by roughly two to one over the following month, which was not what anyone expected, the thread got twenty times the impressions. The reply, posted into someone else's audience, produced the highest conversion rate of the three by a wide margin.

Then the pricing page moved. One edit, and the pinned post, which was still collecting clicks daily, kept working.

The reputation caveat, said plainly

t.co checks destinations against safety lists. A shortener domain with a poor history can get an interstitial warning or a hard block, and that block applies to every link on the domain including yours.

This is the strongest argument for a custom domain on X specifically. go.yourbrand.com/x1 carries your reputation, not a shared one, and it cannot be taken down by somebody else's phishing campaign.

Check the chain before you post

Paste the link you are about to publish. You want to see your hop, then the destination, then a 200, and nothing dropping to plain http along the way.

The branded links page covers aliases and editing destinations, and custom domain links covers the two DNS records that put your own name in front of the slash.