writing/12 Sep 2026/8 min read

Link rot: what happens when a shortener shuts down

Shortening a URL replaces a name you control with a name someone else controls. That is the whole trade, and it is usually worth it. But it makes a short link a dependency, and dependencies deserve the same scrutiny as any other.

What actually breaks

When a shortener disappears, the destination pages are all still there. What is lost is the mapping, and the mapping lives in places you cannot edit.

Anything printed
Business cards, packaging, posters, conference badges, vehicle livery. Unfixable by definition.
Sent email
Every newsletter in every archive. You can fix the template; you cannot fix what already arrived.
Other people's writing
Citations, forum answers, documentation that references your link. This is the part that quietly matters most over a decade.
Old social posts
Mostly uneditable, and the platform will keep serving them for years after the link stops working.

There is a second-order risk that is less obvious and worse. When a shortener's domain lapses, someone else can register it, and every link ever created on it now points wherever the new owner chooses. Your old post now recommends something you have never heard of. This has happened, repeatedly, and it is the strongest argument against the cheapest possible provider.

This is not hypothetical

The shortener graveyard is large. Services run by major platforms have been retired with a year's notice; independent ones have closed with a month, or none. Some kept redirects alive indefinitely as a courtesy, and that courtesy has no expiry date attached to it, which is its own kind of uncertainty.

The pattern worth noticing is that free services die most often. A redirect table costs almost nothing to run but is not free, and a product with no revenue attached to it is the first line item cut when priorities change. Paying a small amount is not a guarantee of survival, but it does mean the service has a reason to exist.

Four habits that make it survivable

Export on a schedule
A CSV of slugs and destinations, in version control, updated monthly. With that file, rebuilding the mapping somewhere else is an afternoon rather than an archaeology project.
Use your own domain where it is permanent
For anything printed or cited for a decade, a path on a domain you own is the only real answer. Reserve third-party shorteners for the ephemeral.
Prefer readable slugs
If the service vanishes, c1k.me/pricing still tells a reader what it meant. c1k.me/x7Fq2 tells them nothing.
Check what the provider promises
Not whether they promise to last, which nobody can, but what happens on shutdown: notice period, export availability, and whether the answer is written down anywhere.

What c1k.me commits to, and what it cannot

Nobody running a small service can honestly promise to be here in ten years, and a page claiming otherwise should make you suspicious. What can be written down are the mechanics, and those are in the terms rather than in a blog post.

At least 90 days notice before discontinuation, by email and on the site, with export available throughout.
The unused part of any paid year refunded if the service ends.
Export in CSV and JSON at any time, self-service, without asking and without a retention clause on the way out.
Links keep resolving for 30 days past a lapsed subscription, so a failed card does not break anything overnight.

The deliberate design choice underneath these is that leaving stays cheap. A service that makes export easy has to keep earning the renewal, which is a healthier arrangement than one that relies on the cost of migrating.

Use shorteners deliberately

None of this argues against short links. It argues for knowing which category each one is in. A link in a chat message that will be irrelevant next week carries no risk worth thinking about. A link etched into product packaging is infrastructure and should be treated as such.

Most teams never make that distinction and use one mechanism for both. Making it takes about five minutes and removes the only genuinely painful failure mode.