URL shorteners are still useful in 2026, but not really for the reason they were created.
The original problem was simple: URLs were too long.
That problem mostly disappeared.
Social platforms increased their character limits, browsers and platforms started hiding long URLs behind rich previews, and users stopped caring about the actual length of a link in many situations.
At the same time, AI introduced a different problem.
AI agents are increasingly being told to distrust shortened URLs because they hide the final destination.
So are URL shorteners still useful?
Yes. But the argument for using one has changed.
The case against URL shorteners has got stronger
Let's start with the argument against them.
URL shorteners were originally created because URLs consumed too much space.
That made sense when a URL could take up a significant part of a tweet or SMS.
That's not really the problem anymore.
A long URL can now be shared almost everywhere without causing a practical problem. On many platforms, users don't even see the raw URL. They see a preview card with a title, description and image.
The URL itself is almost secondary.
There is also a more serious problem.
AI agents are being designed around domain allowlists and blocklists.
An agent may be allowed to visit:
example.com
but not an unknown domain.
A short URL creates a problem here because the URL the agent sees isn't necessarily the URL it will eventually visit.
For example:
zee.gl/abc123
could redirect to:
example.com
or:
another-domain.com
The short URL can pass an initial domain check while the destination doesn't.
That's not a misunderstanding of how URL shorteners work. It's exactly how redirects work.
From a security perspective, hiding the destination is a legitimate reason to treat shortened URLs with more caution.
So if all you need is to make a URL shorter, there isn't a particularly strong reason to use a shortener anymore.
But that's not the only thing a modern URL shortener can do.
What changed in favour of URL shorteners
The interesting part is attribution.
When someone visits your website from a normal webpage, you can often use the HTTP referrer to understand where the traffic came from.
If someone clicks a link on another website, the browser can tell your server which page sent the visitor.
AI traffic doesn't always work like that.
An analysis of more than 446,000 visits found that 70.6% of AI-driven traffic arrived without a referrer header.
Logged-in ChatGPT sessions can strip the referrer. Mobile applications can do the same.
The result is predictable.
Your analytics system sees a visitor, but it doesn't know where that visitor came from.
The session gets classified as Direct, in the same bucket as someone who typed your domain manually into the browser.
That's a problem if you're trying to understand which channels actually generate traffic.
GA4 helps, but doesn't solve everything
Google added a native AI Assistant channel to GA4 in May 2026.
That's useful, but it doesn't completely solve the attribution problem.
The estimates cited in the original analysis suggest that around 70% of AI-driven sessions can still show up as Direct or Referral even after the update.
So there is still a large gap between where the visitor actually came from and what your analytics system can see.
This is where URL shorteners become more interesting.
Referrer vs. UTM parameters
There is an important difference between these two things.
A referrer is information sent by the browser or application.
The application can decide not to send it.
A UTM parameter is part of the URL itself.
For example:
https://example.com/product?utm_source=ai&utm_medium=assistant&utm_campaign=product
The tracking information is inside the URL.
If the user clicks that URL, the UTM parameters travel with it.
They don't depend on the browser sending a referrer.
This is one reason why a URL shortener can still be useful.
You can start with a long URL containing all your tracking parameters and turn it into something much easier to distribute:
zee.gl/abc123
The visitor sees the short link.
The destination still contains the campaign information.
And the redirect gives you another point where you can measure the click.
This doesn't mean that URL shorteners magically solve AI attribution.
They don't.
But they give you another piece of the journey that you can control.
That's useful when the traffic source itself isn't sending reliable referral information.
The token argument is real, but minor
There is another argument you'll see when people discuss URL shorteners in the context of AI: tokens.
It's technically true.
A long URL with tracking parameters can easily consume 60–80 tokens.
A short URL might consume only a handful.
If you're putting thousands of URLs into an AI context window, that difference can become meaningful.
For normal web usage, though, I wouldn't use this as the main reason to shorten a URL.
If you're dealing with one or ten URLs, the token savings are basically irrelevant.
If you're processing thousands of URLs inside an AI workflow, it starts to matter.
So the argument is real.
It's just not the most important one.
Short URLs have a security problem
There is still a fundamental issue with shortened URLs.
You can't see the destination.
Compare:
https://example.com/pricing
with:
zee.gl/abc123
The first one tells you where you're going.
The second doesn't.
That's convenient, but it also means you have to trust whoever created the redirect.
And this is exactly why security systems can dislike URL shorteners.
I don't think the right answer is to pretend this isn't a problem.
The better answer is to make short links inspectable.
A short link that wants to be trusted should be able to show the destination before anyone commits to it.
You should be able to see things such as:
the destination domain;
whether the connection is secure;
when the link was created;
whether other visitors have flagged it.
This is one area where a modern shortener can be different from a basic redirect service.
ZA.GL's URL shortener uses a preview page that shows the destination domain, connection security, creation date and community safety signals before the redirect.
Visitors can also mark a destination as safe or unsafe, with flagged links reviewed by a person.
The point isn't that every shortener needs to work exactly the same way.
The point is that destination transparency matters more now than it did a few years ago.
If AI agents and security systems are going to treat opaque redirects with suspicion, making the destination inspectable is a much better answer than simply arguing that short links are safe.
Tracking should be part of the shortener
Another problem with basic URL shorteners is that they stop at the redirect.
You get a short URL.
Someone clicks it.
They arrive at the destination.
That's it.
If you're using a shortener for marketing, you usually need more than that.
You want to know:
how many people clicked;
where they came from;
which countries they are in;
which devices they use;
which campaign generated the traffic.
ZA.GL includes click analytics for short links, including clicks, countries and device types. It also supports UTM parameters, so campaign information can be added to the destination URL automatically.
You can also add a Google Tag Manager container if you need the click to become part of an existing tracking setup.
This is particularly useful for links pointing to pages you don't own.
For example, you might be sending traffic to:
an Amazon listing;
an app store;
a partner website;
a marketplace;
a page managed by another company.
You can't install your analytics code on those pages.
You can't add your tracking pixel.
But you can control the link people click before they get there.
That's where the redirect becomes useful.
When does a URL shortener actually make sense?
There are still several cases where I would use one.
1. Printed materials and QR codes
This is probably the easiest use case to justify.
Imagine putting a QR code on:
a flyer;
a menu;
product packaging;
a business card;
a billboard.
Once it's printed, you can't change it.
The destination behind the link can be changed.
That's why a short URL is useful here.
You can create a short link such as:
zee.gl/menu
and generate a QR code for it.
Later, you can change the destination without replacing the QR code.
ZA.GL generates a QR code together with the short link, which makes this workflow particularly straightforward.
No amount of AI changes this use case.
2. Anywhere attribution matters
Newsletters, PDFs, podcast show notes, community answers and other content can generate traffic without preserving useful referrer information.
This is becoming more important as AI assistants increasingly become part of the discovery process.
A short URL with UTM parameters gives you another way to carry campaign information with the link itself.
You don't have to depend entirely on the referrer.
3. Links you cannot put a tracking pixel on
This is a very practical use case.
You don't control Amazon.
You don't control an app store.
You don't control a partner's website.
You can't install analytics there.
A redirect you control is one of the few places where you can still measure the click.
This is also where Google Tag Manager support can be useful. ZA.GL can fire a GTM container before sending the visitor to the destination.
4. URLs people need to type or say
This one hasn't changed.
If someone needs to type a URL manually, shorter is still better.
The same applies when someone reads a URL over the phone or shares it verbally.
Compare:
example.com/products/summer-sale?utm_source=podcast&utm_campaign=august
with:
zee.gl/summer
The second one is much easier to communicate.
A short URL can also be changed after you share it
This is another feature that has nothing to do with character limits.
Imagine you publish this URL in 500 places:
zee.gl/summer
A week later, you want it to point to a different landing page.
With a basic direct URL, you have a problem.
You now have hundreds of copies of the old URL distributed across the internet.
With a managed short link, the URL can remain the same while the destination changes.
ZA.GL supports editing an existing link after it has been shared on its Pro plan. The short URL stays the same while the destination can be changed.
This is particularly useful for campaigns, QR codes and links that are distributed across multiple channels.
The URL becomes a stable identifier.
The destination becomes something you can manage.
You can also control who can open the link
Not every short link needs to be public.
There are cases where you want the URL to stop working after a certain number of clicks, expire at a specific date or only work for certain users.
For example:
a limited offer;
a private document;
a one-time invitation;
a campaign that ends on a specific date;
a link that should only work in certain countries;
a mobile-only destination.
ZA.GL supports password protection, expiration dates, click limits, country targeting and device targeting.
Again, this isn't about making URLs shorter.
It's about turning a URL into something you can actually manage.
When should you use the plain URL?
There are also plenty of situations where a short URL adds little value.
If you're linking to your own website from another webpage, the direct URL is usually the better choice.
It's transparent.
There's no additional redirect.
And if the referrer is available and you don't need separate campaign tracking, there isn't much reason to introduce another layer.
There's also a specific case where I would actively avoid the shortener.
If you're handing a URL to an autonomous AI agent that works against a domain allowlist, give it the actual destination.
If the agent needs to know that it is visiting:
example.com
then give it:
https://example.com
Don't make it resolve:
zee.gl/abc123
first.
In that situation, the redirect doesn't solve a problem.
It creates one.
So, are URL shorteners still useful?
Yes.
But they're useful for different reasons than they were 10 or 15 years ago.
The character-limit problem is mostly gone.
That's not what makes them interesting anymore.
The useful part is the layer between the click and the destination.
A modern URL shortener can give you:
click analytics;
UTM tracking;
destination management;
QR codes;
a stable URL for printed materials;
link expiration;
access controls;
destination previews;
a measurement point on third-party platforms.
AI adds another reason to think about them: attribution.
A large percentage of AI-driven traffic doesn't arrive with a useful referrer.
If you rely exclusively on referrer data, you can end up with a significant amount of traffic sitting inside Direct or Referral.
UTM parameters can help because they are part of the URL itself.
But there is another condition.
The security problem isn't going away.
A short URL hides its destination.
AI agents and security systems are increasingly aware of that and may block or distrust shortened links.
That means the future of URL shortening probably isn't about making redirects even more invisible.
It's the opposite.
Short links need to become more transparent.
The destination should be inspectable.
The click should be measurable.
The link should be manageable after it has been shared.
And the person using the link should have enough information to decide whether they trust it.
That's the direction a modern URL shortener should take.
So no, I don't think URL shorteners are dead.
I think the original use case is.
A URL shortener isn't particularly interesting anymore because it turns a 120-character URL into 20 characters.
It's interesting because it gives you control over what happens between the link being shared and the destination being reached.
And that is still useful.
Possibly more useful than it was before.