Short link 301 vs 302 redirects: which one your shortener should use

A short link is a redirect with a status code. The status code is either 301 (permanent) or 302 (temporary). Both work mechanically. The difference is in three places: browser caching behavior, search-engine treatment, and whether the campaign is editable after publish.

For most marketing short links, 302 is the right default. The reasoning below.

What each one means technically

301 (Moved Permanently).

• Browsers cache the redirect indefinitely. Once a visitor's browser learns that acme.co/q2 resolves to yoursite.com/landing, the browser may bypass the shortener and go directly to the destination on subsequent visits.
• Search engines treat it as a permanent redirect and pass link equity (PageRank, authority) from the source URL to the destination.
• The destination is treated as the canonical URL for the short link's place in the web.

302 (Found, sometimes called Moved Temporarily).

• Browsers do not cache the redirect. Every visit re-resolves the short link through the shortener.
• Search engines treat it as situational and do not pass link equity in the same way.
• The shortener can change the destination at any time and visitors will pick up the new destination on their next click.

Why 302 is the right default for marketing short links

Three reasons:

1. Campaigns shift. A marketing short link printed on a poster might be live for 6 to 24 months. The destination URL might change once or twice during that window (landing page redesign, URL slug normalization, A/B test routing). With 302, the change just works on the next visitor's click. With 301, browsers that already cached the old destination keep going there and the campaign edit is partially broken.

2. Click tracking depends on the redirect happening. A 301 redirect that browsers cache locally never re-hits the shortener. The shortener does not record subsequent clicks because the redirect happened in the browser rather than at the server. Click count understates actual visits.

3. Repointing during the campaign is normal. Pivots happen. The campaign brief calls for a new landing page mid-flight. The destination domain moved. With 302, the shortener's database is the source of truth and the next click picks up the new destination. With 301, the visitor population's cached redirects fight the change for weeks.

When 301 is the right call

Two cases where 301 is correct:

1. Permanent URL migration. You moved yoursite.com/old-page to yoursite.com/new-page and want search engines to transfer the SEO ranking. This is canonical URL migration rather than a marketing short link. Use a 301 on your own domain's redirect; the short link wrapping it stays 302.

2. Decommissioned services that should never come back. You shut down a feature, retired a sub-brand, sunset a campaign. The URL should stop working visibly: redirect to the homepage with a 301 so search engines deindex the old URL. This is a domain-level redirect; a marketing short link does not need it.

For a short link wrapping a marketing campaign URL, you almost never want 301.

What modern shorteners actually do

Most marketing-grade shorteners default to 302 for the reasons above. A few use a pattern that combines the best of both:

• The HTTP response is 302 (so browsers do not cache).
• The shortener's database is the source of truth (so destinations are editable).
• A short server-side cache reduces redirect latency for the common case (the same short link being clicked many times in a short window).

The result is the editability of 302 with the latency of 301.

Trakl uses this pattern. Bitly's marketing tier and Rebrandly use similar patterns. TinyURL Pro uses a 302. Dub uses a 302 with a short edge cache.

What about the SEO question on 302s?

A common worry: does using 302 for short links hurt the destination's search ranking?

For marketing short links, no. The destination URL is what gets indexed by search engines. The short link itself is not the indexable surface; it is a redirect. Whether the redirect is 301 or 302, the destination is what ends up in Google's index. The short link does not enter the ranking signal.

Where the SEO question matters is canonical URL migration: replacing one URL with another for a page that already ranks. In that case, 301 is correct because you want to transfer ranking signals. But that is not a marketing short link; it is a same-domain redirect on your own canonical URL structure.

If you are unsure whether you are doing one or the other, ask: does the URL on the left-hand side of the redirect already rank in search results? If yes, you are migrating a canonical URL and should use 301. If no, you are wrapping a campaign URL and should use 302.

What about HSTS and HTTPS?

Two related concerns that are not the redirect type itself but show up in the same conversation:

HSTS (HTTP Strict Transport Security) is a header that tells browsers to always use HTTPS for a domain. This is independent of the redirect status code; both 301 and 302 should serve HSTS on the response.

HTTPS itself is non-negotiable for short links in 2026. Modern browsers flag HTTP redirects as insecure, and email apps refuse to unfurl HTTP links. Your shortener should serve HTTPS for the short domain (yourbrand.co) regardless of redirect type.

Common mistakes

• Using 301 because "permanent sounds better." It does not. Permanent in the HTTP spec means "browsers should cache forever," which works against editable campaigns.
• Using 302 for a canonical URL migration. When you do want SEO equity to transfer, 301 is the right call. 302 is for situational redirects.
• Mixing both inside the same campaign. Some shorteners let admins override the default per link. Pick one and stay consistent across the team's links.
• Worrying about the redirect type on the short link when the actual SEO problem is on the destination URL's canonical handling.

What to verify on your shortener

If you are not sure what your shortener does:

1. Open a terminal. Run curl -I -L https://your-shortener.com/<a-known-slug>.
2. The response shows the redirect chain. Look for "HTTP/2 301" or "HTTP/2 302" on the first response.
3. Confirm the response includes the destination in the Location: header.
4. Confirm subsequent requests still hit the shortener (open the short link in a fresh incognito window and watch your shortener's analytics).

For Trakl: the response is 302 with editable destinations. The dashboard's click count reflects every visit because the browser does not cache the redirect locally.

For the broader case on short link mechanics, the short links pillar guide covers the redirect step and what happens around it. For the case for branded domains regardless of redirect type, branded short links is the next read.