# What is a URL shortener? How short links work

> What is a URL shortener? Learn how short links redirect (301 vs 302), why people use them, the risks, the privacy questions and how to choose a shortener you trust.

Source: https://blinkhop.com/guides/what-is-a-url-shortener

What is a URL shortener? It is a service that turns a long web address into a short one, such as `https://zou.sh/summit`, and sends everyone who opens it to the original page with an HTTP redirect, so the link is easier to share, type, print and measure. This guide explains how the redirect works, why 301 and 302 behave differently, what can go wrong and how to choose a shortener that respects your visitors.

## What is a URL shortener, exactly?

A URL shortener keeps a simple lookup table: a short code on one side, a destination URL on the other. When you shorten a link, the service adds a row. When someone opens the short link, the service looks up the code and forwards the visitor to the destination.

Take a typical campaign link:

```text
https://example.com/events/2026/autumn-summit/agenda?utm_source=newsletter&utm_medium=email&utm_campaign=autumn_summit
```

After shortening, it becomes:

```text
https://zou.sh/summit
```

Both addresses lead to the same page. The short one fits in a text message, reads well on a slide and can be typed from a poster. The tracking parameters are not lost: they are part of the destination, so they arrive with every visit.

A short link has two parts. The first is the short domain, which is zou.sh for Blinkhop. The second is the code, either generated (like `7Kp2x`) or chosen by you (like `summit`). Some services also let organizations put short links on their own domain. At Blinkhop, branded domains come with accounts, which are in early access.

## How a short link redirect works

Here is what happens in the fraction of a second after someone clicks `https://zou.sh/summit`:

1. The browser sends a request to the zou.sh server for the path `/summit`.
2. The server looks up the code `summit` in its database.
3. It answers with a redirect: a status code such as 302, plus a `Location` header that contains the destination URL.
4. The browser reads that header and requests the destination page.
5. The destination page loads. Most visitors never notice the extra step.

You can watch it happen. The `-I` option asks curl for the response headers only, so it shows the redirect without following it:

```bash
curl -sI https://zou.sh/summit
```

```http
HTTP/2 302
location: https://example.com/events/2026/autumn-summit/agenda?utm_source=newsletter&utm_medium=email&utm_campaign=autumn_summit
```

The output above is trimmed to the two lines that matter: the status code and the destination.

## 301 vs 302: why the redirect type matters

HTTP has several redirect status codes. Link shorteners mostly use two of them, and the difference affects caching, click counts and what happens when a destination changes.

| Redirect | 301 Moved Permanently | 302 Found (temporary) |
|---|---|---|
| What it tells the browser | The address has moved for good | The address points somewhere else for now |
| Browser caching | Browsers may cache it and skip the shortener next time | Not cached by default, so each click goes through the shortener |
| Click counting | Repeat visits from a cached browser are invisible | Every click can be counted |
| Changing the destination later | Visitors with a cached redirect may keep going to the old page | Takes effect on the next click |
| Google Search | Treated as a signal that the target should be canonical | Not treated as a canonical signal |

The last row comes from [Google's documentation on redirects](https://developers.google.com/search/docs/crawling-indexing/301-redirects): Googlebot follows both kinds, uses permanent redirects (301 and 308) as a signal that the target should be the canonical URL, and does not use temporary ones (302, 303 and 307) that way. For short links shared in messages, posts and print, this rarely matters, because the short address is not a page you want in search results.

Blinkhop uses a 302 for every zou.sh link. Each click reaches the server, so counts stay accurate, and destination edits, which come with accounts (early access), apply from the very next click.

You may also meet 307 and 308. They behave like 302 and 301, but they require the browser to repeat the same request method, which matters for forms and APIs more than for short links.

## Why people use URL shorteners

- **Space.** Text messages, social bios, video descriptions and slides have little room. A 20-character link fits anywhere.
- **Readability.** `zou.sh/summit` can be read aloud on a podcast or typed from a poster. A long URL full of parameters cannot.
- **QR codes.** A shorter URL produces a simpler QR code with larger squares, which is easier to scan. See [how to make a QR code for a link](https://blinkhop.com/guides/qr-code-for-a-link).
- **Tracking without clutter.** Campaign tags such as UTM parameters stay in the destination while the visible link stays clean.
- **Click counts.** A shortener can count clicks per day, country, referring site and device type. Blinkhop counts them without cookies and leaves out bots, scripts and link previews from apps like Slack and WhatsApp.
- **Automation.** APIs and AI assistants can create links in bulk, for example every link in a newsletter.
- **Control over time.** Some services let you change a destination, set an expiry date or cap the number of clicks. At Blinkhop, these come with accounts (early access).

## Risks and downsides

Short links are useful, but they come with trade-offs worth knowing before you rely on them.

### Hidden destinations

A short link hides where it goes, which is why phishing messages often use them. Good shorteners screen destinations and offer a preview. Blinkhop checks every destination at creation against a blocklist of about 390,000 phishing and malware domains, refreshed every night from two open sources, and anyone can add + to a zou.sh link to see where it leads before visiting. Our guide on [checking where a short link goes](https://blinkhop.com/guides/check-if-a-link-is-safe) covers previews for other services too.

### Link rot

A short link works only as long as the service keeps it. Some services delete inactive links, and some shut down. Google's goo.gl is the best-known case: public link creation ended in 2019, and after August 25, 2025, Google stopped serving goo.gl links that showed no activity in late 2024. The [goo.gl shutdown guide](https://blinkhop.com/guides/googl-shutdown) has the verified timeline.

### Tracking you did not agree to

Every click passes through the shortener's server, which can see the visitor's IP address, browser and the page they came from. What the service does with that data is up to its policies. Read them before you send your audience through it.

### Extra steps before the destination

The redirect itself adds one request. Some services also show an ad or a waiting page before sending visitors on. Blinkhop shows no ads, and redirects go straight to the destination.

### A single point of failure

If the shortener is down, every link on it fails at the same time. Look for a public status page. Blinkhop publishes live checks of redirects, the API and the MCP server on its [status page](https://blinkhop.com/status).

## How to choose a URL shortener

Use these questions to compare services:

| Question | Why it matters |
|---|---|
| Do links expire, or get deleted when inactive? | Printed and archived links need to keep working for years |
| Does it redirect directly, without ads or waiting pages? | Extra pages slow visitors down and can look suspicious |
| Can people preview a link before visiting? | Previews build trust and make phishing harder |
| How does it handle abuse? | Spam on a shared short domain can make filters distrust every link on it |
| What does it store about visitors? | Your visitors' privacy reflects on you |
| Does it offer custom endings or your own domain? | Readable links tell people what to expect |
| Is there an API, bulk shortening or an AI integration? | Automation saves time at scale |
| What are the limits and the price? | Limits decide whether it fits your volume |

Our [comparison pages](https://blinkhop.com/compare) look at how Blinkhop and other popular shorteners differ.

## URL shorteners and privacy

When someone clicks a short link, the shortener's server receives an ordinary web request. Technically, it can see:

- The visitor's IP address, which reveals an approximate location
- The browser and device, from the user agent
- The referring page, if the browser sends one
- The time of the click

What happens next depends on the service. At Blinkhop, redirects set no cookies and visitor IP addresses are never stored. We keep aggregated counts only: clicks per day, country, referrer domain and device type. Rate limiting keeps IP addresses in memory for at most 24 hours, never on disk. When you create a link, we store the destination, the code, the creation time and how it was created (web, API or MCP), and no IP address. The service also works over Tor and VPNs, without captchas.

One privacy point applies to every public shortener: anyone who has a short link can find out where it goes. Do not shorten private URLs that contain secret tokens, access keys or personal data.

## Key takeaways

- A URL shortener maps a short code to a long URL and forwards visitors with an HTTP redirect.
- A 301 is permanent and can be cached by browsers. A 302 is temporary, so every click reaches the shortener. Blinkhop uses 302.
- People use short links for space, readability, QR codes, clean tracking and click counts.
- The main risks are hidden destinations, link rot, tracking and downtime.
- Choose a service by its link lifetime, redirect behavior, safety tools, privacy practices and automation options.

## FAQ

### Are URL shorteners safe to use?

The shortener itself is harmless, but a short link hides its destination, so scammers sometimes use them. Check the destination before you click, for example by adding + to the end of a zou.sh link.

### Why does Blinkhop use 302 redirects instead of 301?

Browsers do not cache a 302 by default, so every click reaches the shortener. That keeps click counts accurate, and when an account owner edits a destination (an early access feature), the change applies from the next click.

### Do URL shorteners track visitors?

A shortener can see technical details of each click, such as the IP address, the browser and the referring site, and what it keeps depends on the service. Blinkhop sets no cookies on redirects, never stores visitor IP addresses and keeps only aggregated daily counts.

### Do short links expire?

It depends on the service. Google stopped serving goo.gl links that showed no activity in late 2024 after August 25, 2025, while Blinkhop links on zou.sh never expire unless an owner sets an expiry date.